SR-A20289 · Issue 245275
Custom header section of Calendar retained after Smartinfo popup displayed
Resolved in Pega Version 7.2.1
If the mouse moved over the custom header section of Weekly, Daily calendar and the SmartInfo popup appeared, the custom value was reset to the label value. To correct this, a custom header check for setting subject to subject time has been added to pzAllDayEventBlock to maintain the custom setting.
SR-A20300 · Issue 239490
SLAs agree in assignment gadget and action area
Resolved in Pega Version 7.2.1
An assignment created with an SLA of 2 years was showing different SLA info in assignment gadget and action area. On the assignment list gadget, the deadline displayed was "1 year 12 months from now" which is correct. On the top right corner of the action area it says, "Due in 1 year 11 months from now". This has been fixed by modifying the base calculations of the pyAssignmentTimeLimitDeadline control.
SR-A20336 · Issue 240862
Corrected SLA name set with passed value
Resolved in Pega Version 7.2.1
The SLA name was not correctly set on the assignment page during creation if the field was left empty for a passed value to fill. This has been corrected.
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-A21835 · Issue 243872
Flow names can now be found when using duplicate search mechanism
Resolved in Pega Version 7.2.1
When using the duplicate search mechanism and trying to resolve a case as duplicate, an error appeared indicating that the flow name could not be found. This was a handling error, and has been fixed.