Salesforce Mobile - Implementation Guide

Version 30.0: Spring ’14

Salesforce Classic Implementation Guide

Note: Any unreleased services or features referenced in this or other press releases or public statements are not currently available and maynot be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are

currently available.

Last updated: April 25, 2014

© Copyright 2000–2014 salesforce.com, inc. All rights reserved. Salesforce.com is a registered trademark of salesforce.com, inc., as are othernames and marks. Other marks appearing herein may be trademarks of their respective owners.

Table of Contents

Chapter 1: What is Salesforce Classic?...................................................................................................1The Mobile Environment.........................................................................................................................................................2Requirements for Using Salesforce Classic................................................................................................................................2Wireless Connection Modes.....................................................................................................................................................3The Mobile Client Application: Capabilities and Limitations..................................................................................................4Device Synchronization.............................................................................................................................................................4Localization...............................................................................................................................................................................5

Chapter 2: Planning a Mobile Deployment............................................................................................7Mobile Business Process Review...............................................................................................................................................9Salesforce Classic Resources....................................................................................................................................................10

Chapter 3: Salesforce Classic Administration.......................................................................................11Salesforce Classic Implementation Tips and Best Practices....................................................................................................12Enabling Salesforce Classic Users...........................................................................................................................................14About the Salesforce Classic Default Configuration...............................................................................................................14

Creating Salesforce Classic Configurations.................................................................................................................15Testing Salesforce Classic Configurations...................................................................................................................17

Defining Data Sets..................................................................................................................................................................19Editing Object Properties for Salesforce Classic.....................................................................................................................24Creating List Views for Salesforce Classic..............................................................................................................................28Setting Up Mobile Dashboards...............................................................................................................................................29Enabling Reports in Salesforce Classic....................................................................................................................................30Salesforce Classic Usage Data in Custom Report Types ........................................................................................................31Setting Up Salesforce CRM Content for Salesforce Classic...................................................................................................32Creating Links to Web and Visualforce Mobile Pages for Salesforce Classic.........................................................................33Notifying Users about Salesforce Classic Availability..............................................................................................................34Managing Salesforce Classic Configurations..........................................................................................................................35Managing Salesforce Classic Tabs...........................................................................................................................................36Managing Salesforce Classic Devices......................................................................................................................................36

Permanently Linking Salesforce Classic Users to a Mobile Device.............................................................................39

Chapter 4: Installing the Mobile Client Application............................................................................43Installing Salesforce Classic and Mobile Lite..........................................................................................................................44BlackBerry Enterprise Server Application Push......................................................................................................................46BlackBerry Self-hosted JAD Package......................................................................................................................................46Mobile Device Simulators.......................................................................................................................................................46

BlackBerry Simulator...................................................................................................................................................47iPhone Simulator.........................................................................................................................................................47

Index.................................................................................................................................................49

i

Table of Contents

Chapter 1

What is Salesforce Classic?

Salesforce Classic helps your teams succeed by allowing users to access theirlatest Salesforce data, whenever and wherever they need it, directly from

In this chapter ...

• The Mobile Environment Android™, BlackBerry® and iPhone® devices. The Salesforce Classic app• Requirements for Using Salesforce

Classicexchanges data with Salesforce over mobile or wireless networks, and stores alocal copy of the user’s data in its own database on the mobile device. Users can

• Wireless Connection Modes edit local copies of their Salesforce records when a data connection isn’t available,• The Mobile Client Application:

Capabilities and Limitationsand transmit those changes to Salesforce when a connection is available again.The app also promotes near real-time logging of critical information by

• Device Synchronization prompting users to enter updates directly in Salesforce or Force.comAppExchange apps after important customer calls, emails, or appointments.• Localization

A Salesforce Classic license is required for each user to use the full version ofSalesforce Classic. For organizations using Unlimited, Performance, andDeveloper Editions, salesforce.com provides one mobile license for eachSalesforce license. Organizations using Professional or Enterprise Editionsmust purchase mobile licenses separately.

Any Salesforce user who doesn't have a mobile license can download a free,restricted version of Salesforce Classic. The free version:

• Supports fewer standard objects

• Doesn't support custom objects

• Doesn't allow administrators to customize or create mobile configurations

• Isn’t available for use by partner portal users

Users are automatically assigned to the default mobile configuration when theyactivate Salesforce Classic from their mobile devices. Mobile configurationsdetermine the data that is sent to each mobile user. Administrators can’t viewor edit the default mobile configuration.

1

The Mobile EnvironmentThe Salesforce Classic server brokers the exchange of data between Salesforce and wireless devices running the mobile clientapplication. The server pulls selected data from your Salesforce organization and delivers it over wireless carrier networks tousers’ devices.

The Salesforce Classic client runs on the device and stores a local copy of the user’s data in its own database. This allows usersto work with their Salesforce records whether or not a wireless connection is available. Any changes or updates made on thedevice are immediately submitted to Salesforce by the mobile server. If a connection is not available, the updates are saved onthe device and sent when the connection is restored.

The Mobile Administration Console within the Salesforce setup pages lets you manage the full life-cycle of your mobiledeployment, including configuration, customization, and installation. This solution lets you maintain devices and make changesto mobile configurations completely over-the-air.

Figure 1: Salesforce Classic System Architecture

Requirements for Using Salesforce ClassicThe Salesforce Classic app can run on Android, BlackBerry, and iOS operating systems, and it's supported by virtually allwireless carriers—if the device can establish a data connection to the Internet, it can typically run the mobile app. Verify thatyour device is supported before installing the mobile app. Recently-released mobile devices may not be immediately supportedbecause every device goes through the official certification and quality assurance process.

Notes About BlackBerry Smartphones• Even if your device meets the minimum operating system requirement, you can improve its performance by upgrading to

the latest supported version of the operating system offered by your mobile carrier.• Mobile users running versions 4.0 - 4.3 of the BlackBerry operating system can still download and install the Salesforce

Classic app; however, the mobile server will detect the older operating system and send version 11.6 of Salesforce Classic,which was the last release that supported BlackBerry operating system versions 4.0 - 4.3. Users on version 11.6 of SalesforceClassic can't use any of the new features included in the current release or future releases.

• Starting in Winter '09, Salesforce Classic no longer officially supports the BlackBerry 8700 series, although the mobileapp may continue to run on those device models.

2

The Mobile EnvironmentWhat is Salesforce Classic?

http://www.salesforce.com/mobile/apps/download/devicesupport.jsp

http://www.salesforce.com/mobile/apps/download/devicesupport.jsp

• BlackBerry touchscreen devices use the same Salesforce Classic app as other BlackBerry devices, so some aspects of SalesforceClassic aren’t optimized for the touchscreen interface.

Notes About iOS DevicesUse of the Salesforce Classic app for Apple products is subject to certain limitations:

• Third parties (including, but not limited to, Apple Inc. and your network connectivity provider) may at any time restrict,interrupt or prevent use of Salesforce Classic for the iPhone and iPod touch devices, or delete the Salesforce Classic appfrom iPhone or iPod touch devices, or require salesforce.com to do any of the foregoing, without entitling the customerto any refund, credit or other compensation from such third party or salesforce.com.

• Service level agreements don’t apply to the Salesforce Classic for iPhone product. Additional limitations are described inthe Order Form Supplement for Salesforce Classic for iPhone, which users are required to accept upon download orinstallation of the Salesforce Classic for iPhone product.

Wireless Connection ModesEach operating system communicates with Salesforce Classic in a different way. Below is a description of the connectionmodes per platform.

BlackBerryBlackBerry smartphones communicate with the Salesforce Classic server through one of two BlackBerry data channels:BlackBerry Internet Service or Mobile Data Service.

BlackBerry Internet Service (via the carrier)BlackBerry Internet Service is a public service offered by Research In Motion (RIM) that provides general Internetconnectivity from BlackBerry smartphones. BlackBerry Internet Service offers the same high level of reliability andperformance as a BlackBerry Enterprise Server, while alleviating some of the technical constraints that can be encounteredin a BlackBerry Enterprise Server environment. BlackBerry Internet Service is available to all BlackBerry smartphones,assuming the carrier offers the service and has installed the BlackBerry Internet Service books.

BlackBerry Internet Service is the preferred data channel for Salesforce Classic. When a mobile user attempts to connectfrom a BlackBerry smartphone, the mobile application first checks for a BlackBerry Internet Service connection. IfBlackBerry Internet Service is unavailable or has been disallowed, the application then checks for a BlackBerry EnterpriseServer MDS connection.

Mobile Data Service (via the BlackBerry Enterprise Server)The BlackBerry Enterprise Server is available from RIM. Its main functions include email integration, address booksynchronization, device security management, and enabling the Mobile Data Service.

When Salesforce Classic communicates through the Mobile Data Service, all device traffic is routed through theBlackBerry Enterprise Server and its associated corporate network. This can create problems if the corporate networkcannot exchange data with the Salesforce Classic server due to firewall or proxy server restrictions.

Additionally, BlackBerry Enterprise Server administrators can severely restrict the ability of BlackBerry users to installor communicate with third-party applications. Before attempting to deploy Salesforce Classic, BlackBerry EnterpriseServer administrators should carefully review the BlackBerry Enterprise Server Requirements on page 8.

iPhoneiPhones communicate with the Salesforce Classic server through TCP/IP. Because TCP/IP is a direct Internet connection,iPhone users are not subject to the same potential security restrictions as BlackBerry users. Even when iPhones are integratedwith a corporate server, the server cannot impose IT policies on the operating systems. Salesforce administrators managingiPhone users generally do not need to review their corporate network infrastructure before deploying Salesforce Classic.

3

Wireless Connection ModesWhat is Salesforce Classic?

The Mobile Client Application: Capabilities and LimitationsUsers download the Salesforce Classic client application to their supported mobile device, and they use the client interface towork with their locally stored Salesforce data. While the local data is updated wirelessly, it is important to note that SalesforceClassic does not maintain an open Internet connection, cannot execute Javascript, and communicates with Salesforceasynchronously through the SOAP API. For these reasons, not all of the features in Salesforce are supported in the mobileclient application.

The following list outlines the capabilities and limitations of the mobile application:

• Available Objects: With Salesforce Classic, you can mobilize accounts, assets, contacts, content, opportunities, leads,tasks, events, price books, products, cases, solutions, notes, and custom objects. You cannot mobilize s-controls, mashups,merge fields, image fields, or custom links. The following do not execute in the mobile client application but will runserver-side after a record is saved and submitted to Salesforce: workflow rules, validation rules, formula fields, and Apextriggers.

• Permissions, Record Types, and Page Layouts: User permissions, record types, and page layouts are inherited fromSalesforce.

• Default Field Values: Salesforce Classic supports default field values only for picklists and multiselect picklists. Defaultfield values for other types of fields, such as checkboxes and numeric fields, do not appear in Salesforce Classic.

• Related Lists: If you mobilize a related object—in other words, add a child data set to a parent data set—the objectautomatically becomes a related list on the mobile device.

• Dashboards and Reports: Dashboards are available in the BlackBerry and iPhone client applications. Reports are availablein the BlackBerry client applications. Reports are sent to the device in Excel format and display in a basic table. The reportviewer in the mobile application does not support sorting, summaries, subtotals, or grouping.

• Custom List Views: BlackBerry users can create custom views in the mobile client application. BlackBerry and users canaccess custom views created by Salesforce administrators in the Mobile Administration Console.

• Phone Integration: All mobile users can log phone calls initiated from Salesforce Classic. BlackBerry users can captureinbound calls from the BlackBerry Call Log.

• Email Integration: BlackBerry users can log emails sent from Salesforce Classic, emails sent from the device's nativeaddress book and contact manager, and incoming emails.

• Address Book Integration: BlackBerry users can export Salesforce contacts and accounts to the native address bookapplication on the device. They can also import entries in the native address book to Salesforce.

• Calendar Integration: BlackBerry users can import Salesforce events to the BlackBerry calendar and export BlackBerryevents to Salesforce.

• Visualforce Tabs and Web Tabs: iPhone and BlackBerry users can access Visualforce tabs and web tabs in the mobileclient application if the tabs have been mobilized by a Salesforce administrator.

The total device memory required by the mobile client application is equal to the base application footprint plus the amountof user data sent during the initial installation. The base application footprint is approximately 500 KB. The initial data pushis defined by the user's mobile configuration and can vary greatly depending on the user’s mobile requirements. User datavolumes range from as little as 50 KB to 100 KB to as much as several megabytes. Typically, the total applicationfootprint—application plus data—falls in the 600 KB to 5 MB range. Deploying to users with mobile configurations thatgenerate greater amounts of data require additional free memory.

Device SynchronizationThe space limitations and usability restrictions of wireless devices make it necessary to send a subset of a user's Salesforce datato the device. The data selected is determined by the mobile configuration assigned to each user in the Mobile AdministrationConsole. Mobile configurations are sets of filter parameters that determine the data Salesforce transmits to users' mobile

4

The Mobile Client Application: Capabilities and LimitationsWhat is Salesforce Classic?

devices, and which users receive that data on their mobile devices. You can edit the configurations at any time to change thedata your users receive.

Once every 24 hours, Salesforce Classic requests a full update of a user's data set. The filters contained in the mobile configurationare executed to rebuild the data set, and the resulting data records are sent to the device. The mobile client application checksfor data changes every 20 minutes. During this incremental update, the server retrieves any newly-created records from Salesforceowned by the user, and then sends that data to the device. Modifications to any records already stored on the device are alsosent. This periodic update may retrieve some records which do not match the filter criteria of the user's mobile configuration.In this case, these records only exist on the user's device until the next full update.

