--- sourceDocument: Brazil IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Customizing DevOps flows # Customizing DevOps flows {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Customizing DevOps flows This content guides ServiceNow customers on how to customize or recreate the DevOps Change Request flows---Manual Approval, Minimal Automation Approval, and Advanced Automation Approval---to better fit their business needs. These flows manage change request approvals and the corresponding updates to step execution states, which are critical for integrating with orchestration tools and automating change processes. Show full answer Show less ## Customizing DevOps Flows * **Cloning Flows:** Customers can clone existing DevOps flows from the Base system or Flow Designer by using the "Copy flow" option. The cloned flow can then be renamed, associated with the DevOps Data Model application, customized, tested, and activated. * **Testing and Activation:** After customization, flows should be tested to ensure error-free execution before activation. ## Customizing Specific DevOps Change Request Flows * **Manual Approval Flow:** Updates the state of step execution based on manual or policy-driven change approvals. This is done by calling the Workflow Studio action *Update state of step execution based on change approval* either via a flow or script. This action triggers the Change Control Callback flow to notify orchestration tools. * **Minimal Automation Approval Flow:** When a change moves from new to implementation state upon approval, the flow calls the *DevOps - Update Step Execution and Change Request States* Workflow Studio action (via flow or script) to update step execution state and trigger orchestration notifications. * **Advanced Automation Approval Flow:** Similar to the minimal automation flow but uses the *Update step execution record* Workflow Studio action to update step execution states after approval, again callable by flow or script, triggering orchestration callbacks. ## Calling Workflow Studio Actions For each flow, the relevant Workflow Studio action can be invoked using Flow Designer flows or programmatically via scripts using the `snfd.FlowAPI.executeAction()` method with the respective action name and inputs. This flexibility allows tailored automation and integration with external orchestration systems. Customize or recreate the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, and DevOps Change Request Advanced Automation Approval flows based on your requirements using a flow or a script. You can clone the DevOps flows and then customize them according to your requirements. To clone a flow, navigate to the flow you want to clone from the Base system DevOps flows sections or from the Flow Designer landing page (All \> Process Automation \> Flow Designer). On the top-right corner of the Flow page, select More Actions \> Copy flow. In the Create a copy of this flow dialog box, enter the new name for the flow, and select DevOps Data Model as the application. Select the Copy button to create the new flow. The new flow will open in Flow Designer. Make any changes to customize it to your business requirements. You can run the flow to make sure it has no errors by selecting the Test button on the top-right corner of the screen before activating the flow. Activate the flow when it's ready by selecting the Activate button. ## Customize the DevOps Change Request Manual Approval flow {#using-dev-ops-model-change-flow__section_bzx_wz4_k2c} In the DevOps Change Request Manual Approval flow, the state of step execution is changed based on the change approval. However, you can customize or recreate this flow based on your requirements. After the change request state is moved to approved, canceled, or rejected (either manually or by using a change policy), call the Update state of step execution based on change approval Workflow Studio action to update the State field of the step execution record. You can use either a flow or a script to call the action. Calling the Workflow Studio action using a flow : Calling the Update state of step execution based on change approval Workflow Studio action is required to update the state of the step execution record according to the approval field in the change request record. This action serves as a trigger for the Change Control Callback flow, which is used to notify the change decision to the orchestration tool. Calling the Workflow Studio action using a script : Method to call the Workflow Studio action from a script: sn_fd.FlowAPI.executeAction('sn_devops.update_state_of_step_execution_based_on_change_approval', inputs); ## Customize the DevOps Change Request Minimal Automation Approval flow {#using-dev-ops-model-change-flow__section_ylq_n1p_k2c} In the DevOps Change Request Minimal Automation Approval flow, the change is approved and the state of the change moves from the new to the implementation state. After the change request state is moved to approved, call the DevOps - Update Step Execution and Change Request States Flow Designer action to update the State field of the step execution record. You can use either a flow or a script to call the action. Calling the Workflow Studio action using a flow : Calling the DevOps - Update Step Execution and Change Request States Workflow Studio action is required to update the state of the step execution record. This action serves as a trigger for the Change Control Callback flow, which is used to notify the change decision to the orchestration tool. Calling the Workflow Studio action using a script : Method to call the Workflow Studio action from a script: sn_fd.FlowAPI.executeAction('sn_devops.devOps-_update_step_execution_and_change_request', inputs); ## Customize the DevOps Change Request Advanced Automation Approval flow {#using-dev-ops-model-change-flow__section_vzy_p1p_k2c} In the DevOps Change Request Advanced Automation Approval flow, the change is approved and the state of the change moves from the new to the implementation state. After the change request state is moved to approved, call the Update step execution record action to update the State field of the step execution record. You can use either a flow or a script to call the action. Calling the Workflow Studio action using a flow : Calling the Update step execution record Workflow Studio action is required to update the state of the step execution record according to the approval field in the change request record. This action serves as a trigger for the Change Control Callback flow, which is used to notify the change decision to the orchestration tool. Calling the Workflow Studio action using a script : Method to call the Workflow Studio action from a script: sn_fd.FlowAPI.executeAction('sn_devops.update_step_execution_record', inputs); **Related concepts** * [Accelerating your DevOps change process](https://www.servicenow.com/docs/m4ir1UkZtzCO9rF4zvrFgA "Enable the change acceleration feature of DevOps Change Velocity for automatic change request creation in your pipeline, and use change approval flows and policies to automate approval under certain conditions.")