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-A13674 · Issue 227843

repeat grid with progressive pagination error fixed

Resolved in Pega Version 7.2.1

A JS error occurred when using repeat grid with progressive pagination due to the system attempting to set the style attribute for a null element. The APIs have been updated for this nested grid scenario and to allow grid initialization to take care of assigning the proper index.

SR-A13691 · Issue 231105

Corrected race condition in rapid LoadDataPage requests

Resolved in Pega Version 7.2.1

If the the same Requester-level data page was rapidly invalidated and reloaded by means of "Load-DataPage", a race condition between the background requestor and main requestor caused some pending requests to be overwritten by new incoming requests before the previous load request were serviced. As a result, information was lost. This has been resolved by ensuring every queued job's ID is different and thereby never conflicts.

SR-A13729 · Issue 231588

Embedded Valuelist/valuegroup count included in manifest file

Resolved in Pega Version 7.2.1

The pxTotalInsertsCount for Embedded ValueList /ValueGroup Property was missing in the Manifest file while the pxTotalInsertsCount for Toplevel ValueList /ValueGroup Property was present. The Embedded Valuelist/valuegroup property count will now be included as expected.

SR-A13779 · Issue 227492

Fixed repeat grid sorting for multiple pages

Resolved in Pega Version 7.2.1

During pagination, the grid was not retaining the sorting state, and sorting was broken from the second page onwards. The SortClipboardData activity for both pagination and sorting action has been updated to correct this.

SR-A13784 · Issue 235357

RedirectAndRun URL built with CSRF token

Resolved in Pega Version 7.2.1

Using RedirectAndRun with CSRF enabled and redirecting to a different thread resulted in a missing CSRF token because the URL was constructed before the initialization of the thread object. The sendHttpRedirect() API has been modified to construct the URL once the thread has been initialized.

SR-A13796 · Issue 229066

Error messages scroll while using WAI

Resolved in Pega Version 7.2.1

After moving all controls into dynamic layouts, error messages were not scrolling with the screen when using PegaWAI (accessibility). To correct this, the error msg span position will be set absolute from its parent.

SR-A13815 · Issue 227490

Events working for repeat grid with Top.<ListProperty> source

Resolved in Pega Version 7.2.1

Single click or double click events on a grid record were not working if Top. was used as source pagelist property. This was due to missing support for "Top.[pagelist]" in grids, which has been added.

SR-A13882 · Issue 228926

Date Control in expandable repeating grid shows proper date value

Resolved in Pega Version 7.2.1

The Date control in the repeating grid was showing the case ID number instead of the date value when configured as master-details with expandable rows. This was due to a missed use case of the "display read-only formatting" feature where a read-only condition configured on the control returned the editable control in the response instead of read-only. This has been fixed.

SR-A13926 · Issue 230498

Resolved invalid page causing missing bulk items

Resolved in Pega Version 7.2.1

When trying to perform bulk transfer, some of the work objects were sporadically not displayed in the bulk processing list. This was caused by an invalid page getting passed while invoking checkActionWhens to act on the 'when' for showing the assignments list. The proper page is now set by updating the GETBULKPROCESSCONTENT activity to set pxRefObjectKey to the assignment page while invoking checkActionWhens.

SR-A13930 · Issue 227345

Calendar popup positioning fixed

Resolved in Pega Version 7.2.1

The calendar popover is positioned to the parent span instead of input, creating space between the input and calendar when there are errors. This has been fixed by positioning the calendar popover to the input field instead of parent span specifically for Text Input + Calendar mode.

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