Source subscriptions
Concurrent jobs
Source subscription jobs can now run at the same time to more efficiently support data updates for multiple data domains. For example, you can load Customer Master data (HCPs, HCOs) and Product Master data in parallel. Previously, all jobs (except jobs that ran in simulation mode) were queued while another job was running.
Enable this enhancement
This enhancement is enabled by default in your Network instance.
Supported objects
-
Custom main objects
HCP and HCO considerations
Jobs that load HCPs or HCOs can run concurrently with jobs that load custom objects only.
Jobs that load only Veeva objects (HCPs, HCOs) cannot run at the same time. These jobs must always run sequentially because updates to HCPs often impact HCOs (and vice-versa) through the parent HCO relationship.
How it works
Subscription jobs can run at the same time if the top-level objects being loaded do not overlap.
To determine the objects, Network checks the model map of each subscription for the defined top-level objects.
-
No intersection of top-level objects - Jobs can run concurrently.
Exception
Jobs that load HCPs and HCOs are always mutually exclusive.
-
Intersection of top-level objects - Jobs must run sequentially.
Examples
Job A: Top-Level Objects | Job B: Top-Level Objects | Job Run Type |
---|---|---|
HCO | HCO | Sequential |
HCO, HCP | HCP | Sequential |
HCO, HCP | BRAND__C, FORM_STRENGTH__C, PACKAGE__C | Concurrent |
BRAND__C | PACKAGE__C | Concurrent |
BRAND__C, FORM_STRENGTH__C | FORM_STRENGTH__C, PACKAGE__C | Sequential |