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.

Addition of Data Access Tab to access control policy condition rules

Valid from Pega Version 8.6

You can now select associations and declarative index classes when creating access control policy condition rules. The Column source field in the policy condition can now accept properties from available associations and indexes. For ease of reference, the selected associations and indexes are available on the new Data Access tab. 

Using the new tab, you can build complex authorization models in which access restrictions for a class depend on the attributes present in the associated and indexed classes, along with the attributes in the current class. For example, a project management application can now separately maintain project lists for each operator and use that information to restrict read/write access to unique projects.

The information available on the new Data Access tab reflects rule form changes, which are similar to the existing functionality of the Report Definition in the Application Data Model. 

 

For more information, see Creating an access control policy condition.

Addition of Servlet Management

Valid from Pega Version 8.6

Pega Platform™ now has Servlet Management in Pega Cloud® Services, which provides a simple and secure way to make changes to Pega Platform servlet definitions.

Servlet Management provides Pega Cloud Service clients with solutions to manage servlet configurations with self-service options. This reduces the cycle time for delivering configuration changes in Pega Cloud Service installations while also improving upgrade reliability

For more information, see Servlet management.

Upgrade impact

Clients with no application servlet customizations will not experience an impact. If you upgrade from Pega Platform version 8.5 or earlier and, prior to the upgrade, the Pega Cloud team provided your application servlet customizations, then following the upgrade, you must manually add, remove, or modify your servlet customizations in your upgraded application using this servlet management landing page in Pega Platform.

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

To manually move your pre-upgrade servlet customizations as appropriate or add new ones to your upgraded application using the new servlet management landing page, follow the steps in Adding a servlet.

Cosmos React-UI supports custom authentication

Valid from Pega Version 8.6

Pega Platform™ now supports custom authentication in applications that use Cosmos React-UI. Depending on the needs of your users and the functionality of your application, you might need to write custom authentication schemes to meet specific requirements. 

Clients that use custom authentication in their applications can now take advantage of the Cosmos React-UI.

For more information, see Securing Cosmos React-UI applications.

Integration and security tab now divided into two tabs

Valid from Pega Version 8.6

The Integration and Security tab is now two separate tabs on the Application Definition form: Integration and Security. While the content of these two tabs are related, they function more effectively as separate tabs. The Security tab now includes the Authentication section, so you can add existing authentication services to your Application Definition to more effectively manage the security of your application. 

For more information, see Security tab of the Application Definition.

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