INC-207631 · Issue 701552
Decision Table property chooser made accessible
Resolved in Pega Version 8.8
The content of the pop-up "Decision Table property chooser" was not accessible by keyboard navigation. This has been resolved by adding the necessary code for focus inside the iframe.
INC-207785 · Issue 721085
Updated check for isPreGeneratedMashup
Resolved in Pega Version 8.8
After embedding Pega mashup from one application into another Pega application, attempting to use the 'Getgadgetdata' method to retrieve property values in the mashup resulted in an infinite loop in the javascript function. This was traced to the handling of encryption of isPreGeneratedMashup in this scenario, and has been resolved by passing the parameter separately to check whether it is pre-generated or not.
INC-208199 · Issue 706445
Added input null check to resolve loading error
Resolved in Pega Version 8.8
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 702515
Corrected Ajax container scrollbar with tabs
Resolved in Pega Version 8.8
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 704588
ReviewArchivedCase shows case hierarchy
Resolved in Pega Version 8.8
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. The original method to fetch the parent case was "Obj-Open-By-Handle" which supports secondary storage but triggers all declaratives, which may lead to errors under specific configuration. Using "Obj-Browse" instead does not support secondary storage, but does not trigger declaratives. In order to ensure the best coverage for various use cases, this has been updated to conditionally use both methods; the system will use "Obj-Browse" first, and if it fails it will check secondary storage using "Obj-Open-By-Handle".The pxBreadcrumbsCount Declare Expression has also been removed in order to facilitate the data page loading.
INC-208713 · Issue 733189
cleanUpHarnessElements invoked to clear dirty objects in memory
Resolved in Pega Version 8.8
The objects for complex fields like table were not getting cleared once the current edits were discarded. This was leading to having the objects with dirty status remain in memory, leading to dirty popups or locks on the page. Investigation showed this was caused by the AjaxContainer div (which contains the grid div) being removed from markup but its reference remained in pega.u.d.harnessElements as a complex element. This has been resolved by explicitly invoking the cleanUpHarnessElements api before deleting the microDCDoc by passing the pzHarnessId as a parameter, which will remove the grid reference in pega.u.d.harnessElements.
INC-208729 · Issue 711403
Repaired Perform for 'Assignments with Errors'
Resolved in Pega Version 8.8
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 703873
Cosmos landing page configuration icon updated
Resolved in Pega Version 8.8
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 706038
Other Currency resolves value in Pega DX
Resolved in Pega Version 8.8
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 704864
AddMessage function shows error on UI
Resolved in Pega Version 8.8
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.