Siebel Business Process Designer Administration Guide > Introduction to Siebel Workflow >

Understanding State Models

The State Models module provides a data-driven method for extending workflow control based on the status of an object such as a service request or a product defect. A state represents the status of an object, such as Open, Closed, or Pending.

You use State Models primarily to enforce authorization and transition rules. A state model restricts who can change a given attribute on an object, such as the status on a service request and the conditions that must be met to make the change.

State Model is the blueprint of acceptable states and state transitions that the state machine enforces. The state machine then makes sure that these objects go through the desired process defined in the state model.

The state machine is the engine that enforces the transitions between states for an object during its lifetime. The state represents where the object is in its lifetime. The state can also control whether or not the data of that object can be modified. As an example, a service request that is in a Closed state may be considered "frozen," such that its attributes cannot be modified.

A state transition defines the allowable migration of an object from one state to the next. For instance, a service request that has been closed but must be re-opened may go from the Closed state to an Open state, and may go from Open to Pending, but may not transition directly from Closed to Pending. The allowable migration of a service request from Closed to Open, or Open to Pending, represents defined state transitions.

 Siebel Business Process Designer Administration Guide 
 Published: 29 May 2003