pxUpdateOperator property of the pyWorkPage holds the operatorID of the last operator who updated the case. That can be used or else,  pxRequestor.pxUserIdentifier will hold the current operator, this value can be read and saved in a property during first assignment and later used.

regards,

Murali

Technically, what you asked can be handled by storing the Operator ID into a property before sending the case to the Approval Work basket.

So, When Operator B who gets the case from Approval work basket rejects the case,  the case can be sent to Operator A's worklist by looking up that property.

However, I do not feel it is a good practise to implement this rejection routing in the manner you mentioned for an enterprise application. If Operator B rejects the case/assignment, then route the case to the Workbasket that Operator A or many other operators have access to. So, even if Operator A is not available, any other operator who have access to the Workbasket can work on this case by accessing 'Get next work'.

One more thing, this question is posted in wrong forum. This forum discuss topics with respect to upgrade.

Thanks, Jaffer

Hi,

Why is this related to the upgrades?

This looks like a implementation query which I think should probably be posted in the CaseManagement or other related forum, but not in the Upgrade forum.

Can you check whether the value of this property helps newAssignPage.pxCreateOperator