A job stream starter can be assigned a job that signals successful completion 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 signals successful completion of the job stream independently from the fact that additional jobs might or might not be executed in the job stream. If execution of this job is caused by the respective job stream starter, then no more jobs in the job stream will be started.

With this feature it is possible to use different jobs that signal successful completion of a job stream per job stream starter, e.g. starting on Monday the job stream instance completes with job3 and starting on Wednesday the job stream instance completes with job4.