SR-A21015 · Issue 239858
AddTime calendar logic updated
Resolved in Pega Version 7.2.1
An issue was found with the final output of using the AddTime function in a Business Calendar with Australian Time Zone to add the difference between GMT and Australian time. In the internal APIs being used by this function, whenever parameters to addTime() were given in such a way that the time to be subtracted was same as the difference between the time of a given input date, start time of a business day, it was considered that there was nothing to add to input time and hence incorrect result. The logic in the engine API, CalendarUtitlity.addTime() which is used in addTime() function, has been changed to correctly calculate the desired time.
SR-A21017 · Issue 239317
Parameter label mismatch corrected for import
Resolved in Pega Version 7.2.1
During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.
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-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-A21588 · Issue 241928
Name retrieval updated for node sub-units
Resolved in Pega Version 7.2.1
A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.
SR-A21810 · Issue 231480
PreClose updated to better handle inactive DC documents
Resolved in Pega Version 7.2.1
The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.