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.
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.
Optimized data schema upgrade
Valid from Pega Version 8.5
Several improvements have been made to optimize the speed of the data schema upgrade to help you experience minimal downtime during upgrade to Pega Platform 8.5™. The data schema upgrade process optimizations include the following improvements:
- Optimized database index creation during upgrade
- Optimized synchronization process to detect duplicate rules during the application import process
- A new upgrade setting for Pega Cloud® Services operators that reduces the time to upgrade clients that run large Pega applications, such as the CRM Suite
For more information, see Limit upgrade downtime with data schema upgrade improvements (8.5).
Case archiving enhancements in Pega Cloud Services
To provide a more complete archiving solution to Pega Cloud clients, we have introduced several enhancements to the archival functionality for your Pega Platform database. This includes support for your data retention policy to expunge (permanently delete) archived data from Pega Cloud File Storage.
Permanently delete case data with data retention policy
In previous versions, Pega Cloud clients could archive resolved cases and associated data from the Pega database to Pega Cloud File Storage after the cases have been resolved for a specified number of days with an archival policy. Now, clients can permanently delete archived data from Pega Cloud File Storage after the cases have been resolved for a specified number of days with a data retention policy.
Faster adoption with testing mode
Clients can now enable a testing mode and specify archival policies in minutes instead of days. Now you create and resolve cases, then run archiving process immediately to test the functionality within minutes.
Easier adoptions with enhanced monitoring capabilities
With the addition of the Log-ArchivalSummary class and its associated log files, clients can monitor their archival jobs in a single view. We have also improved logging for archival jobs, offering you greater insight into the success of your archival process.
To learn more about archiving and purging your case data in your Pega Cloud environment, see Improving performance by archiving cases.
LDAP Authentication Service URL resolution
The latest Pega Cloud infrastructure update includes Java JDK (JDK 89u181), which contains improvements to LDAP support. This Java JDK enhancement can prevent insecure logins by verifying that the hostname specified in the LDAP URL matches the hostname that you specified in the Trust store certificate in the JNDI Binding Parameters section of the Authentication Service rule. An LDAP Authentication Service can no longer resolve using IP addresses.
This is a one-time fix and does not affect Pega Cloud clients with security-compliant LDAP settings and certificates.
Required client workaround
For clients that previously configured LDAP in their applications running in a Pega Cloud environment using IP addresses, after Pega Cloud Services notifies you that the update is complete, you must edit your LDAP Authentication Service rule form Directory field to use the URL value of the domain name or a machine within the domain that matches the URL used by the SSL certificate in the Trust store.
For example, if your SSL certificate uses the test.abc.com machine name, enter ldaps://test.abc.com:[portNumber] inthe Authentication Service Directory field.
For more information about creating or editing an LDAP Authentication Service, see Creating a custom authentication service.
Organization Setup superseded by New Application Wizard
Valid from Pega Version 7.1.3
The Organization Setup Wizard has been retired in PRPC 7.1.3. This feature was previously launched from the Designer Studio > Org & Security > Organization > Organization Setup menu. Users are encouraged to run the New Application Wizard (also known as Application Express) instead:
This tool quickly generates an application along with all of the artifacts previously offered by the Organization Setup Wizard. This includes, but is not limited to, the class hierarchy, application rule, organization/division/unit rules, and all relevant data instances.
See the following PDN article for more details on the New Application Wizard:
Valid from Pega Version 7.1.4
This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer. The layout of the New and Save As forms were made more intuitive and intelligent. Specification actions were made to be more consistent across various aspects of the Case Designer.
- After removing specification references, users can create and save a new specification.
- Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
- If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
- In the outline view, specification changes will be preserved when switching from tab to tab.
- The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.
Valid from Pega Version 7.1.3
In this release, specification support in Case Designer was improved. Also, improvements and fixes were made to the New Application Wizard.
- Changes were made to support a split schema environment
- Shared and Component RuleSets can be copied.
- Can edit in Word from either Grids or Lists.
- More than 50 case types are now supported for an application.
DCO and PMF integration is unavailable
Valid from Pega Version 7.1.5
DCO and PMF integration functionality is not available in this release. Related project management controls have been removed from the following:
- System Settings landing page ( )
- Application Profile landing page ( )
- Add/Edit Specification dialog
Attachment support for requirements
Valid from Pega Version 7.1.6
Requirements now support attachments. You can add attachments from the Designer Studio > Application > Profile > Requirements landing page, the Add/Edit Requirement modal, or the requirement rule form.
Enhanced document generation
Valid from Pega Version 7.1.6
The following usability improvements have been made to documents generated by the Application Document Wizard:
- Stages and Processes now appear for case types that use Case Lifecycle Management. This diagram includes hyperlinks to corresponding sections in the document and is scoped to top-level processes only.
- All flows (excluding pyStartCase) referenced by a case type now appear in documents. This removes previous constraints on non-starting, draft, and checked out flows.
- Entity Relationship Diagrams (ERDs) are now embedded in documents as Visio objects.
- Sections without content are omitted from the generated document.
- Screenshots are labeled.
- Requirement text (Long Description) is included in the Requirements Matrix section.
- Linked requirements appear in context beneath their associated specification.
- Acceptance Criteria appears in context beneath the associated specification, report, or correspondence item.