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-B93011 · Issue 346343

Harness layout fixed for Work Area "Upgrade Now" using pyCWWorkList

Resolved in Pega Version 7.4

When upgrading the Work Area using the "Upgrade now" button, it was seen that a tab which called the Harness pyCWWorkList did not create a Harness Layout as expected but instead created a Section Include @baseclass.pxLocalAction, a deprecated function with an empty actionName. To resolve this. the pzDetermineOptimizedUpgrade activity has been updated so it will not optimize when a section include is configured with parameters.

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-131726 · Issue 202769

Fail-over updated to cover server crash scenarios

Resolved in Pega Version 7.1.9

In a testing event, the user session did not properly fail over to another server if the original server was shut down; an error was thrown instead. This was found to be an authentication issue where on node crash, a new requestor was created on the second node and then immediately authenticated as it is SSO. As part of authentication, the mRequiresSpecialProcessingForNodeCrash flag was cleared, meaning the node crash activity was not executed and entire portal was not refreshed. This has been corrected by updating the system to execute crash node activity for SSO cases.

SR-B85680 · Issue 341307

Ensured update details passed to WO conflict message

Resolved in Pega Version 7.4

With optimistic locking, when SLA is processing the work object and the assignment is submitted, the conflict information message shown to was blank. This was due to the Assign-.ExecuteSLA activity workPage being saved using Obj-Save, leading to the work page's pxSystemUpdateDetailsList not being populated and not having anything to pass when the page list is later used in preparing the conflict message. This has been fixed.

SR-B81856 · Issue 335124

Cursor behavior fixed in search text field

Resolved in Pega Version 7.4

The cursor was moving ahead when typing search text in a filter grid, causing typos. This was an unintended side effect of a fix to the method used when focusDomElement is called in settimeout, and has been fixed.

SR-B86181 · Issue 334246

Cursor behavior fixed in search text field

Resolved in Pega Version 7.4

The cursor was moving ahead when typing search text in a filter grid, causing typos. This was an unintended side effect of a fix to the method used when focusDomElement is called in settimeout, and has been fixed.

INC-191902 · Issue 677412

Updated security for importing Excel to a decision table via a delegated rule

Resolved in Pega Version 8.7

An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.

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-B86753 · Issue 339777

Mouse resize of modal dialog fixed

Resolved in Pega Version 7.4

After opening a flow in a modal dialog and resizing the first window by using the mouse (drag bottom-right corner), the resize option disappeared after proceeding to the next assignment. In this case, when back-to-back assignments were executed in the modal dialog, the resizehandler was not registered when navigating to the second assignment as the modal dialog was not initialized again but instead used a section refresh. A script has now been added to call pega.u.d.modalDialogExtras in pzModalActionAreaContainer if the resize handler is not available for back-to-back assignments.

SR-C6035 · Issue 349019

Set urandom for Unix/Linux to resolve connection reset

Resolved in Pega Version 7.4

On a Unix system where securerandom.source is not set to /dev/random, running an installation on Oracle using a new version of the JDBC driver caused connection reset. To fix this, Djava.security.egd=file:///dev/urandom has been added to prpcUtils.xml and migrateSystem.xml for use when the database is Oracle and environment is Linux/Unix.

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