Adjust the synchronization process to your business case by specifying how
Pega Platform handles action queues from the client before
performing the actions on the current application data in the server
When in offline mode, the mobile app saves all user actions in an action queue. After
regaining network connectivity, the app sends the action queue to the server. By
default, Pega Platform buffers the action queue in chunks, and then
saves the chunks in the server memory. When the server receives all actions, Pega Platform performs the actions on the data in the server database.
Alternatively, you can configure Pega Platform to omit the buffering
and saving stages and send the actions directly into the database.
The default configuration occupies server memory and adds time to the synchronization
process, but ensures backward compatibility. By configuring Pega Platform to send the actions directly into the database, you
accelerate the synchronization process, but you might also experience synchronization
issues if the number of connections to the database exceeds the application server
limit.Note: Sending actions directly into the database is not available for on-premises
installations with a PostgreSQL database.
- In the navigation pane of Dev Studio,
- Expand the SysAdmin category, and then
click Dynamic System Settings.
- On the Dynamic System Settings tab, in the
Setting Purpose column, click
Tip: Click the filter icon to search for the
storage/class/actionqueue:/type dynamic system
- On the Dynamic System Settings: Action queueing
configuration tab, in the Value field,
perform one of the following actions:
- To stream the actions from the client directly into the default Pega Platform database, enter
- To buffer the action queue in the server memory until the server
receives all actions, leave the field blank.
- In the upper-right corner of the rule form, click