SR-B41815 · Issue 300938
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-B42009 · Issue 304044
Authentication timeout smoothed for re-login
Resolved in Pega Version 7.3
If custom authentication was used with a stream specified to enter credentials upon authentication timeout, re-login failed after the timeout. This was traced to two issues: first, the custom configuration defaulted to using the out-of-the-box stream "Web-TimeOut", which expects the password to be in base64 encoded format and so attempts to base64 decode it. This caused an authentication failure. Second, when restarting with authentication instead of a timed-out request, the starting activity of operator was being executed and the portal was rendered unexpectedly. To resolve this, the object references needed for the successful resumption will be cloned when there is authentication timeout and used for redirection upon successful authentication.
SR-B42110 · Issue 299959
RD "Available & Valid Values" properly populated
Resolved in Pega Version 7.3
The filter conditions in the report definition for the Available and Valid value list was displayed as blank or empty for properties which were exposed for reporting purpose and are at one level below the PyWorkPage. This was traced to an improper splitting of the property when pointed from the Parent, and has been fixed.
SR-B42586 · Issue 299297
Modified RD filtering rule to support custom validation
Resolved in Pega Version 7.3
Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.
SR-B42586 · Issue 300843
Modified RD filtering rule to support custom validation
Resolved in Pega Version 7.3
Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.
SR-B43182 · Issue 301518
pzSUS Param properly URLEncoded
Resolved in Pega Version 7.3
The Tomcat 8+ server was rejecting DWA URLs due to characters such as {,} that it considered to be unsafe. These characters were introduced by pzSus key in the URL, and these values will now be encoded for the browser to resolve these issues.
SR-B44146 · Issue 300050
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B44199 · Issue 300058
Fixed Access Control Policy in Assign- classes
Resolved in Pega Version 7.3
An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.
SR-B44199 · Issue 299984
Fixed Access Control Policy in Assign- classes
Resolved in Pega Version 7.3
An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.
SR-B44199 · Issue 297134
Fixed Access Control Policy in Assign- classes
Resolved in Pega Version 7.3
An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.