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.
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.
New PEGA0084 alert - Search node count
Valid from Pega Version 7.2.2
The PEGA0084 alert is generated when the number of available index host nodes does not meet the quorum ((replicas/2) + 1) required for index writes to succeed. This alert can occur when some of the index nodes go down, causing the number of available index host nodes to be less than the quorum. For more information, see PEGA0084 - Search node count.
Style charts in the application skin
Valid from Pega Version 7.2.2
You can now style charts in your application skin by selecting Charts in the Controls section and setting a theme. When you style charts by using a theme, charts that are generated for report definition reports and the autogenerated chart control are styled consistently, and you do not need to style charts individually. In addition, you can preview chart themes in the Skin form to see how different charts look without launching an application.
For more information, see Styling charts in the application skin.
Condition builder enhancements
Valid from Pega Version 8.5
To enhance the precision of condition builder in both App Studio and Dev Studio, the new instances include comparator helps you specify the number of field group and field group list instances to which a when rule applies. In addition, a search option that returns results on keypress helps you easily look for existing values.
For more information, see Create conditions in an enhanced condition builder (8.5), Defining conditions in the condition builder.
Support for nested Declare Trigger rules
Valid from Pega Version 8.5
Pega Platform™ now supports nested Declare Trigger rules so that you can conveniently create correlations between actions in your case types. Declare Triggers rules invoke an action when a specified event takes place in a case type. You can now design more complex scenarios faster by nesting more Declare Trigger rules that work in the context of running another Declare Trigger rule. For example, when a case participant changes a postal code in their personal details, a Declare Trigger rule runs and a respective customer service representative (CSR) receives an email. After the CSR receives the email, a nested Declare Trigger rule runs and your application creates a document with the updated personal details and attaches it to the case.
For more information, see Develop applications faster with nested Declare Trigger rules (8.5), Declare Trigger rules.
Support for validations in Declare Expression rules
Valid from Pega Version 8.5
Pega Platform™ now correctly evaluates validations on target properties in Declare Expression rules. As a result, any validations defined on properties that have Declare Expression rules in previous releases, now work correctly.
Upgrade impact
Any unintended validations on properties that have configured Declare Expression rules, both default and user-defined, might cause issues in an application upon saving work objects and data objects that refer to Declare Expression rules.
What steps are required to update the application to be compatible with this change?
If you experience issues when saving objects, debug your application by setting the declareexp/target/validation/disable dynamic system setting to true. If your application works correctly after the change, it means that validations on Declare Expressions cause the issues. For your application to work correctly, analyze the log files and remove any unintended validations.
For more information, see Declare Expression rules.