Customizing DevOps flows

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
  • Summarize
    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 provides instructions for ServiceNow customers to customize DevOps Change Request approval flows, including Manual, Minimal Automation, and Advanced Automation approval types. Users can clone and modify these flows to align with specific business requirements using Flow Designer or scripts.

    Show full answer Show less

    Key Features

    • Cloning Flows: Navigate to the relevant flow, select More Actions > Copy flow, name the new flow, and select DevOps Data Model as the application.
    • Flow Customization: After cloning, make necessary adjustments in Flow Designer, and test the flow using the Test button before activation.
    • Workflow Studio Actions: Utilize specific actions like "Update state of step execution based on change approval" and "Update Step Execution and Change Request States" to manage the state of change requests and executions.

    Key Outcomes

    By customizing the DevOps flows, customers can accurately reflect their change management processes, ensure efficient handling of approvals, and maintain synchronization with their orchestration tools. Activating these tailored flows will enhance operational effectiveness and streamline the DevOps change process.

    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

    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.

    DevOps Change Request Manual Approval flow

    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

    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.

    DevOps Change Request Minimal Automation Approval flow

    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

    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.

    DevOps Change Request Advanced Automation Approval flow

    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);