Workflow Web Services

I think this is what you're looking for??

Here's an example of parallel workflow. Under videos you'll see a Parallel Workflow video.

However, don't do it this way if you're creating hundreds of tasks. The persistence data that gets stored with the workflow will get massive and cause problems on your server. Instead, create a second workflow for the user request tasks and use the Web Service Caller component generator to create a component to call the second workflow. Doing it this way gives you the asynchronous behavior, like in the parallel workflow example, because when you start a workflow via a web service it returns immediately with the tracking id. If you need the workflow to wait for all the tasks (sub workflows) to complete and merge you can use the Embedded Merge Component which gives you a model that decides if the workflow can continue. Generally, what you’d do in this case is log what’s going on in the database so you can have a simple query that decides if it should continue. For example, in the main workflow I might write a record to a table with attributes related to the overall workflow, like the submitter and the tracking id. I’d have a second table for the tasks that includes the parent tracking id, tracking id and some sort of status. In each sub workflow I’d write a record to the tasks table and make sure that status of that record is updated whenever the sub workflow completes. Then the query in the Embedded Merge Component might be something like this: select count(*) from MyTasksTable where ParentTrackingID = @ ParentTrackingID and Status = ‘Pending’