Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Published Release Notes

Find release notes for the selected Pega Version and Capability.

Browse resolved issues for Platform releases.

Customized application overview documents in App Studio

Valid from Pega Version 8.3

Keep stakeholders notified of the status of an application by customizing and generating an application overview document in App Studio. The overview may include information such as case types, roles, features in your application, and more. Select the chapters that you want to include in the overview, and then highlight the most relevant information by ordering the chapters. In addition to the application overview document, you can generate a detailed data model, either in Microsoft Word or Excel format.

For more information, see Creating project documents for stakeholders in App StudioExporting a data model into a document.

New send email automations and enhancements

Valid from Pega Version 8.3

You can now configure cases, flows, and activities to compose and send guardrail-compliant emails that conform to the MIME standard by using email automations. Use the new Call-Automation method to call an automation from an activity without writing Java.

You can also now categorize error messages in automations to quickly understand the type of error that occurred. In addition, page list data types are now supported for inputs and outputs in automations.

For more information, see Calling an automation from an activity and Viewing automations.

More efficient navigation between applications in App Studio

Valid from Pega Version 8.3

The new My Applications gadget helps you switch applications in App Studio more conveniently. You can also search applications by name instead of choosing an application from the list, and then select the access role that you want to use. In addition, you can see descriptions of your applications and create an application by going to the My Applications landing page. To use the My Applications gadget, ensure that you update the UI Kit to version 14.

For more information, see Adding the My Applications gadgetSwitching between applications in App Studio.

Pega Cloud Services support for the AWS Asia Pacific (Mumbai) region

Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) Asia Pacific (Mumbai) region. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.

For more information about regions and availability zones, see Pega Cloud Services capabilities.

Editable list of build-on application features

Valid from Pega Version 8.4

Pega Platform™ now provides you with an option to edit the list of features in your application stack. Now you can define the order of the features to generate application documentation that lists the features by their priorities instead of the time of creation. For example, you can reorder the features when you want to communicate to your stakeholders which elements are top priorities.

For more information, see Learning about feature order.

Anypicker control in a condition builder

Valid from Pega Version 8.4

The condition builder now uses the Anypicker control to categorize the entities, such as fields or when conditions, that your application compares at run time. As a result, you can create conditions in a simplified and accelerated way. You can also select fields that are up to four levels deep within field groups.

For more information, see Create conditions faster with an Anypicker control (8.4)Adding an Anypicker controlDefining conditions in the condition builder.

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.

Business logic-based routing cards enhancements

Valid from Pega Version 8.5

To ensure that the sequence of business logic-based routing cards conforms to your business requirements, you now have the option to change the order of the cards. For easier navigation across multiple routing cards, the system automatically collapses the cards for you, and you can then easily expand the cards that you need to display.

For more information, see Navigate easier across business logic-based routing cards (8.5), Assigning users automatically at run time.

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.

All Pega product release notes can be found on their product pages.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us