SR-A7487 · Issue 221276
Better Japanese font handling in CreatePDF smart shape
Resolved in Pega Version 7.2
The CreatePDF smart shape was not able to properly parse Japanese font characters in section data. This has been corrected by changing the default font to 'MS PGothic' which better supports Japanese.
SR-A8298 · Issue 218280
Resolved connection reset error on nested grid harness refresh
Resolved in Pega Version 7.2
When the Harness contains nested Grids, refreshing the harness would throw ?Bad Request -Connection reset? error. This was caused by a large number of hidden fields created by Grids being included in the request query string, thus exceeding the GET request size limit. The issue is now fixed by not adding the hidden fields to the query string when Refresh is called without Submit.
SR-A8430 · Issue 218096
Resolved connection reset error on nested grid harness refresh
Resolved in Pega Version 7.2
When the Harness contains nested Grids, refreshing the harness would throw ?Bad Request -Connection reset? error. This was caused by a large number of hidden fields created by Grids being included in the request query string, thus exceeding the GET request size limit. The issue is now fixed by not adding the hidden fields to the query string when Refresh is called without Submit.
SR-A10532 · Issue 226036
iOS8 Mobile Autocomplete design reworked for better display
Resolved in Pega Version 7.2.1
When new auto-complete was used in an iPhone/iPad device running on iOS8 in landscape mode, the display moved to the top and the auto complete field was not visible. This was an issue with the window handling, and the Mobile Autocomplete design has changed in 7.2. to resolve this and other related landscape display issues.
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.