All ideas

The field "Command after put" should support at least the RENAME command.

The name of the conflicting partner should be shown as part of the error msg. When creating a new partner or adding an identification value on an existing partner, you should get a proper error message in case of conflict. "The identifcation value...

Customers have no insight in performance problems etc. - would be nice for them to view status on pods.

In many other products, it's possible to create a new tag immediately when you choose between available tags (e.g. on a partner). So the list of tags should also contain an empty field, from where you create a new one.

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.

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...

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....