Note: Note the following about data synchronization:

• The BlackBerry client application adjusts its data polling time based on application usage. If the application isnot in use, the polling time interval increases in an exponential fashion, until it reaches eight hours. From thatpoint forward, the device polls for data every eight hours. This prevents the mobile application from draining thedevice battery when the application is rarely used.

• Because only one application can run on the iPhone at a time, Salesforce Classic cannot request a data updateunless the application is open. When you launch the application on the iPhone, it performs an incremental updateif a data synchronization has not occurred in the past 20 minutes.

Users can search for and download records that do not match the filter criteria of their mobile configuration. Those are calledmarked records; they are flagged on the mobile server and delivered to the user's device on every full data update. When a userdownloads a record that does not match his or her mobile configuration, the mobile server also sends any records referencedby the record the user retrieved.

Listed below are common actions and the resulting synchronization behavior:

SynchronizationAction

The mobile application immediately sends the record toSalesforce. The user cannot edit the new record until the

The user creates a new record in Salesforce Classic.

mobile application receives confirmation from Salesforce thatthe record was properly saved.

The record will be removed from the device at the next fulldata update, which occurs every 24 hours.

The user edits a record in Salesforce Classic, and the recordno longer meets the criteria of the user's mobile configuration.

Users assigned to the mobile configuration will receive a newdata set at the next incremental update, which occurs every20 minutes.

The administrator edits the data sets of a mobile configuration.

Users assigned to the mobile configuration will see the newpage layout on their devices at the next full data update, whichoccurs every 24 hours.

The administrator changes the mobile page layout assignedto a mobile configuration.

LocalizationThe Android, BlackBerry, and iPhone apps are available in English, Japanese, French, German, and Spanish.

Other languages have limited localization support. Hard-coded text in the mobile application, like menu options and systemmessages, cannot be localized; however, the following items are translated:

• Data entered by users

5

LocalizationWhat is Salesforce Classic?

• Metadata set up by administrators, including field labels and related list names

• Translated terms set up in the Translation Workbench

6

LocalizationWhat is Salesforce Classic?

Chapter 2

Planning a Mobile Deployment

The process of enabling Salesforce Classic on a user’s device is more than justproviding access to a website. The wireless world introduces a new set of

In this chapter ...

• Reviewing the Device Inventory technical factors for Salesforce administrators, so your mobile deploymentrequires careful consideration and planning.• BlackBerry Enterprise Server

RequirementsThere are two key components of the planning process:• Mobile Business Process Review

• Salesforce Classic Resources • reviewing the environmental factors that may have an impact on mobiledeployment

• ensuring that the mobile configurations truly reflect your users’ requirementsfor mobile access

The important parts of the planning process—understanding a company’snetwork infrastructure and the unique ways its users leverageSalesforce—typically cannot be accomplished without significant involvementfrom members of your organization. Input may be required from IT personnel,BlackBerry Enterprise Server administrators, and users across a variety ofSalesforce roles, such as business analysts, administrators, and end users.

7

Reviewing the Device InventoryIf your organization has existing mobile devices, review the inventory and verify that they are listed as supported devices.

To find out if the devices meet the model and memory requirements for Salesforce Classic:

• On a BlackBerry smartphone, click Options > About to determine the model and operating system version. The first lineof information lists the model. The version number of the operating system is typically a few lines below the model number.To find the amount of total memory and available memory, click Options > Status. The information is located in theFile Free and File Total fields.

• On an iPhone or iPod touch, tap Settings > General > About to view the amount of free space on the device and theoperating system version.

When possible, use the latest devices. Because they have more memory and faster processors, they provide a better mobileexperience. Also, make sure users are familiar with the devices.

BlackBerry Enterprise Server RequirementsIf your organization uses a BlackBerry Enterprise Server to control device traffic, verify that the server meets the followingrequirements. Failing to configure your BlackBerry Enterprise Server for Salesforce Classic will cause problems when usersattempt to install the mobile client application and download data from Salesforce. For more information about adjusting yourBlackBerry Enterprise Server settings, visit the Research in Motion website.

BlackBerry Enterprise Server IT Policy SettingsSalesforce Classic requires that certain BlackBerry Enterprise Server IT policy settings be set properly for the application toload and function correctly. The following settings apply to the IT policies in the BlackBerry Enterprise Server security policygroup:

ValueSecurity Policy Group Setting

Set to False so the Salesforce Classic client application can beinstalled on the BlackBerry smartphone.

Disallow Third Party Application Downloads

Set to True.Allow Third Party Apps to Use Persistent Store

Set to True to allow outbound communication to theSalesforce Classic server.

Allow External Connections

MDS EnabledIf you disabled BlackBerry Internet Service from your BlackBerry Enterprise Server, or if your wireless carrier does not offerBlackBerry Internet Service, Mobile Data Service must be running on the BlackBerry Enterprise Server and enabled for everySalesforce Classic user.

Outbound Communication RestrictionsThe BlackBerry Enterprise Server must allow free and open communication to the mobile server so the mobile client applicationcan exchange data with Salesforce. Any block on Internet traffic—such as firewalls, proxies, content management systems,user authentication, and Internet session timeouts—must be configured so that outbound communication to the mobile serveris allowed. Below are the correct settings for outbound communication:

PortsIP Address BlockDNS NameTransport

80, 443204.14.233.0/24http://tp.mobile.salesforce.comProduction

8

Reviewing the Device InventoryPlanning a Mobile Deployment

http://www.researchinmotion.com

PortsIP Address BlockDNS NameTransport

80, 443204.14.233.21http://test-tp.mobile.salesforce.comSandbox

Note: We recommend white-listing the DNS name instead of the IP address. If the IP address changes in the future,your users may experience problems with Salesforce Classic.

For more information about using your sandbox organization with Salesforce Classic, see Activating a Sandbox Account inSalesforce Classic on page 45.

Mobile Business Process ReviewWhen your organization implemented Salesforce, you likely evaluated your business processes and set up the application toincrease productivity and meet your business objectives. Implementing Salesforce Classic also requires analysis and planning.Not all of your users need mobile access to Salesforce, and your mobile users likely have different requirements for visibilityinto their Salesforce data. During the mobile business process review, you will identify which users will be enabled for SalesforceClassic, what they need to accomplish in the field, and what initial data they will receive on their mobile devices. You will usethis information to create your mobile configurations.

Mobile configurations are sets of parameters that determine the data Salesforce transmits to users' mobile devices, and whichusers receive that data on their mobile devices. Organizations can create multiple mobile configurations to suit the needs ofdifferent types of mobile users. For example, one mobile configuration might send leads and opportunities to the sales division,while another mobile configuration might send cases to customer support representatives. For more information, see ManagingSalesforce Classic Configurations on page 35.

Evaluating and Defining Groups of Mobile UsersEvaluate the functional groups in your Salesforce organization and decide which users have a clear need to access their Salesforcedata in the field. Target these groups during the initial phase of your mobile deployment, then roll out the mobile solution toother groups who might benefit from the ability to use Salesforce from a wireless device.

Different functional groups—such as account executives, sales managers, service managers, and administrators—typically havedifferent mobile requirements, so you will likely create a mobile configuration for each functional group in your organization.You can assign individual users and profiles to each mobile configuration. If you assign a profile to a mobile configuration,the mobile configuration applies to all Salesforce Classic users with that profile unless a specific user is assigned to anothermobile configuration.

Analyzing Users' Mobile ObjectivesUnderstanding what your users want to accomplish in Salesforce Classic will help you decide which objects needs to bemobilized. To begin defining your mobile configurations, examine use cases for different functional groups. Users might wantto:

• Log calls and emails• Look up and edit records• Review activity history• Create opportunities and add products• Assign tasks and events• Use custom objects

Identifying User Requirements for MobilityDuring a mobile deployment, many customers want to know why users cannot receive all of their Salesforce data on a mobiledevice. Mobile devices by nature have memory and performance constraints, and they cannot physically store massive amounts

9

Mobile Business Process ReviewPlanning a Mobile Deployment

of data. Additionally, mobile users have different needs than traditional Salesforce users. An account executive in the fieldprobably does not want to navigate through 300 opportunities on the small screen of a handheld device; she might prefer tosee just opportunities she owns that are scheduled to close this month, and then use the search feature for the opportunitiesthat were not automatically sent to her device.

Identify the relevant records for each group of mobile users. For example, you might be able to limit opportunities by amount,tasks by activity date, or accounts by ownership. A well-designed mobile configuration delivers most of the data a user requireswhile staying within the memory limitations of the mobile device.

See Also:Sample Data Sets

Salesforce Classic ResourcesNumerous resources are available to assist you with the planning of a successful Salesforce Classic deployment.

Where to Get HelpRefer to the Salesforce Classic website for links to valuable resources, such as:

• Salesforce Professional Services• Mobile Certified Salesforce partners• Salesforce Classic training classes• Salesforce Classic online demos

Product DocumentationReview Salesforce Classic documentation to become more familiar with the product:

• Salesforce Classic User Guide for BlackBerry• Tip Sheet: Salesforce Classic for BlackBerry• Salesforce Classic User Guide for iPhone

Device DocumentationVisit the following websites for more information about your mobile devices:

• Research in Motion for BlackBerry Smartphones• Apple for iPhones and the iPod touch

10

Salesforce Classic ResourcesPlanning a Mobile Deployment

http://www.salesforce.com/platform/mobile-platform/index.jsp

https://na1.salesforce.com/help/doc/en/salesforce_axm_user_guide_for_blackberry.pdf

https://na1.salesforce.com/help/doc/en/salesforce_axm_blackberry_cheatsheet.pdf

https://na1.salesforce.com/help/doc/en/salesforce_mobile_user_guide_for_iphone.pdf


http://www.apple.com

Chapter 3

Salesforce Classic Administration

After planning the mobile deployment, Salesforce administrators can beginconfiguring the Mobile Administration Console in Salesforce. This chapter

In this chapter ...

• Salesforce Classic ImplementationTips and Best Practices

walks you through the process of working with the Mobile AdministrationConsole and managing your mobile users.

• Enabling Salesforce Classic Users• About the Salesforce Classic Default

Configuration• Defining Data Sets• Editing Object Properties for

Salesforce Classic• Assigning Tabs to a Salesforce

Classic Configuration• Creating List Views for Salesforce

Classic• Setting Up Mobile Dashboards• Enabling Reports in Salesforce

Classic• Salesforce Classic Usage Data in

Custom Report Types• Setting Up Salesforce CRM Content

for Salesforce Classic• Creating Links to Web and

Visualforce Mobile Pages forSalesforce Classic

• Notifying Users about SalesforceClassic Availability

• Managing Salesforce ClassicConfigurations

• Managing Salesforce Classic Tabs• Managing Salesforce Classic Devices

11

Salesforce Classic Implementation Tips and Best PracticesSet up the Salesforce Classic app using these tips and best practices.

User Permissions Needed

“View Setup and Configuration”To view Salesforce Classic configurations:

“Manage Mobile Configurations”To create, change, or delete Salesforce Classic configurations:

Building Lean Data Sets• Keep the data sets in your mobile configurations as small as possible. Not only do lean data sets greatly improve the

Salesforce Classic app's performance, but they also make the app easier to use. Pushing massive amounts of data to thedevice might seem like a good idea, but the important records tend to get lost among the ones that aren't relevant to users'day-to-day activities. Small data sets are powerful because the Salesforce Classic app synchronizes with Salesforce every20 minutes, so the data is constantly refreshed with new and updated records. Even if your mobile configurations don'taccount for every possible record your users might need, they can search for records that aren't automatically synchronizedto their devices.

To build small data sets:

◊ Nest the objects in the data set tree. For example, add contacts as a child data set of the account object so that the dataset includes contacts related to the mobilized accounts instead of all the user's contacts.

◊ Avoid setting the record ownership filter to All Records unless your organization uses a private sharing model. It'sunlikely that users need to see all of an object's records on their devices. Instead of mobilizing all opportunity records,for example, mobilize just the opportunities owned by the user or the user's opportunity team.

◊ Use filters that synchronize the most relevant records. For example, even if you limit the opportunities on the deviceto records owned by the user, you could further prune the data set by mobilizing only opportunities closing this month.

◊ Set a record limit to prevent the data set from getting too large. Generally, a single data set should generate no morethan 2,500 records.

• Another way to build lean data sets is to mobilize the Salesforce recent items list, add the data sets, and set the recordownership filters in your data sets to None (Search Only). The user's data set is populated with records recently accessedin Salesforce, and those records in turn synchronize additional data based on the data set hierarchy. For example, let's sayyou create a data set with the account object at the root level and add the contact, task, and event objects as child data sets.When the Salesforce Classic app synchronizes an account from the Salesforce recent items list, it also synchronizes thecontacts, tasks, and events related to that account.

• If you're not sure which fields to use as filters for your data sets or mobile views, consider using the Last Activity Datefield. For example, set up a filter that synchronizes contacts with an activity logged this week or this month. The LastActivity Date field is a better indicator of a record's relevance than the Last Modified Date field—often the main detailof a record remains unchanged even though users frequently log related tasks and events.

Mobilizing Records Users Need• Before mobilizing a custom object, make sure the object's functionality is compatible with the Salesforce Classic app.

Salesforce Classic doesn’t support S-controls, mashups, merge fields, image fields, or custom links.• To obtain a relevant set of activities, mobilize the task and event objects at the root level of the data set hierarchy and nest

