Workflow Soluiton

Top of the Morning

Suppose you have created a Web Form and you run it through the Debugger.  At some point in debugging, the Form you have created is now being presented to you and you fill it out and click Submit and the debug process keeps going.  All is good with the Web Form and it is doing exactly what you want.  At the end of the debugging session the Data that you entered into the Form, what happens to it and/or where does it go?
Thanks

The difference between a debug project and a published project is minimal.  The debug project is put into a temporary folder in the Debug folder (.../Workflow Designer/WorkflowDeploy/Debug).  A published project is permanently put into the Release folder (.../Workflow Designer/WorkflowDeploy/Release).

There are multiple ways for you to save data from a form.  You can connect your web form to a database, you can save data to your file system, you can email it, etc...These functions will work exactly the same whether they are called from a published project or from a debugging process.

Thanks for the response

So you are saying, if my Web Form is developed to save the data to the Ensemble DB, when I run it through the debugger it WILL WRITE the data to the Ensemble DB.  Hence, I better have a dev Ensemble DB and during the Dev phase of the WEB Form have it pointed to dev and then, just prior to publishing, point the Form to the production Ensemble DB.  ('Point to Production' may not be they best choice of words, in reality I will have to configure any WorkFlow Component to point from dev to prod, correct?)

Thanks again

Yes, the above is correct. Typically your database connectivity is set by:

1. a "connection string" project property (which you would have to manipulate before publishing between dev/UAT/prod environments - this is usually the case for connecting to a non-ProcessManager database)
2. whatever the Workflow Server's task tray tool is pointing to that you publish to, as far as a ProcessManager server. In a Dev box's case, it's probably pointing to itsself and thus using it's PM database (same for UAT/Prod/etc.)

Thanks