FileRelayDocumentation
Try for Free

Connections Overview

Understand connections (pipelines) in FileRelay that wire sources to destinations for document delivery.

Connections Overview

Connections are the pipelines that link sources to destinations in FileRelay. They define where documents go after being received from SAP and how they are routed, named, and organized at the destination.

What is a Connection?

A connection wires a source (SAP content repository) to one or more destinations (cloud storage, services, or notification targets). When a document arrives at a source, FileRelay evaluates all active connections for that source and delivers the document to each configured destination.

Think of connections as the plumbing of your document flow:

Source (SAP repo Z1)  --->  Connection  --->  Destination (S3 bucket)
                      --->  Connection  --->  Destination (SharePoint)
                      --->  Connection  --->  Destination (Email)

Connection Components

Each connection consists of:

Component Description
Source The SAP repository that provides documents
Destination The target where documents are delivered
Routing Rules for subfolder paths and file naming at the destination
Status Active or inactive toggle

Creating a Connection

To create a new connection:

  1. Navigate to the Connections page from the sidebar
  2. Click Add Connection
  3. Select a source from the dropdown (your configured SAP repositories)
  4. Select a destination from the dropdown (your configured connectors)
  5. Configure routing options (subfolder structure and file naming)
  6. Save the connection

REPLACE: Screenshot of the "Add Connection" dialog showing source and destination selection with routing options

The Visual Pipeline UI

The connections page displays your configured pipelines in a visual layout that shows the flow from sources through to destinations. Each connection is represented as a line connecting a source to a destination, with status indicators showing whether the connection is active.

REPLACE: Screenshot of the connections page showing the visual pipeline view with sources on the left and destinations on the right

This view makes it easy to understand your entire document flow at a glance and identify any sources that are not connected or destinations that are not receiving documents.

Active and Inactive Connections

Each connection can be toggled between Active and Inactive states:

State Behavior
Active Documents arriving at the source are delivered to the destination
Inactive The connection is skipped; documents are not delivered to this destination

Toggling a connection to inactive does not delete it. The configuration is preserved and can be reactivated at any time. This is useful for:

  • Temporarily pausing delivery to a destination during maintenance
  • Testing a new connection before enabling it in production
  • Disabling a connection without losing routing configuration

Connection Behavior

Multiple Connections per Source

A source can have multiple connections, each pointing to a different destination. When a document arrives, it is delivered to all active connections simultaneously. This is called fan-out.

Multiple Connections per Destination

A destination can receive documents from multiple sources through separate connections. Each connection can have its own routing rules, so documents from different sources can be organized into different folders at the same destination.

Delivery Tracking

FileRelay tracks delivery status for each document at each destination independently. If a document is wired to three destinations through three connections, each has its own delivery status:

  • Pending: Document is queued for delivery
  • Delivered: Document was successfully delivered to the destination
  • Failed: Delivery failed after all retry attempts
  • Retrying: Delivery failed but retries are in progress

You can view delivery status on the Documents page by expanding a document to see per-destination status.

Editing a Connection

To modify an existing connection:

  1. Click on the connection in the connections list or visual pipeline
  2. Update routing rules, file naming, or other settings
  3. Save the changes

Changes take effect immediately for newly received documents. Documents already in the delivery queue are not affected by routing changes.

Deleting a Connection

To delete a connection, open it and click Delete. This removes the pipeline between the source and destination. Documents already delivered through this connection are not affected at the destination, but no new documents will be delivered through it.

Next Steps