Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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-A19652 · Issue 246778

BIX filter failure alert added

Resolved in Pega Version 7.2.1

A warning has been added to issue an alert when filters are not being added while generating a BIX query.

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-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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us