SR-D28496 · Issue 499082
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.4
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using Microsoft Internet Explorer 11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.
SR-D28657 · Issue 500586
Corrected Reference value's description in Table
Resolved in Pega Version 8.4
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 readonly case. This has been corrected.
SR-D28859 · Issue 502006
Declare expressions validation message persists when clicked
Resolved in Pega Version 8.4
After configuring a section with fields and validation through validate rule where some of the field properties were sourced in declare expressions, clicking on the validation message caused it to disappear. Investigation showed that when validations are displayed on the screen, clicking on any of the fields which have calculatexpression as validationtype triggers a check for errors on the field with caluclateexpression validationtype. As there were no errors, the existing validation message on the field was removed. To resolve this, the system has been updated so that If the calculate expression does not have any error and the field has existing validations, the removal of validation message will be skipped.
SR-D28869 · Issue 499317
Resolved Tooltip not relaunching after hide when using autocomplete controls
Resolved in Pega Version 8.4
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-D29517 · Issue 513174
OpenURLWindow works after click on MailTo
Resolved in Pega Version 8.4
After configuring an openURLWindow action for a link in a modal dialog, clicking on any email ID link and then clicking the openURLwindow action did not launch the URL as expected. This has been corrected by stopping the unload event in dom when clicking on a MailTo.
SR-D29809 · Issue 505257
Extra <p> tag removed when not needed in RTE generation
Resolved in Pega Version 8.4
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-D29918 · Issue 503067
Resooved duplicated aria-level attribute in layout headings
Resolved in Pega Version 8.4
Headings on layouts automatically applied the aria-level attribute. This meant if the markup was an H tag with an aria-level attribute, the screen reader read it out twice. This has been corrected.
SR-D29926 · Issue 501408
FormatType reset added to ensure accurate DateTimes
Resolved in Pega Version 8.4
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 503684
XSS protection added to ClientDynamicData
Resolved in Pega Version 8.4
Cross-site scripting protection has been added to the "DesignViewIframe" & "pzHarnessID" parameters in the pzClientDynamicData HTML rule.
SR-D31336 · Issue 501287
Dropdowncontrol shows correct value in read-only mode
Resolved in Pega Version 8.4
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.