Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

When a document is processed in Link, it is important to understand that it can be in different states, and it is also important to have a good understanding of what the individual states mean.

Typically, the document status is used in tracking scenarios (e.g. you could perform a document search for all documents with status “Failed”).

This section goes through each of the built-in statuses in Link. Note that it is also possible to introduce custom statuses - this is an advanced topic that is further described in the “Developer” section of this documentation.

This list is organized in logical order in relation to a document’s journey through the Link engine.

Inbox

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]

Processing

Document has been picked up by Link, but has not yet been delivered.

Batching

Sometimes multiple documents need to be merged into one big file. This status indicates that the document is currently being created as a batch.

Awaiting Control

The document has been delivered, but Link is waiting for a control message from the receiving system or an acknowledgement that the message has been received.

Failed

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”] section.

Ignored

The document has been manually handled.

Ready for test

Document will have this state if it has a test flag.

Outbox

The document has been delivered to an internal server at Bizbrains.

Completed

The document has been successfully delivered to the intended receiver.

Stakeholder

This dropdown contains all the stakeholders in your Link solution. If you know the stakeholder responsible for handling the error, you can input it here.

  • No labels