Offline-enabled mobile apps and Pega Mobile Client

Consider the following information when building an offline-enabled mobile app with Pega Mobile Client:

• You must enable offline support in the mobile channel interface, access groups, and case types that are required to run in the app when not connected to the network.
• The cache manifest is no longer used to identify static resources that require updating for offline caching. You must force full sync operation to push changes to a mobile device in situations when files listed in the cache manifest are modified.
• The native tab bar is not supported in Android and iOS mobile apps. You must disable the native bottom menu. You can only reuse a Pega Platform web portal, such as Case Manager, on the Layout tab when configuring a mobile channel interface.
• Logging in to an offline-enabled mobile app as a different user is only possible online.
  • When you log off while your work was not fully synchronized with the server, the work is lost after another user logs in.
  • To avoid losing data, do not log off from the mobile app until your work is fully synchronized with the server.
• You can take advantage of the more versatile window.pms.plugins.clientstore JavaScript API that is based on promises and events instead of callbacks and listeners.
  • The API replaces the window.launchbox.PRPC.ClientStore JavaScript API.
  • The original API is available but is considered deprecated.
  • The batchExecute() method in the deprecated JavaScript API is no longer executed in a single database transaction. You must use the writeItems(), getItems(), and deleteItem() methods in the new JavaScript API, instead.