Scope

• 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.10. 
• 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.

Motivation

• What is this feature good for? 
  • The end users can edit the in-conditions, out-conditions, add or remove events, write the expressions and can see the workflow of the jobs execution by the graphical representation in the Job Streams tab. 
  • 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. 
     
    • 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

Implementation 

• How to ...... Articles 
  • How to edit conditions for job execution in Job Streams? 
  • How to insert expressions in Job streams? 
  • How to add event in Job Streams? 
  • How to remove event in Job Streams? 
  • How to switch to compact view in Job Streams? 
  • How to switch to detailed view in Job Streams? 
  • How to start a job execution? 
  • How to include the Job Streams feature? 
  • How to enable the JobScheduler plugin? 
  • What is Graphical view and where it is located? 

Use Cases

Use Case 1: Implement a simple backward dependency

job1 → job2 → job3 → job4

Use Case 2: Implement split & join

Use Case 3: Implement a job stream across folders

Use Case 4: Use job streams for monitoring

Use Case 5: Use job streams to analyze job execution problems

References

• Links to other articles
• Links  to JIRA
  • JOC-712 - Getting issue details... STATUS