All ideas

On LINK3 'Distributions' it shall be possible to test upload mutiltiple files and not just one as now. See MBM coding on LINK2 where a limit about 100 files, or the total filesize gives the limit. This required 'feature' has to be implemented on L...

The UI enum has been extent like the backend enum to have both the original depricated type and the new "type2". When using the UI service to get artifacts of a specific type, both the old and the new type need to be supplied in order to ensure al...

When editing a batching configuration, adding or editing a trigger so that there is no weekdays selected and then pressing Save causes a fail, that can only be recovered by pressing F5.

This is two ideas that are somewhat connected. The first one is easy to implement: When I import a Distribution from Test into Prod, the import fails when the location names are different. This makes sense, however there should be an option to ove...

Deleting any of these objects throws a database reference exception in the UI. It would be nice to be able to soft delete these objects because as it is now, it is very hard to get rid of these when they have been used for processing documents.

Many A2A integration scenarios require us to communicate directly with a SQL server. We currently need this for the internal master data project but will need it for migrating some of the large customers as well. The following scenarios should be ...

It would be great if Link had a page that could be shared with our partners. It could be generated from the Partner's page in Link, something like "Invite to Connect" or "Send Connection Details" or "Create & Send onboard invite". First the us...

HTTP components in LINK are able to do PUT, POST and PATCH. In some cases we at least need to support GET but DELETE would also be nice to have. HEAD, OPTIONS, TRACE and CONNECT, I don't see much use for but unless the underlying implementation is...

When I need to make a change to an itinerary if a document config is in use by a distribution, then it will display a warning and prevent me from making changes. Right now I have a few document configs that are our standard formats and will be use...

We would like to be able to send a report as email when you run it, the same way as you can send it when it is scheduled.