All ideas

Many A2A integration scenarios require us to communicate directly with a SQL server. We currently need this for the internal master data project but will need it for migrating some of the large customers as well. The following scenarios should be ...

HTTP components in LINK are able to do PUT, POST and PATCH. In some cases we at least need to support GET but DELETE would also be nice to have. HEAD, OPTIONS, TRACE and CONNECT, I don't see much use for but unless the underlying implementation is...

Settings => settings => Create new Setting. If i want to create an new setting under an existing Category. i need to type the name of the existing Category. it would be nice to have an drop down with the category's there already exists.

Trying to overwrite UNB6_1 and UNB6_2 segments has no effect unless they already have a value set on the partner.

Monitor on Inbound SFTP transport location throws exception:

Many logs and statuses in Link reference interchange ids but it is not possible to search for interchange ids in the UI.

Sometimes, partners need varying values in their UNB segments. It should be possible to overwrite the UNB fields for EDIFACT documents. This should be applied on distribution level. Another option could be that a partner has the possibility to hav...

IP address and user id tracked as fields on interchange in, so they are filtereable fields on tracking search. Maybe in time also seachable fields. Of course only if relevant for the specific transport method.

Since we are moving away from the .dk domain, it would be perfect and not look like spam/phishing if our all of our mail communication came from the .com domain - especially external communication.