Published Release Notes

The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application

In a Pega^® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.

For more information, see Offline mobility guidelines.

Custom mobile app assets file validation at upload

When you build a custom mobile app, and upload branding assets or custom modules within a compressed file, Pega^® Platform validates the file that you upload and displays confirmation and warning messages. For more information, see Uploading branding assets and custom modules.

New appearance of smart app banners

When you build a custom mobile app, you can use smart app banners to advertise your app. The look of these smart app banners has been modernized. Also, if you upload branding assets to customize the appearance of your custom mobile app, the smart app banners now display an icon that you upload as the main icon of your custom mobile app.

For more information, see Adding a banner for mobile app download.

Ability to delete the Mobile channel interface

When you build a Pega^® Platform application, you can create a mobile app for your users. When you no longer need the mobile app, you can now delete an existing Mobile channel interface, just like any other channel that is available from the Channels and interfaces landing page.

For more information, see Channels and interfaces.

Improved Back button support in custom mobile apps for Android

In a custom mobile app for Android, you can press the Back hardware button to go back, instead of exiting the app. Custom mobile apps now function in the same way as native Android apps. For example, you can close a dialog box, dismiss an overlay, or collapse an expanded section by pressing the Back hardware button. On the home screen, pressing the Back hardware button displays a confirmation message before you can exit the app.

Support for multiple custom mobile apps for a Pega Platform application

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

Changes in large data page support in offline-enabled custom mobile apps

You can now create offline-enabled custom mobile apps that store reference data in large data pages that are sourced from report definitions, even if these report definitions return no records. Synchronization of these custom mobile apps does not fail. Also, you can now use page type properties as large data page properties.

For more information, see Creating and sourcing large data pages to store large reference data in offline-enabled applications and Custom populator JavaScript functions for large data pages.

Troubleshooting offline-enabled applications in a browser

You can now troubleshoot offline-enabled applications by using the Tracer tool and developer tools that are available in a web browser. You can troubleshoot scripts that are running when the application is running, without having to use additional debugging tools.

For more information, see Application debugging using the Tracer tool, Troubleshooting offline-enabled applications with the Tracer tool in a browser, and Offline capability.

Support for native search in custom mobile apps

To improve the overall user experience in a custom mobile app, you can configure native search in the user interface of the application. To use the search capability, first configure the pySearchConfiguration rule. This rule allows you to optionally define a set of search categories as a local data source. You then configure the mobile search action for any user interface control, for example, a button in a section. Users can tap the search field to see the most recent search results, including results that are grouped by categories, as they enter search text.

For more information, see Native search capability in custom mobile apps and Configuring search in custom mobile apps.

Enhanced Pulse performance and layout on mobile devices

Pulse performance is now faster on mobile devices. The user interface has been enhanced to enable better collaboration among users. The new Pulse mobile layout provides a better user experience for posting messages, adding attachments, bookmarking content, and so on.

For more information about Pulse, see:

• App Studio – Communicating with users by using Pulse
• Dev Studio – Communicating with users by using Pulse