SR-D47146 · Issue 515647
Pick Values modal updated for deprecated list view handling
Resolved in Pega Version 8.1.8
Pick values were not displaying in the menus below Case Management-> Tools -> My Work, including "Work entered by me", "Work by workbasket", and "Work resolved by me recently". This was due to the use of deprecated list views: the pick values modal was failing to show and hide the busy indicator because the indicator now uses jQuery, but list view does not include jQuery. In order to resolve this, the equivalent Report Definition pyEnteredByMe has now been added under the navigation rule : pzProcessAndCaseRulesMainMenu.
SR-D59504 · Issue 524641
Attachment drag drop searches only current Ajax context
Resolved in Pega Version 8.1.8
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 547842
Updated retry logic for S3 AddAttachmentFromEmail
Resolved in Pega Version 8.1.8
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-D80120 · Issue 544216
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.1.8
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.
INC-188469 · Issue 714844
Updated retainLock for DoClose activity
Resolved in Pega Version 8.6.5
After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.
INC-208394 · Issue 713554
Error handling updated for Data-Work-Attach-File
Resolved in Pega Version 8.6.5
If a file is uploaded which has the same name as an existing case attachment or if any issue happens during file attachment, the attachment will fail and an error message is displayed with an option to cancel the operation. However, even if the upload was not successful the related Data-WorkAttach-File instance was created and persisted in the Workattach table. Investigation showed this was caused by the process for persisting the Data-WorkAttach-File record occurring prior to the process that returns the errors, and this has been resolved.
INC-209404 · Issue 710406
MultiFilePath supports file upload with leading special character
Resolved in Pega Version 8.6.5
Updates have been made to the pzMultiFilePath control in order to support uploading a file with a special character such as "%" at the beginning of the name.
INC-210787 · Issue 710393
Multiple child case assignments open correctly in Ajax container
Resolved in Pega Version 8.6.5
After configuring two cases with a parent-child relationship, the child case was configured with a parallel process with two assignments. When trying to open the child case assignments in an Ajax container, only the first assignment would open. Investigation showed this was caused by the "reloadAlways" parameter not being sent to openAssignment due to a custom control being used. To resolve this, the reloadAlways has been added as an argument to the OpenAssignment function call in pyAssignmentsLabel.
INC-213654 · Issue 726002
Logic added to skip FLAudit class during compliance check
Resolved in Pega Version 8.6.5
An application compliance error was seen related to classes starting with FLAudit, which are created as part of field level audit history for the classgroup validation. This has been resolved by adding an extra condition to the Rule-Obj-Class-.Validate activity to check if inheritance is from "FLAudit-" class, and if so to skip them as their purpose is similar to History- classes which are ignored for the class group validation.
INC-215354 · Issue 712665
Data- flow actions working in Bulk Process
Resolved in Pega Version 8.6.5
When trying to render a flow action whose 'applies to' class was inherited from Data-, an error was generated indicating that the flow action could not be found. This was traced to non Work- flow actions not being correctly populated, and was an inadvertent side effect of work done to set class for inheritance if Work- is not present. This has been resolved by updating the pzPreBulkProcessModal activity to set the TempWorkPage class to Work- only if .pyActionName is pyTransferAssignment.