All ideas

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

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

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

When receiving messages from an inbound transport location, Link does not set the content-type based on the init config.

I would like a quick way of finding endpoints addresses/endpoints/links to a Link environment. This should include: Integrated FTP address AS2 endpoint AS4 endpoint API base URL Swagger API documentation Måske vise opsatte http-handlers? Maybe lin...

In some cases, the same tracking field makes sense regardles of document type. This could be an IDOC number or an azure run id. Having these tracking fields as one field instead of creating one for each document type, makes the UI alot smoother an...

Add support for processing responses from synchronous transport types. Sometimes a synchronous response contains information needed to complete or fail a document. It would be nice to easily add a component, that could process these responses.

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

I think we should integrate our compare tool into tracking search. Being able to select two files, press compare, and choose a step to compare. I have seen a lot of scenarios where a file fails and we want to compare it to a file that does not fai...