Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Tracking Search Details

Note Please note that through the Document search result screen, you might may have selected to view several documents together. In this case, the individual documents are visible as separate boxes in the top of the screen:, as shown in the figure below. 

You can switch between the documents simply by clicking on them. To remove a document, click in on the top-right corner of the corresponding box. 


Overview

The document detail page. There is quite There is a a lot of information here, and there are also on the document detail page as well as many different possible actions and functionalities available features. 

If a document has the a "Failed status", there will be even more information available - this is described for that document. Read more in the Failed documents section. If you would like to read more about our proposed way of troubleshooting how to troubleshoot failed documents, we recommend that you read the How to handle errors please read the Self-service support for the business article.

Some users might be confused by the vast amount of information presented here - lots of it is even rather pretty technical. But one of Link's key strengths are exactly is that it provides very detailed information in - all presented in one place, and we are in this article going to . Here we´ll go through all the sections, files, fields and logs shown on the screen from top to bottom.

Action buttons

Depending a Link user's permissions, there will be action buttons available from the document detail page. Several of these are identical to the ones present on the document search result page and you can read about their possibilities what you can do with them in the Document action buttons section.

Files

This section of the screen gives you the ability to download and view the document in all the different ways it looked during all stages each stage of the document flow. If you are not familiar with these concepts, we recommend that you please read the Document stages article.

You can download the state of the document for each stage by clicking "Save" - if you'd like to just quickly . If you just want to view it, you can click "View.  It is also possible to inspect You can also view the document in a more human readable reader friendly format by clicking "Print". The "Print" option however, is only available if this it has been correctly set up. Developers can read about how to set this up in the TODO: INSERT LINK section under "Developer"the "Print" option in the Link technical guide. The "Size" field shown to the right of each document refers to the size of the zipped document.


In this example, a sales order was received in EDIFACT format and sent in a custom XML format. We can compare them by clicking "View" on the "Interchange In" and "Interchange Out" rows:

TODO: INSERT SCREENSHOT ETC. WITH HUMAN READABLE EXAMPLE


Additional Files

This section is intended only for advanced users/developers. 

Each row in on the list gives shows additional logging information for each step which is useful for developers troubleshooting advanced integration scenarios.

Document

The Document section contains detailed information about the document. Depending on the document and its current status, some data may not be available. It also contains a shortcut to the distribution associated with the document. 

Document Type

The This option show the document type of the document is shown here, e.g. Purchase Invoice, Sales Order etc.

Created Date

Shows This options shows the time and date and time the document was created. 

Document Number

A This option shows the unique document number will be shown here. It varies . The number will vary, depending on the document type and exactly which field it refers to.

Last Status

Shows This option shows the last recorded status of the document. 

Init Configuration

This field is intended only for advanced users/developers and contains the document configuration when it entered Link.

Context properties for Interchange

This field is intended only for advanced users/developers and contains metadata for the interchange , before being disassembled. Will This information will only show if they have it has been saved by the system.

Context properties for Message

This field is intended only for advanced users/developers and contains metadata about the message , after being disassembled.  Will This information will only show if they have it has been saved by the system.

Document

IdA unique id given

ID

This option will display a unique ID assigned to the document by Link. 

Document

GuidA

GUID

This option shows the unique GUID given assigned to the document by Link.

Distribution

Id

ID

Displays This option displays the distribution id and contains a link to the distribution associated with the document.

Ingoing/Outgoing

The ingoing and outgoing sections contain information about the sender and receiver receiving partners.

Partner

Shows This section shows the partner name. Click it to be redirected to the page for assigned to that partner.

Interchange Number

If the incoming message format supports interchange number (e.g. EDIFACT and X12) it will be shown here. In other cases, it will be auto-generated on for the outgoing message.

Format/Variant/Version

Shows This section shows the format, variant and version of the document. 

Address

Displays This section displays the address from where the document was received/sent. The format will vary upon the used protocol used. 

Port Name

Displays This section displays the name of the transport location that was used when receiving/sending the document.

Interchange Id

AutoThis section displayed the auto-generated interchange id. Mainly ID and is mainly used for internal systems.

Transmission Id

Id This section displays the ID of the transmission . Only and is only supported by some transport types.

Interchange Log File

Transport This section displays the transport log file . Is and is only available on for some protocols - in . In the example above, an SFTP-log file is available for the sending of the document.

Message Number

If the incoming message format supports message number (e.g. EDIFACT and X12) it will be shown here. In other cases, it will be auto-generated on for the outgoing message.

Tracking Fields

If any tracking fields have been configured for the document type, these can be shown here. Press Click 'Load tracking fields' to display them on the page. See the 'Tracking Fields' page Read the Tracking fields page in the user guide for more information on tracking fields.

Status Flow

At the bottom of the tracking search detail page is the status flow. This contains information about the various steps that have occurred in the document flow, such as messages being sent and received. This information is especially useful , if there are several servers involved in the document flow. Each step holds contains data about the current status of the document at that time , as well as a short description of what occurred. The status flow is displayed as a data grid, which means it supports standard sorting, filtering and grouping functionality.  It's recommended to Please read the Using data Data grids section if you are unfamiliar with this.

By default the , this list is only showing shows simple logging. If you need to have more technical logging info to be displayed, you can tick check the 'Include technical status types' checkbox. 


Status events

Status events is an advanced topic that is not relevant in all Link setups. If you are not familiar with this concept you can read more in the Status events article. 

It there are any associated status events with the document, they can be loaded by clicking the "Load status events" symbol.

Image Added


This will give you a grid showing the associated status events as well as a few action buttons.

Image Added

Here we will refer to the Status event result section where both grid content and buttons are explained in detail.


Panel
borderStylesolid

Content on this page:

Table of Contents