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.

Post files and links with pxPostMessage API

Valid from Pega Version 7.1.4

The pxPostMessageAPI now supports text messages, file attachments, and hyperlinks. You can programmatically update Pulse streams using this API from activities or SLA rules.

Create, Save As, and Specialization forms

Valid from Pega Version 7.1.4

The familiar “New” and “Save As” forms have been streamlined to make record creation faster and more intuitive. You can easily target a specific layer in your application stack, interactively define the record’s configuration and select only those circumstance definitions that make sense for your use case.

While the underlying behavior for creating a record is not new for this release, the redesigned UI of these forms and new defaulting strategy for fields is worth noting:

PRPC_7_1_4_Release_Notes-1.jpg

To launch these forms, use one of the new options found in the action area of the form header:

PRPC_7_1_4_Release_Notes-2.jpg

Note that not all record types support the ability to specialize by circumstance.

For more guidance on how to use the Create, Save As and Specialization forms, please refer to: Intuitive record creation and specialization

Quickly create ad-hoc cases

Valid from Pega Version 7.1.4

The My Cases work area on the Case Manager portal introduces a Quick Create feature that lets users create cases and assign tasks that are not included in the processing of business cases (instances of case types defined in the Cases Explorer).  For example, a manager can create a case and a task to set up a phone conference with her staff, or a reminder to enroll in an online seminar. Users can also set up a series of tasks to represent all they work they need to do to accomplish a specific goal.

Redirect users to logout screen

Valid from Pega Version 7.1.4

New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout.

 

A new template, Web-Session-Return-Template, has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.  This template can be copied to a ruleset visible to unauthenticated requestors (via node configuration) and used to override Web-Session-Return.

Support for additional health metrics on the Application Quality landing page

Valid from Pega Version 7.4

On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.

For more information, see Application Quality landing page.

View the configuration settings for Pega Platform nodes in Designer Studio

Valid from Pega Version 7.4

On the new Configuration Settings landing page, you can view a list of the configuration settings for a specific node, current or remote, or for an entire cluster. From this landing page you can diagnose settings issues, determine whether settings are loaded correctly, and review the settings' purposes. You can also download the prconfig.xml file for any node in a cluster to modify the settings. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings. For example, if a started agent does not run, you can check if agents are enabled on your system; or if some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.

For more information, see Viewing the current configuration settings of a node or the whole cluster, Downloading and viewing the prconfig.xml file for a specific node, REST APIs for viewing the configuration settings for Pega Platform.

Stakeholder management extended to case followers

Valid from Pega Version 7.4

You can now control which users follow a case. By actively involving the people with relevant skills and roles in your application, you can resolve cases more quickly.

For more information, see Case followers.

Support for templated auto responses during email triaging of interaction cases

Valid from Pega Version 7.4

When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.

For more information, see Defining suggested replies for the Email channel.

Submit application changes made in Pega Express to a continuous integration and delivery pipeline

Valid from Pega Version 7.4

After you make changes to your application in Pega® Express, you can submit these changes into a continuous integration and delivery pipeline that is configured in Deployment Manager. By using Pega Express to submit your application changes into staging, preproduction, and production systems, you can quickly start builds without involvement from IT.

For more information, see Starting a continuous delivery build.

Enhanced adaptive model reporting

Valid from Pega Version 7.4

The new Model report replaces the Behavior and the Performance overview reports to improve report usability and provide consistent information. You can export your Model reports into PDF or Excel files to view or share them outside the Pega® Platform. The Model report also includes information on the groups of correlated predictors where the best performing predictor from each group is active in the model and other remain inactive; this information helps you understand why predictors are active or inactive.

For more information, see Generating a model report.

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