Skip to main content


 

Symptoms


Unable to release work list requests where the Destination is not a specific person i.e (If AD group)
 

Diagnoses


Users are unable to release work list requests where the Destination is not a specific person i.e (If AD group). Requests that are Open to a specific user (DOMAINUser1) can be released, but requests that are Open to a group (DOMAINGroupName) cannot be released and gives an error. This happens in all workflows where the Destination is a Group.

26030 Worklist item 0 not found for K2:DOMAINUser2
 

Resolution

I believe this is expected behavior if you are using "Plan Just Once" with an AD Group. When doing so:

a. If userA of the group opens the item, ONLY userA who has it opened can release the item from the his/her worklist
b. This will NOT be releasable from the global/management worklist by a K2 admin
c. You can use custom code to impersonate the userA and release the task as userA

3. If a client event is configured for "Plan Per Destination" "Resolve all roles and group to users"

a. If userA of the group opens the item, userA who has it opened can release the item from the his/her worklist
b. A K2 admin CAN release this this item from the global/management worklist (by selecting the user's whose worklist item status is 'Open')
c. You can use custom code to impersonate the userA and release the task as userA

Please see the documentations below regarding the difference between "All at once" and "One at a time":

https://help.k2.com/onlinehelp/k2blackpearl/userguide/current/webframe.html_destination_rule-destination_rule_options.html
https://help.k2.com/files/2604

The option above the "Resolve all roles and groups to users"/"Create a slot for each role and group" option will result in variant expected behaviors.




 
Be the first to reply!

Reply