Step 1
Get started
What the action does, what you need, licensing, and a first workflow that runs a deployed map.
IntroductionWhat Compose using XSLT does, and how it differs from the stock Logic Apps XSLT actions.RequirementsThe Logic Apps project type, runtime and tools the action needs.LicensingDeveloper, trial and production licenses, the LAMBOGENIUS_LICENSE setting, and where no license is needed.Quick startInstall the package, add the connection and a map, and run a workflow locally.
Step 2
Use the action
Inputs and outputs, maps and modules, parameters and workflow variables, C# scripts, and Azure Function calls.
Inputs and outputsEvery input of the ComposeXslt action and what it returns.Maps and modulesDeployed and inline maps, include and import, output methods, and what XSLT 1.0 features are available.Parameters and variablesPass xsl:param values from the trigger, workflow variables or expressions, and pick maps dynamically.C# scriptsmsxsl:script C# helpers: what is supported, how they are compiled, and how errors point at the map.Azure Functions from mapsCall HTTP-triggered Functions from XPath with az:InvokeText, the registry, authentication and caching.
Step 3
Samples
Four runnable Logic Apps with checked demos.
Step 4
Operate
Settings and limits, error codes, deploying to Azure, and fixing common problems.
Configuration and limitsApp settings for the map folder, scripts, workers and Functions, and the size and time limits.Error codesEvery error code, its HTTP status, and how to read the phase and location.Deploy to AzureThe Logic App settings Azure needs, a Bicep template, and checks after deployment.TroubleshootingCommon problems and how to fix them.