Logic-based assignment routing
Valid from Pega Version 7.2.2
You can now define business logic that controls when and by whom an assignment is processed in a case. By routing assignments to a specific user or group of users, you can help ensure that cases are resolved faster.
For more information, see Logic-based assignment routing.
Support for additional rule types for PegaUnit test cases
Valid from Pega Version 7.2.2
To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:
- Activities
- Data transforms
- Strategies
- Decision trees
- Decision tables
After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.
For more information, see PegaUnit testing.
Page assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.
For more information, see Configuring page assertions.
New Automated Testing landing page
Valid from Pega Version 7.2.2
The new Automated Testing landing page displays all the PegaUnit test cases in your application. You can use it to quickly access, run, and view results of tests. In addition, if you have the AutomatedTesting privilege enabled, you can switch to the Automated Unit Testing landing page to access rules that are supported by both PegaUnit testing and Automated Unit Testing, such as activities.
For more information, refer to Automated Testing landing page.
Enhancement for specifying filter conditions in reports
Valid from Pega Version 7.2.2
You now have the option to select comparison values from a list of available values when you add or edit the filter conditions for a report in Pega Express. This option is available for all columns, except for numeric or text columns when the comparator setting is , Greater than or equal, Less than, or Less than or equal.
For more information, see Adding filter conditions.
Define hotfixes as dependencies for product rules
Valid from Pega Version 7.2.2
When you package an application or product rule for export, you can specify a list of required hotfixes. Those dependencies are validated when you import. The import operation proceeds only if all required hotfixes are installed on the target system. For more information, see Packaging an application.
Export branches from the command line
Valid from Pega Version 7.2.2
Use the prpcServiceUtils command-line tool to export branches to an archive. You can later import the branch archive to another system.
For more information, see Exporting products, applications, or branches from the command line.
Update access groups from the command line
Valid from Pega Version 7.2.2
Remotely update access groups by using the prpcServiceUtils tool. This feature is useful in automated deployment scenarios when you want to provide access to a new application version.
For more information, see Updating access groups from the command line.
Cluster-wide tracing for service rule
Valid from Pega Version 7.2.2
RuleWatch Tracing of Service Rules has been enhanced to support cluster-wide tracing. Cluster-wide tracing makes it easier for you to troubleshoot services in clustered configurations where a load balancer dynamically assigns service requests to nodes in the cluster. This functionality is especially useful for debugging mobile applications, REST Web Services, and other stateless service executions. When tracing across the cluster, the trace feature captures only one trace at a time, which might result in some concurrent service executions not being traced. All other concurrent service executions in the cluster continue unimpeded. When the trace in progress is completed, the next new service execution in the cluster is traced. For example, you might see traces for invocation one on node A, invocation two on node C, and invocation four on node B. This selective tracing approach ensures that tracing with a breakpoint will not stop all service executions across the cluster. The trace/cluster/ServiceRuleWatchmaxProductionLevel Dynamic System Setting has also been added, which allows you to selectively disable tracing based on production level to eliminate performance issues related to tracing in production systems.
As a result of this enhancement, only one user can trace a service rule at any given time. An error message is displayed if you try to trace a service rule that is being traced by another user.
For more information, see Cluster-wide tracing of service rules.
Support for creating PegaUnit test cases for strategy rules
Valid from Pega Version 7.2.2
You can create PegaUnit test cases for strategy rules in Designer Studio and in the decisioning user portals to compare the output of a strategy to the results that are returned by running the strategy. For example, you can verify that the number of propositions per customer is less than or equal to a certain value.
For more information, see:
- Creating test cases for strategy rules, if you are working in the decisioning user portals.
- PegaUnit testing