Table of Contents

Best practices for upgrading offline-enabled mobile apps


Only available versions of this content are shown in the dropdown

Upgrading to the latest Pega Platform versions provides unique advantages in mobile app development. By following the best practices for upgrading offline-enabled apps, you ensure that your apps work correctly and benefit from low-code prescriptive authoring and modern native features.

General guidelines

  • Follow all recommended UI and mobile app guidelines. For more information, see Designing applications for mobile use and Designing applications for offline mode.
  • Upgrade legacy mobile channels that reuse web portals to Pega Mobile Client-based channels. For more information, see Upgrading mobile channels that reuse web portals.
  • Avoid any JavaScript customizations; instead, build and configure your app in the mobile authoring model.
  • Move your legacy access group and case type configuration to the mobile channel, which offers prescriptive and low-code authoring.
  • Move your offline-specific configuration of explicitly supported or excluded components and resources to offline configuration templates. For more information, see Creating offline configuration templates.
  • Use Pega Cosmos design system as a production design system. If not available, then use the latest available version of the UI Kit instead. For more information, see Styling your application with design systems.
  • Switch from using window.launchbox.* APIs to corresponding window.pms.* APIs.

Migration guidelines

  • If you migrate your application from earlier Pega Platform versions, ensure that the data page that you use as a source for a mobile list page contains the pzInsKey property.

    For more information about configuring mobile list pages, see Authoring mobile list pages.

Did you find this content helpful?

Have a question? Get answers now.

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