SR-D73260 · Issue 536889
Multiselect control support for offline-enabled iOS app
Resolved in Pega Version 8.1.8
After a custom mobile application for iOS was built and was running on iPad for an offline-enabled user adding a multiselect control into a section as part a flow caused the screen to hang when a save or submit was performed. This has been resolved by enhancing support for offline multiselect submit with the addition of pzpega_ui_template_multiselect_capsule to offline static bundle.
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-135335 · Issue 588510
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.5.1
A Breadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.
SR-D77719 · Issue 569769
OpenIfStale updated to resolve optimistic locking race condition
Resolved in Pega Version 8.5.1
A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.
INC-134912 · Issue 581326
Handling updated for wait shapes with different outgoing connector flow actions
Resolved in Pega Version 8.5.1
After configuring a flow with a wait shape that by default used the pyContinueAfterWait flow action for the outgoing connector of the wait shape refer, adding any other valid flow action resulted in the error "Action To Take must be a valid flow action for this assignment". This was due to the post-processing of the connector properties modal updating the ActionToTake value based on wait shape, so that changing the flow action on a connector caused the validation on save to fail if the ActionToTake on wait shape and the connector flow action did not match. To resolve this, the system has been modified to validate a wait shape with different flow action on the outgoing connector.