SR-A98390 · Issue 252437
Scheduled report cleanup error resolved
Resolved in Pega Version 7.2.2
Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.
SR-A77514 · Issue 239717
@baseclass!pyMemo has been made available
Resolved in Pega Version 7.2.2
Opening up property pyMemo (which applies to Link-) and trying to save it into a custom ruleset generated an error due to @Baseclass having a final version of pyMemo. To correct this, @baseclass!pyMemo has been made available.
SR-A87928 · Issue 255259
Fixed cataloging for v5 hotfixes
Resolved in Pega Version 7.2.2
Recent modifications to obtaining catalogs for supporting additional products (i.e. frameworks) caused a regression in being able to check dependency information on v5 hotfixes, preventing DL files from being created for them. This has been fixed.
SR-B5634 · Issue 274715
Stack frame handling made more robust
Resolved in Pega Version 7.2.2
Stack frame handling has been made more robust to prevent the stack trace from getting out of sync in cases where the strategy execution throws an exception.
SR-A89757 · Issue 258099
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.