SR-A21043 · Issue 241137
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A21096 · Issue 241281
Clarified dynamic text handling to better support localization
Resolved in Pega Version 7.2.1
The use of properties and multiple field values to show dynamic text caused an issue where separate field values (3 fvs) were created for each part of a sentence and the context was not being correctly kept during localization. To resolve this, the system now uses a single field value with parameters.
SR-A21096 · Issue 239803
Clarified dynamic text handling to better support localization
Resolved in Pega Version 7.2.1
The use of properties and multiple field values to show dynamic text caused an issue where separate field values (3 fvs) were created for each part of a sentence and the context was not being correctly kept during localization. To resolve this, the system now uses a single field value with parameters.
SR-A21266 · Issue 239797
Ensured default display after grid takes effect in tree grid without explicit erase
Resolved in Pega Version 7.2.1
Old configurations were still visible after choosing ?Default (display after grid)? unless the value of the section name was explicitly erased. This was due to the generated java code that still contained the data displaying the values in fields it did not consider empty, and the handling has been corrected to resolve this.
SR-A21298 · Issue 240041
NPE on mobile list open resolved
Resolved in Pega Version 7.2.1
A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.
SR-A21304 · Issue 242768
Corrected Case Stages rendering on Perform harness
Resolved in Pega Version 7.2.1
After upgrade, the case stages were not rendered properly on the Perform harness. This was an issue with the InsHandle parameter and has been fixed.
SR-A21322 · Issue 241736
CaseDesigner SLA flows updated for MSSQL and PostgreSQL compatibility
Resolved in Pega Version 7.2.1
When the SLA for a process in Case Designer is given the internal flow(pzInternalProcessFlow) as companion flow for the process, the order of pxFlow pages is different on the pyWorkPage between MSSQL and PostgreSQL based 7.2 systems. This was due to the differences in iterating these loops and removing the completed flows, and the system has been updated to produce consistent results.
SR-A21337 · Issue 240900
Bulk transfer includes correct assignment status
Resolved in Pega Version 7.2.1
The pyAssignmentStatus value was being blanked out when doing a Bulk Transfer. This was caused by the system attempting to set a status using an empty field, and has been corrected to ensure the correct assignment status has been set.
SR-A21501 · Issue 242372
Search improved for case tags
Resolved in Pega Version 7.2.1
Search functionality for tags in cases was updated from Lucene search to elastic search, but the change class context was not properly set in all cases. It is now updated to run in workgroup as well as class.
SR-A21526 · Issue 244743
Decimal formatting kept in autocomplete
Resolved in Pega Version 7.2.1
In some installations, clicking on the auto-complete field caused the decimal format to be lost. For ex: an initial value of 21,000.00 becomes 21000.00. To correct this, the function reload of ajaxengine API has been modified to pass an extra parameter in signature of processOnBeforeSubmit function (of ui_doc_submit API ) that checks 'layouts2refresh' in the function "processOnBeforeSubmit".