SR-D77004 · Issue 542349
View Full History will not include private edits
Resolved in Pega Version 8.4.1
After upgrade, clicking 'View Full History' and then 'History of All Versions', showed the history of discarded private edits of other users. This was an inadvertent side effect of work done to improve the support for rollback and migration, and has been resolved by updating the system to not save the history when in a personal ruleset (checkouts/private edits). The help documentation has also been updated to note there is no history available for checkouts/private edits.
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.
SR-C43831 · Issue 383613
Updated data retained when form error is encountered during offline application validation
Resolved in Pega Version 8.1
If a hard edit error message appeared during validation in the offline mobile app, changing the property value and syncing resulted in only the old data being retained and not the new. This was due to missing handling: when a form error was encountered on the page, diffSnapShot was updated with the recent changes but they were not added to the action queue. When the form error was corrected and resubmitted, only the new diff changes were sent to the action queue and the earlier changes were discarded. To correct this, the algorithm has been modified to perform the diffing for the workpage snapshot during record action, instead of during the mergeWorkAndForm.
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 688134
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.6.3
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-190708 · Issue 695488
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.7.1
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-190708 · Issue 688133
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.5.6
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-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 603616
Custom rich-text editor plugin support updated
Resolved in Pega Version 8.5.2
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.