...
In Link, there is a very big conceptual difference between receiving and sending documents . We will handle document receival and sending in separate which will be covered in their respective chapters.
Note that it It is easy simple (for developers) to create new transport types, so don’t panic if you have a special scenario that is not covered by this chapter. To learn about creating custom transport types, you can check read the OLD Link Technical Guidetechnical guide.
...
Receiving documents
Link offers In Link, you can receive documents in several ways of receiving documents. As you can see seen in the diagramfigure above, there are different types of receive sites and also as well as the possibility to set up so-what are called Polling “Polling” locations in Link. We will explain the different types These will be explained in detail in the chapters sections below.
Resolving document type, sender and receiver
A key topic It is important to understand is, that in order to process a document correctly, Link needs to know the document type, who sent the document and who should receive it - i.e. who the sending partner is and who the receiving partner is. With these key pieces of information.
In many cases, Link will be able to learn all “learn” these three things simply just by analyzing the document content . E.g. because Link has built-in functionality for understanding the global standards like EDIFACT, X12 and PEPPOL, but it . This is also easily achievable done using custom formats like CSV or a home-made XML format. In any case, your developers just need to have set up the relevant document types and format/variant/versions beforehand.
It is You can also possible to configure one or several of this these pieces of information directly on a Polling location by setting up an Init configuration.
There are many roads leading to Rome, but regardless No matter how the document type, sender and receiver are resolved, Link will be able to route the document through the appropriate distribution (assuming a matching distribution has been set up).
Receive sites
The most commonly used receive site is the REST (API). This offers several methods including a way to send documents into Link. Link also offers a more old-school SOAP API.
It will depend Depending on individual customer setups is , AS2 and/or AS4 receive sites are available - if you believe you should have this option available, you need to talk to will be available. If you want this option to be available to you, contact your administrator to get request the relevant URL, certificates, etc.
Inbound polling locations
Inbound polling locations are often associated directly with a specific partner , and you can set up as many as you want. The possibilities are described This is explained in detail in the Incoming transport location details chapter.
You can also set up global locations - e.g. relevant when , which is relevant if you receive lots of many mixed documents from a VANS-partner.
Integrated FTP
With Link also offers the possibility of integrating , you can also integrate your preferred internal FTP software (Cerberus is supported). This makes is it possible to add new partner-specific in- and out- folders with only just a few clicks in the your partner configuration.
Sending documents
...
One of the many configuration possibilities for a specific partner is that you can set up one or several outbound locations. A common example would be a designated FTP-folder for delivering invoices, but Link supports many other protocols. You can read about them all in detail here: Outgoing locations.
It’s important to understand that the target outbound location for a specific document flow is configured as a part of the distribution setup.
Asynchronous transport locations
Outbox
Sometimes, companies need Link just to place outgoing documents in a queue from where they can be picked up (e.g. via the Link API) later. The “Outbox” is a queue, and can be chosen as the target location instead of a “real” one.
Testbox
A lot of the work done when establishing new integrations is in testing. Setting the outbound location to “Testbox” on a distribution setup will prevent Link from actually sending a document (which you often do not want to do in test scenarios).