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.

Predictive models can drive predictions

Valid from Pega Version 8.6

You can use predictive models as the basis of your predictions. As a data scientist, you can now use Machine Learning Operations (MLOps) to replace models in your system. You can replace a model in a prediction with a PMML, H2O MOJO, or Pega OXL predictive model, as well as a scorecard or field, and then approve the update for deployment to a production environment. You can respond to a Prediction Studio notification that an active model does not generate enough lift and decide to replace the low-performing model with a high-accuracy model. You can also update a prediction on a regular basis, for example, whenever you develop a new churn model in an external environment.

For more information, see Replace models in predictions and migrate changes to production with MLOps.

Enhancing the performance of your Next-Best-Action strategy with globally optimized strategies

Valid from Pega Version 8.6

Starting in version 8.6, Pega Platform™ combines the versatility of Next-Best-Action Designer with strategy performance enhancements provided by using globally optimized strategies (GOS). Decrease the run time and memory usage of executing the Next-Best-Action strategy in batch or real-time scenarios by using the globally optimized strategies generated by Next Best Action Designer.

GOS is supported by Pega Platform's standard business change management process. GOS rules are automatically included in relevant revision packages.

For more information, see Enhance the performance of your Next-Best-Action strategy with globally optimized strategies (8.6).

Support for picklists with parameterized data pages in App Studio in Cosmos React UI

Valid from Pega Version 8.6

You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.

For more information, see link Dropdown control Properties — General tab.

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.

Upgraded selected third-party JAR files to support Pega Platform functionalities

Valid from Pega Version 8.6

Pega Platform™ 8.6 now provides upgraded versions of the JAR files that support various functionalities within the Platform, such as generating documents or PPTX files.

Upgrade impact

If you have custom implementations and use any classes from the upgraded JAR files directly in your code or through JAR APIs, after your upgrade to Pega Platform 8.6, your application might experience unexpected run-time behavior if the upgraded JAR version lacks any elements from the previous version. For example, custom implementations can typically include activities, functions, or non-autogenerated sections. Unexpected run-time behavior might also occur when you use a third-party library that has dependencies on the upgraded JAR files. If you use only default Pega Platform functionalities without any customizations, the JAR files continue to work correctly without any additional actions.

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

If you have any JAR customizations, ensure that you test the upgraded JAR files for compatibility and upgrade impact. The following table lists the upgraded JAR files that might impact your application:

JAR file nameUpgraded version
apache-mime4j-core0.8.3
apache-mime4j-dom0.8.3
commons-codec1.15
commons-collectionons44.4
commons:commons-math33.6.1
commons-compress1.20
commons-lang33.9
fontbox2.0.19
httpclient4.5.12
httpcore4.4.13
httpmime4.5.12
istack-commons-runtime3.0.8
jackson-annotations2.10.3
jackson-core2.10.3
jackson-databind2.10.3
jaxb-runtime2.3.2
java-libpst0.9.3
jcommaner1.78
junrar4.0.0
metadata-extractor2.13
openjson1.0.11
parso2.0.11
pdfbox2.0.19
poi4.1.2
poi-ooxml4.1.2
poi-ooxml-schemas4.1.2
poi-scratchpad4.1.2
slf4j-api1.7.28
xmlbeans3.1.0
xmpcore6.1.10

For more information, refer to the documentation of  your JAR provider.

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.

Enhanced Pulse gadget for Cosmos React

Valid from Pega Version 8.6

Together with the DX API, the Cosmos React component now provides an overlay in which users can quickly view and select the feed sources from which to view Pulse messages. Users can also add attachments to their messages, and remove the messages that they post. These enhancements improve collaboration and speed up case resolution. For example, a case worker can view only posts from particular cases, to quickly find a request for additional information about a case, and then provide necessary details by attaching a relevant document.

For more information, see Configuring Pulse feed sources for Cosmos React and Posting a message in Pulse.

Easier customer record management in Customer Profile Designer (early preview)

Valid from Pega Version 8.6

The new Customer Profile Designer module of Pega Customer Decision Hub™ makes it possible for marketing analysts and strategy designers to define the associated data for each customer context directly in the Pega Customer Decision Hub portal. It is also possible to define more complex associated data structures that use a custom data flow, or define associated data of different types, such as RDBMS and Cassandra, for the same customer context.

Customer Profile Designer is available in Pega Customer Decision Hub 8.6 version as an early preview version. The functionality will be further expanded in future releases.

For more information, see Manage customer records in Customer Profile Designer (8.6).

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