SR-B38647 · Issue 297399
ServiceExport folder access restricted for guest users
Resolved in Pega Version 7.3
In order to increase data security, access to the 'ServiceExport' folder has been blocked for Guest users (Un-Authenticated users who have pre-atn cookie) on single-tenant sites. Once the user is logged in with valid credentials, the folder contents will be available. For backward compatibility the PRConfig setting 'serviceexportcontent/allowtoguestusers' has been added; if set to true then guest users will have access. The default is false.
SR-B38649 · Issue 296249
Corrected ClassCastException error on Connect-REST
Resolved in Pega Version 7.3
After a REST Connector was run with the QUEUE Method Parameter, executing the "System-Queue-ExecutionRequest- ProcessQueue" activity resulted in an error. This was traced to the invoke activity of class RULE_CONNECT_REST, and has been fixed.
SR-B38649 · Issue 295456
Corrected ClassCastException error on Connect-REST
Resolved in Pega Version 7.3
After a REST Connector was run with the QUEUE Method Parameter, executing the "System-Queue-ExecutionRequest- ProcessQueue" activity resulted in an error. This was traced to the invoke activity of class RULE_CONNECT_REST, and has been fixed.
SR-B38674 · Issue 301022
Descendant class logic made more robust
Resolved in Pega Version 7.3
The 'Report on descendant' option in the report definition/Listview was giving incorrect results. This was caused by the code used to execute the RD looking up the descendant class from the current application that inherits from the applies-to class (tools.getDatabase().getConcreteDescendantsInCurrentApplication(class name);) of the RD and executing the RD against this class. While this is appropriate when an application is built on another and case types are directly inherited into the new layer, this will not work when application layers are added which do not include equivalent case types for every case from the built upon applications. This becomes a more common problem when the MBO feature starts getting used more often on the customer implementations. To ensure the descendant class is correct, the Useimplemenation class has been updated to be more robust.
SR-B38802 · Issue 295105
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-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.