SR-B38802 · Issue 285255
Resolved error for data flow using abstract start shape
Resolved in Pega Version 7.3
A Data Flow starting with a Data Set was running correctly, but when refactored to start with an Abstract the same flow generated errors in Production. This was traced to an error in the code that was attempting to write a null value to the array, and has been fixed.
SR-B38867 · Issue 297937
VBD loads based on collection start date
Resolved in Pega Version 7.3
An application querying VBD without a time range forced the loading of all IH records, causing performance issues. To lower the impact of such queries, VBD will now use the Start Date configured on the VBD Data Source landing page as the starting point for loading IH records. This will be enforced for queries and Eager partition loading. Note that IH Sync has NOT been modified, and will continue to copy & aggregate all IH records. This enables the start date to be adjusted backward if needed.
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.