Scope

• JobScheduler now supports event handling using in- and out-conditions for the jobs. see 

  Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-712

• 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.12.10 includes a number of gaps: 

1. In-condition:
   1. A job can have a condition, which executes the job automatically if the condition of the job becomes true.
2. Out-condition:
   1. A job can have a condition, which adds or delete an event if the job execution results in making the expression for the
   execution
   1. execution to true. 
3. Graphical representation:
   1. The graphical representation is available with JOC Cockpit to manage/edit the expression for the condition.

• Who is the target audience? 

  • The feature is implemented for the end-users who want to edit conditions from the graphical representation of jobs execution. 
• From which release does this feature applies? 
  • The "Job Streams" feature is introduced for the first time in the release 1.12.11. 
• What is covered by the docs? 
  • 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. 
  • Description of the feature 
  • Types of conditions 
    • In-condition 
    • Out-condition

• What skills/experiences should a  reader have? 

  • The reader should know the technical terms like what is Job, Event and Job Chain, etc. and working of the JobScheduler and JOC Cockpit. 
  • The reader should not start with this article if he/she is new to the JobScheduler. 
  • To implement the conditions for the jobs, the user should have the basic knowledge on how to create the jobs.

...