them under parent objects, like contacts, accounts, and opportunities. Adding tasks and events at multiple levels ensuresthat users will see their personal activities and activities related to the records on their devices. Avoid mobilizing too muchactivity history or too many tasks and events not owned by the user. Generally, there are more task and event records inan organization than any other type of record, so it's easy to bloat data sets with too many activities.

• If your sales representatives frequently take orders in the field and need a comprehensive inventory list, add the productobject at the root level of the data set hierarchy. Nesting the opportunity product object below the opportunity object won'tmobilize all products.

12

Salesforce Classic Implementation Tips and Best PracticesSalesforce Classic Administration

• If your users need to assign tasks to other users or change the record owner, mobilize the user object so that the names ofother users will be available on the device. Avoid mobilizing all user records—instead, set up filters based on the role orprofile.

• Be sure that users assigned to a mobile configuration have field-level access to all the fields used in the configuration's filtercriteria. If a user doesn't have access to a field in a data set's filter criteria, the Salesforce Classic app won't synchronize therecords for that data set or its child data sets.

• You can sometimes use cross-object formula fields to work around limitations of the Salesforce Classic app. For example,Salesforce Classic doesn't support campaigns, so you can't add the campaign object as a data set and add the opportunityobject as its child data set to get the related records. However, you can create a text formula field on the opportunity objectequal to the name of the parent campaign. The field needs to be visible, but it doesn't need to be included on your pagelayouts. Then add the opportunity object to the data set and use the new formula field to filter opportunities related to aspecific campaign.

• Although a mobile configuration might include an object at multiple levels in the data set hierarchy, users won't see duplicatetabs in the Salesforce Classic app. Only one Task tab appears on the device even if you mobilize the task object at the rootlevel and as a child data set of three objects.

Customizing Mobile Configurations• Clean up your mobile page layouts by excluding fields from the objects in the mobile configuration. Less data is sent to

the device, and mobile users don't have to scroll through unnecessary fields.• If you mobilize the Dashboards tab, be sure to select any other tabs that should appear in the Salesforce Classic app.

Customizing the tabs for a mobile configuration overrides the default tab set—if you only mobilize the Dashboard tab, itwill be the only tab sent to the device.

• Due to the small size of mobile device screens, you can only select two display columns for mobile views. If you need threecolumns of data, create a text formula field on the object that concatenates the three fields, then use the formula field inthe mobile view criteria.

• When creating mobile views, you can filter based on the current user with the $User.ID global variable, but you can't entera user's name as a value in the filter criteria. To build a view based on users, create a text formula field on the appropriateobject, then use the formula field in the mobile view criteria. For example, to create a view that displays opportunitiesowned by an opportunity team, create a text formula field on the opportunity object that contains the opportunity owner'suser ID or role, then create a view that filters on values in that field.

Testing and Deploying the Mobile Product• It's important to test mobile configurations to make sure they're synchronizing an acceptable amount of data. Test

configurations against active users who own a very large number of records. Typically, most data sets generate between500 KB and 4 MB of data. If the data sets are over 4 MB, refine the filter criteria to limit the amount of data sent to thedevice.

• You can use the Salesforce Classic app in the sandbox before deploying to your organization.• Use of the Salesforce Classic app requires a data plan. The wireless data volume for the Salesforce Classic app varies greatly

between customers and even users in the same organization. It's impossible to predict your organization's data usage, butwe can offer some guidelines:

◊ The initial data download consists of records that match the criteria specified in the user's mobile configuration andthe metadata needed to support these records when disconnected. On average, the data sizes range from 500 KB–4MB.

◊ After the initial download of data, incremental update requests are initiated by the client app every 20 minutes. Eachof these requests and the corresponding server response are approximately 200 bytes.

◊ If any new data is downloaded to the client app as a result of the update request, only the new or changed values aresent. For example, the Salesforce Classic app only downloads the new phone number in a contact record, not the entirecontact record. The amount of data transmitted differs for every organization and every user.

Generally, the volume of data transmitted by the Salesforce Classic app is low compared to moderate email usage.

• If you're deploying to BlackBerry users, evaluate your corporate network infrastructure before implementing the mobilesolution.

13

Salesforce Classic Implementation Tips and Best PracticesSalesforce Classic Administration

Best Practices• Use the zero-administration deployment option to experiment with the Salesforce Classic app before you set up mobile

configurations. You'll create better blueprints for your mobile configurations if you've tried using the Salesforce Classicapp.

• Talk to users about their favorite reports, views, and dashboards to get ideas for what filter criteria to use in mobileconfigurations.

• After setting up mobile configurations, deploy the Salesforce Classic app on a limited basis with a select group of users.Adjust the mobile setup based on their feedback, then deploy to all of your users.

Enabling Salesforce Classic Users


“View Setup and Configuration”To view Salesforce Classic settings:

“Manage Mobile Configurations”To change Salesforce Classic settings:

To enable users to access to the full version of Salesforce Classic:

1. Allocate mobile licenses to users by selecting the Mobile User checkbox on the user record. The Mobile User checkboxis enabled by default for all Unlimited, Performance, and Developer Edition users.

2. Edit each custom profile to which Salesforce Classic users are assigned to include the “API Enabled” permission. SalesforceClassic users need access to the API so their mobile devices can communicate with Salesforce. The “API Enabled” permissionis enabled by default on standard profiles.

Note: The Android, BlackBerry, and iPhone apps are available in English, Japanese, French, German, and Spanish.Contact salesforce.com to turn on Salesforce Classic for your organization.

To prevent users from activating the full version of Salesforce Classic on their mobile devices before you’re ready to deploythe app, disable the Mobile User checkbox for all your users.

Note: If you deselect this checkbox for a user who is already assigned to a mobile configuration, Salesforce removesthat user from the mobile configuration and assigns the user to the default mobile configuration.

The free version of Salesforce Classic is enabled by default. If you want to block users without Salesforce Classic licenses fromaccessing their Salesforce data on mobile devices, disable the free version of Salesforce Classic.

1. From Setup, click Mobile Administration > Salesforce Classic > Settings.2. Click Edit.3. Deselect Enable Mobile Lite.

Note: If you deselect this option while users are running the Salesforce Classic app, the Salesforce data on theirdevices is erased the next time the devices synchronize with Salesforce.

4. Click Save.

About the Salesforce Classic Default ConfigurationMobile configurations for the Salesforce Classic app are sets of parameters that determine what data Salesforce transmits tousers' mobile devices and which users receive the data on their mobile devices. A default mobile configuration is provided for

14

Enabling Salesforce Classic UsersSalesforce Classic Administration

Professional, Enterprise, Unlimited, Performance, and Developer Edition organizations. Administrators can’t view or editthe default mobile configuration.

Users are automatically assigned to the default mobile configuration when they activate their Salesforce account from a supportedmobile device using the Salesforce Classic app.

The default mobile configuration:

• Allows users with an assigned mobile license to install and activate Salesforce Classic, even if you haven’t yet assigned themto a mobile configuration.

• Allows users without an assigned mobile license to install and activate the free version of Salesforce Classic.

You can disable Salesforce Classic to prevent users from activating the Salesforce Classic app.

The default configuration can mobilize the following objects:

• Accounts

• Assets

• Cases

• Contacts

• Dashboards

• Events

• Leads

• Opportunities

• Reports

• Solutions

• Tasks

Note:

• Not all objects available in the Salesforce Classic app are mobilized with the default configuration.

• Assets aren’t available as a tab in the Salesforce Classic app but display as a related list for accounts, cases, andcontacts.

The default configuration automatically synchronizes records the user recently accessed in Salesforce on the Salesforce Classicapp. Users can search for records that aren’t automatically synchronized; once the user downloads a record, the record becomesa permanent part of the data set. In addition to recently accessed records, the default configuration synchronizes activitiesclosed in the past five days and open activities due in the next 30 days.

Creating Salesforce Classic ConfigurationsTesting Salesforce Classic Configurations

Creating Salesforce Classic Configurations




Mobile configurations are sets of parameters that determine the data Salesforce transmits to users' mobile devices, and whichusers receive that data on their mobile devices. Organizations can create multiple mobile configurations to simultaneously suit

15

Creating Salesforce Classic ConfigurationsSalesforce Classic Administration

the needs of different types of mobile users. For example, one mobile configuration might send leads and opportunities to thesales division, while another mobile configuration sends cases to customer support representatives.

Before creating your mobile configurations, plan which profiles and users you want to assign to each configuration. Eachmobile configuration only affects the mobile devices of users assigned to the configuration.

To create a mobile configuration:

1. Enter Basic Information2. Assign Users and Profiles3. Set Total Data Size Limit4. Complete Your Mobile Configuration

Note:

A default mobile configuration is provided for Professional, Enterprise, Unlimited, Performance, and DeveloperEdition organizations. You can’t view or edit the default configuration.

Any Salesforce user who doesn't have a mobile license can download a free, restricted version of Salesforce Classic.These users are assigned to the default mobile configuration when they activate their Salesforce account from a mobiledevice.

Enter Basic Information1. From Setup, click Mobile Administration > Salesforce Mobile > Configurations to access the mobile configurations list

page.2. Click New Mobile Configuration.3. Enter a name for the mobile configuration.4. Select the Active checkbox if you want to activate the mobile configuration immediately after creating it. The mobile

configuration does not work until you select this checkbox.

If you deactivate an active mobile configuration, Salesforce saves all requests from devices of the users assigned to themobile configuration for up to one week. If you reactivate the mobile configuration, Salesforce executes those requests inthe order received.

5. Optionally, enter a description for the mobile configuration.6. Optionally, select the Mobilize Recent Items checkbox to mark recently used records in Salesforce for device

synchronization.

Selecting this option ensures that mobile users assigned to the configuration will not have to search for and download itemsthey recently accessed on Salesforce, even if those records do not meet the configuration's filter criteria. Only recordsbelonging to mobilized objects can be marked for device synchronization; for example, if you do not mobilize the accountobject in a configuration, users assigned to that configuration cannot automatically receive recent accounts on their devices.

7. If you select the Mobilize Recent Items checkbox, select a value from the Maximum Number of Recent Itemsdrop-down list. Set a low number if your users have minimal free space on their mobile devices.

8. Optionally, select the Mobilize Followed Records checkbox to automatically synchronize records users are followingin Chatter to their mobile device. The device only synchronizes followed records for objects included in the mobileconfiguration's data set.

The Mobilize Followed Records checkbox is only available if Chatter is enabled for your organization.

Assign Users and ProfilesYou can assign individual users and profiles to each mobile configuration. If you assign a profile to a mobile configuration,the mobile configuration applies to all Salesforce Classic users with that profile unless a specific user is assigned to anothermobile configuration.

16

Creating Salesforce Classic ConfigurationsSalesforce Classic Administration

Tip: For ease of administration, we recommend that you assign mobile configurations to profiles; however, you mayhave situations in which you need to assign a configuration directly to individual users.

To assign users and profiles to a mobile configuration:

1. In the Search drop-down list, select the type of member to add: users or profiles. This drop-down list is not available ifyou have not enabled the Mobile User checkbox on any user records, or if all users are already assigned to a mobileconfiguration; in that case, you can only assign profiles to this mobile configuration.

2. If you do not immediately see the member you want to add, enter keywords in the search box and click Find.3. Select users and profiles from the Available Members box, and click the Add arrow to add them to the mobile

configuration.

You can assign each user and profile to only one mobile configuration.

The Available Members box only displays users who have the Mobile User checkbox enabled.

4. If there are users or profiles in the Assigned Members box you do not want to assign to this mobile configuration, selectthose users and click the Remove arrow.

Warning: Removing a user from an active mobile configuration deletes the Salesforce-related data on the user'smobile device but does not delete the client application.

Set Total Data Size LimitDifferent types of mobile devices offer different memory capacities, and some devices experience serious problems if all of theflash memory is used. To avoid overloading mobile devices, optionally specify a total data size limit for each mobile configuration.The total data size limit prevents Salesforce from sending too much data to the mobile devices of users assigned to the mobileconfiguration.

To set the total data size limit, use the Don't sync if data size exceeds drop-down list to specify the amount ofmemory that is consistently available on the mobile devices of users who are assigned to this mobile configuration. If thecombined size of all the data sets exceeds this limit, users assigned to this profile receive an error message on their mobiledevices, and Salesforce will not synchronize any data sets in this mobile configuration. Test your mobile configuration to makesure the data sets do not exceed the total data size limit.

Tip: To reduce the size of your data, do one or more of the following:

• Delete a data set.• Reduce the scope of your data sets.• Refine the filter criteria of your data sets.

Complete Your Mobile ConfigurationClick Save. Note that your mobile configuration is not active until you select the Active checkbox.

Testing Salesforce Classic Configurations


“View Setup and Configuration”To view Salesforce Classic data sets:

“Manage Mobile Configurations”To test Salesforce Classic configurations:

17

Testing Salesforce Classic ConfigurationsSalesforce Classic Administration

When you create a Salesforce Classic configuration, you specify a total data size limit for the configuration. The total datasize limit prevents Salesforce from sending too much data to the mobile devices of users assigned to the mobile configuration.After defining the data sets, it’s important to test the mobile configuration to make sure the total data size limit isn’t exceeded.

To estimate the size of the data set that the mobile configuration will deliver to a user's device:

1. Click Mobile Administration > Salesforce Mobile > Configurations, and click the name of the mobile configurationyou want to test.

2. In the Data Sets related list, click Edit.3. In the Test Data Size section, click the lookup icon next to the Select a user field to choose the user you want to test.

While users must be mobile-enabled in order to assign them to mobile configurations, you can test the configuration'sdata size against any user account.

