INC-142066 · Issue 600044
Dirty confirmation alert added for standalone Ajax container
Resolved in Pega Version 8.6
In the Pega CS interaction portal, an interaction could be launched to create a service in the Ajax container. If the same service was opened from the search results or the worklist, however, it was not prompted with the dirty popup message to save or discard the changes. This was a missed use case for a standalone Ajax Container, and has been resolved by adding a check to evaluate whether the document has an Ajax Container so the proper dirty state handling will be called.
INC-144320 · Issue 600536
Dirty Flag reset updated
Resolved in Pega Version 8.6
After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.
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-225511 · Issue 733185
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-144888 · Issue 603617
Custom Rich Text Editor plugin support updated
Resolved in Pega Version 8.6
At runtime, two Rich Text Editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for Rich Text Editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden Rich Text Editor. Investigation showed that if plugins were added to pega.ctx.customRTEPlugins, then the plugin manager discarded plugins from pega.u.d.customRTEPlugins. To resolve this, the Rich Text Editor plugin manager has been modified to merge the plugins from pega.ctx.customRTEPlugins and pega.u.d.customRTEPlugins.
INC-190708 · Issue 688135
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.8
After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.
INC-144888 · Issue 603618
Custom rich text editor plugin support updated
Resolved in Pega Version 8.4.4
At runtime, two rich text editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for rich text editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden rich text editor. Investigation showed that if plugins were added to pega.ctx.customrich text editorPlugins, then the plugin manager discarded plugins from pega.u.d.customrich text editorPlugins. To resolve this, the rich text editor plugin manager has been modified to merge the plugins from pega.ctx.customrich text editorPlugins and pega.u.d.customrich text editorPlugins.
INC-132590 · Issue 590491
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.4.4
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-132590 · Issue 590493
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.6
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-225247 · Issue 729607
SessionTimer correctly working in Mashup
Resolved in Pega Version 8.8
When using the pxSessionTimer in the mashup at section pxCaseActionArea, the timer pop up did not appear. Investigation showed the pxSessionTimer control was not correctly triggering in mashup. This has been resolved by updating the pega.desktop.support.restartTimeoutWarningTimer and closeAllPRPCChildWindows functions and adding the new functionality logOff() which uses the control_actions_logoff functionality.