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- · Issue 319981

Field labels localized in pyAccountSettings

Resolved in Pega Version 7.4

Localization has been added to the field labels in the pyAccountSettings section rule.

SR- · Issue 324033

Files updated to resolve memory leaks

Resolved in Pega Version 7.4

The following files have been updated to address memory leak issues when processing a large number of cases: PZPEGA_UI_DYNAMICCONTAINER_LITE PZPEGA_PROCESS_ENGINE PEGA_TOOLS_EVALDOMSCRIPTS PZPEGA_UI_DOC_LIFECYCLE PZPEGA_CONTROL_DROPDOWN

SR-B47513 · Issue 328997

Logic updated for expandAll to resolve CME

Resolved in Pega Version 7.4

A concurrent modification exception was appearing on a node level page when using expandAllToproperties due to two threads simultaneously trying to expand the page. This has been fixed by modifying the logic in expandAll(true, true).

SR-B64115 · Issue 330040

Handling and logging added for null PRThread tenant ID

Resolved in Pega Version 7.4

In cases where no PRThread was not found from the thread container when writing a ruleset index to DB, the tenant ID was lost and the system used the default "Shared". This resulted in a tenant RSL shown twice in the DB, one as the tenant itself and the other as Shared. Two changes have been made to resolve this: first, debug logging has been added to the stack trace if the thread is null, and second, if this happens in a MT environment, the system will skip writing to the DB so the tenant TSL will not be given as Shared.

SR-B64115 · Issue 329896

Handling and logging added for null PRThread tenant ID

Resolved in Pega Version 7.4

In cases where no PRThread was not found from the thread container when writing a ruleset index to DB, the tenant ID was lost and the system used the default "Shared". This resulted in a tenant RSL shown twice in the DB, one as the tenant itself and the other as Shared. Two changes have been made to resolve this: first, debug logging has been added to the stack trace if the thread is null, and second, if this happens in a MT environment, the system will skip writing to the DB so the tenant TSL will not be given as Shared.

SR-B67903 · Issue 330405

Params passed to createNewWorkWithParams and displayed

Resolved in Pega Version 7.4

An issue with createNewWorkWithParams where parameters were not displayed in the UI even if they were available in the pyWorkPage was traced to a code function-ordering error with passing parameters to createNewWorkWithParams that caused Work Page data that was set in CreateNewWork to be overridden before it was used. This has been corrected in the process engine createNewWorkAction.

SR-B67903 · Issue 331567

Params passed to createNewWorkWithParams and displayed

Resolved in Pega Version 7.4

An issue with createNewWorkWithParams where parameters were not displayed in the UI even if they were available in the pyWorkPage was traced to a code function-ordering error with passing parameters to createNewWorkWithParams that caused Work Page data that was set in CreateNewWork to be overridden before it was used. This has been corrected in the process engine createNewWorkAction.

SR-B70116 · Issue 328876

Missing backlink fixed for deferred save

Resolved in Pega Version 7.4

Reference errors were generated when opening a work object on an end user portal due to the backlink on an empty source property being lost during a deferred save operation. This has been fixed.

SR-B73244 · Issue 332729

mParams changed to local maps in PresenceSessionStateTrackerDaemo.java

Resolved in Pega Version 7.4

In order to resolve a managed connection CME error and memory leak for java:/eis/PRAdapterConnectionFactory when using JBoss 6.4 EAP with Oracle 12c DB, the mParams member variable in PresenceSessionStateTrackerDaemo.java has been removed. Local maps in startThreadInETier() and requeueETierInvocation() will be used instead.

SR-B74096 · Issue 327439

Special German characters encoded in URL

Resolved in Pega Version 7.4

Microsoft Internet Explorer was not encoding some German characters, resulting in unexpected special characters being sent to the engine in a URL as parameters that resulted in crashing the application. The HttpAPI and URLComponentProcessor have been modified to solve the issue by encoding the queryString if it isn't already encoded.

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