INC-155587 · Issue 621840
Handling added for controls applied directly to parameters
Resolved in Pega Version 8.5.3
After upgrade, the section displayed by the out of the box flow action pyDisplayRolesOfApplication was not displaying the role count and application name, instead highlighting values as null. Beginning with Pega 8.4, completely templated mode changes were introduced to repeating dynamic layouts. This led to parameter values which should have been passed to the field parameter to be missed because a control was added to the parameters explicitly. This has been resolved.
INC-155648 · Issue 617396
Corrected reference of PropertyExists in pyAdjustSLAPostAction
Resolved in Pega Version 8.5.3
The PropertyExists function was returning incorrect results. This has been resolved with the addition of a 'property exists' check in pyAdjustSLATimes.
INC-159334 · Issue 626764
Handling added for custom attachment method
Resolved in Pega Version 8.5.3
When sending a correspondence using the standard SendSimpleEmail activity, choosing only one attachment from the multiple attachments in the work object by passing the pxLinkedRefTo property from the clipboard page to the AttachmentKeysToSend parameter instead of passing the value to the AttachmentCategoriesToSend parameter successfully sent the message and attached it to the work object. However, opening the correspondence attached to the work object showed the attached file as blank even though the attachment was present in the receiver�s email. Research showed that during the comparison of keys in place of pxLinkedRefTo, pzinskey was used. This caused the comparison to not register as true and the attachments display was skipped. This has been resolved by updating the Data-Corr-Email.Show Html rule to use the pxLinkedRefTo field to find the right attachment. The URL encryption was also updated to ensure the links are functional and attachments can be downloaded.
INC-160078 · Issue 628840
Work object status correctly set to Resolved after refresh
Resolved in Pega Version 8.5.3
When using the Refresh option from the Other Actions menu before submitting the flow action, the work object status was not updating to Resolved-Completed. Investigation showed that when performing the Refresh action, the RefreshOnConflicts activity created a Clipboard page named LatestWorkPage with a copy of the work object. This page was not removed after use, causing the Resolved-Completed status to be set on LatestWorkPage instead of pyWorkPage. To resolve this, a step has been added to RefreshOnConflicts to remove LatestWorkPage.
INC-160115 · Issue 627651
Editing Approval flowshape retains decision tree
Resolved in Pega Version 8.5.3
Editing the Approval flowshape caused the decision tree to become blank when selecting 'Use Business logic' in the dropdown for "Route to dropdown". This was traced to a missed use case for earlier work done on enhancements for email approver shapes regarding retaining previous values while switching back to using the business logic option, and has been resolved.
INC-160420 · Issue 627961
RefreshFor correctly returns validation messages
Resolved in Pega Version 8.5.3
After upgrade, the PUT method on /api/v1/assignments/{ID}/actions/{actionID}/refresh?refreshFor was not returning validation messages on the child level. This was an unintended consequence of refactoring work done on pzApiCreateJsonForField around the default value calculation, and has been resolved.
INC-167606 · Issue 665869
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.6.2
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651079
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.6.2
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
INC-171842 · Issue 664387
Visible element populated for field value controls
Resolved in Pega Version 8.6.2
When implementing a section which had several labels with visible when conditions, this is not reflected in the DX API Get Assignment View. This has been resolved by adding a visible element.
INC-173068 · Issue 654067
HTML tags escaped in Audit History field values
Resolved in Pega Version 8.6.2
The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@#$ %^& amp;*&# 40;&# 41;_&# 43;.". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.