Boomi Connector Framework & Dynamic Document Routing
Master Boomi document properties, dynamic routing, cross-reference tables, and Trading Partner B2B EDI orchestration.
Key Takeaways
- Boomi processes data as individual discrete "Documents" traveling through the process pipeline
- Dynamic Document Properties (DDP) attach metadata to individual documents; Dynamic Process Properties (DPP) are global to the entire execution
- Route Shape enables multi-condition routing based on document field values or property metadata
- Cross-Reference Tables (CRT) provide quick in-memory lookups for standardizing status codes across external systems
The Diagnostic Context
In Boomi, every transaction moving through a process is encapsulated as a "Document." Mastering how Boomi manages document lifecycle, properties, and connector operations is essential for building scalable enterprise integrations.
The Core Technique
Document Scope: DDP vs DPP
graph LR
subgraph ProcessExecution["Process Execution Context"]
DPP["Dynamic Process Property (DPP)<br/>Scope: Global across all documents<br/>Example: GlobalBatchID = 'BATCH-901'"]
subgraph DocStream["Document Pipeline Stream"]
Doc1["Document 1 (Invoice 101)<br/>DDP_CustomerID = 'CUST-A'<br/>DDP_RetryCount = 0"]
Doc2["Document 2 (Invoice 102)<br/>DDP_CustomerID = 'CUST-B'<br/>DDP_RetryCount = 1"]
end
end
- Dynamic Document Property (DDP):
- Scope: Tied exclusively to a specific document.
- Behavior: When a document is split or mapped, its DDPs travel with it. Ideal for record-level tracking (e.g., ).CODE / PROMPT
DDP_OrderId
- Dynamic Process Property (DPP):
- Scope: Global to the entire process execution.
- Behavior: Overwritten by any shape during runtime. If Document 2 sets , Document 1 will see that change. Ideal for batch-level constants (e.g.,CODE / PROMPT
DPP_Status = "FAIL"
).CODE / PROMPTDPP_BatchRunDate
Cross-Reference Tables (CRT)
Cross-Reference Tables replace hardcoded
if/else
switch
| Salesforce Lead Status | SAP Customer Status | Internal Canonical Status | |---|---|---| | Open - Not Contacted | 01_NEW | PROSPECT | | Working - Contacted | 02_ENGAGED | IN_PROGRESS | | Closed - Converted | 03_QUALIFIED | ACTIVE_CUSTOMER | | Closed - Not Converted | 09_DISQUALIFIED | REJECTED |
Flow Control: Threads & Batch Sizing
The Flow Control Shape allows developers to alter processing concurrency:
- Parallel Processing: Splits document streams across multiple JVM threads (or Molecule nodes) to accelerate bulk processing.
- Batching: Groups single documents into batches (e.g., 500 documents per bundle) before invoking database or NetSuite insert operations.
Try This Right Now
Construct a Boomi mapping scenario using a Cross-Reference Table to translate 5 country codes (USA, CAN, GBR, DEU, FRA) into standard ISO alpha-2 codes (US, CA, GB, DE, FR) with a default fallback of "XX" for unrecognized countries.
Tip: Knowledge only becomes capability once you run the prompt yourself.