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-A19549 · Issue 237574

Create work passes custom parameters in IAC flow

Resolved in Pega Version 7.2.1

In some circumstances, the create work on a button in a UI was not passing flow parameters when the section was launched inside the IAC Gadget. This has been fixed by updating the openSpaceInGadget API to pass custom parameters for the enternewworkfromflow switch clause.

SR-A19579 · Issue 236678

JAWS support added to tablist menu

Resolved in Pega Version 7.2.1

Screen readers were not reading when focus was on the tablist menu. Aria attributes have been added to correct this.

SR-A19580 · Issue 236677

IAC-NonGateway cookie set by encryption check

Resolved in Pega Version 7.2.1

Some site security mandates require all cookies to either have secure and httponly attributes set or be removed. Sites that were not making use of IAC were encountering a non-removable IAC-NonGateway cookie that violated this policy. To resolve this, the system now has a check for an encrypt condition before using setCookie for iac_nongateway, and will only set the cookie when encryption is found.

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

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