Skip to content
Build 6ff80cd

Camel Flows

This is the migration map from the Mule-to-Camel documentation vault into PopDocs. It tracks business-flow documents that describe code which exists in the Camel repositories today; proposed designs and Mule-only flows are kept separate so they are not mistaken for current behavior.

Point-in-time review — 20 July 2026

Coverage was checked against the migration vault, the current local Camel source, and the existing PopDocs pages. A code path is not automatically a live production path: where deployment state is uncertain or a scheduler is disabled, the table says so.

Current Camel flows

Flow Migration-vault source PopDocs coverage State
B2C order lifecycle and Cirro fulfillment flow-docs/flow-01-b2c-cirro-fulfillment.md; flow-docs/b2c-cirro-fulfillment-current.md; flow-docs/b2c-cirro-fulfillment.md B2C Order Lifecycle Verified against production code and runtime on 20 July 2026
Gladly customer lookup (CRM order context) flow-docs/exp-docs/endpoint-migration-strategy.md (single endpoint row; page written fresh from code) Gladly Customer Lookup Verified against master code, served config, and production logs on 22 July 2026 — production lookups currently failing auth (see page warning)
Custom-product batching flow-docs/flow-02-custom-product-batching.md PrintStation & BatchStation Migrated
Platform → OMS → NAV → BatchStation flow-docs/flow-03-platform-oms-nav-batching.md Split across B2C Order Lifecycle, NAV Order Release, and PrintStation & BatchStation Migrated
B2B EDI fulfillment flow-docs/flow-04-b2b-edi-fulfillment.md; edi/edi-flow-process.md EDI Pipeline and the Cirro B2B vendor pages Migrated
NAV order release flow-docs/nav-order-release-migration.md NAV Order Release Migrated
Arena item lookup arena/arena-item-lookup.md Get Arena Item Migrated
Arena outbound events → OMS, BatchStation, and Jackyun flow-docs/flow-05a-arena-event-polling-future-state.md; arena/arena-product-sync-camel.md Arena Product Event Sync Migrated
Cirro inventory export for Snowflake architecture/cirro-inventory-servicebus-flow.md Not yet published Verify deployment and completion state first
Jackyun orders → BatchStation jackyun/jackyun-to-printstation.md Mentioned in Camel Topology Built, but the production poll is disabled; publish with that scope made explicit
Image analysis inventory/camel-existing-flows.md; planning/business-flows.md Not yet published Current code exists, but there is no detailed source page to migrate

The B2C page is the first flow re-reconciled service by service against the production branches. The old site remains useful for intent and payload history, but its topic fan-out, callback, cancellation, credential, and retry descriptions are not treated as evidence of current behavior.

Do not publish these as current behavior

Source Why it is excluded from the current-state queue
flow-docs/assembly-order-processing.md Documents Mule as current and Camel as a proposed future state.
edi/b2b-assembly-order-flow.md Contains Camel implementation requirements and an unresolved NAV status-update gap.
item-master/xb-item-master-camel.md Explicitly a target-state design with unresolved decisions.
flow-docs/b2c-cirro-fulfillment-future.md Future architecture, not deployed behavior.
architecture/cirro-inventory-servicebus-flow.md Code exists, but the migration index still labels the work in progress; verify runtime state before presenting it as complete.

Migration rule

Each page is rewritten as a concise current-state reference, not copied wholesale. Before publishing a flow:

  1. Trace its entry point, queues/topics, service calls, and error handling in the current Camel source.
  2. Separate deployed behavior from code that is disabled, incomplete, or only proposed.
  3. Remove credentials, connection strings, real customer/order payloads, and unnecessary internal addresses.
  4. Use D2 for topology and Mermaid for request/processing sequences.
  5. Run mkdocs build --strict before committing.