A job stream starter can be assigned a required job for fulfillment of a job stream instance

Current Situation

A job stream instance is considered being "in progress" if not all In Conditions are consumed and if at least one In Condition waits for events that probably will be created by Out Conditions of the job stream.

Desired Behavior

It should be possible to assign a job to a job stream starter that is considered the "required" job to "fulfill" the job stream. A "fulfilled" job stream instance can continue to run successor jobs to the "required" job, however, these jobs and their execution results will not change the "fulfilled" status of the job stream instance.

This means that the job stream instance is considered being not "fulfilled" if the In Condition of the "required" job is evaluated to true. For different job stream starters different "required" jobs can be assigned.

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.