INC-131296 · Issue 569578
Updated duplicate file name handling for drag and drop
Resolved in Pega Version 8.4.2
When files with the same name were attached with drag and drop, the files were being overridden and became visible to non-authorized users. This has been resolved by using the AppendUniqueIdToFileName parameter when using the pzMultiFilePath control which will append a unique ID to the fileName and pass it in the request along with the file data.
INC-131385 · Issue 573456
Swagger APIs updated
Resolved in Pega Version 8.4.2
The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .
SR-D72456 · Issue 561119
Added duplicate page handling for Bulk actions
Resolved in Pega Version 8.4.2
Trying to resolve cases using Bulk Actions and Bulk Resolve resulted in the exception "Trying to save an invalid page. The cover open count is incorrect; it is -1". This was traced to duplicate pages available on the clipboard with same the insHandle. To resolve this, the pzUpdateAndDeleteAssignments activity has been updated to check for duplicate pages, then pick the right page which is not being served by the findPageByHandle engine API.
SR-D85664 · Issue 559012
Added handling for flow Status values over 32 characters
Resolved in Pega Version 8.4.2
After upgrade, flows were throwing exceptions due to the 32 character limit for the Status field, causing issues for flows where the status on the case is determined dynamically based on value from expression builder. To resolve this, the limit has been removed on the property and a validate rule has been added that will only use the 32 character limit to check static plain text.
SR-D87898 · Issue 552590
SaveAttachment Activity in Data-WorkAttach-URL updated
Resolved in Pega Version 8.4.2
A 'when' condition was not properly evaluated for Activity SaveAttachment (CL:Data-WorkAttach-URL ), causing the Next assignment screen to not be displayed. This has been resolved by modifying the handling of Page Names used as activity parameters to remove the use of the specific PageName "pyAttachmentPage" in the operation and make it generic to Primary in the SaveAttachment Activity of CL: Data-WorkAttach-URL.
SR-D92352 · Issue 553618
Completed onChange will reset FileInput value to null
Resolved in Pega Version 8.4.2
When attaching a file using the "Select File" button, it was not possible to attach the same file after deleting it. Re-attaching the file worked as expected when using Drag and Drop. Investigation showed that the onchange event occurred only when the value of an element was changed, so in this case trying to attach the same file did not change the value of the element and did not fire the onchange. To resolve this, the value of FileInput in pzMultiFilePath Control will be set to null at the end of the onChange event so that an onChange event will be triggered next time even if the same file is added.
SR-D96254 · Issue 555277
ViewID parameter passed as part of DX API response payload for all application levels
Resolved in Pega Version 8.4.2
When application level was set to '5' (Production), the DX API was configured to skip passing 'ViewID' parameter as part of response payload. This only applied to application level '5' and not to other levels. In order to support enhanced customization, the system has been modified to not consider production level and always pass 'viewID' parameter as part of DX API response payload.
SR-D97673 · Issue 561504
Assignment opens correctly in tabbed AJAX container
Resolved in Pega Version 8.4.2
When opening a case in review mode and then clicking the assignment link, the assignment opened in a new browser window instead of opening in the tabbed AJAX container. This was due to the AJAX container being stateless: directly opening the assignment with href replaced the entire document. To resolve this, the "pega.desktop.openassignmnet" API will be used.
SR-D98336 · Issue 558994
V1 DX API response now includes "Label" or "Header Title"
Resolved in Pega Version 8.4.2
When FlatList was opted to 'Full', the GET and PUT calls made to get the JSON response for an action did not return the header object information of that group. This has now been modified so the labels are returned in the V1 API response.
INC-147457 · Issue 621708
Elapsed time in Work History Table includes sub-flow
Resolved in Pega Version 8.4.5
Elapsed times were not captured when an assignment was in a wait shape followed by a utility which set a ticket and moved the assignment to a sub-flow. Investigation showed that when flow execution is in a sub-flow and a ticket is raised, the assignment in sub-flow was removed but audit history was not captured. To handle this scenario, the functions pzCleanSplitForTicket and pzRemoveFlowForTicket have been added, and FlowMethodBody FUA has been modified to include pzCleanSplitForTicket instead of CleanSplit.