Update digital integration form

Use the digital integration form to update the digital integration between two business applications.

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. As 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, it doesn’t refer to the data flow direction (incoming, outgoing, bidirectional). It’s managed by the Data Flow Direction attribute. This field is automatically generated and can’t be edited.
Subscriber Digital Interface	Name of the r 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. Therefore it’s affected by the changes or an outage face connection or data loss. Note: Being a provider or subscriber business application, it doesn’t refer to the data flow direction (incoming, outgoing, bidirectional). It’s managed by the Data Flow Direction attribute.
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. It helps Application Owners and Architects to look up which version of an Integration is in use or should 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

Data flow direction	Direction of the data flow in the integration. Use the following options: Outgoing - Data flow from the Provider business application to the Subscriber business application. Incoming - Data flow from the Subscriber business application to the Provider business application. Bidirectional - Data flow in both the directions between the Provider and Subscriber business applications.
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

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.

Related tasks

• Update a digital integration