The Select a user field defaults to the name of the user currently logged in; however, it is important to test a mobileconfiguration with the accounts of users who will actually be assigned to the configuration, particularly users who own alarge number of records.

4. Select the Include metadata checkbox to include metadata in the estimate. Metadata consists of page layout and schemainformation, and the amount of metadata sent to a device can be very high depending on the size of your organization andthe complexity of its setup.

Warning: It might take a while for Salesforce to calculate the metadata size in addition to the data size. Even ifyou choose to hide the metadata in your test results, the metadata is still factored into the total data size when themobile device synchronizes with Salesforce.

5. Click Estimate Data Size.

The size of each data set is calculated. Results display in the hierarchy tree, which is the left pane of the data set region atthe top of the page. Additional results appear in the Test Data Size section below the hierarchy.

• In the hierarchy tree, two numbers appear next to each data set. The first represents the number of records generatedby the data set, and the second represents the total size of the data set in bytes or kilobytes. This breakdown is usefulfor identifying which data sets might require additional filtering criteria to reduce the size.

• The Test Data Size section provides an estimate of the data that the current mobile configuration would deliver to theselected user's device, including:

◊ The size and number of records in each object's data set.◊ The total size and number of records, which includes records in the data set and marked records. A marked record

is a record that is not part of a user's mobile configuration. There are two ways marked records can become part ofthe data set:

- The user downloads records to his or her device through online searches, and the records are flagged so thatthey get sent to the user's device every time the device synchronizes with Salesforce.

- Records in the user's data set contain lookup fields to records that do not match the mobile configuration's filtercriteria. Salesforce synchronizes the records referenced in the lookup fields so that users do not encounter brokenlinks in the mobile app.

Tip: For an accurate count of the marked records, synchronize the data in the mobile app beforeestimating the data size. To synchronize the data:

- On an Android device, tap Application Info > Sync Now > Refresh All Data.- On a BlackBerry device, open the menu and select System Info, then open the menu and select

Refresh All Data.- On an iPhone device, tap More, then tap App Info. Tap Sync Now, then tap Refresh All Data.

18

Testing Salesforce Classic ConfigurationsSalesforce Classic Administration

◊ The size of the metadata that would be sent to the device for the user, if you selected the Include metadata checkbox.◊ The total mobilized data set, which is the sum of all the records.

• Reports are not included in the data size estimate.

6. Compare the test results to the total data size limit that was set for the configuration; the limit is located in the top of theTest Data Size section. Click the size limit to increase or decrease the value on the Edit Mobile Configuration page.

• If the total data size is below the limit, the selected user can safely be assigned to the mobile configuration. However,keep in mind that the test results are an estimate because different devices have different storage algorithms.

• If the total data size exceeds the limit, reduce the size of the data by reducing the scope of your data set, refining thefilter criteria of your data sets, deleting a data set, or removing fields from the mobile page layout. Repeat the testingprocess until the data is below the total limit.

Note: The data size estimate in the Test Data Size section does not automatically refresh if you edit the datasets. Click Refresh Data Size to update the test results.

Defining Data Sets


“View Setup and Configuration”To view mobile data sets:

“Manage Mobile Configurations”To create, change, or delete mobile data sets:

Accessing Salesforce from a mobile device is very different than accessing it from your computer. This is because mobile devicesgenerally have less memory and screen size than computers, and they do not maintain a constant network connection. Towork with these limitations, each mobile configuration only transfers data sets, which are subsets of the records users accessin the Salesforce online user interface. Mobile devices store data sets in on-board databases, allowing users to access their mostimportant records and work offline when no network connection is available. Salesforce automatically synchronizes the on-boarddatabases when the mobile device reestablishes a network connection.

Each data set can contain records related to a single object and is classified by the name of that object. For example, theAccounts data set only includes account records.

Data sets can have child data sets, which are data sets that contain records associated with a top-level (parent) data set. Forexample, if the first level of your hierarchy has an Accounts data set, you can add a Contacts child data set that includes allcontact records related to the account records. Child data sets appear as related lists on mobile devices.

A single mobile configuration can have multiple data sets for the same object and at different levels. For example, you canhave an Events parent data set and an Events child data set under Leads.

Tip: Review the sample data sets to see how you might define data sets for common groups of Salesforce users.

After creating a mobile configuration, you must define its data sets. To access the data sets for a mobile configuration:

1. Click Mobile Administration > Salesforce Mobile > Configurations, and click the name of the mobile configurationyou want to modify.

2. In the Data Sets related list, click Edit.3. From the Data Sets page, you can:

• Add a data set.

19

Defining Data SetsSalesforce Classic Administration

• Remove a data set by selecting the data set you want to remove and clicking Remove.• Edit a data set by selecting the data set you want to edit in the hierarchy. The right pane displays the filters for that

data set.• Test your mobile configuration.

As you define and modify the data sets, Salesforce automatically saves your changes.

4. Click Done when you are finished.

Adding Data SetsTo add a data set:

1. In the hierarchy, select Data Sets to create a parent data set, or select an existing data set to create a child data set.2. Click Add....3. In the popup window, select the object for the records you want the data set to include. Salesforce lets you create parent

data sets for all custom objects and the following standard objects:

• Accounts• Assets• Attachments• Cases• Contacts• Content• Events• Leads• Notes• Opportunities• Price Books• Products• Solutions• Tasks• Users

Note:

• Although attachments are available as a data set, they're only supported in Salesforce Classic for Android.Salesforce Classic for iPhone and BlackBerry don't currently support attachments.

• Salesforce Classic supports default field values only for picklists and multiselect picklists. Default field valuesfor other types of fields, such as checkboxes and numeric fields, do not appear in Salesforce Classic.

When adding to an existing data set, the popup window displays any object with a relationship to the selected object. Thisincludes child objects, and also parent objects with a master-detail or lookup relationship to the selected object.

For example, assume you created an account field called Primary Contact with a lookup relationship to the contact object.If you add Account as a top-level data set in a mobile configuration, you see two sets of contacts when you add Contactbelow Account:

• Contact: Represents the standard relationship between the account and contact objects.• Contact (Referenced by Account): Represents any object that is the parent in a lookup or master-detail relationship

for the selected object. In this case, the contact object is referenced by the Primary Contact field on the account object.

Because Salesforce distinguishes between these two types of relationships, you could, for example, mobilize just the contactsreferenced by a custom account field without sending any child contact records to the device.

4. Click OK. The data set you created appears in the hierarchy.

20


5. Optionally, use filters to restrict the records that a parent or child data set includes:

a. Use the Filter by Record Ownership options to configure Salesforce to automatically synchronize records based on theowner of the record. The possible options are:

• All Records: Salesforce automatically synchronizes all records the user can access. The All Records optionis not available for tasks and events when they are parent data sets in a mobile configuration. This helps preventfailed data synchronization due to activity filter queries that take too long to run.

• User's Records: Salesforce automatically synchronizes all records the user owns.• User's Team's Records: Salesforce automatically synchronizes all records owned by the user and the user's

subordinates in the role hierarchy.• User's Account Team's Records: Salesforce automatically synchronizes accounts for which the user is an

account team member, but does not include accounts owned by the user.• User's Opportunity Team's Records: Salesforce automatically synchronizes opportunities for which the

user is an opportunity team member, but does not include opportunities owned by the user.• None (Search Only): Salesforce does not automatically synchronize any records for this data set; however, users

can use their mobile devices to search all of the records they can access.

Salesforce only displays options that relate to the selected data set. For example, selecting an account data set displaysthe User's Account Team's Records option, while selecting an opportunity data set displays the User'sOpportunity Team's Records option.

If your mobile needs for an object require a combination of the available record ownership filters, you can add the sameobject data set up to four times on the same hierarchy level. For example, a sales manager might want to synchronizehis opportunities, opportunities owned by his subordinates, and opportunities for which he is an opportunity teammember. In this case, you would add an opportunity data set and select User's Team's Records, then add a secondopportunity data set at the same level in the hierarchy and select User's Opportunity Team's Records. Notethat objects with only one ownership filter option, such as Case Comment, cannot be added multiple times at the samelevel of the hierarchy.

b. Set the filter criteria to automatically synchronize only records that meet specific criteria in addition to the Filter byRecord Ownership option you selected. For example, you can set the filter to only include opportunity records withamounts greater than $50,000, or contact records with the title “Buyer.”

c. To prevent a single data set from consuming all the memory on a mobile device, select the second radio button underSet Max Record Limit and enter the maximum number of records this data set can transfer to mobile devices. Use theOrder By and Sort drop-down lists to specify which records are synchronized if the data size limit is exceeded.

If the limit is reached, Salesforce updates the records currently on the mobile device approximately every 20 minutes,and replaces the records approximately every 24 hours in accordance with the Order By and Sort settings. For example,if the settings are Last Modified Date and Descending, Salesforce transfers the most recently modified records tomobile devices and removes the same number of records that were least recently modified.

If you selected the None (Search Only) Filter by Record Ownership option, the limit you set does not apply becauseno records are automatically synchronized.

Tip: Do not use Set Max Record Limit in place of filters. Only use Set Max Record Limit as a safetymechanism, and use filters as the primary means of limiting the number of records on a mobile device. Thisensures that your mobile users receive the correct records on their devices.

Because of the memory restrictions of mobile devices, Salesforce prevents a single query from returning more than2,500 records.

6. Be sure to test your mobile configuration to make sure the data does not exceed the total data size limit.7. Click Done.

Merge Fields for Mobile Filter CriteriaSample Data Sets

21


Merge Fields for Mobile Filter CriteriaSome of the $User merge fields are available when defining filters for mobile configurations and mobile custom views. Inmobile configurations, you can use these merge fields to synchronize records where the user is linked to a record but is not therecord owner. For example, you can send cases created by the current user to the mobile device, or you can send records to thedevice where the current user is referenced in a custom field. In mobile views, you can use the merge fields to define view basedon the record owner; for example, you might create a view that displays the current user's accounts with a rating of “Hot”.

The following table describes the available user merge fields:

DescriptionMerge Field

References the ID of the current user. This merge field canbe applied to fields that contain a user lookup. The valid

$User.ID

operators for this merge field are Equals and Not Equal To.When creating mobile view filters that reference an ownerfield, you can only use the $User.ID merge field.

References the username of the current user. This merge fieldcan be applied to any text or lookup field, except picklists. The

$User.Username

valid operators for this merge field are Equals, Not Equal To,Greater Than or Equal, Less Than or Equal, Contains, DoesNot Contain, and Starts With.

References the first name of the current user. This merge fieldcan be applied to any text or lookup field, except picklists. The

$User.Firstname


References the last name of the current user. This merge fieldcan be applied to any text or lookup field, except picklists. The

$User.Lastname


References the first and last name of the current user. Thismerge field can be applied to any text or lookup field, except

$User.Fullname

picklists. The valid operators for this merge field are Equals,Not Equal To, Greater Than or Equal, Less Than or Equal,Contains, Does Not Contain, and Starts With.

Sample Data SetsMany administrators create mobile configurations based on the functional groups in their organization because users in thesame group usually have similar mobile requirements for data. Below are sample data sets for common Salesforce groups. Yourmobile users have unique needs, but you can use the examples as a reference to help you get started with mobile configurations.

Sales ManagerSales managers usually need to see records they own and also the records of their subordinates. They also tend to closelymonitor large deals in the pipeline.

22

Merge Fields for Mobile Filter CriteriaSalesforce Classic Administration

This mobile configuration allows sales managers to see:

• The opportunities they own.• The opportunities owned by users who report to them in the role hierarchy.• All opportunities scheduled to close in the current quarter with an amount greater than $100,000.• All accounts related to the opportunities.• A subset of their contact and activity records.

Figure 2: Sample Mobile Configuration for Sales Managers

Sales EngineerThe sales engineer mobile configuration retrieves opportunities owned by the other members of the user's opportunity team,but does not include the user's records. The configuration is opportunity-based because all accounts and contacts sent to thedevice are related to the opportunities. The sales engineers would see activity history related to the opportunities on the deviceand also their own activities.

Figure 3: Sample Mobile Configuration for Sales Engineers

Account ExecutiveThis account executive mobile configuration is account-based, which means the device pulls down the user's accounts andopportunities related to those accounts. The opportunities are filtered so that only open opportunities scheduled to close inthe current quarter appear on the device. The Task and Event child data sets retrieve all activities related to those opportunities,not just the user's activities. Only open tasks and events from a two-month window are sent to the device. The Task and Eventparent data sets pull down just the user's activities and restrict the activities to open tasks and events scheduled for the next30 days. The Contact data set delivers the user's contact records, but limits the record count to the 500 most recently activecontacts.

23

Sample Data SetsSalesforce Classic Administration

Figure 4: Sample Mobile Configuration for Account Executives

Customer Support RepresentativeCustomer support representatives are focused primarily on cases and solutions. This mobile configuration delivers all opencases to the user's device, along with related accounts, contacts, case comments, case history, tasks, and events. The CaseSolution child data set sends all solutions related to the cases, and the Solution data set lets the user search for solutions fromthe Solutions tab on the device. The support representatives also have access to a subset of their activity records.

Figure 5: Sample Mobile Configuration for Customer Support Representatives

Editing Object Properties for Salesforce Classic



“Manage Mobile Configurations”To edit Salesforce Classic object properties:

You can change the properties of standard and custom objects in the Salesforce Classic app. For example, you can restrict thepermissions of Salesforce Classic users, or you can exclude unnecessary fields from the object's mobile page layout.

