Would inline code in Logic App workflows not be a more cost/performance-effective than our Regex Translation component?

[stijnmoreels]

I was wondering if there would be scenarios if where running some inline code in your Logic App workflow would be a better alternative than using a constantly running an Azure Function and linked Azure Table for simple regular expression translations.

https://learn.microsoft.com/en-us/azure/logic-apps/add-run-javascript?tabs=consumption

[pim-simons]

A valid question since this component was from before the javascript was available in Logic App Consumption.
We use the regextranslator mainly from the exception handler component to do translations, see https://github.com/invictus-integration/docs-ifa/blob/master/framework/components/exceptionHandler.md#translations.

For simple regex translations I would indeed use the inline code.

[stijnmoreels]

@GoutsmitSam , is it an idea to 'merge' the Regex Translator functionality into the Exception Handler component?

[pim-simons]

Not entirely sure we can merge the Regex Translator into the Exception Handler, as I seem to recall the regex translator was needed/used in other areas as well (it has been a while but I think it was also used from APIM policies)

[stijnmoreels]

Okay, another question to ask the masses. 😄

[stijnmoreels]

Oh, and by 'merge' I mostly mean that the exception handler app directly runs the regex translation, instead of calling a different running app.