10,730
edits
Important: Deprecating old WebView — Publish failed error
Mobile device management: Difference between revisions
Jump to navigation
Jump to search
→App-specific configuration support
| Line 126: | Line 126: | ||
App-specific configuration can be used to pre-initialize newly deployed apps with user- or organization-specific detail (e.g., organization URL or user name). | App-specific configuration can be used to pre-initialize newly deployed apps with user- or organization-specific detail (e.g., organization URL or user name). | ||
Mobile CRM app (and custom apps as well) supports app-specific configuration on iOS inherently as it’s incorporated in the iOS API. Some MDM providers (such as MS Intune) support | Mobile CRM app (and custom apps as well) supports app-specific configuration on iOS inherently as it’s incorporated in the iOS API. Some MDM providers (such as MS Intune) support native Apple ''plist'' dictionary file format of configuration (Intune section App-specific config for managed iOS devices). This is a sample content of the plist file with all key-value pairs supported by the Resco Mobile CRM app: | ||
<syntaxhighlight lang="xml"> | <syntaxhighlight lang="xml"> | ||
| Line 167: | Line 167: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
App-specific configuration on Android is limited to custom apps with MDM-specific support (having MS Intune MAM SDK included). Such apps consume app-specific configuration in the form of key-value pairs from the following list: | App-specific configuration for managed apps on Android is limited to custom apps with MDM-specific support (having MS Intune MAM SDK included). Such apps consume app-specific configuration in the form of key-value pairs from the following list: | ||
<syntaxhighlight lang="text"> | <syntaxhighlight lang="text"> | ||