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.

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.

Upgrading to Hazelcast 4.x requires downtime during upgrades to Pega Infinity 8.6

Valid from Pega Version 8.6

Pega Infinity™ uses Hazelcast distributed clustering technology to share data and send events between server nodes. Beginning in Pega Infinity release 8.6, Pega Infinity supports Hazelcast 4.x.
 
Note: Note: Because Hazelcast 3.x is in extended support, upgrade to Hazelcast 4.x before the extended support period for Hazelcast 3.x ends.

Upgrade impact statement

On-premises upgrades of Pega Infinity release 8.4.2 and later to version 8.5.1 or later on Tomcat and PostgreSQL are completed with near-zero downtime. However, upgrading to Hazelcast 4.x requires that you shut down and restart your application server.

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

Hazelcast 3.x is enabled by default. For near-zero downtime upgrades, you do not need to perform any action.

For instructions about upgrading to Hazelcast 4.x, see one of the following topics:

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.

Improved indexing of StringList and StringGroup property types

Valid from Pega Version 8.6

Search and Reporting Service in Pega Platform™ 8.5 may improperly index StringList and StringGroup property types. As a result, the data model does not include the affected properties.

Upgrade impact

After upgrading to Pega Platform version 8.6, the system requires that the classes with the StringList or StringGroup type are reindexed. 

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

On the Search Landing Page, manually reindex all the classes that include properties with the StringList or StringGroup types to ensure that all your data is present in the data model. Alternatively, if finding specific instances of classes is difficult, you can reindex all classes in your application.

For more information, see Indexing class data.

 

Behavior changes when reporting on descendant classes

Valid from Pega Version 7.3.1

Report Definitions that use the Report on descendant class instances option with the Include all descendant classes option apply only to the Applies to Class. Join classes are not included as they were in previous Pega® Platform versions. The following example shows what happens for each possible scenario for Report on descendant class instances when the report is defined on ClassA with a class join with Work-.

  • If Report on descendant class instances is disabled, the report runs against ClassA and the join happens with Work-. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
  • If Report on descendant class instances is enabled, and Include single implementation class is selected, the report runs against ClassA and the join happens with the MySampleClass implementation class. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
  • If Report on descendant class instances is enabled, and Include all descendant classes is selected, the report runs against ClassA and its descendants and the join happens with Work-. In previous Pega Platform versions, the join happened with the MySampleClass implementation class.

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