Propagating application model changes to offline-enabled mobile apps
When you modify rules in an existing application that users access with an offline-enabled mobile app, propagate the changes to mobile devices by forcing full synchronization for the access group to which the mobile users belong.For example, you can modify the flow of your expense reporting application by adding a subprocess for creating a new expense category and make the new flow available to users by propagating the change to their mobile devices.
When you modify the rules in the application, the changes are propagated to the mobile devices when full synchronization takes place.
In the navigation pane of Dev Studio, click Records.
Expand the Security category and then click Access Group.
Double-click the access group that you want to modify.
Click the Advanced tab.
In the Offline configuration section, click Force full sync for all users.
In the Force full sync for all users window, confirm the synchronization by clicking Submit.
- Offline case packaging optimization during synchronization
When you design an application that users can access with an offline-enabled mobile app on a mobile device, you can improve the performance of an offline-enabled mobile app when the application contains a large number of case types. You do this by optimizing offline case packaging during synchronization.
- Understanding offline data synchronization
When an offline-enabled mobile app is not connected to a network, an action queue stores local user actions. When network connectivity is restored, the contents of the action queue are pushed to the server, and Pega Platform processes them. At the same time, all modified data pages and work objects are synchronized to the mobile device.