All ideas

Would save a lot of time if you could name payloads in Save flow state. There are often several steps you want to be able to see, especially during testing, and right now you have to guess a little ahead/or count up to the one you want to see

We are currently having some issues allowing inbound connections via AS/2 and it is very difficult to analyze why this is happening. It would be great if there was a page with information and settings regarding the AS/2 connection. There could be ...

When using the REST Api to get outbox documents it would be very useful to be able to filter for certain conditions. For instance when getting some document type from the outbox it would be helpful to be able to specify format/variant/version. We ...

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

Some very basic and common errors do not have any solution and are classified as unexpected errors For the two errors illustrated in the screenshots, we need to have relevant and helpful texts in: Execption solution Technical description Exception...

Having to create the same alert setup for multiple distributions, can be a lot of work. It would be nice to be able to reuse the alert setup on multiple distributions.

When alowing an itineray step to be configured on a distribution, all configuration is shown on the distribution. Very rarely would you like to change any of the general properties (Retry count, retry interval etc.) It clutters the UI and makes th...

Monitor on Inbound SFTP transport location throws exception:

When you have some parts of the integration workflow outside link. That could be external mapping services, logic apps, validation APIs etc. it is often useful to be able to track workflow ids or other information and have them searchable in Link....

It would be nice with a report showing processing. E.g. a monthly scheduled report with the processing time for their transactions.