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-A11447 · Issue 243018

Importing an archive no longer fails when using DynaTrace

Resolved in Pega Version 7.2.1

Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.

SR-A14359 · Issue 232227

Context-aware paths for SMA jmxclient.css and global.js files

Resolved in Pega Version 7.2.1

In some cases the jmxclient.css and global.js files were not found when running SMA due to the use of relative path names. The path names have now been made context-aware.

SR-A14386 · Issue 230949

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 my more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.

SR-A14619 · Issue 229625

Alignment resolved for repeating grid headers

Resolved in Pega Version 7.2.1

Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.

SR-A15710 · Issue 236472

Additional logging added to diagnose stale thread errors

Resolved in Pega Version 7.2.1

In order to better diagnose issues with stale threads, loggers have been added to the ThreadData class to capture and print any stack trace which is causing the thread to be cleared or destroyed. These loggers will only be printed whenever a stale thread error is thrown in order to maximize log space.

SR-A15710 · Issue 236472

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

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-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-A16406 · Issue 231876

Validation handling added for complex criteria values

Resolved in Pega Version 7.2.1

Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.

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.

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