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 keep track of suggestions for product enhancements received from customers and employees. To do this, they created a new business component called Enhancements, along with a supporting Product Enhancements 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 Enhancements 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 Enhancement business component.

The state model contains four allowed states:

• New. This is set as the default state, the state of any newly received enhancement ideas.
• Assigned.
• Accepted. This is set as a No Delete and No Update state so that an accepted enhancement is read-only and cannot be deleted.
• Rejected. This is set as a No Delete and No Update state so that a rejected enhancement is read-only and cannot be deleted.

The state model contains three allowed transitions:

• From Open to Assigned. Managers assign enhancement suggestions to the most suitable employees for investigation. Because of this, the transition from Open to Assigned is restricted to the managers' positions.
• From Assigned to Accepted.
• From Assigned to Rejected.

  Employees are required to write an assessment of each suggestion before rejecting or accepting it. To encourage this, conditions are created so that the status cannot be changed to Accepted or Rejected if the Assessment field is left blank.

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