INC-208199 · Issue 706446
Added input null check to resolve loading error
Resolved in Pega Version 8.7.2
The application was freezing while loading if action was taken on the controls while a page level message was visible. This has been resolved by adding an additional null check for input before calling the focus API.
INC-208499 · Issue 714947
Corrected Ajax container scrollbar with tabs
Resolved in Pega Version 8.7.2
The scroll bar was not working as expected for a pyCaseWorker Section configured with an Ajax container and "Show as tabs". This has been resolved by overriding the div[data-mdc-recordid] with overflow-x: auto style to get the proper horizontal scroll in the Ajax container.
INC-208629 · Issue 704589
ReviewArchivedCase shows case hierarchy
Resolved in Pega Version 8.7.2
After update, opening the archived cases in the ReviewArchivedCase harness did not show the case hierarchy dropdown. Investigation showed this was caused by the D_CaseBreadCrumb data page calling the source activity with wrong instance key, along with the pxCaseBreadCrumbPopulate activity not supporting breadcrumbs for archived cases. This has been resolved by changing the method how the parent case item is being fetched from storage, using Obj-Open-By-Handle instead of Obj-Browse as the latter doesn't support checking the second storage. The pxBreadcrumbsCount Declare Expression has also been removed in order to facilitate the data page loading.
INC-208729 · Issue 711402
Repaired Perform for 'Assignments with Errors'
Resolved in Pega Version 8.7.2
The 'Perform' button was not working on the "Assignments with errors" pop-up. This was an inadvertent side effect of changes made in 'pega_desktop_support' (Pega-Desktop ruleset), and has been resolved by adding a check before calling pega.mobile.isMultiWebViewPegaMobileClient.
INC-208848 · Issue 703874
Cosmos landing page configuration icon updated
Resolved in Pega Version 8.7.2
In order to allow changing the Cosmos landing page configuration icon, the harness has been made available. The default icon has also been updated.
INC-209071 · Issue 706039
Other Currency resolves value in Pega DX
Resolved in Pega Version 8.7.2
When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.
INC-209906 · Issue 704865
AddMessage function shows error on UI
Resolved in Pega Version 8.7.2
After updating from Pega 8.1 to 8.6, an addmessage function which previously displayed an edit validate rule error message was not working. This was an issue with textinput inside a grid, and has been resolved by adding a style to input text when it has a symbol left aligned and giving the error icon a z-index to show the message when the symbol is configured.
INC-210495 · Issue 708118
Left and right arrow keys work for tabbed Ajax container
Resolved in Pega Version 8.7.2
The left and right arrow keys were not working for input fields inside a tabbed Ajax container. This was traced to a disableArrowKey function in pzpega_ui_tabs js file, and has been resolved by adding an additional check for attribute "data-mdc-recordid" to ensure the arrow keys are active for an input field.
INC-210760 · Issue 708531
Corrected malformed URL
Resolved in Pega Version 8.7.2
The function used in the session timer to log off the user was not working consistently, and attempting to discard a checked-out delegated Rule did discard the rule. Both issues reported the error "HTTP Status 400 - Bad request". This was traced to a badly formed URL, and has been resolved by wrapping the URL with SafeURL_createFromURL.
INC-210864 · Issue 706384
Tooltip added to specify Display Confirmation Message works for for template table only
Resolved in Pega Version 8.7.2
The Display Confirmation Message check box is a feature only available in template table and is not supported for legacy tables and Repeating Dynamic Layers. Text has now been added for an info tool tip to specify that use. There is a workaround for other areas to call the 'removeFromRepeatSource' function in UserWorkForm.