MQSeries.net :: View topic

drgincbia · Posted: Tue Jan 06, 2004 5:54 am Post subject:

I have a business area using the web client for workflow. They have process activities where the staffing assignment is made to a virtual user (UCT) using the People from Container (AssignedUser). One of the people in the UCT group will then assign it to an available underwriter by updating the AssignedUser container value, and advance workflow to the next step. That works OK as long as there is an actual assignment activity. However, there are other activities where they want to reassign the work to a new user, but stay in the same activity. They can not use a worklist transfer because this AssignedUser data element value is used in the Description and tracked in their application database, so must be updated via custom application.

Here are two possible options that I'm sure would work, but the first would cause a performance hit & be hard to track and the second would be double maintenance on activities:

1) Have each activity that can be reassigned in a block with an exit condition and a data loop, so the AssignedUser can be updated and the block restarted with the new AssignedUser in the People from Container field.
2) Have a duplicate activity back-to-back for the times that a reassignment must be done.

In the programming guide I noticed that there is an option to do a ForceRestart and specify an different input container to be used in the restarting of the workitem (which would have an updated AssignedUser field). Is this a viable option in the described situation, and can it be used in conjunction with the web client?

I'm looking for a recommendation on the best way to handle this situation. Any help would be appreciated!!

Thanks.
_________________
D. Grandia