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-C86126 · Issue 423259
CSV import for delete date values will be formatted before row processing
Resolved in Pega Version 8.1.4
In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row.
SR-C80129 · Issue 425385
Enhancement added to hide class join warning from end user
Resolved in Pega Version 8.1.4
An enhancement has been added to hide the joined class warning message at the end user portal if the section pzManageRecords is delegated to the user. This is done by by checking pxLimitedAccess on the pxThread clipboard page.
SR-C61477 · Issue 418266
HTML conversion added to email IVA
Resolved in Pega Version 8.1.4
When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.
SR-C64192 · Issue 415847
Activity Run allows autocomplete control for data transform
Resolved in Pega Version 8.1.4
An enhancement has been added to allow changing the control from Dropdown to Autocomplete when an activity is Run and the "apply data transform" checkbox is checked.
SR-C65841 · Issue 425807
Added handling for cases where IE causes a SAXParseException
Resolved in Pega Version 8.1.4
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: IE sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-C69729 · Issue 415717
External Entity Injection security improved
Resolved in Pega Version 8.1.4
Several updates have been made to improve security against External Entity Injection.