How to set Job Chain Dependencies

General

JobScheduler can handle different type of dependencies at Job Chain level, Job level, Task level and Order level
Some use cases for the dependencies are

1. JobC can only be started when JobA and JobB are successfully ended.
2. JobB on ServerB can only be started when JobA on Server B is finished.
3. JobC should not be started if JobA is running

JobScheduler can manage complex dependencies using a variety of built-in features such as

1. Locks
2. Split and Sync
3. Eventing
4. API jobs
5. Pre-processing
6. Post-processing

Different Scenarios

1. Wait_for_all_the_predecessor_jobs_to_finish
2. Start_jobs_in_different_servers_(Distributed_Processing)
3. Job_depended_on_previous_execution_status

Downloads

This example can be downloaded here: JobChainDependencies.zip
.