SR-D25251 · Issue 493798
Added support for non-auto DisplayYesNo control
Resolved in Pega Version 8.3.1
A Change event on post value and refresh was not firing as expected in a section configured with a TrueFalse type property associated with a DisplayYesNo control. The same configuration worked correctly when used with a pxRadioButtons control. This was traced to non-auto control action JSON not generating on the second radio button(No) , and support has been added for this.
SR-D26244 · Issue 501191
Label control cross-site scripting protection added
Resolved in Pega Version 8.3.1
Cross-site scripting protection has been added to label control.
SR-D28060 · Issue 505636
Cross-site scripting protection added to Pega App Studio Spaces
Resolved in Pega Version 8.3.1
Ajax Request's callback success method has a mechanism to process the response object's HTML responseText, initiate and modify the changeTracker changes, and eventually call renderUI to render the DOM. However, the response object sometimes may return a different type (JSON) that may expose cross-site scripting vulnerabilities. To improve security for the Pega App Studio, the system will process the Ajax request's response text only if the response date type is not JSON by accepting a flag in the callback object passed by the caller.
SR-D28496 · Issue 499079
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.3.1
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.
SR-D28657 · Issue 500583
Corrected Reference value's description in Table
Resolved in Pega Version 8.3.1
When a user was given 'property for value' as an ID and 'property for display text' like a name, launching the portal showed the display text correctly until 'refresh' was clicked, at which time the current section showed the property value instead of the property text. Investigation showed that the parameter string split inside the parameterised data page used as a dropdown source failed in the read-only case. This has been corrected.
SR-D28869 · Issue 499315
Resolved Tooltip not relaunching after hide when using autocomplete controls
Resolved in Pega Version 8.3.1
When a tooltip was configured with SmartInfo and 'Auto-dismiss on hover away' was not checked, the tooltip disappeared when an autocomplete control was clicked and could not be reopened afterwards. The tooltip behaved as expected when it used input text control. This behavior was traced to autocomplete controls being set to hide all other active popovers because autocomplete results are displayed in a popover and only one active popover can exist on the DOM. However, it was seen that the tooltip's Smartinfo popover status was still active even though it was hidden, which is why it could not be launched again. To resolve this, when an autocomplete control is clicked, any active popovers being hidden will also be marked as inactive.
SR-D29809 · Issue 505255
Extra <p> tag removed when not needed in RTE generation
Resolved in Pega Version 8.3.1
The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.
SR-D29926 · Issue 501406
FormatType reset added to ensure accurate DateTimes
Resolved in Pega Version 8.3.1
Read-only Date Time fields in the Case Information screen were displaying just the Date in Review Harness mode but displaying Date and Time properly in perform mode of the case. This was traced to a scenario where if any section which had only a date property was rendered in non-template, then 'pyFormatType' was being set as 'date' in tools and not reset afterwards. That meant any datetime type property rendered after this date property was rendered without a timestamp. This has been corrected.
SR-D30215 · Issue 503683
Cross-site scripting protection added to ClientDynamicData
Resolved in Pega Version 8.3.1
Cross-site scripting protection has been added to the "DesignViewIframe" & "pzHarnessID" parameters in the pzClientDynamicData HTML rule.
SR-D31336 · Issue 501285
Dropdowncontrol shows correct value in read-only mode
Resolved in Pega Version 8.3.1
The dropdown control was not showing the correct value in read-only mode when the standard value of one option was the same as the prompt value of another. Investigation showed that in read-only mode, the loop to fetch the selected value from the datapage results was not stopping when it found an exact match. This has been resolved with the addition of a break statement.