Footprint Workflows

Author or modify a Datex Studio footprint-workflow (configurationTypeId: 23) on a branch — a low-code TypeScript implementation that the Footprint platform invokes at a named extension point in its own processing (before an entity status commits, while cartonizing, while planning allocation, while recommending a location, …). It is the modern replacement for the legacy XAML "Datex Workflow" activities. The platform owns the slot, the GUID, and the input/output contract; you own the body.

References

• ../datex-studio-shared/branch-setup.md — Branch/connection selection (shared across skills)
• references/footprint-workflows.md — Authoritative reference: body shape, the slot binding + workflowsMetadata discovery, the fixed param contract, per-slot field breakdowns, the extension-point catalog, code patterns, CLI lifecycle, pre-flight checklist
• ../datex-studio-shared/configuration-roundtrip.md — The get -O envelope → jq .json → upsert -D round-trip and the silent-wipe bug it avoids
• ../datex-studio-conventions/file-format.md — configurationTypeId table, code-string editing rules, the return;-with-outParams rule
• ../datex-studio-conventions/naming-conventions.md — _workflow suffix preference; backend types are not bound by the display-name rule
• ../datex-studio-conventions/universal-checklist.md — cross-cutting checks every component must pass
• ../datex-studio-runtime/calling-conventions.md — execution-tier rules; workflow runs action-tier (calls actions via $flows, reads fpds, no $db, no functions)
• ../datex-studio-shared/flow-code-patterns.md — $utils.isDefined, date defaulting, and other flow-code idioms
• ../action-creator/references/actions.md — actions are the dispatch target the workflow body calls; same Footprint-server tier
• ../datasource-creator/references/datasources.md — fpds_* footprint-datasources the workflow reads (action-tier)

Dependencies