How do you keep it so the new owner retains ownership of the process instance?
Imagine if you have the following scenario.
1) Process is started by a server account.
2) It is assigned to an group
3) Whoever gets to it first (using a client event), gets ownership of the process instance.
4) There is a series of activities with client events that the owner needs to perform.
If it has a client event, it needs a Destination Rule. But destination rules can only be set to a specific user or originator. But in this case, the originator is a service account and not the current owner.
Page 1 / 1
Hi Randar
Note that u can also use process datafields in the destination rule e.g. In the destination rule right click on the Send To option and select the Insert K2.net Data , the data browser will open allowing you to select a datafield containing the username. Now all you need to do is store the Username of the user taking care of the first work item in a process datafield and then use that datafield in all subsequent destination rules.
Let me know if you need further assistants on this topic.
Note that u can also use process datafields in the destination rule e.g. In the destination rule right click on the Send To option and select the Insert K2.net Data , the data browser will open allowing you to select a datafield containing the username. Now all you need to do is store the Username of the user taking care of the first work item in a process datafield and then use that datafield in all subsequent destination rules.
Let me know if you need further assistants on this topic.
Sounds like a reasonable solution.
One feature request would be to have a concept of "Current Thread Owner" alongside Originator. It would just make it easier for threads wiht many steps.
One feature request would be to have a concept of "Current Thread Owner" alongside Originator. It would just make it easier for threads wiht many steps.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.