Objects on Dependencies

How to link additional objects directly to a dependency in Docusnap365 – e.g., integrations like REST APIs.

Introduction

In addition to the classic representation of dependencies between two objects (e.g., applications or services), Docusnap365 now offers the ability to link additional connection objects directly to the relationship itself.

This allows you to document how two systems communicate – for example via a REST API, middleware, a protocol, or relevant informational objects. This feature is particularly useful for modeling integration landscapes and technical interfaces.

Use Case

The following example shows a modern architecture in which not only two applications are directly connected, but also the technical integration layer and the underlying informational objects are documented.

![Screenshot: Connection Objects on Dependency]

In this case:

  • Salesforce and myDocusnap are applications with a mutual dependency.
  • The technical integration is handled via the connection object “myDs-REST”, which represents the REST API interface between the two systems.
  • In addition, the informational object “Customer Information” is linked to the API – describing which data is processed in this context.

These connection objects are not standalone systems but instead contextualize the connection using technical, business, or organizational metadata.

Maximum Flexibility: Any Object Can Be Linked to a Connection

A key feature of this enhancement is the complete flexibility in documenting dependencies:
In Docusnap365, any object can be placed on a connection (dependency) – whether it’s an application, process, data object, contract, integration, organizational unit, or documentation element.

As a result, the dependency itself becomes an information carrier that reflects more than just a structural link.

Examples

  • A REST API is documented as a technical connection object between two applications.
  • A contract or service level agreement (SLA) is linked to a critical connection between an internal system and a cloud service.
  • An informational object describes the data exchanged over a specific connection.
  • A risk assessment or responsible party is documented on the connection.

Key Benefits at a Glance

BenefitDescription
Any objects linkableFull freedom in modeling context
Maximum expressivenessCombines structure, relationships, and related metadata
End-to-end technical and business contextMerges business, technical, and organizational information
Scalable and future-proofSuitable for complex integrations, hybrid scenarios, and multi-tier architectures

Create Connection Objects

How to create connection objects on a dependency in Docusnap365 – explained step by step.

Displaying Connection Objects

How to display connection objects in Docusnap365 – visually and in table form.