Reference: Integration project properties and values
The following table lists required and commonly used project properties for the Reltio Integration for Veeva Vault CRM. These values are typically configured in the Reltio Integration Hub (RIH) under Project Properties and used across recipes.
Project properties
| Property | Required | Description | Usage notes |
|---|---|---|---|
| Address – Reference attribute name | Yes | Specifies the reference attribute in Reltio used to identify the address. | Example: Address |
| AWS Micro Batch Size | Yes | Defines the number of records processed per AWS batch. | Maximum allowed is 150. Default is 150. |
| Email for Reltio Exports Notifications | No | Email address that receives notifications for Reltio export jobs. | Example: abc@xyz.com |
| Email for RIH Job Notifications | No | Email address that receives notifications about RIH jobs. | Example: abc@xyz.com |
| HCO – Entity name | Yes | Name of the Healthcare Organization (HCO) entity in Reltio. | Example: HCO |
| HCO – HCO relation name | Yes | Specifies the relation name between healthcare organizations. | Example: OrganizationHierarchy |
| HCO – Reltio export filter condition | No | Filter condition used to export HCO records from Reltio. | If not provided, all records are exported. Example: equals(id,'6t1dB9m') |
| HCP – Entity name | Yes | Name of the Healthcare Professional (HCP) entity in Reltio. | Example: HCP |
| HCP – HCO relation name | Yes | Relation name between HCPs and HCOs. Supports multiple values if needed. | Example: HCPisAffiliatedWithHCO |
| HCP – Reltio export filter condition | No | Filter condition used to export HCP records from Reltio. | Example: equals(id,'6t1dB9m') |
| Raise DCR in Reltio | Yes | Indicates whether to raise a Data Change Request (DCR) in Reltio. | Default: No |
| Reltio environment URL | Yes | Base URL of the Reltio environment in use. | Example: https://dev.reltio.com/ |
| Reltio tenant ID | Yes | Unique identifier of the Reltio tenant. | Example: XXXXXgsNwcq7XXX |
| RIH service user | Yes | Username used for RIH API or service authentication. | Prevents infinite data sync loops. Example: VEEVA_INTEGRATION_PROCESS_DEV |
| Veeva service user ID | Yes | User ID used to authenticate with Veeva services. | Example: 12345678 |
| Veeva source type | Yes | Specifies the type of Veeva source. | Example: Veeva |
| VQL export filter | No | Veeva Query Language (VQL) filter condition for selecting records to export. | Example: modified_date__v > '2025-10-23T14:24:00.000Z' and modified_by |