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 name | Upgraded version |
|---|---|
| apache-mime4j-core | 0.8.3 |
| apache-mime4j-dom | 0.8.3 |
| commons-codec | 1.15 |
| commons-collectionons4 | 4.4 |
| commons:commons-math3 | 3.6.1 |
| commons-compress | 1.20 |
| commons-lang3 | 3.9 |
| fontbox | 2.0.19 |
| httpclient | 4.5.12 |
| httpcore | 4.4.13 |
| httpmime | 4.5.12 |
| istack-commons-runtime | 3.0.8 |
| jackson-annotations | 2.10.3 |
| jackson-core | 2.10.3 |
| jackson-databind | 2.10.3 |
| jaxb-runtime | 2.3.2 |
| java-libpst | 0.9.3 |
| jcommaner | 1.78 |
| junrar | 4.0.0 |
| metadata-extractor | 2.13 |
| openjson | 1.0.11 |
| parso | 2.0.11 |
| pdfbox | 2.0.19 |
| poi | 4.1.2 |
| poi-ooxml | 4.1.2 |
| poi-ooxml-schemas | 4.1.2 |
| poi-scratchpad | 4.1.2 |
| slf4j-api | 1.7.28 |
| xmlbeans | 3.1.0 |
| xmpcore | 6.1.10 |
For more information, refer to the documentation of your JAR provider.
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.
Upgrading to Hazelcast 4.x requires downtime during upgrades to Pega Infinity 8.6
Valid from Pega Version 8.6
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:
- For near-zero downtime upgrades from Pega Infinity release 8.4.2 or later on Tomcat and PostgreSQL, see "Optional: upgrading to Pega Platform version 8.6: Upgrading to Hazelcast 4.x" in Near-zero downtime Upgrade Guide for Pega Platform version 8.4.2 and later for Tomcat and PostgreSQL.
- For all other upgrades, see "Optional: upgrading to Hazelcast 4.x" in the appropriate upgrade guide.
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.