State machine Workflow
state machine workflows are often used to simulate an alternative to the flow of events that cannot be predicted by human behavior, for example, when an event-driven process executes in an approval process, usually as an external event and as a directed transformation, usually as an external event and as a guide between other possible states. The state machine workflow must include the initial state and the final state, which represents the start and finish status of the process. This is a flexible logic flow that loops back and forth between the States of a workflow, because external events drive a state machine workflow, which is inherently passive.
It contains several important basic elements.
State Entry (enter), status Exit (left state), Transitions (transition), Trigger (Trigger), Condition (condition), action (behavior), final state (final)
Transitions:State machine Use
TransitionsLets you switch from one state to another. The logic flow of the state can be converted,
TransitionsOnly one direction of flow. Therefore, if the state changes from one state to another and then returns to its original state, it must go through two
Transitions
Trigger:Can be done by using
TriggerExecute custom code bookmark activity, usually as a bookmark activity container.
Condition:An expression used to determine the success or otherwise of a state transition after a bookmark activity has been activated
Summarize
This is a function implemented in NET 4.0, Flowchar can fully implement all the StateMachine business logic, the structure of Flowchar to show StateMachine, by intercepting the bookmark implementation [into the state],[end state ]
State machine Workflow