Data Integration terminology changes
Some Data Integration terms are changing to align with Boomi's established naming conventions and the broader Boomi Enterprise Platform. You will see the updated terms throughout the application and documentation. The new terminology will be incorporated into training content and other assets over time.
What terms are changing
The following table lists the existing Data Integration terms and their new equivalents.
| Existing term | New term | Definition |
|---|---|---|
| Rivers | Data Flows | The top-level container for all data movement in Data Integration. A Data Flow defines the end-to-end path that data takes from a source to a target. |
| Source to Target River | Source to Target Flow | A Data Flow that moves data directly from a source to a target, typically used for ELT pipelines. |
| Logic River | Logic Flow | A Data Flow that applies transformation logic, business rules, or conditional processing to data before it reaches a target. |
| Actions River | REST Action | A Data Flow that exposes REST endpoints, enabling Data Integration to respond to external HTTP requests. |
| Sub Rivers | Sub Data Flows | Reusable Data Flow components that can be embedded within other Data Flows to modularize and simplify complex logic. |
What's not changing
To maintain backward compatibility, the following will not change in this release:
- API endpoint names, request and response structures, and field values
- Connector SDK interfaces, methods, and variables
- Custom scripting interfaces, methods, and variables
note
No API changes are included in this release. Existing API integrations and scripts that reference current Data Integration terms will continue to function without modification.
