Associate rules and project management work items with features
Valid from Pega Version 7.3
You can now link a project management work item with a rule when you create a rule, check in a rule, and save a rule as a new rule, which automatically links the rule with any features that are associated with the project management work item. Associating project management work items, rules, and features maintains traceability and makes it easier for you to extend the application, because you can identify the rules that are associated with each feature. On the Application Overview landing page, you can also link existing rules directly to features in the Associated rules section of a feature.
For more information, see Associating existing rules with a feature.
Record Editor and data import enhancements
Valid from Pega Version 7.3
The Record Editor and Import wizard for data types have been enhanced to make the import process faster and easier to use. You can now perform the following tasks.
- Configure the Record Editor to use full-text search, which makes searching faster.
- Configure the location of the data import error file. For example, you can set the location to a shared location so that users can access the file from any node in a multinode system.
- Pass the keys of the records that were added, updated, or matched directly to custom postprocessing without additional database I/O.
- Search and filter records and export only the results instead of all records.
- Stop an import that is in progress.
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.
Rollover policy for log files
Valid from Pega Version 7.3
The rollover policy for log files is now based on time (daily) and file size (maximum file size is 250 MB). Log files are rolled over daily or when the maximum file size is reached. Current (not rolled over) log files do not have a time stamp. The time stamp is added when the log file is rolled over. In addition, the log file name for the current log file does not include the date. You can add the date to the current log file; however, the log file will not be rolled over. In addition, the web.temdir variable for setting the log file location is no longer supported; use the pega.logdir variable instead.
For more information, see Pega Platform logging with the Log4j 2 logging service.
Enhanced functionality of the Decision Manager portal
Valid from Pega Version 7.3
The Decision Manager portal now provides more revision management options. The Decision Analytics work area for development of predictive, adaptive, and text analytics models is now part of the Decision Manager portal. PegaUnit testing of rules is more convenient from a new Automated Testing landing page. Revision managers can reassign change requests back to strategy designers or other users of the Decision Manager portal without losing changes that were already made.
For more information, see Enhancements to the Decision Manager portal.
Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.
For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.
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.
Create email correspondence by using templates
Valid from Pega Version 7.3
You can configure email correspondence rules by using email templates. Email templates provide custom email formats for users and give developers a greater degree of customization in designing email correspondence. Select an email template on the Corr tab of a correspondence rule by clicking Edit mode and selecting Templated email from the menu. You can also create a section as an email template by clicking Email template on the Settings tab of the section form. For more information see Creating email correspondence by using a template.
OAuth 2 token support in Pega Mobile Client
Valid from Pega Version 7.3
The Client Store module in Pega Mobile Client has been extended to support OAuth 2 tokens. The tokens are used to authorize data synchronization requests that are sent to the Pega® Platform. Once the OAuth 2 token support is turned on and configured on the server, Pega Mobile Client starts using it automatically. This functionality is available on both iOS and Android devices.
For more information, see Enabling data synchronization with OAuth 2 tokens.