Recipe organization and execution flow
Learn about how recipes are organized and executed within the Reltio Integration for Veeva Vault CRM to support real-time and batch data flows.
Learn how recipes are organized and executed within the Reltio Integration for Veeva Vault CRM to support real-time and batch data flows. It describes the folder structure, recipe types, and the flow of execution across real-time and batch modes. Understanding this layout helps administrators trace data paths and troubleshoot integration behavior.
Folder structure and recipe types
Recipes are organized into logical folders based on function and direction. Each folder contains recipes for a specific purpose, such as triggering an event, processing a payload, handling errors, or raising a DCR.
| Folder Type | Example Folder Name | Purpose |
|---|---|---|
| Trigger (Inbound) | `RIH | Trigger Veeva to Reltio` |
| Trigger (Outbound) | `RIH | Trigger Reltio to Veeva` |
| Process | `PROC | Reltio to Veeva |
| DCR | `PROC | Raise DCR in Reltio` |
| Error Handler | `PROC | Error Handler` |
| Folder and recipe names follow consistent naming patterns for easier maintenance across environments and directions. | ||
Recipe execution flow patterns
Recipes follow predictable patterns depending on the integration direction and mode (real-time or batch). This section outlines how recipes execute in each supported flow.
Real-time flow (Reltio → Veeva)
This flow is triggered by events emitted from the Reltio queue when changes occur to HCP, HCO, or relationship data. It ensures near real time propagation of updates to Veeva Vault CRM.
- The trigger recipe consumes messages from an external queue (SQS, Pub/Sub, or Azure Topic).
- The process recipe transforms the payload using mapping logic.
- Veeva Vault integration actions (example, create, update) are executed.
- If errors occur, the error handler recipe logs them and applies retry logic or routing.
Real-time flow (Veeva → Reltio)
This flow retrieves data from Veeva Vault CRM using polling or scheduled extract logic. It brings HCP or HCO updates into Reltio tenant from Vault in near real time.
- The trigger recipe polls Vault CRM or receives extracts on a defined interval.
- Matching or creation logic is applied in the process recipe.
- Reltio records are created, updated, or enriched.
- DCR-approved records are identified and tagged during processing.
- Errors are captured using the shared error handler.
Batch flow
Batch recipes are used for periodic synchronization tasks such as full data loads or scheduled relationship updates. These flows run on a fixed schedule rather than being triggered by events.
- Recipes are triggered on a defined schedule (example, daily, hourly).
- Data is extracted from Vault CRM or Reltio using VQL or API calls.
- Process recipes apply mapping logic and write to the target system.
- Logs, email notifications, and error handlers track results.