Siebel Business Process Designer Administration Guide > Using State Models >

State Models Overview


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

The state transition can also enforce other behavior. It can control which individuals or groups of individuals can initiate the transition. It also can verify that specific conditions have been met before the transition occurs.

In this state model, the starting point state for all service requests is Open.

Allowable state transitions for this model are listed in Table 89.

Table 89. State Transitions for a Service Request
From State
To State
Cancelled
Open
Closed
Open
Open
Cancelled
Open
Closed
Open
Pending
Pending
Cancelled
Pending
Closed
Pending
Open

The state transition can define the required authorization for transitioning an object. For example, a transition of moving service requests from Open to Cancelled may be restricted to the service center manager. By default, anyone with update authority on an object can change the state, unless this authority is explicitly overridden by the state transition definition within the state model.

The state transition can be preempted if required conditions have not been met. The state machine reviews all required conditions defined for the state model before the state transition is completed.


 Siebel Business Process Designer Administration Guide 
 Published: 29 May 2003