SR-A14336 · Issue 230881
Resolved NPE when @checkForSubstitute used
Resolved in Pega Version 7.2.1
If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.
INC-146837 · Issue 602673
PerformCriteria contains CurUserHasRequiredSkills 'when' rule
Resolved in Pega Version 8.1.9
A customer version of the PerformCriteria data transform was generating a validation error due to a qualified statement that resulted in a null result. This has been resolved by updating the PerformCriteria DT to include the CurUserHasRequiredSkills 'when' rule.
SR-A19512 · Issue 238622
Standardized date time used for memo history compare
Resolved in Pega Version 7.2.1
History compare displayed unexpected results for the pxSaveDateTime for a Rule-Application record when a memo was added and then it was compared to another record in the history log. The comparison logic was not looking at the save time of the memo, but rather the save time of the rule itself, resulting in the mismatch. This has been resolved.
SR-A19704 · Issue 234771
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-A16904 · Issue 234334
Wrapper added to expression builder for the jump transition on a step
Resolved in Pega Version 7.2.1
While using expression builder, selecting the option for "Enable conditions after this action" in an activity and submitting the expression did not show the expected result in the When input box. Attempting to use the expression builder again and submitting it then resulted in the screen freezing and requiring a refresh. To resolve this, a "pyStepsTransSection" wrapper section was been added for the "pyStepsTransParamsWhen" when condition.
SR-A14412 · Issue 229299
Corrected SLA comparisons involving daylight savings
Resolved in Pega Version 7.2.1
A calendar using the "Sao_Paulo" timezone was eliminating the user-entered close dates when calculating SLA times between that calendar and one using "America/NewYork". This was an issue with the parse API not honoring Daylight Saving for some time zones, and handling for that has been added.
SR-A13472 · Issue 231026
History tables updated for deletion and importing.
Resolved in Pega Version 7.2.1
The history table was not properly updated for actions on Data tables when deleting or importing new records using the pzDeleteRecord activity. There were no problems for adding or updating. Previously, pzDeleteRecord activity did not modify the history table, and that tracking has been added so that activity can be used in this manner.
SR-A22933 · Issue 241566
Check added to resolve Google Chrome-based value localization error
Resolved in Pega Version 7.2.1
A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.
SR-A8475 · Issue 233560
Fixed Multiselect grid drag and drop
Resolved in Pega Version 7.2.1
When using MultiSelectList Control, if a value was selected and then 'submit' was used to populate the Grid's data, dragging and dropping the Grid's row to some other workbasket did not work. This happened because the clipboard calls the remove property with a symbolic delete when doing a drag and drop. While processing this delete, if the mode of property was unknown the system was unable to look up the property definition in the dictionary, and an exception occurred. To fix this, handling has been added to lookup the definition of the property if it is unknown before removing it.
SR-A13187 · Issue 229142
JSON mapping performance enhanced
Resolved in Pega Version 7.2.1
JSON mapping performance has been enhanced with the addition of a native JSON property cache along with the introduction of a DSS to skip all unnecessary intensive checks if the JSON node name is found to be valid. This will be handled through a DSS JSON/useNativeAPI which when set uses adoptJSONObject/adoptJSONArray() as the API for inbound JSON parsing. Please note that if the DSS is set, homogeneous arrays are only supported with valuelist configuration in connectors. Heterogeneous arrays are not supported when DSS is set.