SR-B13517 · Issue 293343
Icon alignment fixed in grids with skin inheritance
Resolved in Pega Version 7.3
The Header Title and the Collapsible Icon of a grid were misaligned due to an error in skin inheritance. The pzTemplateNewSkin1 legacy standard format has been changed to correct this.
SR-B13606 · Issue 287616
Angle brackets escaped for RD drill down
Resolved in Pega Version 7.3
In a report definition with drill down, if the column parameter had a value that used the wrong parameter was getting passed in Query. This was due to the characters getting converted into their HTML equivalent < and >., and the character escaping has been corrected to resolve this.
SR-B13647 · Issue 291863
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13647 · Issue 291683
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13702 · Issue 287232
SLA correctly calculated for migrated rules
Resolved in Pega Version 7.3
After upgrade, using the case designer view to look at a case type created in an earlier version displayed errors in the right panel for the goal-HH:MM:SS and deadline-HH:MM:SS fields if the assignment had the SLA rule "Default". This was an error in backwards compatibility related to whether the "pzIsAutoGenerated" property used to distinguish the SLA was auto generated or not, and has been corrected by setting the Visibility condition .pzAutoGenerated to 'true' in the lower Dynamic layout to avoid a null value in migrated rules.
SR-B13718 · Issue 285582
Improved handling for discarded decision data rules
Resolved in Pega Version 7.3
When the decision data rule was discarded after choosing the 'custom form' from that data rule, the associated section was deleted and the decision data rule could not be checked in. The issue was due to the deletion of the base layout rule upon discard of the decision data rule. To prevent this, an additional when condition has been added in the activity 'cleanUp' to ensure that only the checked out version of the layout rule is deleted and not the base rule associated with the decision data rule.
SR-B13775 · Issue 293697
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B13775 · Issue 286916
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B13785 · Issue 284733
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 284743
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.