Pega Platform automatically packages the components that you reference in the application model for use in offline mode. You can use your offline configuration template to ensure that any components that are not automatically packaged are available for use in your offline-enabled app.
The usage of some components in offline mode is limited. For more information about the implementation of specific components in offline-enabled apps, see Understanding offline features.
- In the header of Dev Studio, click .
- On the Offline configuration tab, in the Configuration template section, click the template that you want to use with your offline-enabled app.
- On the Allow list tab, select the component category that you want to add to the allow list.
- If you select the Field values category, in the
Field values section on the right side of the form,
determine how you want to add field values to the allow list:
Choices Actions Add a field value with the base class
- Click Add field values.
- Populate the autocomplete field with the field values that you want to enable for offline use, and then click Add.
Add a field value with multiple run-time classes
For more information about classes, see Understanding class hierarchy and inheritance.
- Click Add field values with multiple run-time class.
- In the Field value field, enter the field value that you want to add.
- In the Run-time classes field, enter the classes for which you want to add the field value.
- Click Add.
- In the section on the right side of the form, populate the autocomplete field with the components that you want to enable for offline use, and then click Add.
- On the offline configuration template form, click Save.
- Excluding data pages from packaging in offline-enabled mobile apps
Improve the performance of your offline-enabled mobile app by excluding data pages from the app installation package. For example, exclude a resource-heavy data page from packaging when you plan to replace the data page with a large data page that is optimized for offline mode.
- Excluding data pages from delta synchronization in offline-enabled mobile apps
Optimize data exchange and save time when your offline-enabled mobile app synchronizes with the server, by excluding data pages from the delta synchronization process. For example, you can exclude a large data page with a list of countries that does not change often and therefore does not have to be packaged during delta synchronization.
- Making custom resources available in offline mode
Ensure that your mobile app displays custom resources and continues the process flow in offline mode by including the resources in the app installation package. For example, you can add offline support for a custom font that matches your company's branding guidelines.
- Routing case status conflicts in offline mode
Provide an uninterrupted experience for the users of your offline-enabled mobile app by routing possible case status conflicts to designated work queues. By adopting this functionality, users continue to use the app while a designated person (for example, a system administrator) can address the conflicts to ensure that no data is lost.