Enabling access group data prepackaging during build

Help users begin their work without unnecessary delays by building offline-enabled mobile apps that start faster when users launch them for the first time. You do this by packaging the access group data within the executable files that you then distribute among the users.

In the prepackaging of the access group data for an offline-enabled app, common rules that apply to the access group are packaged when you build the mobile app executable files on the mobile channel configuration page. As a result, when the user starts the mobile app for the first time, the initial data synchronization is faster because only the data that differs between the package and the current server state is synchronized.

The data that is prepackaged comes from the access group cache which stores rules and static data that is used in offline-enabled apps. Node scope data pages that you specifically include in the access group cache settings are prepackaged into the executable files in addition to common rules, while node scope data pages that you specifically exclude in the access group cache are excluded from the prepackaging.

Note: Access group data prepackaging is supported in offline-enabled mobile apps that are based on Pega Infinity Mobile Client.

Before you begin: Ensure that you prepare your mobile app for the prepackaging of access group data:

Enable offline support for the application. For more information, see Configuring offline support for a mobile app.
Enable the caching of common rules in the access group settings. For more information, see Defining advanced offline configuration for an access group.
For generating the executable files, ensure that the corresponding access group is selected in the Application Access section on the Profile tab of your operator rule form. For more information, see Defining operator contact information and application access.

In the Offline support section of a mobile channel interface, select the Enable offline support check box.
Select the Incorporate access group data in the mobile app for faster initial login.
In the Select access group field, press the Down arrow key, and then select the access group for which you want to package the cache data into the mobile app executable files.
Click Save.

Result: When you build the mobile app, the common rules that apply to the access group are packaged into the mobile app executable files that you generate on the mobile channel configuration page.