SR-B36134 · Issue 294147
Security fix to prevent URL tampering
Resolved in Pega Version 7.3
Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.
SR-B37775 · Issue 300342
Action item refresh properly triggers
Resolved in Pega Version 7.3
Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.
SR-B37923 · Issue 295190
null-pointer exception fixed for ForceCaseClose
Resolved in Pega Version 7.3
An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.
SR-B38619 · Issue 298574
Action item refresh properly triggers
Resolved in Pega Version 7.3
Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.
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-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-B39484 · Issue 296141
Calculation Builder made more robust for use in segments
Resolved in Pega Version 7.3
An error was generated when using the Calculation Builder in a segment, though the Calculation Builder for Report Definition worked. This was traced to code in the Calculation Builder which assumed the report page class would always be "Rule-Obj-Report-Definition", which failed for segments. To correct this, the logic has been modified to be more robust.
SR-B39730 · Issue 301187
tempItem parameter added to createworkprocess API
Resolved in Pega Version 7.3
The parameter tempItem has been added to the createWorkProcess API to hold a temporary work object which is passed to AddWork activity. The same naming convention is used.
SR-B39792 · Issue 298418
Validation removed for survey name property
Resolved in Pega Version 7.3
If the survey driver parameter "survey" was configured with a property reference to provide the survey name in the subprocess SurveyDriver, adding validations to it caused the property panel to generate an error. This was due to Validations on the pySurvey property checking if the survey existed with the configuration. To avoid this, validations on the pySurvey property have been removed and an added required condition has been put on the pySurvey
SR-B40812 · Issue 304049
New section made available for customized RB report generation date
Resolved in Pega Version 7.3
In order to support customized formats in the generated date used by Report Browser, the new section PYDISPLAYREPORTGENERATEDDATETIME has been made available. This is accessed through pzDisplayReportSectionForPDF, and replaces the "generated on" datetime property used previously.