Hi ParwezZ6696

not sure about this. 
I will forward your question to the relevant SME. They will get back to you.

Regards
DIMIS

> The current behavior (Pega 7.1.6) is that the WorkObject moves back to WorkBasket when the user closes the WorkObject.

I think what you are really saying is that if the user clicks on a workbasket assignment, fills out the form a bit and saves it but does not submit (advance the flow), then the assignment remains in the workbasket.

How about offering a local action to assign to yourself?  Or instead of a form to fill out, a simple connector action to "take possession"?

Hi Parwez,

After opening the work object from WB, whether that assignment is performed by the user or after opening it is just closed?

There is a Final MoveToWorklist Activity.  If you Trace GetNextWork you will see it executed (unless you disable that behavior by changing the default DSS value which you do not have to do). You need to use "old:" as a prefix if searching for that Activity.

You could use a Rule-Declare-Trigger that checks whether newAssignPage is the Workbasket in question and, if so, call MoveToWorklist.

Sounds like you also want to call addWorkObjectParty specifying "Owner" as the role and "CurrentOperator" as the model/transform.

From that point on always route to the Owner work party.

Your Declare Trigger would have to be smart enough not to fire when originally saved.

Hi,

We can implement this requirements in 2 ways

1) In pre-activity of flow action, call MoveToWorklist activity which will move case to current users worklist(may add some pre conditions if required).

2) In perform default activity, call MoveToWorklist activity which will move case to current users worklist(may add some pre conditions if required like particular workbasket etc..).

Please let me know if this helps.

Thanks

GKC