SR-A10871 · Issue 231166
Extra parameter support added to CreateNewWork
Resolved in Pega Version 7.2.1
Code changes in _navigateGadgetFrame caused issues when calling createNewWork function in a custom control. Support has been added to pass parameters along with flow name to correct this.
SR-A11262 · Issue 229919
Resolved JS exception after editing data-bound grids
Resolved in Pega Version 7.2.1
On expand of row, a 'Rule not found' exception was thrown when a data-bound grid had a row added in the middle and then deleted. This was caused by the improper updating of the ID handles making the grid object look stale, and has been fixed.
SR-A12114 · Issue 227211
Customization added to conflict dialogue
Resolved in Pega Version 7.2.1
An enhancement has been added to conflictDialogTextTemplate to allow customization.
SR-A12209 · Issue 230428
Updated Module Indexing to avoid duplicates
Resolved in Pega Version 7.2.1
Module indexing was not unique, potentially creating a problem with the Module Group where the same index could be created for two different document. This has been resolved by changing showDocument to use the thread id to build the module id so that it will be consistent and unique.
SR-A12357 · Issue 230904
Corrected error handling logic when using KeepMessages
Resolved in Pega Version 7.2.1
Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.
SR-A12357 · Issue 231872
Corrected error handling logic when using KeepMessages
Resolved in Pega Version 7.2.1
Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.
SR-A12544 · Issue 230235
Error Header and Button Footer scrolling fixed
Resolved in Pega Version 7.2.1
Error Header and Button Footer scrolling was corrupted due to an absolute positioning error in the harness. This has been corrected.
SR-A12708 · Issue 228601
Resolved JS exception after editing data-bound grids
Resolved in Pega Version 7.2.1
On expand of row, a 'Rule not found' exception was thrown when a data-bound grid had a row added in the middle and then deleted. This was caused by the improper updating of the ID handles making the grid object look stale, and has been fixed.
SR-A12708 · Issue 231848
Resolved JS exception after editing data-bound grids
Resolved in Pega Version 7.2.1
On expand of row, a 'Rule not found' exception was thrown when a data-bound grid had a row added in the middle and then deleted. This was caused by the improper updating of the ID handles making the grid object look stale, and has been fixed.
SR-A13063 · Issue 227020
Autocomplete handles parameters with special characters
Resolved in Pega Version 7.2.1
Auto-complete was not properly handling filtering values containing apostrophes or other special characters. This has been fixed.