While redirecting individual worklist items is similar to the capabilities in K2 ‘03 from either the K2mng or workflow.management APIs, you have much more power and flexibility provided within SmartObjects to satisfy this need in a way that is auditted and tracked automatically in the "out of the box" reports.
The worklistitem.redirect(struser) method is only useful for reassigning a worklist item to an individual. The link between group assigned activities, slots, and allocations would be completely confused if tried to redirect a single worklist item to a group from this API call. If you want to redirect an activity to multiple people, or if you require a reasonably reportable and auditable trail during re-assignments or delegation, you should employe a redirection method that completes and re-instantiates the same activity with the new destination information.
Typically this can been accomplished by either:
1) A loopback line that allows the activity to be finished resolving a certain action (ie. “Redirect”) to a line that is looped back to the same activity. This way you can leverage the destination sets associated with the activity and make fresh use of slots when assigned the activity to a different group, list, roles etc within the organization.
(see loop-back line in the image below)
2) A second activity customized for this particular group (ie. Redirecting a support ticket to the development team). This allows for specialized actions, client and server events that apply only to the redirected recipient.


