All ideas

I was expecting more things to come pre-configured out of the box and a bit more of intro information to be provided: Format types for XML, EDIFACT and Passthrough could come out of the boxIn particular Passthrough was "difficult" to set-up becaus...

Instead of having to navigate to support.bizbrains.com, it would be great if documentation pages were directly available on the UI of Link in case you want to understand how to use them. Naturally this might not be of use for all users, but maybe ...

When initiating a new tracking search, any search filter applied to an old search is not reset, leading to users not finding the data they expect.

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.

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

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

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

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