Salesforce Classic object properties are customized per mobile configuration. To edit mobile object properties:

1. Click Mobile Administration > Salesforce Mobile > Configurations.2. Click the name of the mobile configuration you want to modify.

24

Editing Object Properties for Salesforce ClassicSalesforce Classic Administration

3. In the Mobile Object Properties related list, click Edit next to an object name.

Only objects you mobilized in the configuration's data set appear in the related list. You can’t change the properties of theuser object.

4. From the Edit Mobile Configuration page, you can:

• Remove Mobile Permissions• Customize Salesforce Classic Page Layouts

5. Click Save.

Remove Mobile PermissionsThe Salesforce Classic app inherits the user's permissions from Salesforce. Some administrators want to further restrict thepermissions of users when they access Salesforce data in Salesforce Classic, usually due to limitations of the app or the possibilityof user error. For example, users can inadvertently delete a record because they don't realize that deleting a record in SalesforceClassic also deletes the record in Salesforce. If this is a concern, administrators can prevent users from deleting records in themobile application, regardless of their standard and custom object permissions in Salesforce. Also, Salesforce Classic doesn’tsupport all Salesforce features, such as S-controls and Apex. If your business process for an object is unsupported by SalesforceClassic, you might choose to prevent mobile users from updating those records in the app.

In the Permissions section, select which permissions to remove from mobile users for this object. Use the Deny Create, DenyEdit, or Deny Delete checkboxes to prevent users from creating, editing, or deleting records in Salesforce Classic.

Note: Currently, you can't block mobile permissions for the content object.

Customize Salesforce Classic Page LayoutsThe Salesforce Classic app inherits the user's page layouts from Salesforce. Administrators may want to exclude some fieldsfrom each object's mobile page layout because unnecessary fields consume memory and make it harder for users to scrollthrough pages on the mobile device.

In the Excluded Fields section, select which fields to display on the mobile device for this object. To add or remove fields,select a field name, and click the Add or Remove arrow.

• Administrators can view all available fields per object, regardless of field-level security.• Certain fields are required in order for Salesforce Classic to communicate with Salesforce. Those fields don’t display in

the Available Fields box because they are mandatory and can’t be excluded from mobile page layouts.• Fields used in custom mobile views can’t be excluded from mobile page layouts.• If you mobilize the content object, all of the content object's fields display in the Available Fields box; however, the layout

of the content detail page in the Salesforce Classic app is hard-coded to show only a few fields. Excluding fields for thecontent object doesn't affect the page layout in the app.

Assigning Tabs to a Salesforce Classic Configuration



“Manage Mobile Configurations”To customize Salesforce Classic tabs:

For each mobile configuration, you can select the tabs that appear in the Salesforce Classic app and define the order of thetabs. The available tabs for a mobile configuration include:

25

Assigning Tabs to a Salesforce Classic ConfigurationSalesforce Classic Administration

• Standard object tabs

• Custom object tabs

• Visualforce and web tabs that have been enabled for Salesforce Classic

Warning: Not all websites and Visualforce features are supported on mobile devices. Carefully review the bestpractices for creating mobile-friendly pages before enabling Visualforce or web tabs for the Salesforce Classic app.

By default, tabs work the same in the Salesforce Classic app as in the full Salesforce site—if an object's tab is hidden inSalesforce, it’s hidden in Salesforce Classic as well.

Note: If you customize mobile tabs, the tabs you select for the mobile configuration are sent to users' mobile deviceseven if the tabs have not been added to a configuration. Although the tabs are sent to the device, they only displayin the Salesforce Classic app if users have permission to view the tab.

There are several reasons you might want to hide an object's tab in Salesforce Classic even though the object records are sentto the device. The Salesforce Classic app has much less screen space to display a row of tabs, so occasionally you might chooseto reduce the number of tabs on the device. Also, sometimes a custom object has a relationship to a standard object, and usersaccess the custom object record from the parent object record. In that case, you could mobilize the custom object but hide thetab.

To assign tabs to a mobile configuration:

1. Click Mobile Administration > Salesforce Mobile > Configurations, and then click the name of a mobile configuration.2. In the Mobile Tabs related list, click Customize Tabs to define mobile tabs for the first time. If you have already set up

the mobile tabs, click Edit.3. Select tabs from the Available Tabs list, and click the Add arrow to add them to the mobile configuration.4. In the Selected Tabs list, choose tabs and click the Up and Down arrows to arrange the tabs in the order they should

appear in the Salesforce Classic app.5. Click Save.

Note: iPhone users can customize the order of their tabs in the Salesforce Classic app. If the user customizes theirtab order, any administrator changes to the tab order in the mobile configuration are ignored by the app, and anynewly mobilized tabs are added below the user's existing tabs.

Enabling Web and Visualforce Tabs for Salesforce Classic

Enabling Web and Visualforce Tabs for Salesforce ClassicYou can make web and Visualforce tabs available in the Salesforce Classic app. When you build the web tab or Visualforcetab, edit the tab properties and select the Salesforce Classic Ready checkbox to ensure that the web page or Visualforcepage displays and functions properly on a mobile device. Selecting the checkbox adds the tab to the list of available tabs foryour Salesforce Classic mobile configurations.

It is important to note that most mobile browsers have technical limitations concerning display size, scripts, processor speed,and network latency. Review the following considerations before mobilizing your web and Visualforce pages to ensure thatthey are compatible with mobile browsers.

Mobile Web Tab ConsiderationsConsider the following when defining a web tab that will be used in the Salesforce Classic app:

26

Enabling Web and Visualforce Tabs for Salesforce ClassicSalesforce Classic Administration

• The ability to mobilize web tabs is only available for BlackBerry and iPhone devices. If you mobilize a web tab, keep inmind that Android users can’t view the tab in Salesforce Classic.

• The minimum BlackBerry operating system requirement for web tabs is 4.3.• The tab type must be URL. The mobile application can’t run S-controls.• Some web pages contain JavaScript and Flash, but not all mobile browsers support them:

◊ Apple's Safari browser supports JavaScript, but not Flash.◊ The BlackBerry browser has limited support for JavaScript and no support for Flash.

• Before mobilizing a web tab, navigate to the target URL on one of your organization's mobile devices to verify that it worksas expected in a mobile browser. In the event that your organization's device inventory includes phones with differentoperating systems—for example, both iPhones and BlackBerry smartphones—be sure to test on each type of device. Ifusers can’t accomplish the necessary tasks on the web page from a mobile browser, do not mobilize the web tab.

• JavaScript must be enabled on BlackBerry devices in order to view JavaScript web pages. The BlackBerry administratorcan globally enable JavaScript from the BlackBerry Enterprise Server. Users can also enable JavaScript on a BlackBerrysmartphone by opening the BlackBerry browser, selecting Options > Browser Configuration, and then selecting theSupport JavaScript checkbox.

Visualforce Mobile Tab ConsiderationsConsider the following when defining a mobile Visualforce tab:

• Visualforce Mobile is only available for BlackBerry and iPhone. If you mobilize a Visualforce tab, keep in mind that Androidusers can’t view the tab in Salesforce Classic.

• The Salesforce Classic app can run on BlackBerry operating system versions 4.3 through 7.0. For optimum performance,however, Salesforce recommends running Visualforce Mobile on BlackBerry smartphones installed with at least version6.0.

• Because the display size is limited on mobile browsers, we recommend redesigning the Visualforce page to optimize it formobile users:

◊ Set the sidebar and showHeader attributes on the <apex:page> tag to false. Phones have small screens andlimited processing power, so it is essential that the page suppresses the tab header and sidebar.

◊ Set the standardStylesheets attribute on the <apex:page> tag to false. The standard Salesforce stylesheetcauses pages to load slowly on the device. Additionally, most BlackBerry browsers older than the 6.0 OS can’t properlyinterpret CSS . The best approach to adding a stylesheet to your page is to include a <style> section just below the<apex:page> component.

◊ Set the columns attribute on the <apex:pageBlockSection> component to 1. There is not enough room on amobile device’s screen to display two columns, so specifying a one-column layout prevents fields from wrappingawkwardly on the page.

• Splash pages don’t display in the Salesforce Classic app.• In the Salesforce Classic app, the Visualforce page is embedded in a tab, so you should avoid using tabs for navigation in

mobile Visualforce pages.• Even if you know that the mobile browser supports the JavaScript in your Visualforce page, keep your use of JavaScript to

a minimum. Mobile devices generally have slow network connections, and too many scripts running on a page creates apoor user experience. To minimize the amount of JavaScript on your mobile Visualforce pages, try to build them usingmostly HTML.

• All Visualforce pages contain JavaScript, even if you don’t create pages that use JavaScript code. JavaScript must be enabledon BlackBerry devices in order to view Visualforce pages. The BlackBerry administrator can globally enable JavaScriptfrom the BlackBerry Enterprise Server. Users can also enable JavaScript on a BlackBerry smartphone by opening theBlackBerry browser, selecting Options > Browser Configuration, and then selecting the Support JavaScript checkbox.

• The embedded browser in the BlackBerry client application doesn’t have built-in navigation. If your Visualforce page is awizard, you should provide navigation links that allow users to return to the previous page and advance to the next page.

• BlackBerry administrators should be aware that the download size setting on the BlackBerry Enterprise Server affects howmuch data can be pushed to the device. Check that the download size setting is appropriate, and be sure to test yourVisualforce pages before deploying them to your Salesforce Classic users.

27

Enabling Web and Visualforce Tabs for Salesforce ClassicSalesforce Classic Administration

• User agent inspection can be executed in a custom controller to support multiple devices. You can do this by inspectingthe appropriate result of the getHeaders() method on the current page reference.

Creating List Views for Salesforce Classic


“View Setup and Configuration”To view Salesforce Classic devices and users:

“Manage Mobile Configurations”To manage Salesforce Classic custom views:

You can create custom list views for Salesforce Classic users. Custom list views for Salesforce Classic, also called mobile views,are different from Salesforce custom views in these ways:

• Administrators set up mobile views for each mobile configuration. The views are available to all users assigned to theconfiguration, and administrators can’t restrict visibility to certain groups of users within the configuration. Each mobilizedobject in a mobile configuration can have up to 10 custom views.

• Users can’t filter mobile views by All Records or My Records. The views apply to all records stored locally on the deviceregardless of ownership; however, ownership filters can be applied using the additional fields in the search criteria.

• Mobile views don't support filter logic.

• Mobile views are limited to a two-column display.

• Users can sort mobile views in ascending or descending order by up to two fields.

For each mobile configuration, you can define up to 10 custom views per object. These views are then pushed to the devicesof users assigned to the affected configurations. To create a custom view for Salesforce Classic:

1. Click Mobile Administration > Salesforce Mobile > Configurations, and then click the name of a mobile configuration.You might need to create a mobile configuration if you haven't already.

2. Scroll down to the Mobile Views related list.3. Choose an object type from the Select an object drop-down list, and then click New Mobile View. Only objects included

in the mobile configuration's data set appear in the drop-down list. You can’t create mobile views for the user object.4. Enter the view name.

Because display space on mobile devices is limited, the maximum length of a mobile view name is 30 characters.

5. In the Specify Filter Criteria section, enter conditions that the selected items must match; for example, Amount isgreater than $100,000.

a. Choose a field from the first drop-down list.

Note: You can’t create views based on fields you excluded from mobile page layouts or fields that are hiddenfor all profiles and permission sets.

b. Choose a filter operator.c. In the third field, enter the value to match.

Warning: Note the following about filter criteria values for mobile views:

• You can use the $User.ID merge field as a value in your filter criteria to reference the current user. Youcan't enter user names in your filter criteria.

• You can only enter special date values in your filter criteria, not actual dates.• You can't use FISCAL special date values in the filter criteria.

28

Creating List Views for Salesforce ClassicSalesforce Classic Administration

d. Select Match All if items in the mobile view should match all the criteria you entered. Select Match Any if items inthe mobile view should match any of the criteria you entered. Mobile custom views do not support advanced filteringoptions.

6. In the Select Fields to Display section, select the fields to use as display columns.

The default fields are automatically selected. You can choose up to two different columns of data fields to display in yourmobile custom view.

7. In the Define Sort Order section, optionally set a primary and secondary sort order for the view.

a. Select a field in the Order By drop-down list. You can sort by fields that have been excluded from the object's mobilepage layout.

b. Set the sort order to Ascending or Descending.

8. Click Save.

Setting Up Mobile Dashboards


“View Setup and Configuration”To view mobile configurations:

“Manage Mobile Configurations”To mobilize dashboards:

You can make the Dashboards tab available in Salesforce Classic by adding it to the tabs for a mobile configuration. Mobiledashboards allow field users to keep up with corporate metrics and key performance indicators even when they are away fromtheir desks.

Note the following about mobile dashboards:

• The Dashboards tab in the mobile application launches an embedded browser to display the dashboards.

• Due to screen size limitations, mobile dashboards display in a single column.

• Links to custom report details are disabled in mobile dashboards.

• The first time a user visits the Dashboards tab in Salesforce Classic, the mobile application requests the last dashboard theuser viewed in Salesforce. Depending on the strength of the cellular or WiFi signal, it could take several minutes beforethe dashboard displays on the page.

• Dashboards do not automatically refresh in the mobile application. Users can request a dashboard refresh by clicking theRefresh button.

• Users are able to work offline in the mobile application. Without a wireless connection, users can see the last vieweddashboard, but they cannot refresh the dashboard or select a different one.

• The minimum BlackBerry operating system requirement for mobile dashboards is 4.5. Mobile dashboards are compatiblewith version 4.3, but tables in the dashboards might not display properly.

