All ideas

It may be because of security reasons but having a random username being generated is not very nice. It would be better if we could choose a username ourselves and Link just verifies if it is available or not. Could be enabled to choose username w...

Allow changing to a Data Group by clicking on the customer name on the top right bar. This way one can simulate and test if the data group has everything that is needed for those users

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

We would like to have report results shown as an HTML table in the e-mail instead of having to open an attached csv file.

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.

There is a wish that a user should be able to save the configuration on a given search grid, in tracking for instance. So that he doesn't have to do reordering and selection of columns every time. For instance he has a tracking field that he would...

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.