---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Define the state transitions model

# Define the state transitions model {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Define the model state transitions and conditions to control how a vulnerability traverses through the different workflow states.

## Before you begin

Role required: sn_oper_res.admin

## About this task

The workflow states set up within the state model are shown on the stepper component overview page. Refer to the following setup to configure the stepper component:

1. Display type: Specify whether the state should appear as As Node or As sub-level.
2. Stepper label: This label is displayed on the stepper component for each state.
3. Parent node: If the display type for the state is set to As sub-level, then define the state that will act as the parent node for this sub-level.
{#define-model-state-transitions-for-vul__ol_ojn_ymd_tcc}

## Procedure

1. Navigate to AllOperational VulnerabilityState Models.
2. To add a new workflow state, select New in the State label column.
3. On the form, fill in the fields.  
   {#define-model-state-transitions-for-vul__table_ok4_tfv_kvb__entry__2}

   | Field | Description |
   |-|-|
   | State | Name of the workflow state. Choices is: New |
   | Model | State model that uses this workflow state. This field is automatically set to the state model name. |
   | Display type | Display type of the workflow state. Choices are the following: * As node: Display as a parent state. * As sub-level: Display as a sub-state of the parent state. {#define-model-state-transitions-for-vul__ul_u3q_2lv_kvb} |
   | Stepper label | Label to be displayed on the stepper component for the state. This field is automatically set to the state. |
   | Is optional | Option to select the state as optional. This field appears only when As node is selected from the Display type field. |
   [Table 1. Workflow state form]

   {#define-model-state-transitions-for-vul__table_ok4_tfv_kvb}
4. Select Update.  
   The example shows the Assessment state. The Model State Transitions and State Model Attributes related lists are displayed.
5. To update the model state transition from the Model State Transitions related list, select it from the display name column in the GRC workflow states list.  
6. To add the model state transition, select New on the Model State Transitions context menu.  
   The Model State Transitions context menu is shown in the example.  
   The Model State Transition New record is displayed.
7. On the Model State Transition record form, fill in the fields.  
   {#define-model-state-transitions-for-vul__table_lrv_yw4_brb__entry__2}

   | Field | Description |
   |-|-|
   | From | Name of the state. This field is automatically set to State \[state\]. |
   | To | State that you want to move to from the selected state |
   | Automatic transition | Option to enable the automatic transition of the workflow state. |
   [Table 2. Model State Transition record form]

   {#define-model-state-transitions-for-vul__table_lrv_yw4_brb}
8. Select Submit.  
   The newly added Model State Transition is displayed in Model State Transitions related list.

*[\>]: and then