I saw you online and thought to contact you about my problem. Please see if you can help me out.

I have multiple destinations for an activity. Like I'm sending a request to different action parties. Now if same user exist in two action parties, as he is added in destination he can view worklistitem but when he gonna perform some action he successfully can perform with one action party while for other action party he is not allowed because no worklistitem found for that user.

 Do you know how to fix this? Thanks in advance.

Hi there,

I'm not sure if I understand your question 100% but it sounds like you have a user that you want to assign the worklist item twice? K2 server always does a filter on the worklist to assign work list items once per user, almost similar to Exchange when you send an email to a few distribution lists and a user exist in all those distribution lists, he will still receive the email only once.

I'm curious now, is there a reason why the user has to be able to open and action the same work list item multiple times?

Cheers,

 

---

Gerhard
-----------------------------------------------------------------------------

Thanks for the reply.

 I dont know you would say it same worklist item or separate but let me tell you the case.

If I have different parties (consider it groups of some members) and let suppose you are member of Party A and Party B both. Now I want you to perform certain action on behalf of both parties while the user means you would be the same. When you will receive notification through email you should get 2 emails for each action party to complete their specific actions.

I wonder how I can accomplish this?

The following link seems having the same discussion. But no resolution. As someone suggested about Parallel activities for each action party. But with this case also I am dynamically getting action parties (groups of members) from database and seems weird to create activity on the fly for each action party.

http://k2underground.com/forums/thread/23173.aspx

I see what you mean, but my suggestion for that would also be to use parrallel activities. Remember to the end user, it would seem the same, they would not notice that it is different activities in your process, but you can make assign Action A to Action Party A, and Action B to Action party B - however Action A and Action B contain exactly the same client event, the same rules, the same everything, it's only the name that differs.

Hope that helps,

 

---

Gerhard
-----------------------------------------------------------------------------