JobScheduler can make the start of a job chain dependent on the execution of previous jobs and job chains.
The following links describe the use of scripts to check job and job chain histories via the JobScheduler's XML interface before starting a job chain:
FEATURE AVAILABILITY STARTING FROM RELEASE 1.10.2
JITL-228 - Getting issue details... STATUS
- For the configuration of job chains whose execution is dependent on the completion of preceding jobs job chains and orders:
- Using a
check_predecessor_job_chainjob
(Method uses a job script to check the job chain and order histories for successful execution.) - Using Scripting and Pre-/Post-Processing - i.e. using a job monitor script
- How to manage complex conditions to check previous job executions and to start successor job chains
(Method checks job histories for successful execution.) - How to check previous job chain executions and to start successor job chains
(Method checks job chain and order histories for successful execution.) - How to add conditions for job execution with date calculation
(Method uses individually scripted conditions to determine job execution.)
- How to manage complex conditions to check previous job executions and to start successor job chains
- For a detailed description of the scripts and history objects used see:
- Using a
- For more information about configuring workflow dependencies see:
Pages
- How to add a condition to check previous jobs before the execution of the current job chain
- How to check previous job chain executions and to start successor job chains
- How to manage complex conditions to check previous job executions and to start successor job chains
- How to add a condition to check previous job chains before the execution of the current job chain
Navigation
Further Resources
There is no content with the specified labelsFrequently Asked Questions
Examples in detail
There is no content with the specified labelsTroubleshooting