--- sourceDocument: Australia IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Customizing DevOps flows # Customizing DevOps flows {#ariaid-title1} Release version: Australia Updated March 12, 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 guide explains how ServiceNow customers can customize or recreate DevOps change request approval flows---specifically Manual Approval, Minimal Automation Approval, and Advanced Automation Approval flows---to fit their unique business requirements. It covers cloning existing flows, modifying them in Flow Designer, and ensuring proper execution state updates to integrate with orchestration tools. Show full answer Show less ## Customizing DevOps Flows * **Cloning Flows:** Clone any base DevOps flow via Flow Designer by selecting *More Actions \> Copy flow* , naming the new flow, and choosing *DevOps Data Model* as the application. Customize the cloned flow as needed. * **Testing and Activation:** Use the Test button in Flow Designer to verify there are no errors before activating the customized flow. ## Customizing Specific Approval Flows * **Manual Approval Flow:** After approval, cancellation, or rejection of a change request, update the step execution state by calling the *Update state of step execution based on change approval* Workflow Studio action. This can be done via a flow or script (using `snfd.FlowAPI.executeAction`). This action triggers the Change Control Callback flow to notify orchestration tools of the approval decision. * **Minimal Automation Approval Flow:** When a change request moves from *New* to *Implementation* state upon approval, update the step execution state by calling the *DevOps - Update Step Execution and Change Request States* Workflow Studio action. This also triggers the Change Control Callback flow. Invocation can be done via flow or script. * **Advanced Automation Approval Flow:** Similar to minimal automation, upon approval, update the step execution state using the *Update step execution record* Workflow Studio action via flow or script. This action also triggers the Change Control Callback flow. ## Practical Benefits By customizing these flows, ServiceNow customers can tailor their DevOps change request approval process to align with internal policies and automation strategies while ensuring seamless integration with orchestration tools through consistent state updates and callback notifications. 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/1IOGCXHTnX02RprvPaB2wg "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.")