---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# State Management

# State Management {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of State Management

State Management in ServiceNow allows administrators to defineState ModelsandState Transitionsthat control how records progress through predefined states.
It is active for all instances and applies primarily to tables extending thetasktable.
This capability ensures records follow a controlled workflow lifecycle by restricting state changes based on specified conditions.
Show full answer Show less  

## Key Features

* **State Models:** Lists of states representing the expected workflow stages for a record type. Administrators can create state models for custom or standard task tables by specifying applicable states and conditions for applying the model.
* **State Transitions:** Conditions defined for entering or exiting each state. These transitions enforce valid state changes and prevent users or integrations from setting invalid states regardless of input method (UI, scripts, REST/SOAP APIs, etc.).
* **Conditional Control:** Using the condition builder, administrators can define rules that control when a state model applies to records and what conditions must be met to move between states.
* **Choice List Restriction:** The State field's choice list dynamically adjusts to show only valid states based on the defined transitions, simplifying user selections and enforcing process adherence.
* **Example State Models:** Includes example models (normal, emergency, standard changes) provided as templates for creating new models. These are not enabled by default and should not be modified for existing change requests to avoid breaking workflows.

## Practical Application for ServiceNow Customers

By leveraging State Management, you can:

* Ensure task records progress through valid lifecycle stages, improving process consistency and governance.
* Prevent unauthorized or invalid state changes from any source, maintaining data integrity.
* Customize workflows for new task types by defining states and transitions specific to your business needs.
* Simplify user experience by limiting state choices to valid options, reducing errors and training needs.

For example, if you create a custom airline reservation table with states like Held, Confirmed, Completed, and Canceled, you can define a state model and transitions so that users can only move from Confirmed to Completed when appropriate, automatically restricting invalid selections.  
State Management enables an administrator to define State Models and State Transitions
that control how a record is allowed to transition through a predefined list of
states.

An example of a state transition is when the State field in a facilities request is moved from the Assigned state to the Work In Progress state.

State Management is active for all instances.

## What is a state model? {#state-model__section_bwb_5pd_fbb}

A state model is a list of states that describe an expected record workflow through the lifecycle of the record.
State models can be defined for any table that extends the task table. State models simplify
defining the state transitions allowed for a specific task type.{#state-model__ph_state_model_workflow}

In the State Model \[sys_state_model\] table, define the name of the
state model and which task table the state model is applied to. Use the condition builder to
specify any conditions for applying the state model to records and any required condition
for moving between states.

For example, you could define a state model for a new custom application for airline
reservations. The custom application has a Reservation Request \[reservation_request\]
table with 4 states: Held, Confirmed,
Completed, and Canceled. You could
define the state model to target the Reservation Request table, and then define the
state transitions for each of the 4 states. When you enable the state model, the choice
list for the State field includes only the choices allowed by the
conditions in the state transitions.  
Note:  
State Management includes example state models that are copies of the normal, emergency, and standard change request state models. By default, these examples are not enabled. Use them only as examples to develop a state model and transitions for a task table that does not have a state model. Do not enable these example state models for change requests and then make changes to them. Doing so breaks existing transitions for change requests.

## What is a state transition? {#state-model__section_nm2_pwd_fbb}

State transitions are a list of conditions for entering or
exiting each state defined for a table. In the State Transitions \[sys_state_transition\]
table, use the condition builder to build a list of conditions required for entering or
exiting each state.

To prevent users from choosing an invalid state, any attempt to update a record's state
is denied if it violates the state transitions, whether the attempt is through user
input, a script, a Web API such as REST or SOAP, or any other source.

State transitions control the choice list for the
State field on the target task table and prevent you from choosing
any state value that does not adhere to the underlying process or does not meet the defined
conditions for the transition.

For example, if the enter condition for the Completed state is
State is Confirmed, only records in the Confirmed state can
transition to the Complete state. When a record is in the Confirmed state, the only
choice in the State field choice list is
Completed.