SR-A23560 · Issue 250384
Check added to ensure proper descendant class report building
Resolved in Pega Version 7.2.2
A declare page initially accessed from an operator runs a query against the implementation class in order to populate the declare page, but if the declare page is initially referenced by a service, the report is run against the framework class instead. This difference could lead to an issue where authorization switching would cause some declare pages to be built with the wrong class if the user's AG matched the service package AG. To avoid this, the Authorization.setActiveAccessGroup() method has been updated to include an additional check to continue the flow if the requestor has service package pool name set.
SR-A97401 · Issue 265625
DASS validation can be switched from ERROR to WARN
Resolved in Pega Version 7.2.2
An enhancement has been added to allow optional switching of the validation of the column type mismatch to WARN as a save-time error/Guardrail warning instead of ERROR. This is based on the new DASS function 'reporting/validateColumnTypeMismatchAs', and the owning ruleset is 'Pega-Reporting'. Note : Even though save-time and run time validations are skipped using this DASS, the query may fail if the database does not support varchar and decimal comparison.
SR-A89836 · Issue 262431
Fixed error from Sales Automation CreateQuote button
Resolved in Pega Version 7.2.2
An exception was being generated by a button click on Sales Automation application due to the reference in the when rule and in the expression being the same but belonging to different loadContexts. This confused the legacy network, and has been modified so the legacy network stops evaluating expressions' tracking refs when the ACR belongs to a decision rule.
SR-A76647 · Issue 253238
Resolved ConcurrentModificationException in mContent iteration
Resolved in Pega Version 7.2.2
When adding or removing the items from a repeat grid and submitting the modal dialog, an intermittent ConcurrentModificationException was coming from the API ClipboardPageImpl.clearMessages(). This was traced to the function iterating over mContent and has been fixed by making a copy of mContent and iterating over that.
SR-A87807 · Issue 260853
Sequencing improved for RDE triggering
Resolved in Pega Version 7.2.2
While data was being mapped from one page to another page using data transform and a page property referred to a data page that was being freshly loaded, then R-D-E expressions were not getting fired even though input properties of R-D-E's were getting changed. If data page instance was found for the referenced page property, then R-D-E expressions were fired as expected. This was traced to the forward chaining not completing before the loader was triggered, and the sequencing has been adjusted to resolve this problem.
SR-A76706 · Issue 252781
Modified pyLoadDataTypes data transform to match expected type
Resolved in Pega Version 7.2.2
Activities configured with "Double" as the data type were converted to "String" datatype in the activity after upgrade. This was due to the Data Transform pyLoadDataTypes rule using the pyLabel "DOUBLE" for double parameter type instead of "Double", and has been corrected.
SR-A77495 · Issue 254777
Corrected delete error with first row of Decision Table
Resolved in Pega Version 7.2.2
After clicking 'delete row' on the first row of a decision table the first row was not visible, but it was observed that when saving the first row it remained as it was and instead the second row was deleted. This was an error in highlighting and positioning, and has been fixed.
SR-A67932 · Issue 251208
Blank query field in Bulk Actions defaults to none instead of all
Resolved in Pega Version 7.2.2
Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. This has been resolved.
SR-A19246 · Issue 254062
Customized ordering ability for delegated rules added
Resolved in Pega Version 7.2.2
Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.
SR-A19246 · Issue 254058
Customized ordering ability for delegated rules added
Resolved in Pega Version 7.2.2
Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.