SR-D80149 · Issue 545604
Correct very large decimal number rounding error
Resolved in Pega Version 8.1.8
Rounding errors were seen in a text input field for decimal property configured to round to 2 decimal places and format with comma group separators if more than 15 digits were entered. The first time the focus moved out of the field, the rounding was correct. After clicking save, which performed a reloadSection with activity SaveAndContinue (form save), the value was rounded incorrectly. This was an issue with the ability of javascript to handle large decimal numbers as type number, and has been resolved by changing the handling to be of type string.
SR-D80798 · Issue 545241
Updated attachment popover handling for IE
Resolved in Pega Version 8.1.8
After configuring a button consisting of two events, 1. On click --> View Attachment and 2. Hover --> Show Smart info, an attachment popup opened whenever the button was clicked, and moving the cursor out minimized the attachment. To resolve this, dismiss callback logic has been added in popover close for use with IE.
SR-D81341 · Issue 546006
Scroll bar scrolls to element automatically with Set Focus
Resolved in Pega Version 8.1.8
An issue with the Scroll bar not scrolling automatically to the correct element when using Set Focus has been resolved by including element select logic in settimeout.
SR-D86937 · Issue 546935
Cross-site scripting protection added to ClientDynamicData
Resolved in Pega Version 8.1.8
Cross-site scripting protection has been added to the "DesignViewIframe" & "pzHarnessID" parameters in the pzClientDynamicData HTML rule.
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.