SR-B36134 · Issue 294119
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-B36134 · Issue 294006
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-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-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-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-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-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-B44787 · Issue 300852
work object lock released if nextAssignment is false
Resolved in Pega Version 7.3
The lock was not getting released on Work object creation even though back-to-back assignment processing was disabled for the flow. To correct this, the work object will be unlocked if the pynextAssignment parameter is false.