SR-D51776 · Issue 531985
Check added to resolve Ajax Container instantiation error in log
Resolved in Pega Version 8.5
When using the Microsoft Internet Explorer or Microsoft Edge browsers, manually launching a Service Intent and clicking the F5 refresh button properly refreshed the screen, but the PegaRULES log file contained the error "(DynamicContainerDataModel) Error occurred while instantiating tab for the thread index." This issue / exception was observed only when pzCustomDCTabHeader was configured (pyEnableCustomTabHeaders) and when there was a AjaxContainer configured in the document. Because the CustomTabHeader recreation (DynamicContainerDataModel.updateCustomTabHeader) should be skipped for AjaxContainer, as CustomTabHeader is applicable only to the top level DC document and not to the AjaxContainer document, a check has been added to resolve this issue.
SR-D85848 · Issue 551847
Improved accessibility for tab key navigation in tables
Resolved in Pega Version 8.5
When using the tab key to navigate to the first cell in a table, the cell itself was taking focus instead of the link and the link did not open when 'enter' was hit. Instead, hitting tab a second time opened the link. By default, the standard was to have tabIndex set on the first cell of every row for accessibility so the link inside the cell gets the next level of focus. To resolve the navigation issue and avoid user confusion, while adding `tabIndex` to first cell of every row, the system will check for focusable content and avoid adding `tabIndex` to `td`.
SR-D80223 · Issue 542923
Cross-site scripting filtering for ActionStringID
Resolved in Pega Version 8.5
Cross-site scripting filter logic has been added to the ActionStringID function.
SR-D73510 · Issue 538664
Cross-site scripting filtering for ActionStringID
Resolved in Pega Version 8.5
Cross-site scripting filter logic has been added to the ActionStringID function.