SR-D68235 · Issue 534781
Stale WorkSearchPreference data cleared when switching apps
Resolved in Pega Version 8.3.3
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-D84480 · Issue 546187
FilterHistory decision tree used for audit log status
Resolved in Pega Version 8.3.3
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-D39264 · Issue 518839
Multiple files uploaded using "select file" will be handled asynchronously
Resolved in Pega Version 8.3.2
In order to resolve an intermittent error when uploading multiple files using the "select file" button, each file will be uploaded asynchronously to avoid overloading the browser threshold.
SR-D92352 · Issue 553615
Completed onChange will reset FileInput value to null
Resolved in Pega Version 8.3.3
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-D51535 · Issue 519474
Enhanced discrimination for tasks in MyPega spaces
Resolved in Pega Version 8.3.2
When using My Pega for spaces and tasks, using drag and drop to move many cases around quickly resulted in tasks intermittently ending up in a state where they could not be updated further and became unusable. Analysis showed that because the milliseconds part of the update time was rounded, the logic of comparing for value between 0 and 1000 failed when the comparison returned -ve value. To resolve this, the comparison has been modified to !=0 and the 'when' rule pyContinueTaskProcessing has been added as an extension along with the appropriate usage guide to restrict processing. By default, the system will consider task name, description, due date, assignee, and rank properties; if more properties are needed to evaluate, this when rule can help.
SR-D87898 · Issue 552588
SaveAttachment Activity in Data-WorkAttach-URL updated
Resolved in Pega Version 8.3.3
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-D90528 · Issue 550665
Localization added to File upload alerts
Resolved in Pega Version 8.3.3
When uploading files as part of adding attachments, error and warning messages were displayed as alerts in English despite using localization. This was traced to the pzMultiDragDropControlStandard control rule having the HTML alert messages hard coded instead of using field values which could be localized. To resolve this, field values have been created for the messages related to DragDropMaxSize, FileNotExistMessage, FileUploadSupportMessage, and UnableToLoadFileMessage.
SR-D88141 · Issue 550008
TemplateButton field correctly set read-only
Resolved in Pega Version 8.3.3
When a control was added to a section using the DX API, a pyTemplateButton field was added to the XML definition of the section with read-only set to 'false'. This has been corrected so the pyTemplate Button field does not allow input.
SR-D59504 · Issue 524640
Attachment drag drop searches only current Ajax context
Resolved in Pega Version 8.3.2
When the Interaction for customer service was open and more than 1 task from the sidebar was open, the drag and drop zone was missing on any subsequent Task/Cases past the first. In an Ajax container scenario, getElementByID js was searching in all the containers because they were present in DOM, and it was losing context. To resolve this, the code has been updated to only search in the current context when using an Ajax container.
SR-D76291 · Issue 547839
Updated retry logic for S3 AddAttachmentFromEmail
Resolved in Pega Version 8.3.3
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.