Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Support for custom pre- and post-JavaScript processing for offline flow actions

Valid from Pega Version 7.1.9

Developers of an offline-enabled mobile app can execute basic business logic before and after a flow action is rendered by adding their own JavaScript code into a custom user scripts bundle. Its functions must be called within a try/catch clause. The JavaScript code, to be executed before a flow action is rendered, is always called afterClientCache is called and before DisplayHarness is called.

Conditional online and offline map display

Valid from Pega Version 7.1.9

The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.

Troubleshooting Pega Mobile Client on the login screen

Valid from Pega Version 7.1.9

An offline mobile developer can now troubleshoot issues that are not related to incorrect credentials when signing in to the Pega Mobile Client app. On the app login screen, an alert box displays where the user can click a link to examine current log files to troubleshoot the issue. The contents of the displayed log file can be filtered.

For more information, see Troubleshooting Pega Mobile Client.

New Pega Mobile Client debugging options

Valid from Pega Version 7.1.9

The Mobile tab on the Application form contains two new options: a check box for enabling debugging in the Pega Mobile Client app, and a drop-down field for setting the log level to one of the following levels: Silent, Error, Warning, Info, or Debug.

For more information, see Mobile settings reference.

Ability to view a PDF file while offline

Valid from Pega Version 7.1.9

Users of offline-enabled mobile apps can now tap a button to view a PDF file, regardless of whether the user is online or offline. The associated button, link, or icon must have a Run Script action defined that calls the pega.ui.pdf.view() function with two parameters: applicationName and pdfName. The PDF file itself must be uploaded to a Rule-File-Binary rule.

For more information, see How to set up viewing of PDF file while offline.

Building a Pega Mobile Client with custom modules

Valid from Pega Version 7.1.9

When you build a Pega Mobile Client mobile app using the Pega 7 Platform, you can now include Android or iOS custom modules. The custom modules must be included in the assets.zip file that contains the Pega Mobile Client branding and customization details.

For more information, see Building a mobile web app into a hybrid mobile app.

Low-code authoring of case pages

Valid from Pega Version 8.6

Mobile authoring for Cosmos React applications now supports the configuration of native mobile pages that include case details. Your mobile channel automatically generates these pages for each case type in your application. This enhancement improves the user experience in your app by providing users with native pages that you can adjust to best suit your business process. For example, you can highlight specific views on a page by modifying which tabs appear on the page, or add a floating action button to help your users edit the case.

For more information, see Authoring mobile case pages for Cosmos React applications.

In Pega Platform™ version 8.6, mobile features in Cosmos React applications are available only as a preview, with limited support for various interface elements and features, such as offline mode. The recommended production design system for Pega Mobile in Pega Platform 8.6 is Theme Cosmos.

For more information about the Cosmos React design system, see Cosmos React and UI architecture comparison.

Automatic packaging of cases for offline use

Valid from Pega Version 8.6

Newly created mobile channels now support automatic packaging of cases for use in offline mode. The packaging process includes case data from all native list pages that you create from offline-enabled case types and add to the navigation of your mobile app. Previously, automatic packaging was limited to assignments in the work list (and their related work items), and cases that were listed in the data page that you manually designated for packaging.

This enhancement improves the user experience for mobile app developers by ensuring that the data that is referenced in list pages for offline-enabled case types is automatically available for the users of your offline app.

Improved user experience for Cosmos React mobile apps

Valid from Pega Version 8.6

Mobile apps that you build for Cosmos React applications now feature a highly performant and responsive user interface that improves the overall user experience.

Native case pages

Prescriptive mobile case pages are now faster and more reliable. Mobile case pages display views and widgets as cards and group the cards into user-friendly tabs. Users can navigate the tabs by swiping left or right. From the case page, users can also edit case page details by selecting the floating action button, or choose an optional action from the case header drop-down menu. 

To improve collaboration, prescriptive mobile case pages support the Pulse widget, as well as uploading, viewing, and downloading case attachments.

Improved case processing 

The case processing interface on mobile devices is now more reliable and ensures a smooth experience for case workers. After users complete an assignment, Cosmos React apps display the task that is next in the flow that you define for the case type. Optional actions open in an overlay drawer component that users can minimize when they need to multitask while processing cases.

Form validation in real time 

Validation of user input for mobile forms is now highly responsive thanks to real-time validation. To ensure that users enter data correctly, forms support validation expressions that you define in App Studio. Expressions are processed on the client side to further improve app performance.

Native Android and iOS controls

Cosmos React apps use a selection of native Android and iOS controls that make mobile apps faster and more intuitive to use. The native controls include map and location controls, date and time pickers, and controls for adding attachments.

 

In Pega Platform™ version 8.6, mobile features in Cosmos React applications are available only as a preview, with limited support for various interface elements and features, such as offline mode. The recommended production design system for Pega Mobile in Pega Platform 8.6 is Theme Cosmos.

For more information about the Cosmos React design system, see Cosmos React (early adopter) and UI architecture comparison.

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