The State Flow Designer allows configuring transitions between the states. In particular, it is used in the practices state models (for example, Incidents State Model, Changes State Models).
You may need to configure transitions for the specified practice (for example, Incidents). For this, you have to create a state model first, and then you can configure transitions.
Creating the state model
The state models are stored in the sys_state_model table.
To create a state model, please complete the following steps:
- Navigate to State Flow Designer → State Models.
- Click New and fill in the form.
- Click Save or Save and Exit to apply changes.
State model form fields
| Field | Description |
|---|---|
| Name | The displayed model name. |
| Table | Choose a table to create a model. |
| Description | Description of the state model in a concise manner. |
| Condition | Specify a condition if you need to create multiple state models for one table. |
The state model is created.
When you are creating conditions, please keep in mind that for the fields types listed below the following operators are supported:
| Field type | Operators |
|---|---|
| True/False |
|
| Choice & Reference |
|
Configuring the transitions
The transitions are stored in the sys_state_transition table.
To configure transitions in existing state model, please complete the following steps:
- Navigate to State Flow Designer → State Models.
- Click on the state model you need to modify.
- In the Related Lists area, click New and fill in the form.
- Click Save or Save and Exit to apply changes..
State Transitions form fields
| Field | Description |
|---|---|
| State model | The state model containing transitions. |
| State | The state will be initial for the subsequent transitions. |
| Available transitions | Choose the transitions available for the state specified in the State field. |
| Description | Description of the transition in a concise manner. |
| Autotransition | Select this checkbox to enable the scheduled automatic state change for the state specified in the State field. |
| Auto State | Specify the state the record will be automatically transited to. |
| Schedule | Specify the schedule to calculate the auto-transition date. |
| Duration | Specify the duration (in business time, days, hours, and so on), after which time the state will change automatically. |
Example of the transitions configured
Consider an example of the transition configured.
For example. the ITSM Incident model for the Incident table exists. And among others, there is the transition:
In this screenshot, the Completed state can change to the Rejected by User. Closed, In Progress and Assigned states. Also, if the state will not change for the three days 8 hours (on an 8-5 weekdays calendar; it's equivalent ten working days 8 hours each), then it will happen automatically.
We can see transitions defined by this model for the Completed state on the incident form.
