SR-B3893 · Issue 279435
Fixed focus move to top on refresh in tabs for Internet Explorer & Chrome
Resolved in Pega Version 7.3
The refresh event from a button control in a section containing a tabbed layout forced the focus to the top of the section when using Microsoft Internet Explorer 9 (IE9) / 11 or Chrome 54.X . To correct this, the initializeTabs method to set scrollTop value has been updated.
SR-B38958 · Issue 296022
Updates to field values reflected on mobile
Resolved in Pega Version 7.3
After updating field values in higher ruleset versions and forcing a full data sync, the mobile app did not reflect the updated value. This was due to rule resolution not happening while packaging the FieldValue rules due to locale, and has been corrected by changing the PZGETFIELDVALUES rule to sort the pzInsName based on the ruleset versions and picking the latest available rules from the ruleset.
SR-B38980 · Issue 299227
createDateTimeCategories function modified to use operator time zone
Resolved in Pega Version 7.3
A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.
SR-B39280 · Issue 298376
HTML updated to replace "\u" in the pyLabel before JSON call
Resolved in Pega Version 7.3
Placing a "\u" in the pyLabel field of a work object caused an "Invalid Unicode escape sequence" JavaScript error and part of the UI became unresponsive. This happened when the call was made to convert the json to values (JSONToValues) when a work object is opened. To avoid this error, the pzClientDynamicData HTML rule has been updated to replace the \ u character before the strPyLabel is set.
SR-B39293 · Issue 296727
Mobile checkbox controls fire validations
Resolved in Pega Version 7.3
Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.
SR-B39293 · Issue 297091
Mobile checkbox controls fire validations
Resolved in Pega Version 7.3
Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.
SR-B39293 · Issue 299867
Mobile checkbox controls fire validations
Resolved in Pega Version 7.3
Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.
SR-B3943 · Issue 279666
NewCorrSummary rule resolution modified for CommunicationType
Resolved in Pega Version 7.3
The Received Via section of the out-of-the-box NewCorrSummary rule was being mapped to the property rule CommunicationType despite that property rule being configured locally. This has been fixed by setting the function to take the class name using dictionary instead of section xml.
SR-B39458 · Issue 299698
Email Listener checks for engine startup before queue processing
Resolved in Pega Version 7.3
Items in an Email Listener queue were not processed upon server restart and an null-pointer exception was generated. This was due to the Email Listener beginning work too quickly, and has been fixed by modifying the Email Listener code to check whether the engine has started or not before beginning processing.
SR-B39476 · Issue 297525
addCalendar() RUF logic updated
Resolved in Pega Version 7.3
The addCalendar() RUF logic has been modified to correctly set the operator time zone and correctly add the given years, months, days etc. This fix will be active based on a DASS setting as addCalendar() cannot be directly changed due to backward compatibility with DateTime issues.