Published Release Notes

Listener management in Designer Studio

On the new Listener Management landing page, you can view and manage available listeners across the cluster, including on the current node and remote nodes. By using this landing page, you can quickly debug and trace listeners. You can start, stop, and restart listeners, and you can filter the list of listeners by, for example, type, status, class, or name.

For more information, see Managing listeners.

Enhancements to PegaUnit test cases

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.

Create email correspondence by using templates

You can configure email correspondence rules by using email templates. Email templates provide custom email formats for users and give developers a greater degree of customization in designing email correspondence. Select an email template on the Corr tab of a correspondence rule by clicking Edit mode and selecting Templated email from the menu. You can also create a section as an email template by clicking Email template on the Settings tab of the section form. For more information see Creating email correspondence by using a template.

Reused forms support fields that can be modified

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

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

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

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

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.

Actions available for custom controls

All standard actions that are available for autogenerated controls are available on non-autogenerated custom controls as well. You can configure actions on custom controls by using the legacy actions options or the standard options that are available to custom and autogenerated controls. By using the standard options, developers can now configure multiple action sets for different types of events on a single custom control.

For more information, see Actions tab.

Relevant records now support class inheritance

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.