Digital integration form in EA Workspace

  • Release version: Zurich
  • 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 Digital integration form in EA Workspace

    The digital integration form in EA Workspace enables ServiceNow customers to manage and update integrations between two business applications or between a business application and an external company. It provides a structured way to document essential details about the integration, its lifecycle, and its business impact, supporting effective governance and operational management.

    Show full answer Show less

    Key Features

    • Identification Fields: Includes unique identifiers such as Name and Number (auto-generated), along with Provider and Subscriber Business Applications and their respective digital interfaces to clearly define integration endpoints.
    • Integration Type and Subtype: Differentiates among Data Integration, Process Integration, and User Interface Integration, with detailed subtypes for Data Integration to specify the nature of exchanged data or processes.
    • Version and Lifecycle Management: Tracks integration versions and lifecycle stages/status to help Application Owners and Architects monitor use, changes, and transitions over time.
    • Functional Attributes: Captures data flow direction (outgoing, incoming, bidirectional), initiating application, trigger methods (manual, scheduled, event-driven), frequency, response type (synchronous/asynchronous), interaction type (e.g., guaranteed message, pub-sub), and middleware used.
    • Business Impact Assessment: Records criticality, confidentiality, integrity, and availability levels of the integration to evaluate risk and importance.
    • Ownership and Support: Details business and IT owners, subject matter experts, and support groups responsible for the integration.
    • Activity Logging: Allows for work notes and comments about the integration for ongoing tracking and collaboration.

    Key Outcomes

    Using this form helps ServiceNow customers to systematically document and manage digital integrations, improving visibility into integration dependencies, responsibilities, and technical details. It supports governance by tracking lifecycle stages and business impact, enabling informed decision-making about changes and risk management. Ultimately, it facilitates smoother operations, clearer accountability, and enhanced communication between business and IT stakeholders involved in digital integration processes.

    Use the digital integration form to update the digital integration between two business applications and between a business application and an external company.

    Table 1. Digital Integration form
    Field Description
    Name Unique and meaningful name of the digital integration.
    Number Number of the digital integration. This field is automatically generated with the DINTG prefix and can’t be edited.
    Provider Digital Interface Name of the digital interface. Because a digital integration between two business applications or services uses a digital interface (API), you must select an interface related to the provider business application or service. This field is automatically generated and can’t be edited.
    Provider Business Application Name of the business application that provides the digital interface and enables to consume or ingest data. Changes, ownership, and responsibilities of the interface are often connected to the provider.
    Note:
    Being a provider or subscriber business application doesn’t refer to the data flow direction (incoming, outgoing, bidirectional). The data flow direction is managed by the Data Flow Direction attribute.
    This field is automatically generated and can’t be edited.
    Subscriber Digital Interface Name of the digital interface that subscribes for the integration.
    Subscriber Business Application Name of the business application that uses the provided interface to consume, exchange, or ingest data to support a business capability. The subscriber business application is affected by the changes or an outage face connection or data loss.
    Note:
    Being a provider or subscriber business application doesn’t refer to the data flow direction (incoming, outgoing, bidirectional). The data flow direction is managed by the Data Flow Direction attribute.
    Subscriber company Reference to the (external) company subscribing to this integration.
    Type Type of the integration.
    Use the following options:
    • Data Integration: Use this option when the integration must mainly focus on the exchange of data such as users, groups, locations, configuration items, and departments.
    • Process Integration: Use this option when the integration is about an interaction of transactional data to support a specific process.
    • User interface Integration: Use this option when the integration opens a connection with another application and sends app data via a URL to query the application.
    Subtype Subtype of the integration.
    This field appears only when Data Integration is selected from the Type field. Use the following options:
    • Process configuration
    • Foundation data
    • Configuration items
    • Events
    • Reporting
    • Sys log
    Version Version of the integration. You can apply a practice of designing, planning, and managing changes to an Integration. You can describe the different changes and capabilities according to version in the Description field. This field helps Application Owners and Architects to look up which version of an integration is in use. This also helps to decide whether to change the life cycle.
    Life Cycle Stage Life cycle stage of the integration.

    Helps to track the life cycles for products, assets, contracts, CIs, locations, and other objects. Using the standard CSDM life-cycle values helps you to track objects through their transitions over time. Reporting can therefore accurately reflect the actual states of CIs: usage, availability, end of support, and so on.
    Life Cycle Stage Status Life cycle stage status of the integration. The state transition of a Digital Integration guides you through the different stages of its life cycle. A life-cycle state is the combination life-cycle stage and life-cycle status of a Digital Integration during the life cycle.
    Business Unit Name of the business unit that the integration belongs to.
    Description Description of the digital integration. Describe in detail why the integration is being created between two business applications or between an external service provided interface and a business application and what business value it adds.
    Table 2. Functional section fields
    Field Description
    Data flow direction Direction of the data flow in the integration.
    Use the following options:
    • Outgoing: Provider to Subscriber: Data flow from the Provider business application to the Subscriber business application.
    • Incoming: Subscriber to Provider: Data flow from the Subscriber business application to the Provider business application.
    • Bidirectional: Flow of data in both directions: Data flows in both the directions between the Provider and Subscriber business applications.
    Initiating application Name of the application, which initiates the data flow. It can be a Provider or a Subscriber business application.
    Trigger How to trigger the integration.
    Use the following options:
    • Manual
    • Scheduled
    • Process Driven
    • Event
    Interval Frequency to trigger the integration.
    Options for the interval are as follows:
    • Seconds
    • Minutes
    • Hours
    • Days
    • Weeks
    • Months
    • Quarters
    • Years
    • On Demand
    • Real Time.
    Response Type of the response received by the subscriber.
    Use the following options:
    • Synchronous
    • Asynchronous
    Interaction type Type of the interaction between the provider business application and the subscriber business application.
    Use the following options:
    • Guaranteed Message
    • Pub-Sub
    • Pull
    • Push
    Middleware Name of the middleware used in the integration.
    Table 3. Business Impact section fields
    Field Description
    Criticality Level of the business impact criticality. Use the following options:
    • Low
    • Medium
    • High
    • Critical
    Confidentiality Confidentiality level of the integration. Use the following options:
    • Low
    • Medium
    • High
    • Critical
    Integrity Integrity level of the integration. Use the following options:
    • Low
    • Medium
    • High
    • Critical
    Availability Availability of the integration. Use the following options:
    • Low
    • Medium
    • High
    • Critical
    Table 4. Owners section fields
    Field Description
    Business owner The owner of the business function who owns the digital integration. It can be the same person who owns the parent subscriber business application.
    IT owner The owner within the IT organization who owns the digital integration. It can be the same person who owns the parent subscriber business application.
    Supported by Name of the Subject Matter Expert (SME) or individual who provides support to the digital interface.
    Support group Name of the group that provides support to the digital interface.
    Table 5. Activities section fields
    Field Description
    Work notes Comments about the integration.