SR-A19670 · Issue 239624
Error on save resolved for defer load activity with empty params
Resolved in Pega Version 7.2.1
When trying to save a section by adding a defer load activity, the error " Problem executing pzAssemblePreprocess for RULE-HTML-SECTION DATA-PORTAL EMPLOYEEONBOARDINGDASHBOARD" appeared if the pyDeferLoadRetrievalActivityParams property was empty. A check has been added to resolve this issue.
SR-A19688 · Issue 238970
Fixed loss of read-only after delegated refresh
Resolved in Pega Version 7.2.1
If two dynamic layouts were configured in a section where the on change property1 in layout1 refreshed the layout2, a read-only declare property in layout2became editable after the refresh. This has been fixed.
SR-A19700 · Issue 236991
cke: cleanup regex fixed
Resolved in Pega Version 7.2.1
The regex function in pzpega_ckeditor_pastefromword_filter_default, which is used to cleanup the markup during cut and paste from RTE/Word, was incorrectly removing the associated text as well as the intended cke: attributes. This has been corrected.
SR-A19704 · Issue 234771
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A19705 · Issue 246975
Hash table logic fixed for invokeMQConnector
Resolved in Pega Version 7.2.1
Logic issues were found and fixed related to hashtable usage for invokeMQConnector.
SR-A19761 · Issue 237142
Fixed Require flag usage for Validate rule
Resolved in Pega Version 7.2.1
Saving a Validate rule that had a Required flag on one or more properties automatically reset the value, resulting in the inability to set the Required flag on any property of the rule. This was an error in the temporary activity handling, and has been fixed.
SR-A19761 · Issue 237073
Fixed Require flag usage for Validate rule
Resolved in Pega Version 7.2.1
Saving a Validate rule that had a Required flag on one or more properties automatically reset the value, resulting in the inability to set the Required flag on any property of the rule. This was an error in the temporary activity handling, and has been fixed.
SR-A19782 · Issue 237144
Mandatory date and amount fields validation performed before reset
Resolved in Pega Version 7.2.1
Date and amount fields changed to incorrect format if any mandatory field was empty and screen was saved. This was traced to a handling error where the reset of read-only formatting happened before the validation check, and has been fixed.
SR-A19803 · Issue 248102
Scheduled report generation errors skip sending email
Resolved in Pega Version 7.2.1
When a scheduled report encountered a database error, a blank email was sent to the recipients each time it retried instead of the expected behavior of stopping the process and not sending the correspondence. The code has been modified to ensure the process will properly skip the rest of the steps if there is StepStatusFail in the report generation.
SR-A19810 · Issue 239496
PopulateRecipient set to consider pyEmail1
Resolved in Pega Version 7.2.1
After upgrade, an error was occurring while trying to save the Data-Corr-Email.populateRecipient activity into an application ruleset due to code changes used to specify the email property field. The "populateRecipients" activity has fallback logic to handle using pyEmailAddress [old method] for pyAddresses(Email) [new method], but some sites had the data in ".pyEmail1". PopulateRecipients has now been updated to look for pyAddresses(Email)").(".pyEmailAddress") and then consider values from ".pyEmail1".