Legacy landing pages removed
Valid from Pega Version 7.3.1
The following legacy landing pages and their links in the Designer Studio menu have been removed:
The streamlined Designer Studio menu facilitates locating and navigating to landing pages.
For information about the replacements for these landing pages, see Deprecated features.
Service REST monitoring
Valid from Pega Version 7.3.1
You can now monitor response and request data for REST services and view the results in Pega® Platform. The ability to monitor REST services is useful for debugging your application during development, for example, when a request fails. It is not recommended that you monitor REST services in production environments because monitoring might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space. You can configure monitoring globally for all of your REST services by using the service/EnableglobalMonitoring Dynamic System Setting with owning ruleset Pega-IntegrationEngine, or by using the service package and service rule forms.
For more information, see Service REST monitoring.
Support for intelligent routing in the Email channel
Valid from Pega Version 7.3.1
When you create an Email channel interface to use as a Pega® Intelligent Virtual Assistant, you can now set up automatic routing of the received email content. You define routing rules so that the Email channel is more responsive and makes an informed decision about how to process the email content. The Pega Intelligent Virtual Assistant can automatically assign it to an operator, add it to a work queue, or create a top-level case. In addition, you can configure multiple email accounts to act as the same Pega Intelligent Virtual Assistant.
For more information, see Configuring routing conditions for automatic email handling.
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.
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