INC-135523 · Issue 590437
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.3.5
When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.
INC-139023 · Issue 591165
Tab will exit portal side menu
Resolved in Pega Version 8.3.5
It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.
INC-138354 · Issue 594356
Third party cookies reminder added for Mashup in incognito browsers
Resolved in Pega Version 8.3.5
When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message.
INC-133951 · Issue 584148
Try catch added for templated refresh when
Resolved in Pega Version 8.3.5
After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.
SR-D23239 · Issue 499591
Support added for multi-operator SAML logins
Resolved in Pega Version 8.4
When a SAML user logged in by Single Sign-On (SAML), the system processed the login to portal as a different operator if there was a function on the Attribute field under Operator identification in the SAML authentication service. In this scenario, using an expression for operator provisioning did not work because all SAML login sessions resolved to same first operator due to parseAndEvaluateExpression() in ExpressionHelper.java ignoring new expression arguments if the expression page already existed. To support the use of multiple operator logins in this format, the system has been updated to clone a new expression page for every session and update it with the correct expression arguments.
SR-D32655 · Issue 510345
Enhancement added to hold Change Tracker values until UI is loaded
Resolved in Pega Version 8.4
Sporadically, an agent attempting to answer a queued call within 10 seconds received a loading screen. By the time the load completed, the next agent had already taken the call. This is a scenario where based on a change, the agent was trying to refresh something on the UI (a section or harness) which was not yet loaded/present on the UI. To address this use case, an enhancement has been added to hold the change tracked values and handle them once the UI is loaded. The new function pega.ui.ChangeTracker.prototype.handlePendingCTChanges in pzpega_ui_changetracker.js is used to handle the pending CT changes. A hook has been added in the pzpega_ui_doc_lifecycle js file to invoke the above function once the UI is loaded.
SR-D18879 · Issue 500643
Logic update made to PrepareColors to resolve calculation ambiguity
Resolved in Pega Version 8.4
When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the Rule-Utility-Function pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.
SR-D19299 · Issue 511324
Support added for calling Export to Excel directly from RD
Resolved in Pega Version 8.4
When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.
SR-D21527 · Issue 491739
Hidden filters will not be shown on the resulting report
Resolved in Pega Version 8.4
After setting up a Report Definition to be visible in report browser with all filters hidden, editing and saving the report resulted in the filter values being visible on the report. This has been resolved by modifying pzResolveCopyFilters activity so that If the filter view option is "Read only, allow no changes" and "Filter not visible in Viewer", it will skip copying the filter values on to the report definition page.
SR-D22319 · Issue 493660
Corrected Flex UI Alignment issues in Microsoft Internet Explorer 11
Resolved in Pega Version 8.4
In Microsoft Internet Explorer 11, a UI rendering issue was observed when Report Definition uses many columns. This was traced to Flex not being fully supported in Microsoft Internet Explorer 11, causing the flexResize function inside pzpega_ui_doc_lifecycle to not perform well when calculating harness width based on content. While there was a workaround of using the flag "pega.u.d.DISABLE_FLEX_RESIZE" to indicate the system should not execute that function, the issue has been resolved by setting table layout to auto.