This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

I N T R O D U C I N G   W I N D O W S   W O R K F L O W   F O U N D AT I O N

922

8849CH26.qxd  10/10/07  11:46 AM  Page 922

---

In contrast to sequential workflows, state machine workflows do not model activities using a

simple linear path. Instead, the workflow defines a number of 

request states and a set of related

events that trigger transitions between these states. Figure 26-4 illustrates a simple state machine

WF diagram that represents the processing of an order. Don’t worry about the details of what each

activity is doing behind the scenes, but do notice that each request state in the workflow can flow

across various states based on some internal event.

Figure 26-4.

State machine workflows do not follow a fixed, linear path.

State machine workflows can be very helpful when you need to model a business process that

can be in various states of completion, typically due to the fact that human interaction is involved

to move between states. Here, we have a request state that is waiting for an order to be created.

Once that occurs, an event forces the flow of activity to the order open state, which may trigger an

order processed state (or loop back to the previous open state), and so forth.