Mobile properties
Mobile properties enable admins to turn on or turn off features in ServiceNow apps without upgrading the ServiceNow instance.
The ServiceNow Platform server controls the features that are available on your mobile app. The server instance is released with new features for every family release. New versions of the mobile apps are released to the Apple Store and the Google Play Store every month. These monthly releases of mobile apps usually contain bug fixes but can also contain new features. These new features can be turned on or off with mobile properties.
Mobile properties can be configured to set flags on your ServiceNow instance. These "flags" are records structured as key/value pairs in the sys_sg_properties table. They can turn on or turn off features on your mobile client apps. The ServiceNow instance sends the mobile property to mobile client apps after authentication.
Mobile properties are available starting with the San Diego release.
Application scope and mobile properties
When you create a mobile property, you select the application scope for which the property is
available in the Mobile Properties New record form. To change the list of available application
scopes, select the globe icon (
) on the instance banner and then select Application
scope:application_scope.
Application scope precedence
When multiple mobile properties of the same name are defined for multiple application scopes, the system applies precedence rules to select a mobile property to use. The following scenarios use the clientRefresh mobile property as an example to show how the precedence rules work.
- Scenario 1: Global application scope always takes precedence
- If a mobile property is defined for multiple application scopes and one of those is the
global application scope, then the property defined for global application scope always takes
precedence. In this case, the following actions occur:
- The system calls for the clientRefresh property on an instance.
- The system finds three clientRefresh properties defined for this
instance:
Property name Application scope Updated (date and time) clientRefresh Global 2021-12-06 10:41:00 clientRefresh Now Mobile 2021-12-06 10:38:41 clientRefresh Agent Workspace 2021-12-06 10:42:06 - The system chooses the clientRefresh property defined for the global application scope.
In scenario 1, the clientRefresh property defined for the global application scope takes precedence.
- Scenario 2: If the mobile property isn't defined for global application scope, then the most recently updated property takes precedence
- If a mobile property is defined for multiple application scopes but if there is no property
with global application scope, then the system uses the most recently updated property. In
this case, the following actions occur:
- The system calls for the clientRefresh property on an instance.
- The system finds three clientRefresh properties defined for this
instance:
Property name Application scope Updated (date and time) clientRefresh Now Mobile 2021-12-06 10:38:41 clientRefresh Asset Management for mobile 2021-12-06 10:42:06 clientRefresh Agent Workspace 2021-12-06 12:06:20 - The system chooses the clientRefresh property that was most recently updated.
In scenario 2, the clientRefresh property defined for the agent workspace application scope was the most recently updated. All three mobile properties were updated on 2021-12-06. The property defined for the agent workspace application scope was updated at 12:06:20. That time is almost one and a half hours after the other two. The system chooses the clientRefresh property defined for the agent workspace application scope because it's the most recently updated clientRefresh property.