Mobile Device Management with the Life Sciences Cloud Mobile App
The Life Sciences Cloud mobile app supports Mobile Device Management (MDM) through the
Salesforce Mobile SDK's managed app configuration. When you manage the app with MDM, field users
don't download or update the app from the public Apple App Store. Instead, you control whether
field users get the app and its updates from your enterprise app store or whether the MDM
provider delivers updates directly to their devices.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Life
Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the
Life Sciences Customer Engagement managed package.
Important Test your MDM configuration with a small group of field users before you
roll it out to your full organization.
MDM Setup with the Salesforce Mobile SDK
The Life Sciences Cloud mobile app is built on the Salesforce Mobile SDK, so it supports
the same MDM framework as other Salesforce mobile apps. To set up MDM for your org,
including certificate-based authentication and automatic custom host provisioning, see Mobile Device Management (MDM).
App Updates with MDM
After your MDM setup is in place, your MDM provider pushes a managed app configuration to
the Life Sciences Cloud mobile app on each managed iPad. The Life Sciences Cloud mobile app
reads specific keys from that configuration to control how field users get app updates.
If you set an enterprise app store URL, the app redirects field users to your enterprise
app store to get the update. If you don't set an enterprise app store URL, your MDM provider
delivers app updates directly to your users' devices.
By default, the Life Sciences Cloud mobile app directs field users to the Apple App Store
to get app updates. On devices managed with MDM, access to the public App Store is often
restricted, so this redirect can fail.
Managed App Configuration Keys
To manage app updates for the Life Sciences Cloud mobile app through your MDM
configuration, set up key-value pair assignments through your MDM provider. These keys are
supported.
Key
Type
Required
Description
AFLS_MDMEnabled
Boolean
Required
If true, MDM manages the app, including app updates.
AFLS_MDMAppStoreURL
String
Optional
The URL of your enterprise app store. When set, the app redirects field users
to this location to get app updates.
Sample Managed App Configuration
One method of setting key-value pair assignments is through an XML property list, or plist.
The plist contains the key-value pair assignments that an MDM provider sends to the mobile
app to enforce update configurations.
This sample plist turns on MDM handling and sets an enterprise app store URL.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.