Aggregation of flows by protocol - NEW! 🚀

Clicking on the arrow that connects the source and the destination, a new screen will open focusing on incoming and outgoing flows associated by protocol.

At the previous level, described in the Actor Lineage page, multiple flows or configurations are present, rather than just a single one. Dozens or even hundreds of configurations could be available. By clicking on the arrow, you advance to the next level, with a more complex view that displays all incoming and outgoing flows categorized by protocol. The system does not simply show two flows (one initiating with a specific protocol and leading to either the same protocol or a different one) but a comprehensive aggregation of all flows, categorized by protocol.
When you select an incoming protocol, the associated outgoing protocol(s) are highlighted, making it easier to understand their relationships. Note that multiple outgoing protocols can be linked to a single incoming protocol.

The figure below shows flows potentially entering Data One with HTTPS or SFTP protocols and exiting with HTTPS or PR4 protocols.

The type of arrow indicates whether Data One is set up as a client or as a server:

• an empty arrow symbol indicates that Data One is set up as a server, i.e.:
  • In input, the actor acts as a protocol client and sends files to Data One, which acts as a protocol server and receives them.
  • In output, the actor acts as a protocol client and receives files from Data One, which acts as a protocol server and makes the files available for retrieval by the recipient.
    DataOne receives files from a remote location through a connection contract and makes the files available to a remote location, again through a connection contract.
• a filled-up arrow symbol indicates that Data One is set up as a client, i.e.:
  • In input, Data One acts as a protocol client and receives files from the actor, which acts as a protocol server.
  • In output, Data One acts as a protocol client and sends files to an actor, which acts as a protocol server.
    DataOne takes the files from a remote location with an input contract and sends files to a remote location with an output contract.

In the figure above, in input, with the HTTPS protocol, Data One is set up as a server and receives files through a connection contract. Conversely, it is set up as a client with the SFTP protocol and collects the files with an input contract. In output, with the HTTPS protocol, Data One is set up as a server, and files are collected by the destination application through a connection contract. With the PR4 protocol, Data One is set up as a client and sends files to a remote location with an output contract.

Clicking on the HTTPS chip or arrow on the left will highlight (in orange) the destination arrow configured for the flow.

A detailed analysis of the configured flows is available in the following pages:

• Lineage with connection contracts
• Lineage with input, mediation and output contracts
• Lineage with any contract type

Only mediation contracts that use "sourceVirtualPath" as the variable name containing the starting virtual path are considered to identify the complete flow.

Any mediations with virtual path variables with a custom name (not a system name) will not be considered in the extraction of complete flows and consequently will not be represented as lineage.