|Bookshelf Home | Contents | Index | Search | PDF|
Siebel Business Process Designer Administration Guide for Financial Services > Using State Models > Creating State Models and State Transitions >
Creating State Models
Creating and defining a state model is handled through the State Models view. To display this view, choose Site Map > Business Process Administration > State Models.
Table 90 describes the fields in the State Models view.
Table 90. Fields in the State Models View Field Description Activation The date on which the state model begins to be enforced. Business Component The business component that the state model is based on. The pick applet for this field displays all of the business components that have been enabled for the state model. To enable a business component that is not enabled by default, see Enabling Business Components for State Models. Created By The Siebel user name for the user who created the state model. This read-only field is not displayed in the list applet. Created Date/Time The date and time that the state model was created. This read-only field is not displayed in the list applet. Comments Text that you can add to describe the state model. Expiration The date on which the state model is no longer enforced. Field The name of the field that the state transitions apply to. The pick applet for this field displays all of the fields that have been defined for the business component selected in the BusComp Name field. Name Name that uniquely identifies the state model. This is a free-form text field. State Description A description of the state that is named in the State Name field. You can specify or modify the description for the current state in the States multi-value group applet. State Name A list of all possible values for the business component field that the state model is based on. This is a multi-value group. All values that are used in the state transition must be added to the values for State Name.To add a new value, click New in the States multi-value group applet. This applet also allows you to change which state name is the default, and to modify the state description.If there is a list of values for the business component field, you can select the value from a pick applet. Otherwise, enter the appropriate value in the State Name field.Optionally, you may specify restrictions for the state model by activating the following flags:
- No Delete. When checked, records in this state cannot be deleted unless they are referenced by a parent record in which the Cascade Delete property is set to Delete. Cascade Delete will always override the State Model restrictions.
- No Update. When checked, records in this state are read-only and cannot be updated. Note that No Update also affects a record's child records. For example, if an account becomes read-only due to use of the No Update restriction, the related contacts for the account also become read-only, so inserting and deleting contacts is no longer possible.
- Restrict Transition. When checked, records in this state that do not have a state transition defined cannot change states. This effectively turns the record's state into an end state.Note that despite No Delete and No Update restrictions specified for the state model, MVG fields that do not have a direct parent-child link between the parent field and the MVG applet will not be read-only when a record is in a No Update or No Delete state of a state model. To avoid this issue, you can use Siebel Tools to remove the MVG field from the user interface.Once all states are defined, you should select one state as the default. The default state name specifies a beginning value for the business component field. For example, in the Service Request business component, the default value for the Status field is Open.To specify or change which state name is the default, click in the Default column on the States multi-value group applet.
To create a new state model
- Choose Site Map > Business Process Administration > State Models.
- In the State Models list applet, click New to create a new record for a state model.
- Fill in the appropriate fields described in Table 90.
Enabling Business Components for State Models
You can enable state models on any business component (not enabled by default) that is based directly on the CSSBCBase class.
NOTE: Enabling state models for business components based on subclasses of CSSBCBase class is not supported.
To enable state models on a business component, the fields used:
- Must be of single value.
- Can only have a specific set of values as defined by the set of records returned by querying Screens/Application/List of Values/List of Values on the corresponding
LOV_TYPE. For example,
TODO_TYPEis the set of action types. The corresponding field in the Activity business component can only take one of those values.
- Should have no dependencies on other fields.
To enable business components for state models functionality
- Lock the project for the selected business component.
- Create a new business component user property with the following properties:
Recompile the Siebel repository.
NOTE: For these Siebel Tools objects to be accessible in the Siebel client, the Siebel repository must be updated in the Siebel database. State models are read from the repository, not from the compiled Siebel repository file (.srf). The client must also have the correct repository name specified in the configuration file (.cfg) in the parameter "DockRepositoryName."
CAUTION: Do not create a state model for the business components Enterprise Service Definitions or SRMSynch Request. These are used for server administration. If a state model for one or both of these business components exists, do not modify it.
|Bookshelf Home | Contents | Index | Search | PDF|
Siebel Business Process Designer Administration Guide for Financial Services
Published: 22 May 2003