Waiting for a Job to finish before another starts

I want to create a workflow where some author is assigned the task of updating some piece of content. No problem.

The part that is getting my head in a knot is the following. I want to be able to say that this job is dependent on these other jobs (already in motion). This task in the job cannot start until some task in all the depending jobs has completed or the depending job end.

I'm not sure how to do this. Its a relatively common thing in other task management applications, but I'm not sure if Teamsite does this easily. Even if its difficult, I want to be able to do this.

Adam

Find more posts tagged with

Comments

MattP

Adam-
Dave has posted a similar request in another forum.

http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=suggestion_box&Number=10844&page=0&view=collapsed&sb=5&o=0&part=

I don't think there was any resolution, unless he heard something from IWOV.

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Migrateduser

Nope, no one from Interwoven responded to my idea. If you use the nesting concept, where you have a parent job, which may do nothing more thant kick off the other 2 workflows you need to be dependent on each other, then I think you can create dependencies that the child jobs would have on each other. I think this is doable because the parent can control variables that both children can manipulate. If, on the other hand, you want to create dependencies on two distinct jobs, then that is quite a bit more complex. I think it still can be done, but you have to build in some extra functionality to both workflows to constantly check whether a dependency has been established. It's something that might be interesting to design. But, for now at least, you have to roll your own solution. Judging by what I've seen coming down the road in the workflow world, it's not likely to become a priority. I don't even know if it's been noticed enough to even get the useless "feature request" tag and been dropped into that black hole yet.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Lee

We've done something similiar. the key question is does your child workflow know its parent(s) workflows.

assuming that it does write a wf variable with a list of parent workflow id's in the child workflow.

transition to a dummy task set to time out in x amount of time.

this transitions to an external task which reads each parent id from the workflow variable and gets info about each parent id. if all parent id's are "complete" then transition task to next task. if parents still not complete transition back to the dummy task. and repeat

lee c