Siebel Applications Administration Guide > State Models >

Scenario for Managing State Models

This topic gives one example of how state model management might be used. You might use state model management differently, depending on your business model.

A company wants to configure its Siebel application to track suggestions from customers and employees about product enhancements. To implement this configuration, a developer creates a new Enhancements business component and a supporting Product Enhancements screen with views.

The administrator must set up a state model for this new business component. She uses Siebel Tools to check that the Enhancements business component is based on the CSSBCBase class. She discovers that the configurator already enabled the state model user property for this business component.

In the Siebel application, she creates a state model for the Status field (an LOV field) of the Enhancement business component. This state model contains the following allowed state values:

• New. She designates this state value as the default state value. When an enhancement idea is first received, the state value for the Status field of the record is always New.
• Assigned. She sets up this state value.
• Accepted. When she sets up this state value, she selects the check box for the No Delete field and the No Update field so that an accepted enhancement record is read-only and cannot be deleted or modified.
• Rejected. When she sets up this state value, she selects the check box for the No Delete field and the No Update field so that a rejected enhancement record is read-only and cannot be deleted or modified.

This state model contains the following allowed transitions between the state values:

• From New to Assigned. Managers assign enhancement suggestions to the most suitable employees for investigation. Therefore, she specifies that only managers can change the Status field value from New to Assigned.
• From Assigned to Accepted. Employees must write an assessment of each enhancement suggestion before accepting it. Therefore, she creates simple criteria indicating that users cannot change the Status field value for a record to Accepted if the Assessment field for the record is blank.
• From Assigned to Rejected. Employees must write an assessment of each enhancement suggestion before rejecting it. Therefore, she creates simple criteria indicating that users cannot change the Status field value for a record to Rejected if the Assessment field for the record is blank.

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