All ideas

Pagero Itinerary Step Async step that calls the pagero API. This call returns a FIleId that needs to be stored as a correlation ID on the async framework. This functionality must be implemented as the framework currently does not support this. Pre...

The possibility to send out an email to a new user directly (obviously this would only be if you dont use Entra for SSO). When a user is created, you would get the option to send the information directly from the user-creation interface in Link. T...

Sometimes you want to run a scheduled task in link immediately and outside the planned schedule. As it is now I must change the schedule to ie. 1 minute, wait for it to run, and then change the schedule back. It would be handy with functionality t...

We get a System.OutOfMemoryException when sending 15 MB (in xml) through the Json Assembler in Link. We often have 40 MB documents and maybe larger, which we need to send.Can the Json Assembler be re-written, so that it does not consume so much me...

The XsltService Component seems to create, multiple bunches of the same, error codes , almost every time, a document is processed in an xslt-itiniary step in Link. That drowns the change log / makes the log difficult to use. Go to Link->setti...

Hi, In many cases we see that the full name of the XSD or XSLT that is placed into the itenrary step is longer than the display length of the text field. It is a bit difficult to copy the full name if we want to search for it in the XML artificate...

Our customer is sometimes seeing an error from Link in relation to receiving AS2 documents. Details moved to internal comment.

Denne opgave er startet direkte i Devops som en bug, men den kræver en refinement - måske i form af en pre-refinement (https://bizbrains-productteam.visualstudio.com/Link%20Whopper/_workitems/edit/1059) When you add a new Configuration key that ap...

When passwords/API keys or other information is used in multiple places it is useful to have them as a Link setting and be able to access them through macros

To support AES256-CTR we need to upgrade SSH.NET to version 2023.0.1 or newer. https://bizbrains.atlassian.net/browse/TICKET-83365