Published Release Notes

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.

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

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

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

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.

Automatic redirection to HTTPS for Pega Cloud Services environments

Pega Cloud Services now redirects HTTP to HTTPS automatically for applications that run in Pega Cloud Services environments. This automatic redirection ensures that your network traffic is always encrypted.

Default value of the threadpoolsize agent affects batch indexing

After you patch Pega Platform to version 8.5.2 or higher, the system changes the default value of the threadpoolsize agent, which controls the number of concurrent activities (threads) in the system, from 5 to 15. Batch indexing in Pega Platform™ does not require all 15 threads, so you can change the agent value to increase system performance by managing the indexing/distributed/batch/numworkers dynamic system setting.
If your deployment does not support that setting, and batch indexing does not use Queue Processors, the system uses the threadpoolsize value for batch indexing instead.

For more information, see Editing a dynamic system setting.

Upgrading to Hazelcast 4.x requires downtime during upgrades to Pega Infinity 8.6

Upgrade impact statement

On-premises upgrades of Pega Infinity release 8.4.2 and later to version 8.5.1 or later on Tomcat and PostgreSQL are completed with near-zero downtime. However, upgrading to Hazelcast 4.x requires that you shut down and restart your application server.

What is required to update the application to be compatible with this change?

Hazelcast 3.x is enabled by default. For near-zero downtime upgrades, you do not need to perform any action.

For instructions about upgrading to Hazelcast 4.x, see one of the following topics:

• For near-zero downtime upgrades from Pega Infinity release 8.4.2 or later on Tomcat and PostgreSQL, see "Optional: upgrading to Pega Platform version 8.6: Upgrading to Hazelcast 4.x" in Near-zero downtime Upgrade Guide for Pega Platform version 8.4.2 and later for Tomcat and PostgreSQL.
• For all other upgrades, see "Optional: upgrading to Hazelcast 4.x" in the appropriate upgrade guide.

Improved indexing of StringList and StringGroup property types

Search and Reporting Service in Pega Platform™ 8.5 may improperly index StringList and StringGroup property types. As a result, the data model does not include the affected properties.

Upgrade impact

After upgrading to Pega Platform version 8.6, the system requires that the classes with the StringList or StringGroup type are reindexed. 

What steps are required to update the application to be compatible with this change?

On the Search Landing Page, manually reindex all the classes that include properties with the StringList or StringGroup types to ensure that all your data is present in the data model. Alternatively, if finding specific instances of classes is difficult, you can reindex all classes in your application.

For more information, see Indexing class data.