The state machine in the screenshot above is quite simple, and most systems will require a more sophisticated model. However, the concepts introduced in the screenshot (states, events, and transitions) are the same concepts we use to build state machine workflows in Windows Workflow.
In WF, the State
activity represents a state in a state machine workflow. As events arrive, the workflow will transition between State
activities. A state machine workflow must specify an initial state, which will be the starting state for the workflow. A state machine workflow can optionally specify a completed state. The workflow will conclude after it transitions to the completed state.
An EventDriven
activity represents an event in a state machine. We place these activities inside State
activities to represent the legal events for the state. Inside an EventDriven
activity, we can place a sequence of activities that will execute when the event arrives. The last activity in...