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.

Enhancements to PegaUnit test cases

Valid from Pega Version 7.3

Several enhancements have been made to PegaUnit test cases.

  • You can now use the following new comparators for the page assertion:
    • Has errors – The assertion passes if the system finds all the pages for which there are errors.
    • Has no errors – The assertion passes if the system finds all the pages for which there are no errors.
  • You can now export a list of all the PegaUnit test cases that are in the system or that are configured on a specific rule type to Microsoft Excel format.
  • You can now view PegaUnit test cases for built-on applications.

For more information, see the Configuring page assertions and Exporting PegaUnit test cases help topics.

Reused forms support fields that can be modified

Valid from Pega Version 7.3

Now, you can choose whether the fields in an embedded form are read only or can be modified at run-time. You can set the reused form to Auto, which maintains the display mode (read only, required, optional) set for each field. Reusing a form reduces development time and maintains a consistent layout for a set of fields.

For more information, see Reusing a form.

Out-of-sequence processing added to steps in a life cycle

Valid from Pega Version 7.3

In Pega Express, you can now add a step to the life cycle of a case type that moves a case from one stage to another. By revisiting or skipping a stage, you can support out-of-sequence processing in a case.

For more information about supporting dynamic stage sequences, see Moving a case to a different stage.

Push notifications added to steps in a life cycle

Valid from Pega Version 7.3

In Pega Express, you can now add a step to the life cycle of a case type that pushes a notification to users on mobile devices when a case requires an action, such as approval or review. By using an event-driven model to send messages, you can ensure that cases are resolved quickly.

For more information about push notifications, see Sending a push notification from a case.

Message posting added to steps in a life cycle

Valid from Pega Version 7.3

In Pega Express, you can now add a step to the life cycle of a case type that updates the social activity stream of a case. By posting information as it becomes available, you can inform case workers and provide a visible discussion thread for stakeholders.

For more information about message posting, see Posting messages to a case.

Stage progression in a life cycle includes alternate paths

Valid from Pega Version 7.3

In Pega Express, you can now add alternate stages to the life cycle of a case type. You can also change the type of a stage from primary to alternate, or alternate to primary. By using different types of stages, you can separate expected behavior from the exceptions in your application.

For more information about stages, see Defining a life cycle for a case type.

Relevant records now support class inheritance

Valid from Pega Version 7.3

Relevant records can now be inherited through your class hierarchy. For example, a property that is marked as a relevant record at the Work- class can also be inherited by the child classes of the Work- class.

For more information, see Adding relevant records.

Support for conversational user channels

Valid from Pega Version 7.3

You can now communicate with users and customers of a Pega® Platform application by using Pega Intelligent Virtual Assistant acting as a conversational user channel. You can now use Facebook Messenger, Alexa voice commands, standard email, or mobile texting (SMS) to interact with Pega Platform, for example, to open a case or display a menu of available options. In addition, in the Facebook channel configuration, you define text analyzer rules for advanced text analysis, based on artificial intelligence, so that the system provides the best response to users.

For more information, see Intelligent Virtual Assistant.

Capture real-time feedback with Agile Workbench

Valid from Pega Version 7.3

Project stakeholders can use the new Agile Workbench tool to capture real-time feedback directly in an application, which can increase the efficiency of application development. You capture feedback by creating a user story, bug, or feedback item, and these work items can include video recordings of screens, annotated screen captures, file attachments, or URLs. In Designer Studio, you can configure Agile Workbench to integrate with Pega® Agile Studio so that bugs and user stories are synchronized between the two systems.

For more information, see:

Adding a conversation to a case type

Valid from Pega Version 7.3

You can add a conversation that uses a messaging or voice application (for example, Facebook Messenger) as a channel for adding information to a case. You configure the messaging workflow as part of the case life cycle. At run time, a user working in the selected application sees (or hears) a series of questions that ask the user to enter information.

For more information about adding a conversation in Designer Studio, see Adding a conversation to a case type.

For more information about adding a conversation in Pega® Express, see Adding a conversation to a case type.

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