SR-B41106 · Issue 298379
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.
SR-B41504 · Issue 299952
Tabbed navigation research wrap-up fixed
Resolved in Pega Version 7.3
Tabbed navigation Research interaction wrap-up was displaying the review harness instead of autoclosing. In order to resolve issues with the Autoclose harness being overridden, in cases where the user is not authorized to perform the assignment AND the harness is set as "Perform", the harness purpose will be set as "Review".
SR-B41652 · Issue 299895
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-B41815 · Issue 303258
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-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-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-B44001 · Issue 302395
Bulk Action filter handles rule withdrawn from landing page
Resolved in Pega Version 7.3
If a property was withdrawn in the Bulk Actions landing page, the other page properties no longer appeared in the Filter Property list. This was due to the getImmutableTerminalPropertyInfo function causing an exception whenever the rule availability was empty. To resolve this, the system will check the availability of the property rules in the "Rule-Obj-Property.LookupList" activity's 3rd step before processing/adding the embedded properties.
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.