Digital Integration Management v1.3.0 got released - August '24 Store release

[Bruno De Graeve]

The August Store release from Digital Integration Management introduces these five key functionalities:

1. You can now define a Provider company instead of a Provider business application for a digital interface, such as Amazon providing an AWS digital interface that you utilize in your integration with ServiceNow ITOM.
2. On the Digital Integration form, it's now possible to set a Subscriber company instead of a Subscriber Business Application, useful when defining integrations with system integrators or vendors for ticket data exchange.
3. Determine which Information Objects are utilized by a digital interface and how it enables interaction with them, including defining CRUD operations, akin to what is done at the Business Application level.
4. SDLC Components can be linked with a digital interface, enhancing the connection between the design and operational aspects of an interface and APIs, building upon the advancements introduced in the May release.
5. Document Credentials (integration/technical accounts) assigned to a digital interface and digital integration.

Now available on Store.

[AttilaTheHun]

@Bruno De Graeve , are you planning to release a functionality to be able to relate integrations to Application Services as well (as opposed to the higher, logical layer of Business Applications)?

[Bruno De Graeve]

hi @AttilaTheHun , apologies for the late reply.
The Application Services, following CSDM, should be related to their parent Business Applications.

The DIgital Integration object is a design object explaining the WHY two Business Apps need to exchange data/information with each other. From an operational point of view, the Application Service will take care of the data exchange.
Is the question, that you're looking for an instantiation of the Digital Integration, represented by a (Application) Service, or you would like to link the Application Services directly to the Digital Integration.
Last related question: what would you like to achieve with it ? is it for visualisation purposes or to report an incident, change on it ?
We have some ideas in our backlog and are happy to understand from you, if any match with your needs.

Thanks, bruno

[AttilaTheHun]

Thank you very much for the response, @Bruno De Graeve,

Imagine that you are Amazon and have a single warehouse management application "Source" with multiple instantiations (application services) such as one for San Francisco, US, one for Frankfurt, Germany, etc. Then, you are doing warehousing operations for local stores "TheOne" in the west coast, "DieEine" in Germany - different companies, and they want to know their stocks and interact with them to ship to their own physical stores or clients at home. 

In this example, "DieEine" would be a subscriber company they are interested in "their" connection with "Source Frankfurt" being up and running giving them live data and would not care about if your SF warehouse can update it`s service clients on the other side of the pond. Being in separate continents, separate data centers, etc. it is separate interfaces that interact with the subscribers (although the business application is the same)

We want to report incidents on the integration, because it matters which client location in which geography is impacted, Hence the requirement to relate an integration to an application instance.

So, in a way the answer appears to be not either or rather both. I might have multiple clients interacting through their own EDIs with my warehouse application instance and the same client might want to query multiple of my warehouses. 

Did I manage to clarify sufficiently, please?