• BlackBerry administrators should be aware that the download size setting on the BlackBerry Enterprise Server affects howmuch dashboard data can be pushed to the device. Check that the download size setting is appropriate, and be sure to testyour dashboards before deploying them to your mobile users.

Note: Currently, dashboards are only available in the BlackBerry and iPhone mobile client applications.

To enable mobile dashboards:

1. Click Mobile Administration > Salesforce Mobile > Configurations, and then click the name of a mobile configuration.

29

Setting Up Mobile DashboardsSalesforce Classic Administration

2. In the Mobile Tabs related list, click Customize Tabs to define mobile tabs for the first time. If you have already set upthe mobile tabs, click Edit.

3. Select Dashboards from the Available Tabs list, and click the Add arrow to add it to the mobile configuration. TheAvailable Tabs list includes standard object tabs and custom object tabs. It can also include web and Visualforce tabs.

Warning: If you have not yet customized tabs in the mobile configuration, you must select all the tabs that shouldappear in the mobile application, not just the Dashboards tab.

4. In the Selected Tabs list, choose the Dashboards tab and click the Up and Down arrows to define where the Dashboardstab should appear in the mobile application.

5. Click Save.

Enabling Reports in Salesforce Classic


“Manage Public Reports”To create, edit, and delete public report folders:


To enable reports in the Salesforce Classic app:

1. Create a Mobile Reports folder in Salesforce. From the reports home page in the full site, click Create New Folder.2. In the Report Folder field, enter: Mobile Reports.

The server won’t load reports on mobile devices unless this folder is named Mobile Reports. Be sure to check for anytypos in the name before saving the folder. Additionally, Salesforce doesn’t require folder names to be unique. SalesforceClassic users can see any report stored in all folders named Mobile Reports unless you restrict access with the folder visibilityoption.

3. Choose a Public Folder Access option. This option doesn’t affect the ability of mobile users to run reports.4. Optionally, select any unfiled reports and click Add to store them in the Mobile Reports folder. You can also add reports

to the folder after saving the folder.5. Choose a folder visibility option.

• This folder is accessible by all users gives every user in your organization the ability to see the list ofmobile reports from their devices.

• This folder is accessible only by the following users lets you grant access to a desired set of users.

Don’t make the Mobile Reports folder private unless you want to hide mobile reports from all users, includingyourself.

6. Click Save.7. Add reports to the Mobile Reports folder. Click the report name on the reports home page, then click Save As and save

the report in the Mobile Reports folder.

After saving the report, you can edit the options to make the report easier to view on a mobile device. For example, youmight reduce the number of columns or enter additional filtering criteria.

8. Add the Reports tab to your mobile configurations. Click Mobile Administration > Salesforce Mobile > Configurations,then click the name of a mobile configuration.

9. In the Mobile Tabs related list, click Customize Tabs to define mobile tabs for the first time. If you’ve already set up themobile tabs, click Edit.

30

Enabling Reports in Salesforce ClassicSalesforce Classic Administration

10. Select Reports from the Available Tabs list, then click the Add arrow to add it to the mobile configuration. The AvailableTabs list includes standard object tabs and custom object tabs. It can also include web and Visualforce tabs.

Warning: If you have not yet customized tabs in the mobile configuration, you must select all the tabs that shouldappear in the Salesforce Classic, not just the Reports tab.

11. In the Selected Tabs list, choose the Reports tab and click the Up and Down arrows to define where the Reports tab shouldappear in the Salesforce Classic app.

12. Click Save.

Note: Currently, reports in Salesforce Classic aren’t available on Android or iPhone devices.

Salesforce Classic Usage Data in Custom Report Types


“Manage Custom Report Types”To create or update custom report types:

“Modify All Data”To delete custom report types:

You can create custom report types with data that shows how your organization uses Salesforce Classic. For example, thereports can show how often users access Salesforce Classic, which mobile device models they use, and so forth.

To create a custom report type with Salesforce Classic usage data, select the Mobile Session Primary Object when defininga custom report type. When you select the fields for the custom report type, choose from the following Salesforce Classic-specificfields.

DefinitionMobile Usage Data Point

Wireless carrierBrand

Total size of records on deviceData Size (Bytes)

Unique physical address of device (PIN for BlackBerry orUDID for iOS)

Device Address

Installed version of Salesforce ClassicDevice Application Version

Model of deviceDevice Model

Version of operating system installed on deviceDevice Operating System Version

Duration of the mobile session in secondsDuration

Date of last registration or activationLast Registration Date

Date of last communication received from deviceLast Status Date

Manufacturer of deviceManufacturer

Size of metadata (page layouts, picklist values, and so forth)on the device

Metadata Size (Bytes)

Name of the device userOwner: Full Name

31

Salesforce Classic Usage Data in Custom Report TypesSalesforce Classic Administration

Date the mobile session startedSession Start Date

Indicator that the user's data set exceeds the maximum allowedsize by the mobile configuration

Status

Note:

• Mobile sessions are similar to Web-based sessions in login history reports; however, mobile sessions have a fixedtimeout value of 20 minutes. Salesforce creates a new Mobile Session when a user logs into or launches SalesforceClassic after 20 minutes of inactivity in the app or on the device in general.

• Mobile session reports only have usage data for the Salesforce Classic app and not other Salesforce mobile apps,such as the Salesforce1 apps.

• Some devices do not provide every physical attribute. For example, Apple devices do not provide brand.

Setting Up Salesforce CRM Content for Salesforce Classic



“Manage Mobile Configurations”To create, change, or delete Salesforce Classic data sets:

Note the following about how Salesforce CRM Content is implemented in Salesforce Classic:

• Content record information is synchronized to the device; however, the files associated with the content records are not.This allows users to deliver content from the app even when a file is too large to be downloaded to a mobile device.

• Users can't search for a specific piece of content in the app. They can only share the content available on the Content tab,which is automatically synchronized to their device based on the filters in their assigned mobile configuration.

• Users can't view a list of their subscribed content in the app. They also can't filter the list of records on the Content tabbased on a particular library.

• While users can preview and share content from the app, they can't update the file associated with a content record. If theyhave the required permissions, they can edit the fields on the content detail page.

• Users must have a data connection to preview and deliver content. Without a data connection, they can only view thecontent detail page.

• Content in Salesforce Classic is only supported on BlackBerry and iPhone devices.

• Content is not available in the free version of Salesforce Classic.

• You can't block mobile permissions for the content object. Currently, the content object in Salesforce Classic is read-only.

• You can't edit the mobile page layout for the content object. The content detail page in the app is hard-coded to displayonly a few fields.

To set up Content for a Salesforce Classic configuration:

1. From Setup, click Mobile Administration > Salesforce Classic > Configurations, and then click the name of a mobileconfiguration.

2. In the Data Sets related list, click Edit.3. Click Add....4. In the popup window, select Content, then click OK.5. Use field filters to specify which content records are synchronized.

32

Setting Up Salesforce CRM Content for Salesforce ClassicSalesforce Classic Administration

Because users can't search for content in the Salesforce Classic app, it's essential to set up filters that make importantcontent available on the device. You can't create filters based on libraries or subscriptions, but here are a few options forsetting up useful filter conditions:

• Date: Filter on the Last Modified Date, Content Modified Date, or Created Date fields. Use special datevalues like LAST 90 DAYS or LAST 180 DAYS to ensure that recently updated content records are synchronized.

• Owner: Filter on the author if certain people in your organization are responsible for publishing content.• File Type: Filter on certain types of documents. For example, your opportunity team might generally be interested in

presentations or PDF documents.• Custom Fields: If you created custom content fields that help you categorize your content, filter on the custom fields.

For example, if you built a Functional Use field with picklist values, you could set up a filter condition whereFunctional Use equals Sales.

6. Optionally, prevent content records from consuming all the memory on a mobile device by selecting the second radiobutton under Set Max Record Limit and entering the maximum number of content records this configuration can transferto mobile devices. Use the Order By and Sort drop-down lists to specify which records are synchronized if the data sizelimit for your mobile configuration is exceeded.

7. Click Done.

Creating Links to Web and Visualforce Mobile Pages for SalesforceClassic


“Customize Application”To create or change custom buttons or links:

To improve the integration between the Salesforce Classic app, Visualforce Mobile, and external websites, you can optionallycreate links from native Salesforce records to Visualforce Mobile pages or external websites. To create the links, build textformula fields on a standard or custom object. The field must be visible on the page layout to appear in the Salesforce Classicapp. The best practice is to include all embedded links in a separate section labeled “Mobile Links” at the bottom of the pagelayout. There is currently no way to hide these links in Salesforce, but users can collapse the section to keep the links out ofthe way.

To create a link from a native record to a Visualforce Mobile page or Web page:

1. Create a custom field by navigating to the fields area of the appropriate object:

• For standard objects, from Setup, click Customize, then select the appropriate object from the Customize menu, andclick Fields.

• For custom objects, from Setup, click Create > Objects, and select one of the custom objects in the list.

2. Click New in the Custom Fields & Relationships section of the page.3. Select Formula, then click Next.4. Enter the field label.

The field name is automatically populated based on the field label you enter.

5. Select Text, then click Next.6. In the formula editor, create the link to the custom Visualforce page or external website:

33

Creating Links to Web and Visualforce Mobile Pages forSalesforce Classic


To create a Visualforce link, type "visualforce:///apex/PageName", and replace PageName with the nameof your Visualforce page. You can append parameters to the string, such as ?contactid=" & Id", in order to passinformation from the record in the client application to the Visualforce page.

•

• To create a Web link, type "weblink:", followed by the URL to which you want the link to point, such as"weblink:http://www.salesforce.com". You can append parameters to the string in order to pass informationfrom the record in the client application to the Web page. For example, the following Web link launches a socialnetworking site from a contact record and performs a search for the contact:

"weblink:http://m.linkedin.com/members?search_term=" &FirstName& "+" &LastName&"&filter=name&commit=Search"

Note: The client application passes the Visualforce or Web link with all parameters to the embedded browser.It is up to the website or Visualforce Mobile page to interpret any parameters. Be sure to construct yourVisualforce Mobile page to consume any parameters passed in the link.

7. Click Next.8. Set the field-level security to determine whether the field should be visible or read only for specific profiles, and click Next.9. Choose the page layouts that should display the field. In the next step, you will customize the layout to change the location

of the field on the page.10. Click Save.11. Edit the object's page layout:

• For standard object page layouts, from Setup, click Customize, select the object, and choose the Page Layouts link.Click Edit next to the name of the page layout you want to modify.

• For custom object page layouts, from Setup, click Create, select the object, and scroll to the Page Layouts section.Click Edit next to the name of the page layout you want to modify.

12. Drag a Section element from the palette to the page layout and drop it below the existing sections.13. In the Section Name field, type Mobile Links.14. Deselect the Edit Page option.15. Select the 1-column layout, then click OK.16. Drag the new text formula field from its current location into the new Mobile Links section.17. Click Save.

Notifying Users about Salesforce Classic Availability


“Edit HTML Templates”To create HTML email templates:

“Mass Email”

AND

“Manage Users”

To send mass emails to users:

When you're ready to deploy the Salesforce Classic app to your users, send them an email to notify them about the availabilityof the app and provide installation instructions. You can send the email using your corporate email application, like Outlook,or you can send mass email from Salesforce. Either way, include the URL that launches the download.

34

Notifying Users about Salesforce Classic AvailabilitySalesforce Classic Administration

• For Android and BlackBerry users, the download URL is mobile.salesforce.com. The link is the same for the initialdownload and for subsequent upgrades.

• If you manage BlackBerry devices with a BlackBerry Enterprise Server, you can use Application Push to remotely deliverSalesforce Classic to users. For more information about BlackBerry Enterprise Application Push, see the Salesforce ClassicImplementation Guide.

• You can obtain the iPhone download URL from iTunes. Open iTunes, click iTunes Store, then search for SalesforceClassic. Click the app icon to view details about the app. At the top of the iTunes window is a bread crumb path representingthe application's location in the App Store: App Store > Business > Salesforce Classic. Drag-and-drop the path into atext editor or word processing program to display the app’s download URL.

To send mass email to Salesforce Classic users from Salesforce:

1. Create an email template that informs users about the availability of Salesforce Classic by going to your personal settingsand selecting Email > My Templates. Optionally, you can also create a separate email template for upgrade notifications.Include the download link in the templates.

2. Create a custom view on the Mass Email page that shows your Salesforce Classic users only.

Note: The Mobile User checkbox on the user record assigns a mobile license to users, which enables use ofthe full version of Salesforce Classic. But other Salesforce users can access the free version of Salesforce Classicwithout an assigned mobile license, so you can’t filter for all Salesforce Classic users by license. Create a view forusers of the free versionby filtering by roles or profiles instead.

3. Send mass email to your Salesforce Classic users, using the custom view that you created. From Setup, click Manage Users> Mass Email Users.

Managing Salesforce Classic Configurations




You can manage your existing Salesforce Classic configurations from Mobile Administration > Salesforce Mobile >Configurations.

• To define a new mobile configuration, click New Mobile Configuration.

• To modify a mobile configuration—including assigning different users or profiles and changing the maximum size of datasets—click Edit.

• To activate a mobile configuration, click Edit, select the Active checkbox, then click Save. Deselect Active to deactivatethe mobile configuration.

• To delete a mobile configuration, click Del.• To view details about a mobile configuration, click its name.

From a mobile configuration detail page, you can:

◊ Modify data sets for a mobile configuration by clicking Edit in the Data Sets related list.

