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-B13088 · Issue 287632

SLA correctly reset after reassignment

Resolved in Pega Version 7.3

When the SLA values were updated on routing the task, the newAssignPage and assign table were updated with the new SLA details but the pxFlow page was still holding the old SLA values. This caused the updated SLA details to not be displayed in the out-of-the-box pyAssignmentListGadget section. This was an issue with the pxAdjustSLA and Reassign activities not completely updating the embedded page pxFlow in the WorkPage completely, and has been fixed.

SR-B13418 · Issue 283237

Attachments removed when work object withdrawn

Resolved in Pega Version 7.3

After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.

SR-B13702 · Issue 287232

SLA correctly calculated for migrated rules

Resolved in Pega Version 7.3

After upgrade, using the case designer view to look at a case type created in an earlier version displayed errors in the right panel for the goal-HH:MM:SS and deadline-HH:MM:SS fields if the assignment had the SLA rule "Default". This was an error in backwards compatibility related to whether the "pzIsAutoGenerated" property used to distinguish the SLA was auto generated or not, and has been corrected by setting the Visibility condition .pzAutoGenerated to 'true' in the lower Dynamic layout to avoid a null value in migrated rules.

SR-B13872 · Issue 290520

StartDependencies RUF logging updated from Error to Debug mode

Resolved in Pega Version 7.3

After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.

SR-B14774 · Issue 285008

Optional Process Child Case correctly sets ObjectClass

Resolved in Pega Version 7.3

When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.

SR-B14774 · Issue 285027

Optional Process Child Case correctly sets ObjectClass

Resolved in Pega Version 7.3

When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.

SR-B15604 · Issue 286328

Made InputProperty not mandatory for business logic

Resolved in Pega Version 7.3

When business logic is selected, pzToDecisionTreeExpress is selected as the routing activity for the assignment. However, errors occurred due to the mandatory parameter InputProperty property being passed as empty. To address this, the parameter will be marked as not mandatory.

SR-B16331 · Issue 303039

Check added to WorkUnlock to ensure cover page exists

Resolved in Pega Version 7.3

An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.

SR-B16331 · Issue 294717

Cover page check added to Work-Close

Resolved in Pega Version 7.3

An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.

SR-B16784 · Issue 287160

Attachments removed when work object withdrawn

Resolved in Pega Version 7.3

After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.

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