Applications Administration Guide > State Models >

Scenario for State Models

This scenario provides an example of a process performed by the administrator. Your company may follow a different process according to its business requirements.

A company has recently configured its Siebel application to support its case review process. To do this, they created a new business component called Case, along with a supporting Case screen and views.

The administrator's task is to set up a state model on this new business component.

First, the administrator uses Siebel Tools to check that Case business component is based on the CSSBCBase class. Then, she discovers that the configurator has already enabled the state model user property for this business component.

Within the Siebel application, she creates a state model based on the Status field (an LOV field) of the Case business component.

The state model contains three allowed states:

• Open. This is set as the default state, the state of any newly created cases.
• Assigned.
• Closed. This is set as a No Delete and No Update state so that a closed case is read-only and cannot be deleted.

The state model contains two allowed transitions:

• From Open to Assigned. Because company policy is that only managers may assign cases, this transition is restricted to the managers' positions.
• From Assigned to Closed. Company policy also requires that employees write a resolution summary of each case before closing. To encourage this, a condition is created so that the status cannot be changed to Closed if the Resolution-Summary field is left blank.

Finally, the administrator activates the state model by restarting the server.