SR-D72121 · Issue 536408
Currency Control accepts value on PostValue action set
Resolved in Pega Version 8.3.2
Currency control in the section was sourced by a decimal property. Irrespective of the value entered, the validation triggered the message "entered value is not a decimal value" and did not allow user to proceed. Investigation showed than on getting the server response for post value action, the target element was updated with the response value when it should be skipped for currency control. To resolve this, an additional check for attribute: data-formatting has been added to the textInput control so when action PostValue is configured on Currency control and there is a change of value, the system will skip replacing the value with formatted value.
SR-D73260 · Issue 536888
Multiselect control support for offline-enabled iOS app
Resolved in Pega Version 8.3.2
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-D73510 · Issue 538662
Cross-site scripting filtering for ActionStringID
Resolved in Pega Version 8.3.2
Cross-site scripting filter logic has been added to the ActionStringID function.
SR-D73847 · Issue 536161
Added exception handler for URL decode error
Resolved in Pega Version 8.3.2
After logging in to Pega Deployment Manager, clicking Users -> People in the left navigation panel resulted ArrayIndexOutOfBoundsException. This was traced to an incomplete trailing escape (%) pattern and has been resolved by adding checks and exception handling for incomplete data from the browser.
SR-D74008 · Issue 537289
AAAFilter on the grid shows value for a second click
Resolved in Pega Version 8.3.2
A Filter on the grid was not showing any record value for a second click. This was traced to a conflict in considering column headers caused by the Filter Icon delegating two Grids, leading the process to take the context of the other Grid instead of the one which had been clicked. To resolve this, a check for the right context of the Grid has been added to the filterOnProperEvent method.
SR-D74057 · Issue 540058
Updated aria handling for Dynamic Layout Group 'Accordion'
Resolved in Pega Version 8.3.2
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-D74165 · Issue 537512
DateRange clear button localized
Resolved in Pega Version 8.3.2
Localization has been added to the 'clear' button in DateRange.
SR-D74704 · Issue 535940
Section and navigation rule localization added
Resolved in Pega Version 8.3.2
Localization has been added for sections and navigation rules that include some of the out-of-the-box rules like Locked and Get help.
SR-D75205 · Issue 543565
Refresh with DT or pre-activity added to dirty pop up check
Resolved in Pega Version 8.3.2
Given a button which when clicked launched a data transform to set a few properties on the UI followed by a section refresh, a dirty warning popup did not appear when closing the work object even though the property changed via the refresh section. This has been resolved with an additional condition in the dirty pop up check to handle a refresh section using a DT or pre-activity.
SR-D75966 · Issue 537944
Check added so DT parameters passed when using anchor tag
Resolved in Pega Version 8.3.2
When using a link control configured such that the value of the text in the link control refers to an anchor tag such as <a href="http://www.google.com">Text</a>, clicking the link to launch a harness and call a DT with passed parameters was not working. Investigation showed that when the link had an anchor tag, pyDataTransformDynamicParams was not getting passed as query string parameter. In pega.desktop.showHarness function, there is a If condition which checks whether any "=" is present in preDataTransformName variable and if there is any, it does not add pyDataTransformDynamicParams. This was not an issue with anchor tag itself, but rather a generic issue: any value with "=" would behave in the same way. To resolve this, the pega.desktop.showHarness API has been updated to check against the proper value (pyDataTransform=) instead of just = to identify old modal parameters.