◊ Change the properties of mobilized objects by clicking Edit next to an object name in the Mobile Object Propertiesrelated list.

◊ Customize mobile configuration tabs by clicking Edit in the Mobile Tabs related list.

◊ Create custom views for a mobile configuration by clicking Edit in the Mobile Views related list.

35

Managing Salesforce Classic ConfigurationsSalesforce Classic Administration

http://na1.salesforce.com/help/doc/en/salesforce_mobile_implementation.pdf

http://na1.salesforce.com/help/doc/en/salesforce_mobile_implementation.pdf

◊ Clone the mobile configuration by clicking Clone.

Managing Salesforce Classic Tabs



“Manage Mobile Configurations”To manage Salesforce Classic tabs:

To manage the tabs for a Salesforce Classic configuration, click Mobile Administration > Salesforce Mobile > Configurations.Then click the name of the mobile configuration and scroll down to the Mobile Tabs related list.

If you’ve already customized the configuration’s tabs, the Mobile Tabs related list shows the selected tabs.

• To change the tab setup, click Edit.• To delete the mobile tab setup and use the default tab behavior instead, click Reset to Default.

If you haven’t customized the configuration’s tabs, the related list indicates that the default tab behavior is used for theconfiguration. To customize the tabs used by the configuration and define their order, click Customize Tabs.

Managing Salesforce Classic Devices



“Manage Mobile Configurations”To manage Salesforce Classic devices:

After a user installs the Salesforce Classic app on a mobile device and logs in for the first time, Salesforce collects informationabout the device and associates it with the user's record. The device information is read only.

While the device entry is created automatically, you can still view and manage all the mobile users and devices in yourorganization from Setup by clicking Mobile Administration > Salesforce Mobile > Users and Devices.

From the All Mobile Users and Devices page, you can:

• View the list of users in your organization who have been enabled to use Salesforce Classic.

• Create custom list views to see different subsets of your mobile users. For example, create a view that shows the users whohave never logged in to Salesforce from theSalesforce Classic app to evaluate the effectiveness of your organization'sSalesforce Classic deployment efforts.

• View details about a mobile device by clicking the device address.

• View details about a specific user by clicking the username.

• View details about a mobile configuration by clicking the mobile configuration name.

• Perform these actions on multiple users at the same time:

◊ Adjust the mobile session timeout value

◊ Erase the Salesforce data from a user's mobile device

◊ Delete a mobile device from a user's record

• Find out why a user's device isn’t synchronizing by hovering your mouse over the red error icon in the Status column.Additional information about the synchronization errors appears on the device's detail page.

36

Managing Salesforce Classic TabsSalesforce Classic Administration

Note: You can also manage mobile users from the Assigned Mobile Devices related list on the user detail page.

Viewing Salesforce Classic Device InformationPermanently Linking Salesforce Classic Users to a Mobile Device

You can prevent mobile users from registering any mobile device other than the one they used for their initial SalesforceClassic activation.

Setting Salesforce Classic Session Timeout ValuesErasing Data in Salesforce ClassicDeleting Mobile Devices

Viewing Salesforce Classic Device Information



“Manage Mobile Configurations”To manage Salesforce Classic devices:

Salesforce collects information about a mobile user's device the first time the user logs in to the Salesforce Classic app. Thereare two ways to access the device details:

• Click Mobile Administration > Salesforce Mobile > Users and Devices, and then click a device address in the list view.

• From Setup, click Manage Users > Users. Click Edit next to a user's name, and then click the device address in theAssigned Mobile Devices related list.

From the Mobile Device page, you can:

• Review device information

• Adjust the mobile session timeout value

• Erase the Salesforce data from a user's device

• Delete a device from a user's record

Below is a description of the fields in alphabetical order that are stored for each mobile device in your organization.

DescriptionField

The brand of the mobile device, if available.Brand

The name of the carrier providing service for the mobile device,if available.

Carrier

The date and time the device established a connection to themobile server. The device loses a connection when the battery

Connected Since

dies or when the session is closed because the server has notreceived data from the device for a long period of time.

The state of the device connection. Possible values for thisfield are Connected, Not Connected, and Not Available.

Connection Status

The name of the first user who registered the mobile deviceand the time and date the registration occurred.

Created By

37

Viewing Salesforce Classic Device InformationSalesforce Classic Administration

DescriptionField

The size of the Salesforce data currently stored on the user'smobile device. The mobile device periodically sends this

Data Size

information to Salesforce, which is helpful whentroubleshooting synchronization errors resulting from anexceeded data limit.

The unique identifier of the user's mobile device.Device Address

The model of the mobile device.Device Model

A flag indicating whether the device is a simulator or a mobiledevice. A simulator is a software application that emulates thebehavior of a mobile device.

Is Simulator?

The last time a full data set was downloaded to the mobiledevice. If a user's data set exceeds the limit defined in the

Last Activated

assigned mobile configuration, the device can be registeredbut not activated.

The last time data was received from the device. Thisinformation is helpful for troubleshooting connection issues.

Last Data Received

The last time a user registered the mobile device. Theregistration process creates the device record in Salesforce andassociates it with the user who registered it.

Last Registration

The last time the mobile device notified Salesforce that thedevice is no longer synchronizing data due to an error. The

Last Status Date

Last Status Date field is only visible when an error ispresent.

The manufacturer of the mobile device.Manufacturer

The size of the Salesforce metadata currently stored on theuser's mobile device. Metadata consists of page layout and

Metadata Size

schema information, and the amount of metadata sent to adevice can be very high depending on the size of yourorganization and the complexity of its setup.

The name of the last user who registered the mobile deviceand the time and date the registration occurred.

Modified By

The number of messages queued on the mobile server waitingto be sent to the device.

Number of Pending Outgoing Messages

The type of operating system installed on the mobile device:Android, BlackBerry, or iPhone.

Operating System

The version number of the operating system installed on themobile device.

Operating System Version

The phone number associated with the mobile device.Phone Number

The version number and build number of the mobile clientapplication installed on the device.

Salesforce Classic Version

38

Viewing Salesforce Classic Device InformationSalesforce Classic Administration

DescriptionField

The total data size of the messages queued on the devicewaiting to be sent to the mobile server. Because the server

Size of Pending Outgoing Messages (Bytes)

processes messages almost instantaneously, this value is usually0.

The total data size of the outbound message queue on themobile server.

Size of Outgoing Messages (Bytes)

Indicates whether any synchronization errors exist betweenthe device and Salesforce. The Status field is only visible

Status

when an error is present. The two error statuses are Data LimitExceeded and Unknown Error.

The Salesforce username of the user who is associated withthe mobile device.

Username

Note: If Salesforce detects the selected device was registered by a user in another organization, an error displays onthe device detail page. This can happen when a device was registered to a user in your sandbox organization and thenlater activated by a user in your production organization. To remove the old device record from your organization,simply delete the device.

Permanently Linking Salesforce Classic Users to a Mobile DeviceYou can prevent mobile users from registering any mobile device other than the one they used for their initial Salesforce Classicactivation.

Free version available in: All editions except Database.com

Full version available in: Performance, Unlimited, and Developer Editions, and for an additional cost in: Professional andEnterprise Editions


“View Setup and Configuration”To view Salesforce Classic settings:

“Manage Mobile Configurations”To change Salesforce Classic settings:

By default, Salesforce automatically associates a device record with the mobile user who most recently activated the device, soadministrators don’t need to update the device record to assign the device to another user. While this behavior makes it easyto switch devices between users in your organization, some administrators prefer that users are permanently linked to thedevices they were originally assigned. This helps administrators of organizations with highly sensitive data ensure that theirusers do not access corporate data from personal devices.

To permanently link a user to a mobile device:

1. From Setup, click Mobile Administration > Salesforce Mobile > Settings.2. Click Edit.3. Select Permanently Link User to Mobile Device.4. Click Save.

39

Permanently Linking Salesforce Classic Users to a MobileDevice


Warning: Enabling the Permanently Link User to Mobile Device setting requires administrative actionwhen users need to switch devices. You must manually delete the existing device from a user's record in order for theuser to register a different device. If you don’t delete the device, the user won’t be able to access the Salesforce Classicapp.

Setting Salesforce Classic Session Timeout Values


“Manage Mobile Configurations”To set Salesforce Classic session timeout values:

For security reasons, the Salesforce Classic app is set to lock out users after 10 minutes of inactivity. Administrators can adjustor disable this setting on a device-by-device basis. For example, you might disable the Salesforce Classic timeout setting if amobile device's operating system has its own locking mechanism.

To change the Salesforce Classic session timeout value:

1. Navigate to one of these pages:

• To deal with multiple devices at the same time, click Mobile Administration > Salesforce Mobile > Users and Devices.In the list view on the Mobile Users and Devices page, select the desired devices.

• To deal with a specific device, from Setup, click Manage Users > Users. Click a user's name, then click the deviceaddress in the Assigned Mobile Devices related list to see the Mobile Device page.

2. Click Set Mobile Session Timeout.3. Choose the new timeout value in minutes. You can also choose Never Expire if users shouldn’t be locked out of the app.4. Click Save.

Salesforce attempts to send a message containing the new session timeout setting to the selected mobile devices.

5. A confirmation page summarizes the results for each mobile device you selected.

Mobile Session Timeout ResultsAfter Salesforce sends the new session timeout session to the selected mobile devices, a results page provides information aboutthe status of each message. The table below describes the three possible outcomes:

DescriptionResult

The Salesforce Classic server has sent the message to thedevice. Salesforce can’t detect if the message was received bythe device.

Message successfully queued

A temporary communication problem between Salesforce andthe Salesforce Classic server prevented the message from beingsent. Try again later.

Unable to send message

The selected mobile user never registered a device, so thereforethe message could not be sent.

User has no mobile device

40

Setting Salesforce Classic Session Timeout ValuesSalesforce Classic Administration

Erasing Data in Salesforce Classic


“Manage Mobile Configurations”To delete the Salesforce data on a device running SalesforceClassic:

When a user accesses the Salesforce Classic app, the user’s mobile device contains both the mobile app and a set of the user'sSalesforce data. An administrator can remove the data from a device without uninstalling the mobile app. This is an effectivesecurity tool when a user misplaces his or her device. You also must erase a device's data if you plan to give it to another user.

To erase the Salesforce data on one or more mobile devices:




2. Click Erase Data, then click OK.

Salesforce attempts to send a message to the mobile devices to erase the data.

Erase Data ResultsAfter Salesforce sends the message to the mobile devices to erase data, a results page provides information about the status ofeach message. The table below describes the three possible outcomes:

DescriptionResult

The Salesforce Classic server has sent the message to thedevice. Salesforce can’t detect if the message was received bythe device.

Message successfully queued

A temporary communication problem between Salesforce andthe Salesforce Classic server prevented the message from beingsent. Try again later.

Unable to send message


User has no mobile device

Deleting Mobile Devices


“View Setup and Configuration”To view mobile devices and users:

“Manage Mobile Configurations”To delete mobile devices:

There are two instances when you would delete a mobile device from a user's record:

41

Erasing Data in Salesforce ClassicSalesforce Classic Administration

• Your organization's mobile settings permanently link mobile users to their devices, and you need to assign a device to adifferent user. If you did not enable this setting, Salesforce automatically associates a device record with the mobile userwho most recently activated the device, so it is unnecessary to delete a device to assign it to another user.

• You want to move a device from your sandbox organization to your production organization.

To delete a mobile device:




2. On the Mobile Devices and Users page, select one or more devices, then click Delete Device. On the Mobile Device page,click Delete.

3. Click OK.

Salesforce attempts to delete the selected device(s).

4. A confirmation page summarizes the results for each mobile device you selected.

Delete Device ResultsAfter Salesforce sends the message to the mobile server to delete the devices, a results page provides information about thestatus of each device. The table below describes the three possible outcomes:

DescriptionResult

Salesforce removed the device record from your organization.Device deleted.

A temporary communication problem between Salesforce andthe mobile server prevented the device from being deleted.Try again later.

Device cannot be deleted at this time. Please try again later.


User has no mobile device.

42

Deleting Mobile DevicesSalesforce Classic Administration

Chapter 4

Installing the Mobile Client Application

After planning and mobile administration are complete, you can deploySalesforce Classic to your users. The mobile client application is installed

In this chapter ...

• Installing Salesforce Classic andMobile Lite

over-the-air. Any user can complete the process by following the detailedinstallation messages on their mobile device. The time required for installation

• BlackBerry Enterprise ServerApplication Push

depends on several factors, including device characteristics, wireless signalstrength, and the amount of Salesforce data being delivered to the device.

• BlackBerry Self-hosted JAD Package Because of these varying factors, some time should be set aside to complete the• Mobile Device Simulators process. While the use of Salesforce Classic does not depend on wireless

coverage, the actual installation process requires a strong wireless signal.

For BlackBerry users, alternate Salesforce Classic installation methods areavailable. You can also install the mobile client using the BlackBerry DesktopManager or the BlackBerry Enterprise Server Application Push package.

43

Installing Salesforce Classic and Mobile LiteYou can install the Salesforce Classic and Mobile Lite applications on any supported iPhone or BlackBerry smartphone.

iPhone InstallationSalesforce Classic is available for download from Apple's App Store. To use the App Store, your iPhone or iPod touch mustbe connected to the network. You also need an iTunes™ Store account to download applications. If you don't already have aniTunes Store account, open iTunes on your computer and select Store > Account to set one up.

To install Salesforce Classic from the App Store:

