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.

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.

Insights from 8.5 require additional configuration after upgrade

Valid from Pega Version 8.6

Upgrade impact

After you upgrade Pega Platform™ version 8.5 to 8.6, the Explore Data landing page might not include insights that come from the earlier version of the product.

What steps are required to update the application to be compatible with this change?

Run the pxUpgrade85Insights activity to make all insights from version 8.5 accessible for you in 8.6. By running this activity, you upgrade insights with new metadata that is required in version 8.6. For example, the pxUpgrade85Insights activity provides you with the option to set the visibility of insights to private, public or shared.

For more information about insights, see Visualizing data with insights.

Reporting

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

  • Multiple boxes may be checked on List view checkboxes
  • Dashboard Charts slider has been improved.
  • Summary View reports and charts have been enhanced.
  • Column properties can be added to a report in the Report Editor.
  • List view column widths can be set by Smart Info.
  • Listviews will display correctly for updated systems.
  • Improvements to the GuardRail Report.

Use "alternate database" as report source

Valid from Pega Version 7.1.6

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

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