Siebel Applications Administration Guide > State Models >

Creating State Models and State Transitions

This topic describes how to create state models and state transitions for those models.

To create a state model for a field on a business component, the field must meet the following criteria:

• The field is an LOV (list-of-values) field or MLOV (multilingual-list-of-values) field.
• The field has no dependencies on other fields.

  For example, do not use a constrained LOV field or a calculated field.

This task is a step in Process of Setting Up State Models.

To create a new state model

1. Navigate to the Administration - Application screen, then the State Models view.
2. In the State Models list, create a new record, and complete the necessary fields.

   Some fields are described in the following table.

   Field	Comments
   Name	Type a name that uniquely identifies the state model.
   Business Component	Select the business component for the state model. The dialog box for this field displays all of the business components that are enabled for state models. To enable additional business components, see Configuring Business Components for State Models.
   Field	Select the name of the field for the state model. The dialog box for this field displays the fields that are defined for the business component.
   Activation	Select the date on which the state model is enforced. NOTE:  You can set up more than one state model for a field as long as the activation to expiration periods for each state model do not overlap.
   Expiration	Select the date on which the state model is no longer enforced.

3. Click the States view tab, in the States list create a new record for each state value for the field in the state model, and complete the necessary fields.

   Some fields are described in the following table.

   Field	Comments
   State Name	Select the state value for the field in the state model.
   Default	Select this check box to indicate that the State Name field is the default state value. The default state value specifies the value that is automatically populated in the state model field when a new record is created. NOTE:  If the field in the state model is populated from Siebel Tools, then you cannot override this default in the state model.
   No Delete	Select this check box to indicate that a record with a field in this state is read-only and cannot be deleted.
   No Update	Select this check box to indicate that a record with a field in this state is read-only and cannot be modified. NOTE:  Even if you select the No Delete and No Update fields for a state in the state model, a record with MVG (multi-value group) fields that do not have a direct parent-child link between the parent field and the MVG applet is not read-only when the state for the record has the No Update or No Delete fields selected. To avoid confusion for users, you can remove MVG fields from the child applet.
   Restrict Transition	Select this check box to indicate that only the transitions that you define for the state value are allowed. If you select this check box and do not define transitions, the state value is an end state, and the state value cannot change to another state value. Clear this check box to indicate that the state value can transition to any other defined state value.

4. Click the Transitions view tab, and complete the following steps:
   1. In the Transitions list, create a new record for each state transition that you want to restrict, and complete the necessary fields.

      Some fields are described in the following table.

      Field	Comments
      From State	Select a source state value in the state transition of the state model field. NOTE:  If you do not define a state transition for the State Name field that is the default value, the field in the state model cannot change.
      To State	Select a destination state value in the state transition of the state model field.
      Public	Select this check box to indicate that all users are allowed to perform this state transition. If you select this check box, the records in the Authorized Positions list are not in effect. For more information, see Step b.
      Rule Field	Select a field that controls the state transition. This field is frequently not the field in the state model, but another field in the business component for the state model.
      Rule Operator	Select an operator for the field in the Rule Field.
      Rule Value	Type the state value for the field in the Rule Field. The Rule Field, Rule Operator, and Rule Value fields allow you to specify simple criteria that must be met for the state transition to occur. For more information about creating simple criteria, see About Criteria for State Transitions.
      Rule Expression	Type complex criteria that must be met for the state transition to occur. Users see an error message when they attempt to perform a state transition, and the transition does not satisfy the rule expression.

   2. To restrict a state transition to a group of users (or positions), create records in the Authorized Positions list, and clear the check box in the Public field for the transition record.

      NOTE:  If the check box in the Public field is cleared, and if you do not create positions in the Authorized Positions list, no users are allowed to perform the state transition.