INC-155855 · Issue 620575
Safe check added to modal window pop-up cancel
Resolved in Pega Version 8.4.5
On click of a link to add items to the rows by selecting the page list from pop-up window, clicking on the cancel button generated a node name undefined error after which clicking the link would not open the pop-up window at all. This was traced to the pre-processing activity in the flow action used to copy page list from one page to other, and has been resolved with the addition of a safe check.
INC-156826 · Issue 625436
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.4.5
When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.
INC-156912 · Issue 627485
Updated accessibility for Rich Text Editor navigation in a modal dialog
Resolved in Pega Version 8.4.5
When navigating through a Rich Text Editor while in a modal dialog, it was expected that once focus was brought to the RTE Toolbar (Alt+F10), pressing Escape on the keyboard would bring the focus back into the RTE text area and the cursor would appear. However, when this Rich Text Editor was within a modal dialog, pressing Escape closed the modal dialog entirely. This has been resolved by updating the code to stop the Escape key event propagation from the RTE toolbar when in a modal dialog.
INC-156992 · Issue 628622
Corrected custom portal JUMP condition
Resolved in Pega Version 8.4.5
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-157041 · Issue 626308
Performance improvements for email listener processing
Resolved in Pega Version 8.4.5
Email processing was taking an excessive amount of time when a very large number of email listeners were running. Performance has been improved by updating the implementation of pzGetChannelByName to use obj-browse instead instead of looping through channels.
INC-157353 · Issue 624009
Handling added for autoclose of assignment in tabbed MDC
Resolved in Pega Version 8.4.5
After configuring an Ajax container in a section using tabs and max doc defined as 8 with 'doClose' set after processing has been completed, finishing the assignment caused the work item tab to stop working. Checking the console showed a script error was being thrown. Investigation showed that when the doClose action was triggered and tried to find the activeTabs in MDC, the target element being fired was null. This has been resolved by adding a condition for the doClose to handle the combination of autoclose and tabbed MDC that will close the current Ajax container div before proceeding.
INC-157367 · Issue 637945
PDF generation corrected
Resolved in Pega Version 8.4.5
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-157404 · Issue 630692
Adaptive Model report information exports correctly
Resolved in Pega Version 8.4.5
Clicking export to Excel or PDF in the Prediction Studio Adaptive Model report was not working. Investigation showed the first double quote of the propositionName was getting replaced from & quot ; to "", which resulted in an error while performing openUrlWindow action. This has been resolved by adding a new helper handler, while creating context menu using Handlebars.
INC-157448 · Issue 638922
Latitude and longitude populated for CreateWork history
Resolved in Pega Version 8.4.5
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 631997
Accessibility updates added for images and icon controls
Resolved in Pega Version 8.4.5
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