Onboard to DevOps Change Velocity using Workspace

  • Release version: Yokohama
  • Updated July 31, 2025
  • 4 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 Onboard to DevOps Change Velocity using Workspace

    After installing DevOps Change Velocity, ServiceNow customers can integrate their DevOps toolchains and automate change requests directly from the DevOps Change Workspace. The onboarding process varies based on user roles—DevOps admin, tool owner, or app owner—each with specific responsibilities and access rights for connecting tools, creating applications, and enabling automated change requests.

    Show full answer Show less

    Onboarding Roles and Responsibilities

    • DevOps Admin (role: sndevops.admin):
      • Connect DevOps tools and orchestration tools via the Connect a tool option.
      • Create applications and associate DevOps objects such as pipelines with them.
      • Enable automation of change requests from orchestration pipelines.
      • Modify pipelines to enforce change control and verify automated change request creation.
    • Tool Owner (role: sndevops.toolowner):
      • Connect DevOps tools using the connect playbook activity.
      • Coordinate with admins or app owners to create and associate applications if not already done.
      • Automate change requests and modify orchestration pipelines to enable change control.
      • Verify automated change requests are created by running pipelines.
    • App Owner (role: sndevops.appowner):
      • Request DevOps admins or tool owners to connect DevOps and orchestration tools.
      • Create applications and associate relevant pipelines.
      • Enable automated change requests and adjust orchestration pipelines for change control.
      • Confirm successful automation by running pipelines.

    Workspace Widgets

    The DevOps Change Workspace includes several widgets to provide insights and management capabilities:

    • Tools widget: Displays connected, disconnected, and unconfigured tools, grouped by capabilities and tool types. DevOps admins and tool owners can connect tools directly from here.
    • Applications widget: Shows the number of applications with and without associated pipelines, along with work items, commits, and pipeline executions over the last 30 days. Admins and app owners can create applications from this widget.
    • Automated Change Requests widget: Provides metrics on change requests created and pending approval in the last 30 days, pipelines with change control enabled but lacking automated change requests, and tool groupings by capability and type.

    Practical Benefits for ServiceNow Customers

    This onboarding guide enables customers to effectively integrate their DevOps environments with ServiceNow, automate change request workflows, and gain operational visibility through workspace widgets. By following role-specific steps, customers can ensure seamless automation, enforce change control in orchestration pipelines, and monitor tool and application statuses to optimize DevOps change velocity.

    After installing DevOps Change Velocity, you can integrate with your DevOps toolchain and automate change requests directly from the DevOps Change Workspace.

    You can onboard as a DevOps admin, a tool owner, or an app owner.

    Onboard as DevOps admin

    Role required: sn_devops.admin.

    1. From the Home page, from the Get started with DevOps Change Velocity guide, select Connect a tool.

      Onboarding page for DevOps admins.

      Note:
      To automate change requests for pipelines, connect your orchestration tool.
    2. Using the connect playbook activity, connect to your DevOps tools.

      For more information about connecting to a tool, see Integrating DevOps Change Velocity with third party tools.

    3. Select Create an application to create an application and associate objects to it.

      For more information about creating an application, see Create an application - Workspace.

      Create an application.

    4. To automate change requests for pipelines, connect your orchestration tool and associate the pipelines with your application.

      For more information on associating pipelines, see Associate tool objects to applications - Workspace.

    5. Select Automate change to create an automated change request.

      For more information about creating automated change requests, see Automate DevOps change request creation.

      Automate change requests.

    6. Modify your orchestration pipeline to enable change control.

      You can run the pipeline to verify that change requests are automatically created.

      Waiting for change request creation.

    The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.Completed getting started guide for tool owner.

    Onboard as a tool owner

    Role required: sn_devops.tool_owner.

    1. From the Home page, from the Get started with DevOps Change Velocity guide, select Connect a tool.

      Connect a tool.

      Note:
      To automate change requests for pipelines, connect your orchestration tool.
    2. Using the connect playbook activity, connect to your DevOps tools.

      For more information about connecting to a tool, see Integrating DevOps Change Velocity with third party tools.

    3. If an application hasn't been created, ask your DevOps admin or app owner to create an application and associate objects to it.

      For more information about creating an application, see Create an application - Workspace.

      Ask app owner to connect an application.

    4. To automate change requests for pipelines, connect your orchestration tool and associate the pipelines with your application.

      For more information on associating pipelines, see Associate tool objects to applications - Workspace.

    5. Select Automate change to create an automated change request.

      For more information about creating automated change requests, see Automate DevOps change request creation.

      Automate change requests.

    6. Modify your orchestration pipeline to enable change control.

      You can run the pipeline to verify that change requests are automatically created.

    The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.Completed getting started guide for tool owner.

    Onboard as an app owner

    Role required: sn_devops.app_owner.

    1. Ask your DevOps admin or tool owner to connect to your DevOps tools.

      Getting started guide for app owners.

      Note:
      To automate change requests for pipelines, connect your orchestration tool.
    2. Select Create an application to create an application and associate objects to it.

      For more information about creating an application, see Create an application - Workspace.

      Create an application.

    3. To automate change requests for pipelines, ask your DevOps admin or tool owner to connect your orchestration tool.
    4. Associate the pipelines for which you want to automate change requests with your application.

      For more information, see Associate tool objects to applications - Workspace.

    5. Select Automate change to create an automated change request.

      For more information about creating automated change requests, see Automate DevOps change request creation.

      Automate change requests.

    6. Modify your orchestration pipeline to enable change control.

      You can run the pipeline to verify that change requests are automatically created.

    The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.Completed getting started guide for app owner.

    Workspace widgets

    Tools widget
    The Tools widget gives an overview of your connected tools, with the following details:
    • Number of tools that are in the connected state. You can select the card to see the list of connected tools.
    • Number of tools that need attention. You can select the card to see the list of unconfigured tools.
    • Number of tools that are in disconnected state. You can select the card to see the list of disconnected tools.
    • Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    • Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    • DevOps admins and tool owners can connect to a tool from the widget.

    Tools widget.

    Applications widget
    The Applications widget gives an overview of your applications, with the following details:
    • Number of applications with at least one associated pipeline. You can select the card to see the list of apps with pipelines.
    • Number of without any pipelines. You can select the card to see the list of apps with no pipelines.
    • Number of work items, commits, and pipeline executions from all applications in the last 30 days. You can select the card to see the list of disconnected tools.
    • Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    • Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    • DevOps admins and app owners have the option to create an application from the widget.

    Applications widget.

    Automated change requests widget
    The Applications widget gives an overview of your applications, with the following details:
    • Number of change requests created in the last 30 days. You can select the card to see the list of change requests.
    • Number of change requests that are pending approval in the last 30 days.
    • Number of pipelines with change control enabled, but hasn't automatically created a change request.
    • Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    • Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.

    Automated change requests widget.