Hi Harish,

If I understand your query correctly, you are trying to move the assignment to an operator. If we move an assignment to an operator that entity will not be present in the workbasket. The reference will only be present in the worklist. So, you can just use route it to an operator directly.

FYI, Assignment Ins key will be in the following format.

(Assign-Worklist/Assign-Workbasket) flow ins key assignment name. Assign-worklist will be appended to assignments in a work list and assign-workbasket to those in any workbasket.

Hi Raviteja ,

The application works on workbaskets , So i will choose workbasket option in assignment configuration.But the only cutsomization i need to do is furthur go ahead and tweek the routing activity to set the pxAssignedOperatorId.You know which activity i need to tweek

I have similar requirement where user wants the work object to assign to workbasket and have workobject open for them to edit as soon as they create work object.Please suggest how to do the same as work object is moving into workbasket but user has to click to open the same

Hi guys,

Is it not possible on your scenarios to just spinoff the flow and have two assignments created one for the workbasket and another one for the user ?

Workbaskets by definition are "unassigned work" that's that they are for. You can either assign to WB and have users "pull work" from WB based on team org structure or assign directly to operators in a "push" model.

In other words, a WB is merely Pega's word for "queue"

I have created the teams as workgroups and use worklist routing to do allocate work to individual users