{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46421,"path":"service-management-for-the-enterprise/c_ImpDsblStFl.md","title":"Implications of disabling SM state flows","bundle":null,"doc_type":null,"release":"australia","body":"\n# Implications of disabling SM state flows\n\nState flows are used by SM applications to control how a work order or request automatically transitions from one state to the next. When state flows are disabled, various aspects of the ServiceNow system are also changed, as described here.\n\nReview the following implications before setting the **Enable state flows** configuration option to **Off**. After the configuration is saved, state flows cannot be re-enabled from the user interface.\n\nWhen state flows are disabled, the state transition-related behavior of the following business rules, UI actions, and security rules are affected.\n\n-   **Business rules on requests:**\n    -   Group change validation\n    -   Move tasks to pending assignment\n    -   Request-driven dispatch\n    -   Unassigned\n    -   Verify work notes\n-   **Business rules on tasks:**\n    -   Apply dispatch method\n    -   Populate schedule\n    -   Populate schedule - new SOT \\(service order task\\)\n    -   Transitions\n    -   Unassigned\n-   **The following business rules run partially:**\n    -   The part of **Build scratchpad and display info messages** that shows an error message if a task is pending dispatch and auto-assignment fails is disabled.\n    -   For the **Validate changes** business rule, the only part that runs is when the system checks for work notes and rolls them up.\n-   **UI actions on requests:**\n    -   When the **Spam** button on the request form is clicked, the state is not changed, but the work notes indicate that the request was closed as spam.\n-   **UI actions on tasks:**\n    -   Assign to me\n    -   View task on map\n    -   New\n-   **Security rules:**\n    -   State-based aspects of security rules no longer apply. For example, when state flows are enabled, the **Short description** field is not editable when a request or task is closed complete, incomplete, or canceled. When state flows are disabled, the **Short description** is always editable.\n    -   Role-based aspects of security rules continue to apply when state flows are disabled.\n-   **Additional changes when state flows are disabled:**\n    -   The process flow formatter is removed from request and task forms.\n    -   The **State** field can be edited on request and task forms.\n    -   The following configuration fields are changed:\n        -   **Process lifecycle** is set to **request-driven**.\n        -   **Assignment method for requests** is set to **manual**.\n        -   **Assignment method for tasks** is set to **manual**.\n        -   **Approval for new request required** is disabled.\n        -   **Qualification is required for new requests** is disabled.\n        -   **Agent must accept or reject the assigned task** is disabled.\n        -   **Use dispatch queue** is disabled.\n\n-   **[Re-enable state flows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/service-management-for-the-enterprise/t_ReEnableStateFlows.md)**  \nWhen service management state flows have been disabled, they cannot be re-enabled from the user interface.\n\n**Parent Topic:**[Service management states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/service-management-for-the-enterprise/c_ServiceManagementStates.md)\n\n"}}