Skip to Main Content
ADD A NEW IDEA

Feature request

Showing 53 of 63

Additional HTTP methods

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...
Claus B. Eide 5 months ago in Feature request 0 Planning to implement

Allow Itinerary changes when marked as optional and not enabled by default

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...
Matias Noe 5 months ago in Feature request 0

Settings settings add drop down with the category

Settings => settings => Create new Setting. If i want to create an new setting under an existing Category. i need to type the name of the existing Category. it would be nice to have an drop down with the category's there already exists.
Guest 6 months ago in Feature request 0 Planning to implement

Option to name Payload's

Would save a lot of time if you could name payloads in Save flow state. There are often several steps you want to be able to see, especially during testing, and right now you have to guess a little ahead/or count up to the one you want to see
Niels Grarup 6 months ago in Feature request 0 Likely to implement

Log & Configuration Panel for AS/2 Connection

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 ...
Matias Noe 6 months ago in Feature request 0 Likely to implement

Link3 Rest Api Outbox filters

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 ...
Nicki Hølund 6 months ago in Feature request 0 Likely to implement

Reuse alert setup on multiple distributions

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.
Claus B. Eide 7 months ago in Feature request 1 Unlikely to implement

Option to not display "General" part of an itinerary step configuration on the distribution

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...
Claus B. Eide 7 months ago in Feature request 1 Likely to implement

REST API: Create tracking field value

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....
Claus B. Eide 8 months ago in Feature request 0 Likely to implement

Overview of addresses/endpoints/links

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...
Claus B. Eide 8 months ago in Feature request 0 Likely to implement