Last post Sep 01, 2009 10:29 AM by Dipesh Chauhan
Jul 01, 2009 08:51 AM|PaulAik|LINK
I'm currently doing a little investigation into WF to find out if it's viable for a project I'm looking to build. I've got the following scenario in my head, do any of you guys know if it's possible with WF?
a) The user enters a 'visit code' against a client visit that has been cancelled/has some special event happen (e.g. visit not possible due to X).
b) The visit info is sent to WF. A main workflow loop reads the Visit Code and starts a workflow to deal with the business rule (via InvokeWorkflow?) - the main workflow has knowledge of all of the visit codes (a big if/else branch?)
c) A new workflow is spawned to deal with the visit/visit code, the main WorkFlow continues indefinitely waiting for new visits.
All of that sounds feasible, however I'd like to know if it would be possible to do the following:
- Allow users of the system to dynamically create new/change Workflows to deal with new business rules (via a Workflow Manager util?), which are then persisted to the Workflow Database.
- Be able to add these new codes into the main Workflow loop so they'd be caught and processed (e.g. add another branch to the main loop containing another InvokeWorkflow)
Is this possible? Or am I looking for too much...!
windows workflow foundation
Sep 01, 2009 10:29 AM|Dipesh Chauhan|LINK
Main idea behind workflow is to get design time control over the flow.If you try to create workflow at run time then you will be loosing advantages.