@bijection/connectors/veeva entrypoint to declare Veeva Vault resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Object records
changes: Object records by VQL modified_date__v with deleted records
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:veeva/objectRecords/changes/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: veeva-vault. Keep credential material in the private credential inventory.
Provider setup requirements:
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Compiled declaration examples and configuration details are published in the connector reference.vault fills https://<vault>.veevavault.com/. A Vault API access token (Bearer) or a session id (bare Authorization) authorizes.
objectRecords.changes first walks VQL ... WHERE modified_date__v > 'T' OR (modified_date__v = 'T' AND id > 'K') ORDER BY modified_date__v ASC, id ASC PAGESIZE 100, a compound keyset that never follows expiring next_page links. It then lists objects/deletions/vobjects/<object> within a window frozen at the last records response’s Date, and those ids are withdrawn. HTTP 200 with responseStatus: FAILURE fails the page. Vault keeps deletions 30 days: a carried deletion bound older than that fails the pass and needs a rebaseline. Direct Data extracts are not read.
Built from the provider’s published API documentation; nothing here has run against Veeva Vault or been qualified.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.