...
The document has been received, is placed in the Link Inbox queue from which it will be picked up and processed.
Initialize[TODO: DESCRIBE THIS]
The document has been received and Link is now working on sorting out the basic context information e.g. sender, receiver, document type etc. This is necessary to determine the future path through Link.
Processing
Document has been picked up by Link and is being processed. It has not yet been delivered.
...
The document has encountered some kind of error during the flow. Link will have given the document an error code and the assigned stakeholder is notified. You can read more about error codes and stakeholder in the [TODO: INSERT LINK TO “Error handling”] Error Handling section.
Ignored
This status is put on a document if a user has selected it and pressed the button “Manually handle”. Link will do nothing further with the document.
Ready for test
Document will have this state if it has a test flag. TODO: DESCRIBE
Outbox
TODO: DESCRIBE
Testbox
TODO: SHOULD THIS BE HERE?This status is indicating that the received document was marked with a test flag. In this case Link will not process the document as normally. The idea is to be able to receive test documents in a production system and then work with them manually to ensure everything works as expected.
Some document formats (e.g. EDIFACT) supports this possibility while others don’t.
Outbox
The “Outbox” status shows that the document has been successfully processed, placed in the “Outbox”-queue and is now ready to be sent to the receiver via an asynchronous transport type.
This could be one of the native transport types (e.g. SFTP), but it is also a common scenario that companies choose to let systems pick messages from the outbox-queue via the REST API.
Completed
The document has been successfully delivered to the intended receiver. Link will do nothing further with the document.
...