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-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.

SR-B74214 · Issue 329140

Null check added to contextClass

Resolved in Pega Version 7.4

If a contextClass was empty, multiple activities, including out-of-the-box activities, would intermittently fail with a NullPointerException. A null check has been added to resolve this.

SR-B75227 · Issue 330906

Performance improvements for opening a Data instance

Resolved in Pega Version 7.4

Logic improvements have been made to improve the performance of opening a Data instance from rule explorer.

SR-B75670 · Issue 328342

Lock & Roll correctly copies data types to new application copy

Resolved in Pega Version 7.4

After upgrade, using the "Lock & Roll" feature to create a new version of the application resulted in the data types not being correctly copied. This was due to a code error in the step "Locking the release", and has been fixed.

SR-B75713 · Issue 336535

Addressed "Cover count -1" error when resolving case with parent and child

Resolved in Pega Version 7.4

A "Cover count -1" error was appearing when resolving a case with both parent and child cases. The "Resolve" activity has been updated to remove the pyTopCaseWork page if findPagebyHandle returns that page and then do findPagebyHandle to get correct cover page. A null check for updatedatetime has also been added.

SR-B77120 · Issue 330083

Writability check added to ClipboardPage

Resolved in Pega Version 7.4

A node level declare page was failing with a readonly exception. This was caused by the assembler generating code to write to a ClipboardPage without checking whether it was writable, and has been corrected by adding a check for isReadOnly on ClipboardPage prior to calling putString on it.

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