This is the process of triggering a Workload Job Definition for a Run. A Workload
Run can be created in two methods.
1. Schedule
2. Explicit Trigger
During a Run, Data Sources within the Workload Job Definition is loaded into the Data Lake, and
then the Data Pipeline starts (Workflow). In a scenario where a Workload Job
Definition consists of only Data Sources (no Actions), it
will load the Data into the Data Lake and complete the Run.
Once the execution is completed, necessary details related to each Run (Data Source loading details, Data Pipeline status, overall Workload Job Definition's execution details) are updated against each Workload Job Definition for further actions (a summary of the Workload Runs is available in the Workload Job Definition page Workload Runs section. Further details can be viewed via Workload Run page).
Both the Workload Job Admin user and Workload Job End user can perform all the activities under this sub-process.
To perform this activity: