Feature request

Currently, the Http Retriever in Link3 provides Link with almost no information about the messages it fetches. The only value it adds to the context is a filename, and it creates no additional files. I think it would be useful to at least have the...

The origin of this feature request is this support case: https://bizbrains.atlassian.net/browse/PTI-383?atlOrigin=eyJpIjoiYTZmZWZkZDE2NDQ3NDBlNzhiM2IzNTMwMjRhM2FmMGEiLCJwIjoiaiJ9 The Edifact disassembler very deliberately accepts fields that conta...

It would be great with XSLT 3.0 support in Link3. BizTalk 2020 already supports XSLT 3.0 through SAXON HE (Home edition), and I know that Bestseller is looking into using this in their Link2 setup. Here are some links that may be interesting to ...

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

Will there be a separate menu for Conversion tables, so you don't have to enter overview from a specific partner?

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

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