SR-B14420 · Issue 296416
Thread locking implemented to handle multiple thread potential on a data flow
Resolved in Pega Version 7.3
When attempting to activate data flow runs from different threads depending on the status of the run, the threads detected that the data flow was not running and triggered the run activation simultaneously. This caused multiple threads to run when only one was expected to be executed. To avoid this, a lock mechanism has been implemented that will prevent multiple threads from triggering a run at the same time if the run is already being executed by a different thread. Those that fail to trigger the run will generate and log an exception indicating that status.
SR-B14432 · Issue 286451
Editability check added to asterisk symbol (mandatory field expression) display
Resolved in Pega Version 7.3
Sections using conditional read-only and editable modes displayed the mandatory expression (asterisk symbol) in both modes. To correct this unexpected behavior, the GenerateLabelCellContent RUF has been updated to check whether the control is editable and only generate the asterisk if the result is true.
SR-B14618 · Issue 285696
Resolved operator authentication error causing Dnode remote execution failure
Resolved in Pega Version 7.3
An "unable to authenticate" error was generated and the Dnode remote execution task failed if the operator definition was not found and an empty username was sent for authentication. This has been corrected with additional diagnostics and a check to avoid a forceAuthentication() call.
SR-B14618 · Issue 286786
Resolved operator authentication error causing Dnode remote execution failure
Resolved in Pega Version 7.3
An "unable to authenticate" error was generated and the Dnode remote execution task failed if the operator definition was not found and an empty username was sent for authentication. This has been corrected with additional diagnostics and a check to avoid a forceAuthentication() call.
SR-B14688 · Issue 289060
Parameter added to consider production rulesets while checking rule resolution
Resolved in Pega Version 7.3
After creating a portal for admin users and adding it to a production ruleset that in turn had been added to the appropriate application and access group, adding the portal to the access group unexpectedly generated the error "Portal name: is not a Valid Record for use by this Rule." This was due to the system not considering production rulesets while checking rule resolution, and the parameter pyUserPreproductionrulesets has been added to the validate activity to handle this.
SR-B14732 · Issue 296513
Resolved error with DateTime property comparison crossing daylight savings time
Resolved in Pega Version 7.3
If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.
SR-B14732 · Issue 296847
Resolved error with DateTime property comparison crossing daylight savings time
Resolved in Pega Version 7.3
If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.
SR-B14745 · Issue 285506
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-B14774 · Issue 285008
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B14774 · Issue 285027
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.