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-A67005 · Issue 251958

Work-.Close function updated to resolve "Flow not at task" error

Resolved in Pega Version 7.2.2

The Work-.Close function has been updated to improve synchronization between operators in cases where having a combined standard flow and screen flow as a sub flow could cause a "Flow not at task" error as one operator moved forward and the other subsequently tried to save an already open work object.

SR-A76914 · Issue 252778

Short Description parameter cleared every loop to ensure data integrity

Resolved in Pega Version 7.2.2

When adding the coverable work types in a case, the description which comes in the Actions menu was not correct due to the Short Description parameter not being cleared. This caused the same description to be used for the next flows. To fix this, the system will now clear the parameter Short Description in the activity LookupCoverableProcessList at the end of every loop, ensuring every flow takes its own short description.

SR-A24246 · Issue 248666

Event size difference on calendar corrected

Resolved in Pega Version 7.2.2

When using the out-of-the-box calendar gadget to display some events apart from the worklist goals and deadlines, an event shown on the calendar was correct in the monthly view but had the wrong time and duration in the daily view. This was traced to the way the height of the div tag was calculated in different functions, and has been corrected.

SR-A38578 · Issue 253239

Population handling added for null value flowType property

Resolved in Pega Version 7.2.2

While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.

SR-A77119 · Issue 255525

Fixed attaching files to pre-existing inflight cases after upgrade

Resolved in Pega Version 7.2.2

After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid ". This was caused by a missing check for LinkPage.pyMemo if LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.

SR-A88588 · Issue 256536

TopCasePage reference retained in CreateTopCase

Resolved in Pega Version 7.2.2

After upgrade, the "pyTopCasePage" page reference was missing in the Clipboard after a new case was created using the "pxCreateTopCase" activity in utility shape in a flow. This was traced to a step in the function that removed the pyTopCase page reference unnecessarily, and the pxCreateTopCase activity has been modified to preserve this.

SR-A90516 · Issue 258175

Resolved App Express error for new operator groups

Resolved in Pega Version 7.2.2

An error was appearing while creating a operator access group via App Express. This was an error in the commit while saving process if the entry in pyObjectsToCreate was FrameWorkAssets, and has been fixed.

SR-A86964 · Issue 256956

Corrected date value created by ShowConflicts

Resolved in Pega Version 7.2.2

An invalid format date value was being created by the "pzShowConflicts" activity, causing problems when trying to submit an assignment updated by another agent. This has been fixed by setting the value with the PRDateFormat.DEFAULT_DATETIME_MEDIUM format instead of DD-MM-YYYY.

SR-A82879 · Issue 254116

FilterHistory WRITE_NONE correctly stops all audits

Resolved in Pega Version 7.2.2

Changing the system settings rule "FilterHistory" from WRITE_SOME to WRITE_NONE was still running an audit when the stage changed instead of completely stopping all auditing. This was due to an RUF call to ADDHISTORY without checking the DSS, and a check has been added to fix this.

SR-A87755 · Issue 256118

Fixed Dynamic Class Reference use for the workbasket name in Wait shape

Resolved in Pega Version 7.2.2

Error "Unable to open assigned's Data-Admin-WorkBasket record" was thrown when using a Dynamic Class Reference to refer the workbasket name in Wait shape. This was traced to the Workbasket in the Wait shape being quoted, leading to the property reference not being honored The quoting of the workbasket has been removed in the pzAfterWait.

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