New Feature

TransmissionId for incoming messages

A new type of Duplicate Check

Transmission Id is a new ID which is unique for an interchange (Interchange In and Interchange Out).
It means that for a document going through Link, there will be a Transmission Id for the Ingoing Interchange and a Transmission Id for the Outgoing Interchange.

Transmission Id comes out of a need from AS4.
In the AS4 SOAP Header, there is a Message ID, that is used for duplicate detection for incoming documents. The AS4 Message ID is mapped to Transmission ID for Interchange In.
The Duplicate Detection is implemented in Link. That means that Link will reject an incoming document with a Transmission ID same as a previous incoming document with the same Transmission ID.

Transmission ID versus Interchange ID

Transmission ID and Interchange ID is similar to each other, because they both are related to Interchange. Interchange ID is an Id that is created by Link for each Interchange, one for the Interchange In and one for the Interchange Out. When a document is Resend in Link, it gets new Interchanges Id's, and that is the difference to Transmission ID. When a document is Resend in Link, Transmission ID stays the same.

Resending

By pressing the 'Resend' button, you will get different opportunity when resending the message.
About Disasssembling
The step from Interchange In to Message In is called disassembling.
The Interchange Infile is the file that arrived to Link.
If the Interchange In file is a batch file, it will be de-batched in the disassemble step.

Plain resend

If you don't mark any of the options, the Message In will be resend. (Look at the first screen dump to see where Message In is in the flow)

Resend by interchange

If you mark Resend by interchange, and resending the document(s) the flow will start at from the beginning with the disassembling step. If the incoming file is a batch of documents, the batch will be disassembled and all the document will go through Link again. 

Resend bypass doublet check

If you mark Resend bypass doublet check, the duplicate check will not be executed on this message. That means that although there is a duplicate message to the resend message, you will not get a duplicate error.

Resend bypass test marking

If you mark Resend bypass test marking the document will be processed even though it is test marked. E.g. has Edifact a test mark property.

Resend by document log

The name should have been Resend with document log.
If you mark Resend by document log, an extended logging will be done. This log is called Document Log. This feature is mainly for the developer, who is debugging.

Resend generate new transmission Id

If you mark Resend generate new transmission Id, a new Transmission Id will be generated on the outgoing interchange, which might prevent the receiver from detecting duplicates.

Resend related new permissions

• Tracking_Action_ResendUseDocumentLog

• Tracking_Action_ResendByPassTestMarking

• Tracking_Action_ResendByPassDoubletCheck

• Tracking_Action_ResendGenerateNewTransmissionId

• Tracking_Action_ResendByInterchange

To see the permissions, go to Settings->Roles, click Edit on a random role and click in the Permissions field:

Link monitor item to a pre-defined time schedule

Being able to differentiate between the severity of errors. (Scenario: Should a given error be handled during work hours or should it be handled immediately).

The problem

Today, the possibility is to either use threshold values or service windows status.
Threshold is not a valid solution, since it is applied all the time.
Service window is not a valid solution because
(A) if the last status from the item is failed, it will stay failed.
(B) Sometimes you might want the monitor item to be executed to notify the stakeholder or execute the action on errors.
Solution would be to on Item Level be able to register whether this is something to react on in normal working hours or 24/7. (Static SLA is good for now, but considerations of possibility to create different SLA like, 24/7, 24/5 etc. should be considered).

Solution Comment:

Reuse Scheduling functionality from Alerts to make it possible to create schedules for SLAs.
Make it possible to choose a SLA schedule for a monitor Item (and not for the group).
When a monitor item is linked to a Schedule (e.g. Normal Working Hours) it should be possible to choose if the Stakeholder notification on the group should still be triggered
The Monitor Xml should include info about if the item is within a time schedule or not (Boolean)
SMS Service should be extended to only send SMS if with a time schedule.

Option of enabling auto refresh on "Chart" page

If you want to use the Link graph page for TV screen, it is nice to have the option of auto refresh.

JSON - New format types

Ingoing JSON file