1. From the Home screen of your iPhone or iPod touch, select the App Store icon.2. Tap Search.3. Tap within the Search field to open the keyboard. Type salesforce.4. Select Salesforce Classic in the list of search results to view information about the application.5. Tap Free, and then tap Install.

Note: There’s no charge to download the app from the App Store. Enterprise, Professional, Unlimited,Performance, and Developer Edition users with mobile licenses run the full version of Salesforce Classic. AnySalesforce user who doesn't have a mobile license can download a free, restricted version of Salesforce Classic.

6. Enter your iTunes Store account and password and tap OK.7. The first time you launch Salesforce Classic, you must activate the app for your device by logging in and downloading data.

Verify that your device is connected to a network.

a. Tap the Salesforce icon on the Home screen.b. Tap I Accept.c. On the activation screen, enter your Salesforce username and password.d. Tap Activate.

Warning: If the application closes or the device locks during the activation process, the iPhone operatingsystem pauses the download process but it will resume the next time you open the app.

BlackBerry InstallationSalesforce Classic is available for download from BlackBerry World. You need a BlackBerry World account to download appson your BlackBerry, but you can create an account from your device if you don't already have one. To install Salesforce Classicfrom BlackBerry World:

1. Select the BlackBerry World icon.

If you can’t find the icon on your device, you might need to download BlackBerry World. BlackBerry World can't run onall BlackBerry smartphones, so be sure to review Research in Motion's system requirements before trying to install BlackBerryWorld on your device.

2. Select the Search icon.3. Enter salesforce in the Search field.4. In the search results, select Salesforce Classic.5. Click Download.6. After the installation completes, select OK.7. When prompted whether to permit the app to access the phone, select Allow.8. When prompted whether to permit the app to access tp.mobile.salesforce.com, select Yes.9. Close BlackBerry World.

44

Installing Salesforce Classic and Mobile LiteInstalling the Mobile Client Application

http://www.apple.com/iphone/appstore

http://www.blackberry.com/appworld/download

10. Select the app icon, which resides on the home page of your device or in the Applications folder. On newer phones, theicon may be in the Downloads folder.

11. The first time you launch the Salesforce Classic app on your device, you must activate the app for your device by loggingin and downloading data. Verify that your device is connected to a network.

a. Read the license agreement and select I Accept.b. Enter your Salesforce username and password.

Because many passwords contain special characters that are difficult to enter on the device, the Show Passwordcheckbox is selected by default. To protect your password, you can deselect the option.

c. Select Activate.

After your username and password are confirmed by Salesforce, the data downloads. The initial data download maylast a few minutes. Future updates to the data occur automatically.

The BlackBerry World is the preferred place for downloading the Salesforce Classic app because users are automatically notifiedas upgrades become available. However, some BlackBerry administrators restrict users from downloading and using theBlackBerry World on their devices. BlackBerry users can install Salesforce Classic over-the-air directly from Salesforce.comif they are unable to access BlackBerry World.

1. Point your mobile browser to mobile.salesforce.com/bb.2. Highlight the Download the application link and select Get Link from the menu.3. Select Download. If prompted to replace an older version of the client application, select Yes.

Note: The minimum BlackBerry operating system requirement for the mobile application is 4.3. If you're runningversions 4.0–4.3 of the operating system, you can still download and install the mobile application; however, themobile server will detect the older operating system and send version 11.6 of the mobile application, which wasthe last release that supported operating system versions 4.0–4.3. You can't use any of the new features includedin the current release or future releases until you upgrade to the most recent BlackBerry operating system for yourphone.

4. Select Reboot to restart your device.5. When prompted to allow an HTTP connection, select the tp.mobile.salesforce.com checkbox. Scroll down and

select Allow this connection.6. Select the Salesforce Classic icon, which resides on the home page of your device or in the Applications folder. On newer

phones, the icon may be in the Downloads folder.7. Read the license agreement and select I Accept.8. Enter your Salesforce username and password.

Because many passwords contain special characters that are difficult to enter on the device, the Show Password checkboxis selected by default. To protect your password, you can deselect the option.

9. Select Activate.

After your username and password are confirmed by Salesforce, the data downloads. The initial data download may lasta few minutes. Future updates to the data automatically occur behind the scenes.

Activating a Sandbox Account in Salesforce ClassicBy default, the mobile client application connects to the transport for your production organization; however, you might wantto test your mobile configurations in your sandbox before deploying Salesforce Classic to your production organization. Inorder to activate a sandbox account from a mobile device, you must configure the mobile client application for the sandboxtransport. To activate a sandbox account:

• For BlackBerry devices, open Salesforce Classic and navigate to the System Info page. Select the Support Commandoption from the menu. Type lzsand, then press ENTER. Confirm that you want to erase the Salesforce data on thedevice. When prompted, enter the username and password for your sandbox account, then select Activate.

45

Installing Salesforce Classic and Mobile LiteInstalling the Mobile Client Application

To activate a production account after using a sandbox account, use the lzprod support command instead of lzsand.

• For iPhone and iTouch devices, tap Settings on the device's Home screen, then scroll down and tap Salesforce. TapTransport URL, then tap Sandbox. Tap the back arrow twice to exit the Settings page. Open Salesforce Classic. Enterthe username and password for your sandbox account, then tap Activate.

To activate a production account after using a sandbox account, follow the same steps, but select Production as theTransport URL.

BlackBerry Enterprise Server Application PushApplication Push is an administrator-initiated delivery technology on the BlackBerry Enterprise Server that installs applicationson BlackBerry smartphones remotely. This technology is not developed or supported by Salesforce, but BlackBerry EnterpriseServer administrators can use it to install Salesforce Classic on their BlackBerry users' mobile devices. Be sure to configure theBlackBerry Enterprise Server settings for Salesforce Classic before pushing the application to devices.

You can find detailed information about Application Push in the official BlackBerry Enterprise Server Administration Guidefrom Research in Motion. If you have any technical issues with Application Push, contact Research in Motion Support.

BlackBerry Self-hosted JAD PackageIf your BlackBerry administrator configured the BlackBerry Enterprise Server so that devices can only download applicationsfrom your internal network, your users cannot install Salesforce Classic over-the-air from the standard download URL. IfApplication Push is not a deployment option for your organization, you can self-host the Salesforce Classic binaries fordownload.

To self-host the files:

1. Navigate to the following URL: http://downloads.salesforce.com/downloads/mobile/index.html.2. Under BlackBerry, click JADpackage.3. Save the JADpackage.zip file.4. Move the .zip file to an executable directory under your web server's document root, then extract the files.5. Direct your users to download the client application by navigating to a URL hosted on your intranet.

Mobile Device SimulatorsWhether you're an administrator who wants to test a complex mobile configuration or a Force.com developer who wants totest a mobile application, it's a good idea to verify that Salesforce Classic works as expected before deploying to users. If youdon't have a device that meets the Salesforce Classic device requirements, you can run the mobile application on a BlackBerryor iPhone simulator.

A device simulator is a program you run on your computer that mimics the operating system, screen, keyboard, and navigationof a mobile device. You can use device simulators for testing, and they are also helpful tools for training and givingdemonstrations. You can run Salesforce Classic on the following device simulators:

• BlackBerry

• iPhone

Warning: Although you can run Salesforce Classic on BlackBerry and iPhone simulators, salesforce.com does notmanufacture or support the simulators. If you have installation problems or experience technical issues while using asimulator, contact the simulator's publisher.

• Contact Research in Motion for issues with the BlackBerry simulator.

46

BlackBerry Enterprise Server Application PushInstalling the Mobile Client Application


http://downloads.salesforce.com/downloads/mobile/index.html

http://na.blackberry.com/eng/

• Contact Apple for issues with the iPhone simulator.

BlackBerry SimulatorThe BlackBerry simulator is developed by Research in Motion (RIM), and you can download simulators for different BlackBerrymodels and operating system versions on the BlackBerry website. The BlackBerry simulators are only available for Windowsusers. Macintosh users must use a PC emulator in order to install and run a BlackBerry simulator.

Salesforce offers a BlackBerry simulator package that comes pre-installed with Salesforce Classic. To set up salesforce.com'sBlackBerry simulator package:

1. Navigate to the following URL: http://downloads.salesforce.com/downloads/mobile/index.html.2. Under BlackBerry, click Simulator Developer.3. Save the SalesforceBlackBerrySimulator_Developer.exe file.4. Double-click the EXE file to run the installation program.5. Click Start > Programs > salesforce.com > Salesforce Classic BlackBerry Sim for Developers > Launch BB Sim.6. In the simulator window, highlight the Salesforce Classic icon and click the trackball.7. Read the license agreement and click I Accept.8. Enter your Salesforce username and password.

Because many passwords contain special characters that are difficult to enter on the device, the Show Password checkboxis selected by default.

9. Open the menu and select Activate to verify your Salesforce account and activate the mobile application on the device.

After your username and password are confirmed by Salesforce, the data is downloaded, and the icon pulses to show activity.

10. Click OK when are prompted to create a passcode. You must use a passcode—which is different than your Salesforcepassword—to access the mobile application after it locks due to inactivity.

11. Enter your passcode, then click OK. The passcode can be between 5 and 32 characters. Do not include any spaces.12. Enter your passcode again for confirmation, then click OK.

iPhone SimulatorThe iPhone simulator application is published by Apple as part of the iPhone SDK, and the simulator is available only for themost recent release of the Macintosh operating system (10.5.x) running on Macintosh computers with Intel processors.Salesforce provides the simulator version of Salesforce Classic as an update to the standard iPhone simulator.

To set up the iPhone simulator:

1. Visit the Apple iPhone development page at http://developer.apple.com/iphone.2. Download the latest version of the iPhone SDK.

Note: You must be a registered iPhone developer to download the iPhone SDK. You can sign up for free at theApple iPhone development page.

3. Double-click the DMG file to launch the installer for the iPhone SDK.4. During the installation, make sure that the iPhone SDK checkbox is selected. If the checkbox is not selectable, you are

running an incompatible version of the Macintosh operating system. Use Software Update to get the latest update of theoperating system.

5. Verify that the installation was successful by running the iPhone simulator.

47

BlackBerry SimulatorInstalling the Mobile Client Application

http://www.apple.com

http://na.blackberry.com/eng/developers/resources/simulators.jsp


http://developer.apple.com/iphone

The path to the simulator application in Finder is MacintoshHD/Developer/Platforms/iPhonesSimulator.platform/Developer/Applications/iPhone Simulator.Drag-and-drop the simulator icon to the dock for fast access to the application.

6. Quit the simulator if it's running.7. Navigate to the following URL: http://downloads.salesforce.com/downloads/mobile/index.html.8. Under iPhone, click Simulator Updater.9. Save the SalesforceiPhoneSimulator.dmg file.10. Open the downloaded DMG file.11. Copy the Download Salesforce for iPhone Simulator application to your Applications folder.12. Double-click to launch the Download Salesforce for iPhone Simulator application from your Applications folder.13. Launch the iPhone simulator from your dock. You can also run it using the following path in Finder: Macintosh

HD/Developer/Platforms/iPhonesSimulator.platform/Developer/Applications/iPhone Simulator.14. Click the Salesforce icon on the Home screen.15. Click I Accept.16. On the activation screen, enter your Salesforce username and password. Click Done to close the keyboard.17. Click Activate.

Warning: Do not close the window or let the device lock. If the application closes, the iPhone operating systemstops the application from running, which causes the activation to fail.

18. When prompted, create your five-digit passcode. You must use a passcode—which is different than your Salesforcepassword—to access the mobile application after it locks due to inactivity.

19. Enter your passcode again for confirmation.

48

iPhone SimulatorInstalling the Mobile Client Application


Index

B

BlackBerrySalesforce Classic installation 44simulator 46

BlackBerry Enterprise ServerApplication Push 46requirements 8

BlackBerry Internet Service 3Business process review 9

C

Client application 4Content

setup for Salesforce Classic 32Creating

mobile configurations 15Salesforce Classic custom views 28

Custom Report Typesmobile 31

Custom views 4

D

Dashboardsmobile 29

Data setssamples in Salesforce Classic 22

Deletingmobile devices 41

Deploying Salesforce Classic 7Devices

deleting 41model and memory information 8synchronizing with Salesforce 4

E

EmailSalesforce Classic deployment 34

I

Installing Salesforce Classic 43iPhone

Salesforce Classic installation 44simulator 46

J

JAD package 46

L

LinksVisualforce Mobile 33

Localization 5

M

Mass mailSalesforce Classic deployment 34

Mobileusage data reports 31

Mobile Data Service 3Mobile deployment 7Mobile usage data reports 31

O

Objects 4

P

Page layoutsSalesforce Classic 24

PermissionsSalesforce Classic 24

R

Record types 4Reports

Salesforce Classic 30Resources 10

S

Salesforce Classicabout 1administration 11BlackBerry Application Server Application Push 46changing timeout values 40client application 4creating mobile configurations 15custom report types 31dashboards 29data sets 19default mobile configuration 14disable access 14DNS name 8emailing users 34enable users 14enabling Content 32environment 2erasing data 41

49

Index

Salesforce Classic (continued)global variables 22installing 43merge fields 22mobile configurations 35mobile devices 36object properties 24planning deployments 7reports 30sample data sets 22settings 39supported devices 2tabs 36testing mobile configurations 17tips 12users 36viewing device detail 37

Self-hosted installation 46Simulators 46

Synchronizing 4

T

Tabsmobile 36Salesforce Classic 24

U

User permissions 4Users

Salesforce Classic 36

V

Visualforcecreating tabs for Salesforce Classic 26

Visualforce Mobilelinks 33

50

Index