INC-155070 · Issue 637580
PDF generation corrected
Resolved in Pega Version 8.5.4
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-156992 · Issue 628624
Corrected custom portal JUMP condition
Resolved in Pega Version 8.5.4
After upgrading Pega from 8.3 to 8.4, a custom portal was not correctly rendering the stream although the activity was getting executed and the clipboard had all the necessary data. This was traced to a syntax error in work done earlier that placed the JUMP condition (.pyDesktopType=="Custom") in ShowDesktop at the pzPopulateRequestor call step, and has been corrected.
INC-157367 · Issue 637947
PDF generation corrected
Resolved in Pega Version 8.5.4
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-157448 · Issue 638924
Latitude and longitude populated for CreateWork history
Resolved in Pega Version 8.5.4
After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.
INC-157662 · Issue 631999
Accessibility updates added for images and icon controls
Resolved in Pega Version 8.5.4
In order to improve accessibility, aria-hidden has been added to button and link controls for decorative images, and the alt attribute will be generated by the icon control only when the icon source is Image. The icon control has also been updated to set accessibility roles based the following:if actions are configured -> role=button if no actions are configured -> role=img if type is url/phone/email -> role=link
INC-157737 · Issue 631688
Added ability to support multiple domains for users
Resolved in Pega Version 8.5.4
Previously, the DSS setting MultiTenant/CrossTenant/DomainName supported just a single domain. In order to support multiple domains for internal and external users, an enhancement has been adde so that given two domain values provided as comma-separated values in “MultiTenant/CrossTenant/DomainName” DSS setting, pzSetCrossTenantDomain will determine the correct domain value using pxRequestor.pxReqServer.
INC-157860 · Issue 633947
Corrected error message display in right-to-left locales
Resolved in Pega Version 8.5.4
When using the standard report definition view in the Arabic (ar_AR) locale, error messages for a filter condition were displayed with an incorrect extended horizontal scroll bar with white space. This was traced to the legacy popover styling causing an issue with locales that display text from right to left, and has been resolved by setting the default overlay left to 0PX for these locales.
INC-158129 · Issue 635306
Left navigation expansion made accessible for tab/keyboard actions
Resolved in Pega Version 8.5.4
The left navigation "aside" DOM element did not expand if reached with the keyboard tab actions, but did with mouse hover. This has been resolved by updating the selectors for focus within left nav and updating the script to collapse the menu pyAutoCollapseLists section.
INC-158974 · Issue 631272
Messages cleared from WorkPage so "load more" link works as expected
Resolved in Pega Version 8.5.4
After being migrated, a link button script for "load more" in a repeating dynamic layer was not rendering more data on the UI if there was an error in pyworkpage. Refreshing the UI to clear the error and clicking the "load more" link then displayed the new set of Data. If no error occurred on pyworkpage, then clicking the "load more" worked the first time. This was traced to the success handler ignoring the response if there were errors on pyWorkPage, and has been resolved by updating the pzinvokerdlpreprocessing activity to add 'Page-Clear-Messages' as the first step.
INC-159506 · Issue 635903
Corrected column alignment for Report Definition exported to PDF
Resolved in Pega Version 8.5.4
Aggregated columns such as count were not properly aligned in the PDF when a report definition was exported. This has been resolved by adding right justification styles in pyReport_ExportToPdfStyles.css. With this change, the PDF will look similar to the report definition displayed in the UI.