My requirement is to use the Get Next Work feature in a Constellation Application, but I do not want to move the assignment to the worklist of the operator. The assignment should remain in the work queue. If the operator just closes the case or if his lock expires everyone with access to the work queue should be able to open the case again.

As I understand the documentation (Get Next Work customization), this should be possible by setting the Application setting GetNextWork_MoveAssignmentToWorklist to false. However using Pega Constellation (Pega Infinity Version 24.2.3) this does not work as expected; the assignment is always routed to the worklist of the Operator.

I investigated why this is the case and stumbled upon the MoveToWorklist (Assign-, Pega-ProcessEngine) Activity where this setting is called. I noticed that it only takes effect if the Requestor is not stateless, which is also mentioned in the description of step 1, otherwise Local.MoveToWorklist is always set to true. Since Requestors are stateless for Constellation applications this setting seems to be not supported. Is this a known limitation? Is there any workaround to fulfill my requirement?

Out of curiosity I simply set Local.Stateless to false in a private edit of the MoveToWorklist Activity and with that the Get Next Work feature works indeed as we would need it, but since the MoveToWorklist Rule is final I cannot use this as a workaround.