Base a data type on an existing data type
Valid from Pega Version 7.3
When adding a data type to your application, you can now select an existing data type on which to base the new type. The new data type reuses assets from the existing type. When building on a strategic application, you can define the class in which the new data type is created to ensure that the data type has the correct pattern inheritance.
For more information, see Adding a data type.
Microsoft Silverlight no longer supported in Mozilla Firefox 52
Valid from Pega Version 7.3
Beginning with Mozilla Firefox 52, Firefox no longer supports NPAPI-based browser plug-ins, including Microsoft Silverlight. Pega Platform features that use Silverlight, such as merging case data into a Microsoft Word template, no longer work.
For more information, see End of Support for Microsoft Silverlight in Mozilla Firefox 52.
Full support for Unicode characters in Pega Express
Valid from Pega Version 7.3
Pega® Express now supports Unicode characters when you name properties, case types, and data types. Languages that use multibyte characters, such as Japanese and Hindi, are now fully supported. An administrator can enable Unicode support for Pega Express by configuring a Dynamic System Setting in Designer Studio.
For more information, see Enabling Unicode character support for object names.
Listener management in Designer Studio
Valid from Pega Version 7.3
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
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.