Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.13.4
-
None
-
None
Description
Current Situation
When a job start is manually forced in the Job Streams view, then the job is started outside of the context of a job stream. The events that will be created after the task ended will not be available within the scope of a job stream instance.
Desired Behavior
There should be an additional action menu item: Start Task for Job Stream Instance. This will start the job in the context of the currently selected job stream and in the same way as the job would be started if the In Condition were evaluated to true. The functionality of the existing action menu item Start Task remains unchanged.
The start of the job should be done with the attribute force=yes which means that the task will be started immediately even if the job has a time period where it may run.
It should also be possible to start the job parameterized.
When a job start is manually forced in the Job Streams view, then the job start should be assigned the currently selected job stream instance and the events that will be created when the task ends should be available for this job stream instance. Therefore, a job stream can be continued by manually starting a job even if the In Condition of the job is not evaluated to true.