Updated default dynamic system setting for requestor pools
Valid from Pega Version 8.4
Clients can now enable or disable requestor pools for processing service requests using a new dynamic system setting called EnableRequestorPools with Pega-IntegrationEngine as the owning rulest. Previously, all deployments utilized requestor pools to improve service processing response efficiency; requestor pools eliminated overhead by automatically returning a requestor to the pool after it fulfills a service request. Starting in Pega Platform 8.4, requestor pools are disabled in Client-managed cloud deployments, since these deployments use autoscaling to handle service request traffic. Enabling requestor pools in Kubernetes environments is not recommended, because they can inhibit the default autoscaling settings in the environment.
Requestor pools remain enabled by default in Pega Cloud and on-premises environments.
To help clients navigate this change, Pega has updated its best practice guidance for configuring requestor pools. For an overview, see Requestor pooling for services. For guidance on the use of requestor pools in your application, see the EnableRequestorPools entry in Dynamic system settings data instances.
Upgrade impact
Requestor pools are disabled by default in Pega Platform 8.4 in client-managed cloud deployments. Clients who deployed previous versions of Pega Platform on a Kubernetes environment and who upgrade to Pega Platform 8.4 could see that their services behave differently.
What steps are required to update the application to be compatible with this change?
If clients that are deployed in a Client-managed cloud environment need to configure their services to use requestor pools and they understand how to configure requestor pools for their optimized use, these clients can re-enable requestor pools. Clients should review the best practice for configuring requestor pools before they re-enable requestor pools. To re-enable requestor pools, you modify the EnableRequestorPools setting in the Pega-IntegrationEngine Owning ruleset from “disabled” to Enabled [no value]. For details, see Editing a dynamic system setting.
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.