Ability to include all properties in search results
Valid from Pega Version 7.4
You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.
In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.
You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.
For more information, see Specifying custom search properties.
Compact style sheet for creating PDF files
Valid from Pega Version 7.4
You can now use a compact style sheet when you create PDF files by using the Create PDF smart shape in a case type or when you use the HTMLtoPDF activity. This style sheet overrides the style sheet that is used by the harness skin and correctly renders certain elements such as headings and inline grid tables. It also renders PDF files more quickly.
For more information, see Creating PDF files by using a compact style sheet and PDF file rendering scenarios.
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.
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.