Navigation support for test ID
Valid from Pega Version 7.4
The Navigation rule supports the addition of a test ID to each node. Test IDs support automated testing by providing a unique identifier for user interface elements. Add Test IDs to a navigation rule in the rule form configuration.
For more information, see Navigation form - Completing the Editor tab.
New PEGA0097 alert
Valid from Pega Version 7.4
In Pega Cloud, if a user attempts to establish a session and the configured maximum number of HTTP requestors on the cluster has been reached, the user is directed to a page that displays the PEGA0097 alert message. This alert helps to prevent a system from becoming overloaded.
For more information, see PEGA0097 alert.
Stakeholder management extended to case followers
Valid from Pega Version 7.4
You can now control which users follow a case. By actively involving the people with relevant skills and roles in your application, you can resolve cases more quickly.
For more information, see Case followers.
Support for templated auto responses during email triaging of interaction cases
Valid from Pega Version 7.4
When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.
For more information, see Defining suggested replies for the Email channel.
No longer supported translator configuration options
Valid from Pega Version 7.4
The following translator configuration options are not needed and are no longer supported. If you previously configured any of these system settings, remove them from the system settings to avoid a warning message. For example, if you set translator/useparserfamily, the following message is displayed at startup: "Translator option, 'translator/useparserfamily' is not needed and no longer supported. Remove this from the system settings."
- translator/useparserfamily
- translator/usecodegenerator
- translator/usenativedouble
- translator/optimization/use71BlockAnalysis
- translator/optimization/use71ConstantFolding
- translator/optimization/use71AssignmentTypeSimplification
- translator/optimization/use71IntrinsicFunctions
- translator/use71PropSetGeneration
- translator/use71ParserAssignment
- assembly/model/useBlock4ContiguousSets
- /translator/pandc/comparepandcalgorithms
- /translator/pandc/use6xalgorithms
- /Compatibility/CheckForTopLevelClassMismatch
In addition, the com.pega.pegarules.generation.parseoverride bootstrap option is no longer supported. Remove this option from the system settings.
Configure role dependencies to grant access rights
Valid from Pega Version 7.4
You can configure role dependencies in a role to grant access rights, which are inherited from the role. Role dependencies are relationships between roles that mirror an organization hierarchy or a more complex relationship among groups of operators, roles, or functional areas. Use role dependencies to simplify role configuration, minimize the number of roles needed by an access group, and minimize the number of privileges that you have to manually define for roles in your application.
For more information, see Access Role rules, Access Role form – Using the Role tab.
Pega Platform ends support for Java 7
Valid from Pega Version 7.4
Oracle has ended support for Java 7 and is no longer issuing security patches for Java 7. Therefore, starting with Pega 7.4, Pega® Platform no longer supports Java 7. For more information about supported platforms, see the Platform Support Guide. For more information about Oracle support for Java 7, see the Oracle documentation.
Improved operator security
Valid from Pega Version 7.4
To improve security, Pega® Platform now requires the following:
- During deployment, you must configure a password for [email protected].
- The administrator must enable new out-of-the-box operators.
- The administrator and new Pega-supplied operators must change their passwords after the first login.
These requirements replace the optional secured mode in earlier versions of Pega Platform.
Aggregating and browsing Visual Business Director data set
Valid from Pega Version 7.4
Visual Business Director (VBD) data set has been enhanced to support the Aggregate and Browse operations. Aggregating aids testing your data in Pega® Visual Business Director. Browsing the content of the Visual Business Director data set provides transparency and helps to troubleshoot issues that are related to Pega Visual Business Director. You can use the new operations from the DataSet-Execute method or by clicking Actions > Run in the Visual Business Director data set form.
For more information see Creating a Visual Business Director data set record and Configuring the DataSet-Execute method for Visual Business Director.
Submit application changes made in Pega Express to a continuous integration and delivery pipeline
Valid from Pega Version 7.4
After you make changes to your application in Pega® Express, you can submit these changes into a continuous integration and delivery pipeline that is configured in Deployment Manager. By using Pega Express to submit your application changes into staging, preproduction, and production systems, you can quickly start builds without involvement from IT.
For more information, see Starting a continuous delivery build.