Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring action queue management in offline mode

Updated on March 3, 2022

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 database.

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.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the SysAdmin category, and then click Dynamic System Settings.
  3. On the Dynamic System Settings tab, in the Setting Purpose column, click storage/class/actionqueue:/type.
    Tip: Click the filter icon to search for the storage/class/actionqueue:/type dynamic system setting.
  4. 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 datastore.
    • To buffer the action queue in the server memory until the server receives all actions, leave the field blank.
  5. In the upper-right corner of the rule form, click Save.
  • Previous topic Configuring external temporary storage options for attachments in offline mode
  • Next topic Adjusting the usability of offline-enabled mobile apps

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us