SR-D83931 · Issue 545871
Header style inheritance corrected
Resolved in Pega Version 8.3.3
When a header style for a container was explicitly set, any layout underneath inherited that style when using container formats set to 'Use Skin Base Settings'. This has been resolved by increasing specificity for the header title.
SR-D85848 · Issue 551846
Improved accessibility for tab key navigation in tables
Resolved in Pega Version 8.3.3
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-D74992 · Issue 546875
Improved CPMHC performance
Resolved in Pega Version 8.3.3
After upgrade, slowness was seen when using the CPMHC application. This has been improved by adding Microsoft Internet Explorer 11 optimization with the most recent javascript API.
SR-D67012 · Issue 537306
Invalid dropdown time will retain entered time
Resolved in Pega Version 8.3.3
If a datetime control using dropdown mode and a timeofday property had a validation error, on refresh the current time was being set in the dropdown. This occurred when selecting only one part of the time property (only minutes or only hours), and included an error indicating that the provided time was not a valid time of day value. To resolve this, an update has been made so that if this combination has a validation error, on refresh setting the user-entered time will be given in the dropdown instead of the current time.
SR-D83476 · Issue 550785
Layout Group (Tab) keyboard navigation behavior made consistent
Resolved in Pega Version 8.3.3
When using keyboard navigation for Layout Groups (tab), arrow keys (up/down/left/right) are used to navigate the tabs once focus is set on the first tab, and the tab contents of each tab is opened automatically. It was noted that pressing tab a few more times caused the second tab to gain focus, but the contents of the tab did not open automatically or when enter was pressed, which was unexpected behavior. For accessibility best practices, tab focus should not be allowed on tab groups. To resolve this issue, this has been removed and the system will continue to follow auto activation of tabs on arrow keys.
SR-D82148 · Issue 546761
Localization improved for ToolTips
Resolved in Pega Version 8.3.3
Attempting to use the Field value to localize the tooltip for Hour and Minute resulted in the time being displayed as "tooltip: Hour". Support has been added for localizing these fields using pyTooltip. In addition, an issue with the tooltip still being displayed after switching helper text to None and saving (without manually clearing the existing text) has been resolved with an update that will clear the tooltip value when helper text is selected as 'None'.
SR-D91964 · Issue 551090
Negative values in optimized table filters show markup
Resolved in Pega Version 8.3.3
HTML markup was shown in the filter popup when Number control was used in a Table cell and there were negative values in the cells at runtime. This was traced to work done on template grid filtering, and has been corrected.
SR-D75421 · Issue 552435
Parameters added to protect font size in HTML to PDF conversion
Resolved in Pega Version 8.3.3
Pega uses the pd4ml external library for HTML to PDF conversion. As part of this, the adjustHTMLWidth API was called to avoid truncation issues, but this resulted in font-sizes not being preserved in the exported document but rather changed as necessary to fit in the PDF. In order to support preserving the font size during export, the pyPDFSettings datatransform will call the protectPhysicalDimensions API along with setHTMLWidth, and avoid calling adjustHTMLWidth. With this change in place, any content width should not be set explicitly to some value as it may lead to truncation if the space is not sufficient. If there is no width set, text will wrap automatically. In case of tables with large number of columns, truncation issues may be seen: to avoid such issues, pass a larger htmlWidth value so that table will be reduced in size and in the rest of the page, font-sizes are preserved.
SR-D84436 · Issue 546247
Popup position calculation check added for frameless portals
Resolved in Pega Version 8.3.3
When trying to select any node under the agent, the complete section was scrolling up to the top. This issue was observed in frameless portals when the user scrolled down and launched the popup, and was the result of the the parent div's scrollTop value being added to the popup's "top" value. To resolve this, an additional check has been added for frameless portals (document.body.scrollTop) while calculating the popup's position.
SR-D90711 · Issue 553090
Portal harness maintained when opening email link
Resolved in Pega Version 8.3.3
When an email link was opened (pxOpenAssignmentLink), the portal harness was replaced with the case Perform harness. This has been resolved by ensuring the 'flex' CSS class is added for the portal harness div when using pyMobileSnapStart and a top navigation portal.