Approch For Complex Workflow

saumil

Hi,
I am having a scenario, where having multiple tasks for different modules (functionality) in a workflow.
The workflow Complexity is increasing like anything.
Should I use nested job kind of thing for every functionality or any better Approach is there ?
I know it's depend on the kind of requirement.
But is there any proposed way for workflow having multiple task ?



Saumil Shah
Technical Associate
Mahindra and British Telecom
+0919819890479

Adam Stoller

Since I'm not sure what you mean by "multiple tasks for different modules (functionality)" it's difficult to answer your questions.

Workflows always have multiple tasks (at the very least 2 - one being an endtask).
Sometime the tasks are run concurrently, sometimes serially - both methodologies can appear within the same workflow (and frequently do).

Nested workflows are a reasonable choice if you need to "divide-and-conquor" a set of files into sub-processing (e.g., images go through one process, html files go through another; or English versions of content go through one process and Spanish versions of the content go through an identical but separate process)

Nested workflows can also be used to modularize workflow component pieces (sub-processes) such that you could create a submit, assign, and new_job workflow where the only difference is in the first couple of tasks, and then have each of them call a common nested workflow "module" to complete the rest of a consistant process from that point on.

Perhaps if you posted your proposed (or existing?) workflow diagram (as an attachment) we could look at it and provide some more specific critiques and suggestions.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com