Usually when your debugger encounters a workflow component, there's a task to be worked to make the workflow continue. On the last tab of the debugger, under Workflow Task response, is a hyperlink to the task to be worked. Once worked, the debugger should continue as normal.

I checked out the link as you said and when I click on it, I'm brought to the item that needs to be worked.  When I click on the button on the form to continue the workflow, it follows through no problem.  The only thing though is that I'm never presented with this  when the workflow runs.  When the blue arrow hits the form for New Employee above, the process just ends and I don't even get to see the form that needs to be filled out.

Each new Dialog workflow is seen as a seperate entity, so you can't flow from one to the other within the same web session. The repsonse page links are different, the session ID's are different etc...

The question is - why exit the first dialog workflow at all? If you want to continue with New Employee right after whatever you are doing in the first dialog workflow, you should just add more web forms in the first dialog workflow. The onl reasn to move from one to the other is so you can assign the task to someone else.

rob

That's what I was thinking and it does make sense.  I was trying to seperate out the whole process as much as possible since this workflow will have multiple forms, but I guess I can use a linked model component to accomplish this.

Thanks for the help on this everyone.

Tom