Enable email notifications on agent failure
Valid from Pega Version 7.3.1
You can now get email notifications each time an agent fails with a PEGA0010 alert. By receiving notifications on agent failure, you can immediately take action to restart or fix the agent. You can enable email notifications on the Agent Management landing page.
For more information, see Enabling notification on agent failure and PEGA0010 alert: Agent processing disabled.
Download the system state information for a node and the cluster
Valid from Pega Version 7.3.1
On the Cluster Management landing page, you can now download a JSON file that contains information about the current system state for a single node or for the whole cluster. You can use this file to compare persisted system state information across time, which can be helpful in debugging system problems. You also can use a new REST API with third-party tools to download the system state file.
For more information, see Downloading the system state.
Select values gadget optimization enhancements
Valid from Pega Version 7.3.1
The Select values gadget includes several enhancements that help reduce performance issues when a data set is very large. Administrators and developers can now add and remove optimizations for fields directly in Designer Studio. Additionally, Select values gadgets were added to the proposition import shape and history shape in the Strategy rule form.
For more information about Select value gadgets and field optimization, see Optimizing properties in Select values gadget.
Enhanced approach for defining user actions
Valid from Pega Version 7.3.1
You can now define user actions, such as local actions and supporting processes for case types and stages, by clicking Optional actions on the Workflow tab. You can add user actions for case types in the Case wide actions section and for stages in the Stage-only actions section.
For more information, see User actions for case types and stages.
Life cycle tab renamed to Workflow
Valid from Pega Version 7.3.1
The Life cycle tab for case types has been renamed to Workflow. On the Workflow tab, you can define a life cycle for case types by clicking Life cycle, and you can define user actions for case types and stages by clicking Optional actions.
For information about defining a life cycle for a case type, see:
- Pega Express 7.3.1 – Defining a life cycle for a case type
- Pega Platform 7.3.1 – Defining a life cycle for a case type
For information about user actions, see:
- Pega Express 7.3.1 – User actions
- Pega Platform 7.3.1 – User actions
REST services support password credentials and JWT Bearer grant types
Valid from Pega Version 7.3.1
Pega® Platform REST services now support password credentials and the JWT (JSON Web Token) Bearer grant type when you enable OAuth 2.0-based authentication. By using password credentials, you can quickly migrate clients from direct authentication schemes, provide additional flexibility when other grants are not available, and integrate your application with REST services in other applications. You can add compatibility with modern JWT-based cloud security IDPs by using the JWT Bearer grant type.
For more information, see About OAuth 2.0 Provider data instances, OAuth 2.0 Client Registration data instances - Completing the Client Information tab, Creating an Identity Mapping data instance.
Mobile optimized grid enhancements
Valid from Pega Version 7.3.1
Grid (table) layouts optimized for mobile support conditional visibility layout, row, and cell content. You can configure visibility as a client-run expression for use offline, or use a when rule or server-run expressions for desktop and mobile applications. Conditional visibility allows applications to use the template-based rendering. The UI Gallery includes an example of such a grid.
For more information see Optimize grid layouts for mobile.
Specify a model transparency policy for predictive models
Valid from Pega Version 7.3.1
Specify a model transparency policy in Pega® Platform to indicate predictive models that are compliant or non-compliant to use in particular business issues. Increase the transparency threshold of particular business issues to allow the use of more transparent models. Decrease the transparency threshold to allow for the use of less transparent and opaque models. Models with a transparency score below the transparency threshold are marked as non-compliant.
For more information, see Model transparency for predictive models.
Test when rules by using PegaUnit automated tests
Valid from Pega Version 7.3.1
You can now create and run PegaUnit automated tests for when rules. These tests reduce the testing effort required for when rules and improve product quality. They also help to identify issues that might be introduced in new releases by providing quick automated regression testing.
For more information, see Unit testing a when rule.
Use of PegaRULES_Extract_Marker.txt to delete cache is deprecated
Valid from Pega Version 7.3.1
The PegaRULES_Extract_Marker.txt file is deprecated. The system uses the presence or absence of the PegaRULES_Extract_Market.txt file to determine at startup whether to delete the static content, service export, and lookup list file system-based caches. In the rare situation that you need to delete these caches manually, use the System Management Application (SMA) ETier Static Content Management page. Using SMA does not require restarting the node.