Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

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.

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).

 

Tracer file size limit to prevent disk usage issues

Valid from Pega Version 8.6

The maximum size of files with event details that Tracer generates is now 10 GB to avoid excessive disk usage and performance issues. Tracer applies the size limit at the node-level, so every node that runs in your system can use up to 10 GB of disk space to create an output file with event details. As a result, you can monitor the health of your system and deliver issue-free applications without experiencing disk space problems.

For more information, see:

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.

 

Enter the machine or domain name in the Directory field
Enter the machine or domain name in the Directory field

 

 

 

New My Pega Cloud portal with enhanced functionality available

You can use the My Pega Cloud self-service portal to restart an environment, download log files, or view high-level details about  an environment. For more information, see Managing Pega Cloud environments from My Support Portal.

To access this portal, you must have the appropriate site credentials. To manage your support contacts, see the Support Contact Administrator Guide for additional information.

Archival support added to cases in Pega Cloud

Valid from Pega Version 8.1

You can now create an archival policy to move inactive cases from Pega Cloud to secondary storage. By periodically purging entries from your database, you can improve application performance.

For more information, see Case archiving.

Support for Data streaming service for Pega Cloud Marketing 7.4 applications

Valid from Pega Version 2.1

Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.

Enhanced support for the Kibana platform

Pega Cloud Services began running Kibana 4.6.x. In addition to this version update, the Kibana viewer now includes:

  • “DEBUG” level messages in PegaRULES log
  • The PegaRULES-SecurityEvent log

Pega Cloud Services support for the AWS EU (Paris) region

Valid from Pega Version Pega Cloud

Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) EU (Paris) 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 availability and resiliency.

This additional region is available as of QI 2019.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us