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.

Use "alternate database" as report source

Valid from Pega Version 7.1.6

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

PRServlet not required in PRPC URLs

Valid from Pega Version 7.1.6

PRServlet is no longer required in a URL when accessing PRPC. A URL typically written like this:

http://example.com/prweb/PRServlet?[QueryString]

Can instead be written like this:

http://example.com/prweb/?[QueryString]

This change is effective only for PRPC 7.1.6 and newer versions. Older versions of PRPC still require using PRServlet in a URL.

Report Browser removed from Designer Studio

Valid from Pega Version 7.1.9

The Report Browser and Access landing page have been removed from Designer Studio. In Designer Studio, developers can create, edit, and test reports by using the Report Definition rule form.

The Report Browser is still available in the Case Manager portal.

Real-time pulse processing for multinode systems

Valid from Pega Version 7.1.9

Multinode development environments now use real-time pulse processing. Previously, when a change was made on one node, the pulse processing interval could take a minute or more for that change to be reflected on another node. Now, when a rule is changed on one node, that change is immediately reflected on all the other nodes in the cluster. This change helps to ensure that users are running a rule on the same node as where the rule was changed.

Verifying that a Pega 7 Platform instance is running

Valid from Pega Version 7.1.9

You can verify whether a Pega 7 Platform instance is up and running by entering this URL: http://<<hostName:port/contextName>>/PRRestService/monitor/pingservice/ping

The Pega 7 Platform Engine responds with HTTP Response Code 200 if the instance is available. The response contains JSON text in the format { "duration":"<time in milliseconds>" }. Any other response codes or timeout indicate that the instance is unavailable.

Database storage used for passivation in High Availability mode

Valid from Pega Version 7.1.9

When an application is running in High Availability mode, the value attribute for initialization/​persistrequestor/storage in the prconfig.xml file or the Dynamic System Settings​ now defaults to "database."

Previously, applications running in High Availability mode required shared passivation, where either initialization/​persistrequestor/storage was set to “OnTimeout” or a custom passivation mechanism was used. The change to using database by default provides persistent storage for passivation, and provides control for the landing page for High Availability.

For more information, see Understanding passivation and requestor timeouts and the High Availability Administration Guide.

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