| Table of Contents |
|---|
Introduction
The Starters are used to start a JobStream as per the assigned runtime or manually start. With the release, 1.13.5 new features are introduced in a starter to make Job Stream more efficient.
Features with starter
The following features are available with the starter.
- Required Job
- Last Job
Required Job
In the Starter, the Required Job field is introduced so, that the Job Stream instance completes its running only if the Required Job is executed. After a successful run of the required job, the Job Stream running state becomes no, and additional jobs in a Job Stream do not affect the Job Stream and executed as per the condition assign on it. In the task history of Job Stream, the required job highlighted with a blue background with the state of the job.
With this feature it is possible to use different "required" jobs per job stream starter, e.g. starting on Monday the job stream instance is considered being "fulfilled" with job3 and starting on Wednesday the job stream instance is "fulfilled" with job4.
How to set Require job in a Starter
- Click on the Edit button from the action menu of the starter.
- Edit window will open for the Starter. Select the Require job from the drop-down menu(E.g: I have used job3)
- After the successful run of the Job Stream, the job3 highlighted with a blue background in history.
Last Job
In the Starter, the Last job field is introduced to end the JobSteam run. If you have assigned any job in the starter field Last Job then no further execution will start in the JobStream. The JobStream will complete and set the running state to no.
With this feature it is possible to use different "Last Job" jobs per job stream starter, e.g. starting on Monday the job stream instance is ended with job3 and starting on Wednesday the job stream instance is ended with job4.
How to set Require job in a Starter
- Click on the Edit button from the action menu of the starter.
- Edit window will open for the Starter. Select the Last job from the drop-down menu(E.g: I have used job4)
- After a successful run of job4, no other job will execute in the Job Stream.
