hello every body
can some one help me to know the difference between state machine workflow and sequential workflow.
what's the advantages of every one
thanks for help
difference between state machine and sequential workflow
Hot Topic
- Beta2: WCA.exe
- When is parent non-null? / How to get to container activity?
- XAMLPad Problem
- Passing parameters into the workflow.
- end-user workflow design & compilation
- Is there any way to time procedures in vb2005.
- Custom WorkflowScheduler issue - Timed workflows are being scheduled twice
- SqlWorkflowPersistenceService exception using beta2
- SqlPersistenceService and Oracle
- Calling into an instance through a web service
Windows Vista
- Multi Display support on Vista
- Vista Install 5342 problems
- WorkFlow Instance Does not Initialize
- Using CallExternalMethodActivity in a state WF machine
- SqlWorkflowPersistenceService exception using beta2
- Problems Installing CTP February on Toshiba Tecra A4
- disabled/inactive menu actions
- Synchronization of Workflow instances?
- UI Graphics Application and Guideline Release Date
- knowing wich activity idled the workflow.
difference between state machine and sequential workflow
jbrunning
lvying
One of the best advantages to a state machine workflow is the ability to describe a process based on business events. Especially in document management types of workflows. Describing workflows based on state also enables users to see clearly what the status of a workflow is. Also, state machine workflows are easier to code based on events and the process of listening for them. Sequential workflows are more ideal for processing and linear stepping logic type of workflows and do not lend themselves to easy understanding by business process analysts or users. The best material for looking at the advantages and disadvantages of both types is the book "Windows Workflow Foundation Book".
smc750