SR-A19582 · Issue 236679
Unique row IDs created for embedded repeat grid Autocompletes
Resolved in Pega Version 7.2.1
pxAutocompletes in a section embedded in a repeat grid did not have unique ID's associated with them, while their labels did. This affected their accessibility. cpega_RLIndex has been added to the autocomplete ID to create the missing row index.
SR-A19599 · Issue 237365
Made getLocalizedValue function call fully qualified
Resolved in Pega Version 7.2.1
In environments where there are multiple versions of the function getLocalizedValue (which is true for any environment where the FSIF and KYC frameworks have been installed), pzFetchCaseStatusUpdate fails due to an unqualified function call. This has been corrected by providing the full context including library while calling functions in the property-set method in the mentioned activity.
SR-A19601 · Issue 238255
Workbasket re-visit issue resolved
Resolved in Pega Version 7.2.1
After selecting a workbasket in the MyGroup drop down and launching the pop-up containing the workbasket details, an error in the closing reset function led to an issue where a second workbasket would need to be launched before it was possible to return to the first one again. This has been corrected.
SR-A19659 · Issue 241725
Autocomplete accepts parameters with special characters
Resolved in Pega Version 7.2.1
Autocomplete was not populating results when it was configured with a Datapage which accepted parameters and those parameters included colons. The handling for the function,"updateParams" (of pzpega_control_autocompleteag.js) has bene modified to send the parameter in the request body instead of the header.
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-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-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-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".