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-127156 · Issue 191611

Corrected lost lock workflow error

Resolved in Pega Version 7.1.8

In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.

SR-127156 · Issue 193608

Corrected lost lock workflow error

Resolved in Pega Version 7.1.8

In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.

SR-127156 · Issue 194906

Corrected lost lock workflow error

Resolved in Pega Version 7.1.8

In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.

SR-126907 · Issue 193779

Work objects in dynamic container corrected for the AES Manager portal.

Resolved in Pega Version 7.1.8

If a dynamic container is embedded in a section, the work objects opened through AES portal are opened in a dynamic container. When using the AES Manager portal with the Microsoft Internet Explorer 11 browser, work objects would open but then immediately the UI would scroll closed. This was a browser issue where harness tabs with IFRAME in production were not triggering the re-flow for DC tabs as they were for static tabs, and the system has been updated to perform this action correctly.

SR-127159 · Issue 192190

Handling added for declare expressions with null page directory

Resolved in Pega Version 7.1.8

The PropertyReferenceImpl.filter() API was an throwing exception if the directory was null for changes (the directory will be null if a copy of top level page is made). To resolve this, the API has been modified to use PRThread as directory if page directory is null.

SR-127161 · Issue 199350

Localization fixed for buttons with shortcut key options

Resolved in Pega Version 7.1.8

Localization was missing for labels on buttons with shortcut key options. This has been fixed.

SR-127180 · Issue 192478

Modified display of Listview filters to show action buttons

Resolved in Pega Version 7.1.8

After upgrading, Listviews used to generate reports that included filtering were not displaying the "Apply" and "Cancel" buttons in the drill-down pop up. To resolve this, the setscrollingDIVHeight API has been modified to properly display the content.

SR-127202 · Issue 192389

Join and Like filters tuned for Listview

Resolved in Pega Version 7.1.8

Listview join filters with LIKE operations were not performing optimal SQL queries, impacting system performance. This has been tuned to improve the system response.

SR-127210 · Issue 190272

Added table-based cataloging

Resolved in Pega Version 7.1.8

The Update Manager catalog has been updated to reside in the Pega database instead of in the file system. This will facilitate cataloging in a multi-node environment, allow for reporting and other visibility into the catalog itself, and improve performance of dependency checking.

SR-127231 · Issue 192212

Validation resolved for Class as property reference in Activity Name

Resolved in Pega Version 7.1.8

If the Class was given as the property reference, attempting to enter the Activity Name generated the validation error "Attempting to access the rule in Bad class name: .HARNESSCLASSNAME" and the rule could not be saved. This was traced to the Property reference not being supported for Activity Name, and that has been added.

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