Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

Mobile Device Management (MDM)

  • Last UpdatedJul 27, 2026
  • 2 minute read

You can configure settings in the AVEVA Work Tasks Pro app using Mobile Device Management applications, such as AirWatch and SOTI.

Note: MDM configurations are supported for the AVEVA Work Tasks Pro app on iOS and Android platforms, but are not supported on the AVEVA Work Tasks Pro Windows app.

In the MDM application, configure the settings as key-value pairs. The keys are fixed, but the values can be customized based on your requirements.

Before installing the AVEVA Work Tasks Pro app, configure the required keys in the MDM application.

Configuration screen

  • ServerPath: Specify the server path.

  • Repository: Specify the Repository name.

  • Provider: Specify the Providers.

    Note: When configuring AIM or AAD providers, specify the ServerPath key-value pair.

    Use the following instance name values for the respective providers:

    Provider

    Instance name

    Repository User Provider

    skeltalist

    Active Directory

    activedirectory

    Forms

    sqlprovider

    ASP.NET Membership

    membershipprovider

  • UserName: Enter the user name of the Repository.

Settings screen

  • ShowInboxInGroups: Enable or disable to show work items in groups

  • SyncAllWorkItems: Enable to sync all the work items in the Inbox

  • WorkItemsToSync: Specify the number of work items (50 to 1000) to be synced in the Inbox

  • ItemsToSyncForLookupAndDataGrid: Specify the number of lookups to be fetched

  • BatteryThresholdValueForSync: Specify minimum device battery level for Sync

  • MemoryThresholdValueForSync: Specify minimum device memory for Sync

  • SaveAsDraft: Enable or disable the Draft option

  • SentItems: Enable or disable the SentItems option

  • OfflineSupport: Enable to submit the items in the offline mode

Fill Form label

  • FillFormLabel: Specify the label for the Fill Form.

When you install the AVEVA Work Tasks Pro app for the first time, the configured values are automatically available in the application..

Note: These configurations can be applied only to the Managed Profile of the device.

To configure the keys in iOS, you need to upload the XML having the key configurations.

For example, you need to import the XML file with the script given below:

<managedAppConfiguration>

<VersionNumber>1</version>

<bundleId>com.vmware.gss.AirWatchAppConfigSample</bundleId>

<dict>

<string keyName="ServerPath">

<defaultValue>

<value>http:// or https://</value>

</defaultValue>

</string>

<string keyName="Repository">

<defaultValue>

<value>Repository</value>

</defaultValue>

</string>

<string keyName="Provider">

<defaultValue>

<value>Provider</value>

</defaultValue>

</string>

<string keyName="UserName">

<defaultValue>

<value>UserName</value>

</defaultValue>

</string>

<boolean keyName="ShowInboxInGroups">

<defaultValue>

<value>false</value>

</defaultValue>

</boolean>

<boolean keyName="SaveAsDraft">

<defaultValue>

<value>false</value>

</defaultValue>

</boolean>

<boolean keyName="SentItems">

<defaultValue>

<value>true</value>

</defaultValue>

</boolean>

<integer keyName="BatteryThresholdValueForSync">

<defaultValue>

<value>20</value>

</defaultValue>

</integer>

<integer keyName="MemoryThresholdValueForSync">

<defaultValue>

<value>100</value>

</defaultValue>

</integer>

<integer keyName="ItemsToSyncForLookupAndDataGrid">

<defaultValue>

<value>2000</value>

</defaultValue>

</integer>

<boolean keyName="SyncAllWorkItems">

<defaultValue>

<value>false</value>

</defaultValue>

</boolean>

<integer keyName="WorkItemsToSync">

<defaultValue>

<value>50</value>

</defaultValue>

</integer>

<boolean keyName="OfflineSupport">

<defaultValue>

<value>true</value>

</defaultValue>

</boolean>

<string keyName="FillFormLabel">

<defaultValue>

<value>Custom Label for Fill Form</value>

</defaultValue>

</string>

</dict>

</managedAppConfiguration>