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-115127 · Issue 163700

Viewing generated Java code with Tracer

Resolved in Pega Version 7.1.7

Previously, Tracer automatically returned the source for generated Java. This functionality was inadvertently removed, and has been restored.

SR-115313 · Issue 164520

BIX execution history did not update all Extracted rules

Resolved in Pega Version 7.1.7

If a BIX (Business Intelligence Exchange) extract was run with two extracts from the same shell script, the execution history was updated for only one of the extract rules. This was caused by the entry in the execution history (pr_log) is being overridden when the -i command line option is used. To ensure complete logging, the system has been updated to add a new entry to pr_log for every value when invoking the -i option.

SR-115719 · Issue 165692

WebSphere WorkManager pool setting correction

Resolved in Pega Version 7.1.7

Due to a coding defect, the WorkManager thread pool setting configured through WebSphere was not being utilized. As a consequence, a large number of daemon threads could be created during certain scenarios and the ability to make connections could be reduced. This has been fixed, and the system will now use the WebSphere WorkManager setting.

SR-115955 · Issue 167257

Enhanced task queue handling for custom applications

Resolved in Pega Version 7.1.7

In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.

SR-119432 · Issue 175615

Enhanced task queue handling for custom applications

Resolved in Pega Version 7.1.7

In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.

SR-116130 · Issue 168010

StackOverflow errors during passivation remedied

Resolved in Pega Version 7.1.7

An issue was found with StackOverflow errors thrown by the passivation daemon, requiring a restart of the JVM. This was found to be related to the AutoPopulate API, and has been updated.

SR-116146 · Issue 169058

CreateUniqueID enhanced to allow custom instances

Resolved in Pega Version 7.1.7

The out-of-the-box PopulateReport activity previously used shorthand notation when referencing the CreateUniqueID function instead of referencing the function using the RuleSet or library name. This caused an issue with systems that contained a custom version of CreateUniqueID in the CMSUtilities library, resulting in "Multiple suitable instances found" errors. In order to accommodate custom instances of CreateUniqueID, long hand notation will be used for matching in place of shorthand.

SR-116157 · Issue 165994

Improved crash recovery in a complex system

Resolved in Pega Version 7.1.7

During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress.

SR-116556 · Issue 170813

AllLinksForParticularRule changed from Final to Available

Resolved in Pega Version 7.1.7

The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500.

SR-116585 · Issue 167063

Screen flow previous button repaired in obfuscated IAC

Resolved in Pega Version 7.1.7

When using IAC with obfuscation is enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed.

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