A managed configuration allows users to apply additional settings to supported iOS and iPadOS applications. In addition, users can apply dynamic placeholders, also known as custom attributes or key value pairs, to expose specific device information. For example, these configurations can be used to identify devices out in the field with their console counterparts and to link devices with certain locations via their aliases or other unique identifiers.
Work with your app developer to surface dynamic placeholder values in the app experience.
Dynamic placeholders are also available for Android applications.
Supported Dynamic Placeholders
The following dynamic placeholders are supported on iOS and iPadOS devices. You may need to discuss with your app developer about the values supported by your application. Values do not update automatically. If a value is updated, a new converge or install command will need to be fired.
| Placeholder | Description | Example Value |
|---|---|---|
${esper.id} |
Esper device identifier | 555e8400-e29b-41d4-a716-446655440000 |
${esper.tenantId} |
Tenant identifier | 123e4567-e89b-12d3-a456-426614174000 |
${esper.groupId} |
Group ID of the group the device belongs to | 7c9e6679-7425-40de-944b-e07fc1f90ae7 |
${esper.blueprintId} |
ID of the blueprint assigned to the device | 9b2d4f1a-3c58-4e7b-a1d6-5f0e8c2b7a34 |
${esper.name} |
Esper Device name | iPad-Office-001 |
${esper.alias} |
Device alias | Reception-iPad |
${esper.serialNumber} |
Device serial number | DMQVGC0DHHL0 |
${esper.udid} |
Unique Device Identifier | 00008020-001C2D8E2E20002E |
${esper.model} |
Device Model | iPhone 13 |
${esper.osVersion} |
Device Current OS Version | 26.0 |
The ${esper.groupId} and ${esper.blueprintId} placeholders resolve to the device's group ID and assigned blueprint ID when a command installs the app or applies the configuration to an app already on the device.
Example Usage
The input configuration is a Property List (Plist) of keys and values wrapped in a dictionary tag.
Example Input
<dict>
<key>DEVICE_SERIAL</key>
<string>${esper.serialNumber}</string>
<key>DEVICE_NAME</key>
<string>${esper.name}</string>
<key>TENANT_ID</key>
<string>${esper.tenantId}</string>
</dict>Example Output
<dict> <key>DEVICE_SERIAL</key> <string>DMQVGC0DHHL0</string> <key>DEVICE_NAME</key> <string>iPad-Office-001</string> <key>TENANT_ID</key> <string>123e4567-e89b-12d3-a456-426614174000</string> </dict>
Applying a Managed Configuration
- In a blueprint, go to the Apps & Configuration section and click on the iOS/iPadOS tab.
- In Manage Applications, add a new application or identify an existing one that supports managed configurations. Then click on the ellipsis button next to the application and select Managed Configuration.
- Then paste the configuration in the input box.
- Click on Apply Changes.
- Then save and publish the blueprint.
When you converge a device to that blueprint, the managed configuration will be applied to the application currently on the device or will be installed with the application.
Remember to converge the device to update these values. Use dynamic placeholders with managed configurations to unlock further customization for your iOS fleet.
Learn more about iOS Managed Configurations.