Defining advanced offline configuration for an access group

Mobile app users can work on assignments and access case data while the device is disconnected from the network. After you enable offline support for an access group, you can define settings that are related to troubleshooting, data synchronization, OSCO (online as a special case of offline) breakout support, data caching, and reporting of the initial download size for users and other requestors who belong to the access group.

Before you begin: Complete one of the following tasks before defining an offline configuration for an access group:
  • Create an access group as described in Creating an access group.
  • Open an existing access group instance from the navigation panel by clicking Records > Security > Access Group and selecting an instance.
  1. Enable offline support for an access group. For more information, see Enabling offline support for access groups.
  2. Optional: To enable offline troubleshooting with a browser, select Enable offline troubleshooting with a browser.
    For more information, see the Pega Community Troubleshooting offline-enabled applications with the Tracer tool in a browser article.
  3. Optional: To force full data synchronization for all users of the offline-enabled application the next time that they synchronize with the server, click Force full sync for all users.
    If synchronization has already been done at least once, the date and time stamp of when the last full data sync operation occurred is displayed below this button.
  4. Select one of the following options:
    • To allow the offline-enabled application to process online cases and use the OSCO breakout capability, select Access group requires a connection for portions of the application.
    • To improve the performance of the offline-enabled application by reducing server load, clear this check box, and also select the Use service session cookie (REST/HTTP only) check box for the offlinehttp service package rule.
    For more information, see About Service Package data instances.
  5. Optional: To enable caching of common rules, click Enable caching.
    This option ensures a faster start of offline-enabled applications from the time of the last Pega Platform server start.
    Note:
    • If a rule for an access group is based on an operator record or other data that varies between users within that access group, caching should be disabled.
    • To clear the cache, click Force full sync for all users.

    If you select Enable caching, you can also select one of the following to control caching of node-scope data pages:

    • Select Additionally cache node scope data pages listed below and specify the names of node scope data pages to cache in addition to common rules.
    • Select Additionally cache all node scope data pages except for those listed below and specify the names of node scope data pages that should not be cached
  6. Optional: To enable reporting of the initial download size, click Disclose application size when users log in for the first time.
    This option allows you to build offline-enabled mobile apps that display a dialog box before they perform the initial data synchronization. The dialog box states the size of data that must be downloaded and prompts for confirmation. If the user chooses not to download data, the application closes.
    • If you selected this option, you can also manually enter a value in the Application size adjustment field.

      The value modifies the number that is presented to the user. It can, for example, represent the total size of cache manifest resources that need to be downloaded before the Pega Mobile Client-based mobile app starts.