SR-D74057 · Issue 540059
Updated aria handling for Dynamic Layout Group 'Accordion'
Resolved in Pega Version 8.1.8
The Dynamic Layout Group display type 'Accordion' was not getting initialized properly on the browser developer inspector. This was traced to the aria-selected attribute set to always be true, and has been resolved by adding logic to set and unset aria- selected only on the active tab. When the tab is not active, then aria-selected will be false.
SR-D76952 · Issue 542076
Popovers properly attached to elements while scrolling
Resolved in Pega Version 8.1.8
Account overlay popups were fixed to the screen, causing the popover to not be attached to its associated element while scrolling. This has been resolved with the addition of the needed scroll handlers.
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-184040 · Issue 688255
Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns
Resolved in Pega Version 8.6.4
When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.
INC-187350 · Issue 703198
UUID added to iOS direct photo upload to differentiate filename
Resolved in Pega Version 8.6.4
When "Content Storage" with the option "Store in repository" was enabled on the "Integration" tab in the Application definition, it was not possible to add more that two attachments to a case with an iPhone when directly capturing a photo through the camera app instead of uploading the photo as an attachment using the gallery. When using the default "Store in Pega database", the additional photos could be uploaded directly from an iOS camera without any errors. Investigation showed that when "Store in repository" was enabled, a file name conflict check was done in the repository. Because the iOS camera app saves/uploads every image as "image.jpg", this caused the error when checking for a filename conflict in the repository. This has been resolved by adding code to append a UUID to the attachname when the device is mobile and browser is Apple Safari.
INC-192673 · Issue 689554
Tab highlighting updated
Resolved in Pega Version 8.6.4
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.
INC-194180 · Issue 704638
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.6.4
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.