INC-206058 · Issue 709519
Property label correctly highlighted after validation failure
Resolved in Pega Version 8.8
The property label was not changing to red after validation failed. This has been resolved.
INC-206220 · Issue 717873
Listener timeout added for fetching external content
Resolved in Pega Version 8.8
Email listeners became stuck and did not recover if there was an issue retrieving external content for a message. To resolve this, a timeout setting has been added when fetching external content.
INC-206401 · Issue 699717
DIrty dialog supported for multiselect and anypicker
Resolved in Pega Version 8.8
The dirty check confirm popup was not displayed after adding items in multiselect or anypicker and then clicking on cancel. This has been resolved by adding special handling with a value property that will store the selected values necessary for this operation.
INC-206483 · Issue 707090
Delegated rules page displays proper warning in Vietnamese
Resolved in Pega Version 8.8
Opening the "Configuration" left navigation item for delegated rules and clicking on edit to modify the rule did not display the guardrail warning message properly in Vietnamese. This has been resolved by ensuring the Vietnamese date time is properly formatted as "Ngày dd tháng M năm yyyy".
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.