22.10 Specifying App Configuration Parameters

As a part of the setup process, many apps require users to specify their email addresses, the port and other configuration settings. The app configuration parameters feature helps in providing the configuration information for apps that support this feature. ZENworks lets you pre-configure this information that become effective as soon as the app is installed on the device. The users are not required to specify these values manually. For each app, the configuration parameters are published in the specific app documentation.

This feature is applicable for the following bundles:

  • App Store App

  • iOS/iPadOS Enterprise

  • VPP Apps

  • Android Bundle

ZENworks also supports app configuration of Micro Focus’ in-house apps, such as Micro Focus Filr, Novell Messenger, and Micro Focus iPrint. For each of these apps, you can obtain their configuration parameters by clicking the following links:

22.10.1 Procedure

To navigate to the App Configuration Parameters page, select Bundles, select a bundle and click the Details tab. Alternatively, for Android apps, you can visit Mobile Management > > Apps Catalog and identify the app against which the icon is displayed. This icon indicates that either app permissions or managed configuration parameters require your attention. You can then click the bundle count appearing beside this app and select the bundle against which the icon is displayed and navigate to the Details tab.

Pre-configuring iOS Apps

You can pre-configure App Store apps, VPP apps or Enterprise apps by selecting either one of the following options:

  • Key-value pairs: Click Add and specify the Key and its corresponding Value. You can specify the value as a string, integer, or as a boolean value. You can also specify built-in variables or custom variables as the Value. The following built-in system variables can be used:

    • ${LoginName}: Retrieves the user login name in the configured user source.

    • ${Email}: Retrieves the first email address associated with the user from the user source.

    • ${ActiveSyncLogonName}: Retrieves the ActiveSync logon attribute from the user source. This attribute is used to authenticate to the ActiveSync Server, while configuring an email account on the device.

    To specify custom variables, you first need to define these variables by navigating to Configuration > Device Management > System Variables. For more information, see Using System Variables.

  • Configuration File: Click Upload to browse and import a configuration file that contains the configuration information of the app. You can also directly specify the file parameters or edit the parameters of the uploaded file in the displayed text box. The configuration file can be obtained from the app vendor.

    You need to ensure that a valid configuration file is imported. A sample format of the configuration file is provided below:

    Built-in or custom variables can also be added as string values within this configuration file. For example:

    <key>com.ibm.mobile.connections.user</key>

    <string>${LoginName}</string>

    The application configuration will be pushed to the device when the application is distributed.

Pre-configuring Android Apps

Select a parameter and click Edit. The following are displayed in the Edit App Configuration Parameter dialog box.

  • A Title and a Key are displayed.

  • The Type of value that needs to be specified is displayed. The supported value types include boolean, string, integer with a value from MIN_VALUE (-2147483648) to MAX_VALUE (2147483647), choice, multi-select list and bundle array. For the bundle array type, to edit a parameter within a bundle, you need to click the bundle array appearing in the App Configuration Parameters section and drill-down to its parameters. You can also click Add to configure multiple bundles within a bundle array that will include the same parameters as the existing bundle.

    NOTE:The Bundles and bundle arrays feature used within Managed App Configurations is specific to Google and are not related to the Bundles feature in ZENworks. Also, this feature is only supported on Android M (6.0) and later versions. On versions older than Android 6.0, these properties are silently dropped on the devices.

    Also, if the configuration parameters of an app is not in accordance with Google’s guidelines, then these parameters will not be displayed by ZENworks. For more information, see Table 1: Restriction entry types and usage.

  • A short description of the parameter is displayed as provided by the app developer.

  • Specify the corresponding value for the key. You can also specify custom or built-in system variables such as:

    • ${LoginName}: Retrieves the user login name in the configured user source.

    • ${Email}: Retrieves the first email address associated with the user from the user source.

    • ${ActiveSyncLogonName}: Retrieves the ActiveSync logon attribute from the user source. This attribute is used to authenticate to the ActiveSync Server while configuring an email account on the device.

      NOTE:If an incorrect built-in or custom variable is specified, then the bundle will not deploy to the device.

You can also restore the default values set by the app developers for any of the parameters. To do this, select a parameter and click Default on the top panel. The app configuration will be pushed to the device when the app is distributed.