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.

INC-136208 · Issue 585227

Case history filter added for manual instantiation of Child Case

Resolved in Pega Version 8.6

After upgrade from v7.4 to v8.3, creating any child case from a parent case unexpectedly added the audit history "Child case xxxxx has been manually instantiated" to the parent case. In order to make this customizable, an "isHistoryAvailable" function has been added in the 'when' condition of "AddCoveredWork" Activity's "History-Add" Step. This will use the FilterHistory decision tree, which now has a setting for "ChildCaseInsAudit" to control whether or not the manual Instantiation of a Child Case will appear in the case history. The default is "true"; setting it to "false" will suppress the message.

INC-136327 · Issue 591467

Stage keeps proper order placement on restart

Resolved in Pega Version 8.6

When a user restarted a stage, the stage moved to the end of the list of stages and stayed there even when completed. Investigation showed that when pxRestartStage was configured as a post-processing activity for a flow action, pxStageHistory was updated with a new list item which considered pxCameFrom and pxStageId as the same. Due to this, the current stage was moved to last in the chevron. This has been resolved by adding a new 'when' condition to pzLoadStageStatusDP that will skip the item of pxStageHistory (Alternate stage) if both .pxCameFrom and .pxStageId are same.

INC-136641 · Issue 586516

OpenIfStale updated to resolve optimistic locking race condition

Resolved in Pega Version 8.6

A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.

INC-138348 · Issue 599769

Added parameter skipPropertyEvaluation to handle CSS in email HTML

Resolved in Pega Version 8.6

While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent. In order to skip the evaluation that removes and replaces the braces, the skipPropertyEvaluation must be checked.

INC-139074 · Issue 587812

Email handling security updated

Resolved in Pega Version 8.6

Cross site scripting protections have been enhanced for email activities.

INC-141751 · Issue 596135

DragAndDrop attaching large file properly disables 'X'

Resolved in Pega Version 8.6

When a large file was attached using the DragAndDrop feature, the 'X' icon/button was not disabled. This made it possible to click 'X' and perform other actions during the upload, which caused the screen to freeze and required a browser refresh to continue the work. This was traced to incomplete work done on large file uploads, and has been resolved by ensuring the busy Indicator shown will be applied to the complete screen to avoid any other actions being performed.

INC-142660 · Issue 595392

Pega API system management launches correctly from Help

Resolved in Pega Version 8.6

The Pega System Management API did not work when launched from help window, although other APIs such as Case Management were working fine. This has been resolved by updating the basePath in pzSystemManagementDocumentation.

INC-143025 · Issue 600608

API performance improvements

Resolved in Pega Version 8.6

Performance improvements have been made for running the get assignment action details API.

INC-143861 · Issue 597556

pzIsScalar 'when' rule updated for Value list and Value group

Resolved in Pega Version 8.6

When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.

INC-144265 · Issue 609286

Updated timestamp handling for duplicate key issue with PyCompleteAutomation

Resolved in Pega Version 8.6

Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.

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