Scope

JobScheduler now supports event handling using in- and out-conditions for the jobs. see JOC-712 - Getting issue details... STATUS
The support for the conditions feature fills the gap of having a backward dependency in the JobScheduler.
The conditions for the jobs with the branch 1.13.0 includes a number of gaps:
- In-condition
  - A job can have a condition, which executes the job automatically if the condition of the job becomes true.
- Out-condition
  - A job can have a condition, which adds or delete an event if the job execution results in making the expression for the condition to true.
- Graphical representation:
  - The graphical representation is available with JOC Cockpit to manage/edit the expression for the condition.

This documentation covers the new feature to create Job Streams with a backward dependency. It includes, how we can implement different in-conditions and out-conditions.
The user should:
- Know the technical terms like what is Job, Event and Job Chain, etc. and working of the JobScheduler and JOC Cockpit.
- Not start with this article if he/she is new to the JobScheduler.
- Have the basic knowledge on how to create the jobs.

Motivation

What is this feature good for?
- The end users can implement backward dependency for jobs using in-conditions, out-conditions, write the expressions and can add or remove events.
- This feature allows graphical configuration of job dependencies.
What problem does it solve?
- This feature was developed to add better backward dependencies to JobScheduler.
  - Backward dependencies: The JobScheduler comes with a number of solutions to support backward dependencies for jobs and job chains.
    - Check the job and job chain history for previously executed jobs and orders.
    - Synchronize job chains.
    - Job Streams.
  - Forward dependencies: The JobScheduler comes with built-in features for implementing forward dependencies for jobs and orders.
    - Basic dependencies are implemented by the Objects for the Jobs, Job Chains and Orders.
    - Successor jobs can be made to depend on the code returned by the current job.
    - Create successor orders for job chains depending on the return code of the current job chain node.
Roadmap
- This feature is subject to future improvement:
  - Improved usability
  - add editing capabilities for jobs in order to replace JOE
  - improved navigation and display of dependent job streams
- Provide export functionality to display (print) job streams in PDF, PNG

FEATURE AVAILABILITY STARTING FROM RELEASE 1.13.0