New formats for styling report data grids
Valid from Pega Version 7.2.2
When you view a report, the data grid that is displayed is now styled by using either the List report format or the Summarized report format, depending on the report type. With this enhancement, you can display report data differently, and perhaps more effectively, than other grids in your portal. In the skin of your application, these new formats will be added and upgraded automatically by copying the Default format for the Trees & grids layout type, which was previously used to style reports.
For more information, see Modifying data grid formats for reports.
Monte Carlo data set
Valid from Pega Version 7.2.2
You can now create a Monte Carlo data set that is filled with varied and realistic-looking data. You can use this type of data set to generate random data records to test strategies and data flows.
For more information, see Creating a Monte Carlo data set record.
System starts slowly after upgrade or update on IBM DB2 for z/OS
Valid from Pega Version 7.2.2
Additional tables are added to upgraded and updated systems. If your system starts up very slowly after an upgrade or update, the database statistics on these new tables might not have generated correctly. To correct this issue and improve performance, your database administrator needs to manually rebuild the statistics for all tables in the rules schema.
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
Conditional filter logic supported in access control policy conditions
Valid from Pega Version 7.2.2
In the Access Control Policy Condition rule form, you can now add conditional logic that allows you to apply different access control policy conditions based on different situations, such as different types of users. The policy condition filters that are enforced are based on the results of Access When rules. Conditional filters can be configured to allow certain highly privileged users to bypass access control security in certain situations. This is accomplished by entering an Access When but leaving the conditional logic field blank. When such a filter is applied to a read access policy it also should be applied to the corresponding discover policy.
For more information, see Creating an access control policy condition.
BIX -I command-line option fails for unexposed properties
Valid from Pega Version 7.2.2
Business Intelligence Exchange (BIX) command-line extractions fail when the extract has a filter that uses unexposed property references that are passed in by the input file that you specified in the -I command-line option. Previously, the BIX extraction ignored the filter and the extraction did not fail.
BIX filtering now works like report filtering
Valid from Pega Version 7.2.2
Filtering for Business Intelligence Exchange (BIX) extracts has been enhanced to work like report filtering, making it easier to use. Existing filters that use the Contains/DoesNotContain filter operation will be converted to use the Equals/NotEquals filter operation.
Improvements to guided tour creation
Valid from Pega Version 7.2.2
Usability improvements to creating and managing guided tours enable you to more efficiently create tours that introduce the key features of your application. Now, you configure the Manage guided tour action on a control to start, continue, or dismiss a tour, instead of specifying an API script.
For more information, see Managing a guided tour.
Decision result assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
When you create PegaUnit test cases for decision trees or decision tables, you can now configure decision result assertions. You can specify one or more input and result combinations that you expect to see when you run a decision tree or decision table, and compare it to the results that are returned by running the rule.
For more information, see Configuring decision result assertions.
Improved requestor management
Valid from Pega Version 7.2.2
You can now manage the requestors from all the nodes in a cluster by using the Requestor Management landing page. You can view performance details about requestors, run traces, and stop requestors. On this landing page, you can also filter the list of requestors, and view cluster-based and node-based views of requestors.
For more information, see Managing requestors.