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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A14132 · Issue 232550

Improved handling for values starting with "." in Developer Portal Explorer

Resolved in Pega Version 7.2.1

A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.

SR-A14132 · Issue 233457

Improved handling for values starting with "." in Developer Portal Explorer

Resolved in Pega Version 7.2.1

A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.

SR-A14151 · Issue 244440

Autocomplete select updates as expected

Resolved in Pega Version 7.2.1

An intermittent problem was found with autocomplete that selected a previously set value if text was typed in the autocomplete box and the value was selected instead of the search text. This was traced to a press of the capslock key being interpreted as an unprintable character, causing an abort of the request and change tracker not having the correct update. The function processkey of autocompleteag.js has now been updated to not abort the request when a non-printable character is typed.

SR-A14168 · Issue 230039

Unique page names generated for nested child work items

Resolved in Pega Version 7.2.1

When multiple child work items were created using pxAddChildWork in one transaction, the same page name was getting used and causing errors. This has been fixed by making pagename unique by appending currentdatetime.

SR-A14230 · Issue 230423

IconRequired fixed for repeating layouts

Resolved in Pega Version 7.2.1

The iconRequired span was only being generated for the first row of any repeating layout structure. This has been fixed in the GenerateCellContent RUF.

SR-A14313 · Issue 227652

Autocomplete displays properly after screen rotation

Resolved in Pega Version 7.2.1

A black gap appeared on the screen of iPad and iPhone devices when tying to use the autocomplete window after the screen was rotated between Portrait and Landscape modes. This was due to the autocomplete popover not accepting a % width setting, and the display method of the popover has been modified to display properly.

SR-A14325 · Issue 228543

Repositioned BusyIndicator to cover Target element

Resolved in Pega Version 7.2.1

If the section with busy indicator was taller than the viewport height, the busy indicator mask did not cover the lower part of the section when scrolling and the section was editable. This has been fixed by repositioning the mask to cover the part of the section editable in the viewport and also show immediately on scroll.

SR-A14386 · Issue 230504

Fixed issue with CSS incorrectly overriding skin rule

Resolved in Pega Version 7.2.1

The skin rule settings "Error Border" and "Error Background" were not having any effect on a text control which contained a validation error. This was an issue with the ErrorShade element being overridden by more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.

SR-A14403 · Issue 230497

Confirmation Message no longer appearing twice in confirm harness

Resolved in Pega Version 7.2.1

When the out-of-the-box pyWorkConfirmMessage section is included in an application and displayed in one of the steps while running the application, the pyWorkConfirmMessage section will display pyConfirmationNote property value of the work object present in pyWorkPage and will also display the pyConfirmationNote value defined at assignment level present in pxFlow page. This was traced to an additional call step in the function, and the handling has been modified to produce the expected results.

SR-A14599 · Issue 229391

Error section close icon positioning fixed

Resolved in Pega Version 7.2.1

The close icon in the error section was not properly positioned. This has been corrected.

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