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-A16012 · Issue 233486

Localization added for locking messages

Resolved in Pega Version 7.2.1

Localization has been added for locking-related messages in LockInfoAdvanced to facilitate translating messages such as "This case is locked by your operator in another PRPC session. Choosing the End other session to release lock option will log out your other PRPC session in order to release the lock. This option may not be effective immediately."

SR-A16026 · Issue 233285

Resolved validation error for saving section rule

Resolved in Pega Version 7.2.1

A Participant.FullName validation error occurred when trying to save a section rule when the Dynamic Layout with the .Participant.FullName property was above a repeat grid that has the Finish Assignment action specified for the Enter event. This was caused by a null clipboard page being passed in this configuration, and has been resolved.

SR-A16337 · Issue 232778

OCXinstaller install.bat script for Windows explicitly sets .cab file path

Resolved in Pega Version 7.2.1

The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.

SR-A16398 · Issue 232765

UI-Kit updated to use Open Work by Handle in pyFavorites

Resolved in Pega Version 7.2.1

In the Manager portal, clicking on a parent case in the "Following" section opened the subcase instead of the parent case that was being followed. The issue occurred when utilizing the pyFavorites section in a UI-Kit that was configured with the Open Work Item action. To correct this, the UI-Kit for this release has been changed to use the Open Work by Handle option.

SR-A16543 · Issue 235300

Resolved Interaction Portal unexpected close

Resolved in Pega Version 7.2.1

In Google Chrome, launching a secondary portal and encountering a Content Security Policy issue relating to an image caused the secondary portal to automatically close and the developer portal to be refreshed. This was an issue with a mismatch in the pyrequestor token, and has been corrected.

SR-A16582 · Issue 233320

Improved BIX extract handling for multiple active agents

Resolved in Pega Version 7.2.1

When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.

SR-A16621 · Issue 233386

Changed image tag to prevent auto-submit of calendar when parameters exceeded

Resolved in Pega Version 7.2.1

When user wanted to select the future date, he navigates by clicking the Year navigation link (arrow link). During this process of selecting a future date in the Year Navigation link, moving beyond the configured Number of years caused the page to be automatically submitted. This was caused by the input tag used for image causing a form submit, and tag has been changed to an anchor to fix this.

SR-A16678 · Issue 234858

Scrollbar retains position after focus change and return

Resolved in Pega Version 7.2.1

In the compliance score landing page, clicking on "All Warning" opens a window with a report of all the guardrail compliance warnings. If that window had a scrollbar, clicking on a rule in the guardrail report to view it in Designer Studio and then returning to the popup was resetting the scrollbar location to the top of the window. This has been fixed to retain the scrollbar position.

SR-A16736 · Issue 232994

Query table counts updated for IIF file with nulls

Resolved in Pega Version 7.2.1

While importing a jar through Import wizard in Designer Studio for a DB2 database, any Alter queries with SET NOT NULL or SET NULL fired the query 'CALL SYSPROC.ADMIN_CMD' to re-organize the altered table. That query generated the error "The number of host variables in the EXECUTE or OPEN statement is not equal to the number of values required" due to it not including the table names, and this has been fixed by populating the parameters in the place of '?' when downloading the SQL.

SR-A16915 · Issue 232937

Browser check added to TextArea for consistent rendering

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, an Enter key press / newline was calculated as two characters during rendering but as a single character in the character counter. This would cause the Text Area to behave differently depending on the browser. To avoid rendering issues, a check has been added to compensate for this difference.

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