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.
SR-D68235 · Issue 534783
Stale WorkSearchPreference data cleared when switching apps
Resolved in Pega Version 8.4.1
The D_pyWorkSearchPreferences data page data was not refreshing while switching between apps, causing stale data to be populated under the case search dropdown for all the applications after switching the application from one to another. This has been resolved by removing the D_pyWorkSearchPreferences data page as part of pzProcessApplicationSwitch.
SR-D73536 · Issue 538403
FetchApplicationLogo modified to Filter by rule resolution
Resolved in Pega Version 8.4.1
It was observed that the Report Definition rule "pzFetchApplicationLogo", referenced by Activity rule "pzLoadApplicationLogo", always returned the older version of the Binary File "webwb • pyapp-logo • svg" because it had been set to retrieve a maximum of one record and in this case the results were sorted in an order where the oldest record was at the top. As the Report Definition did not indicate any sorting, most DBMS were returning the results in no particular or predictable order. To resolve this, "Filter by rule resolution" has now been enabled for RD pzFetchApplicationLogo.
SR-D76291 · Issue 547843
Updated retry logic for S3 AddAttachmentFromEmail
Resolved in Pega Version 8.4.1
When using the AddAttachmentFromEmail activity with S3 repositories, performing an obj-save on the data-workattach-file page executes a deferred save while also saving the file into the repository. if the data was inserted into S3 successfully but encountered an issue when saving the related data-work-attach-file page, the system was trying to call the save operation again. This tried to insert the duplicate attachment again to S3, causing an error on that side of the process. To resolve this, the duplicate Obj-Save functionality in AddAttachmentFromMail Activity has been removed.
SR-D79113 · Issue 543723
Updated DisplayAttachment to handle SIngleClick download from Case Worker portal
Resolved in Pega Version 8.4.1
On using the script "pega.ui.HarnessActions.doAttachmentSingleClick" in the Worker portal to download attachments displayed within a screen flow, the entire application was hanging and no action was invoked even on clicking the Continue or Finish buttons of the screen flow. Whenever an attachment is downloaded using the script function pega.ui.HarnessActions.doAttachmentSingleClick() , an iframe is used and changetracker is called to communicate data between different iframes. However, the case worker portal is a single thread model while the manager and admin portals are multi threaded, which resulted in changetracker freezing on the worker portal. To resolve this, the DisplayAttachment HTML rule has been updated to build the necessary changeTrackerMap for the worker portal.
SR-D84480 · Issue 546189
FilterHistory decision tree used for audit log status
Resolved in Pega Version 8.4.1
Attempting to use the “FilterHistory” decision tree in the work class to return value “false” for “pyCloseOpenAssignmentsOnResolution” to hide the “pyCloseOpenAssignmentsOnResolution” field value (“Unfinished assignments were cleaned up by the system after the completion.. ”) from history was not working as expected, and still returned the audit message. This was due to the system setting this AuditNote parameter within the “pzProcessResolutionStage” activity, where Param.UpdateHistory was set to true always. In order to support more flexibility, the Param.updateHistory paramter in step3 of the pzProcessResolutionStage activity will be set based on the FilterHistory decision tree. When set to false in FilterHistory decision tree, pyCloseOpenAssignmentsOnResolution will be set as false and audit will not be logged.
SR-D84754 · Issue 548165
Resolved erroneous problem assignment error
Resolved in Pega Version 8.4.1
If a user processed a work item while the SLA agent was also attempting to process it, it sometimes resulted in an assignment with the error: "Error: Flow Not At Task." In this scenario, an error message was displayed stating that "Assignment already completed" even though the assignment was not yet finished, causing confusion. Investigation showed that in cases where the success indicator was -28, the assignment was marked as problem assignment even though it was processed. To resolve this, the system has been updated to skip marking the assignment as a problem when the success indicator is -28.