Skip to content
LambogeniusDocs

BizTalk Orchestration Viewer

Shape types and migration notes

How the viewer recognises each shape type, and the Logic Apps note it shows for it.

VS Code extensionlambogenius.biztalk-orchestration-viewerFree · MIT license

How shapes are recognised

For each XML element, the viewer looks for keywords in the element name, its Type, ShapeType, ClassName and Name attributes, and the Type, ClassName and Name properties of an om:Element. The first type in the table below whose keywords match wins.

TypeKeywordsMigration note
ReceivereceiveLogic Apps trigger or Request action. Confirm activation, correlation, and port binding behavior.
Sendsend, sendshape, sendport, transmitLogic Apps connector/action. Preserve operation, retry policy, response handling, and promoted context values.
Constructconstruct, messageassignmentCompose, Variables, or inline code. Watch for message immutability and distinguished/promoted properties.
Transformtransform, map, mapping, btmMap action, Liquid, XSLT, or custom function depending on map complexity and functoids.
Decidedecide, decision, branch, rule, condition, ifCondition or Switch. Review rule expressions and branch ordering.
Looploop, while, foreach, repeatFor each or Until. Check concurrency, ordering, and timeout semantics.
Scopescope, transaction, compensationScope action. Map exception, compensation, and transaction behavior explicitly.
Expressionexpression, assignment, codeExpression, variable assignment, or Azure Function when XLANG/s code is non-trivial.
Callcallorchestration, startorchestration, callChild workflow invocation. Confirm synchronous/asynchronous behavior.
Listenlisten, parallel, pickParallel branches with trigger-like waits. Confirm first-wins behavior.
Delaydelay, timeout, waitDelay action. Confirm timeout and dehydration assumptions.
Terminateterminate, suspend, throwTerminate action. Preserve fault details and status codes.
Exceptionexception, faulthandler, catchRun-after failure path or Scope error handling. Preserve compensation logic.
Artifactschema, element, record, binding, service, porttype, operationReferenced artifact. Link this to schemas, maps, ports, and deployment bindings.
Unknown(no keyword; shown when the element has a name and shape-like attributes)Unrecognized BizTalk/XML node. Inspect attributes and map manually.
Check the source tag

Because the match uses keywords, a shape's name can decide its type: an Expression shape named Send reminder shows as Send. In an .odx, every designer element is an om:Element, so declarations that match no other type (ports, messages, variables) usually show as Artifact. The shape list and inspector show the source tag next to the type.