Workflow Services
-
Ok so I am looking into the 3.5 workflow services and developing support for some application form workflows. So far I have only come across fairly simplistic tutorials, the best being on channel9. I can understand that, there seems to be an astonishing level of complexity involved in putting one of these together. My intentions are to have ASPX forms deployed via sharepoint services. The forms are to be served by a workflow service and data stored on SQL Server. Basically a form to be filled, various levels of sign off with a reject or cancel option where reject allows the originator to resubmit. There may be substantial delays during the workflow. From my investigations so far it seems a state machine workflow will be the best solution but a sequential workflow may meet most requirements. Issues are Which workflow to use? It seems all interaction needs to go through a send/receive event and therefore serialised datasets will be passed through the service. Should the supporting data for the form (tables for dropdowns) also pass through the workflow service or should I seperate the static data from the workflow data? So far the tutorials seem to assume the data is discarded once the workflow is completed (stored as xml during the workflow) but I would like to retain the information for analysis. Should the xml data be parsed out to tables etc for easier query access. Am I missing anything from the following list Persistence data store - SQL Server Form information and static data - SQL Server Logic layer to interact with the form information database (Program.cs) Contract/Interface per application form Workflow Service Client (ASPX) Also if there is a tutorial/article out there related to this type of workflow I would appreciate a link.
Never underestimate the power of human stupidity RAH