INC-206577 · Issue 704421
ParentKey handling updated for for CS portal
Resolved in Pega Version 8.8
After creating an interaction in the CPM portal and refreshing the CPMPerformIncludes section (top-level section in the Perform harness) on button click, the focus was set to the first property and a large number of "Uncaught harness context does not exist" error appeared on the console and the screen became frozen. Analysis showed that after the refresh the parentKey property was empty, causing the flow to be executed in the wrong context. This has been resolved by adding a condition to set the parentKey for CS portal 'Add document' scenarios.
INC-206773 · Issue 708376
ScreenFlow called from Dataclass section completes as expected
Resolved in Pega Version 8.8
When calling a screen flow from a section of another screen flow, the flow did not work properly in the modal dialog screen flow but did work in the process flow. Investigation showed that when the second screenflow was opened from the Data class section, the assignment of the first screenflow was not deleted post submission. This has been resolved by adding a conditional block for screenFlow Dataclass section.
INC-207524 · Issue 714707
Handling added for modal flow to resolve unexpected submit window closure
Resolved in Pega Version 8.8
After creating a child Task and submitting the TaskCreation flow action, a validation error was seen. Clicking on the Submit button again caused the modal TaskCreation window to close. Investigation showed that the WorkLock activity was executed as desired on the first click on submit, but for the second submit the WorkLock activity called Obj-Refresh-And-Lock and the page was refreshed, the work object lock was released, and the error was no longer seen. To resolve this, an update has been made to the WorkLock activity to use a new when rule 'pyIsModalFlowTemporary' so that Obj-Refresh-And-Lock is not called twice. This change has also been added to pzRunFlow.
INC-207593 · Issue 702428
Spell Check flag removed from Preview and Public Articles
Resolved in Pega Version 8.8
If the spell check button was used when editing a Knowledge Management article, flagged words that were not corrected or set to be ignored continued to display the red flag even when previewing or when the article was being viewed from a public help site. In order to support not showing the flags while previewing or viewing from the Knowledge Management help site, an addition has been made to sanitize underlined words before save or submit.
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.