Import to and export from network storage
Valid from Pega Version 7.3.1
You can import development artifacts from and export development artifacts to network storage. Use the Import wizard, the Export wizard, or the service-enabled system management command-line tool for these activities.
For more information, see Tools for migrating rules and data.
Support for advanced text analysis when routing incoming emails
Valid from Pega Version 7.3.1
You can use text entity, category and sentiment analysis during the automatic routing of incoming emails. You provide text analysis of the text-based email content by defining routing rules, so that an automatic decision is made about how to process the received emails by the Pega® Intelligent Virtual Assistant. You can route the email content to an operator, assign it to a work queue, or open a top-level case with the information.
For more information, see Configuring routing conditions for automatic email handling.
Conditional paths added to case life cycle
Valid from Pega Version 7.3.1
You can now add a conditional path to a process in the life cycle of a case. By defining the decisions that cause a process to follow different paths, you can create cases that support more than one outcome.
For more information about conditional paths, see Conditional paths in a case life cycle.
Use of the @java function in expressions is deprecated
Valid from Pega Version 7.3.1
Use of the @java function in expressions is deprecated. Use a utility function or other product feature instead.
For more information about expressions, see Building expressions with the Expression Builder.
Enhancements to rule comparison
Valid from Pega Version 7.3.1
For rules that contain a large amount of text, you can now highlight all the changes between rule versions and apply the changes from the version that the rule is compared with. By comparing versions, you can see what changed in the code and resolve conflicts. This ability to compare versions accelerates the development cycle, allowing for a faster time to market with higher quality code.
For more information, see Comparing rule versions.
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