Details
-
Feature
-
Status: Dismissed (View Workflow)
-
Minor
-
Resolution: Works as designed
-
None
-
None
Description
Current Situation
- Out Conditions in Job Streams can create global events at any time.
- Such global events can be consumed by jobs in the same or in a different JobScheduler Master.
Desired Behavior
- Use Case
- The first Job Stream creates a global event for a second Job Stream.
- For specific dates or weekdays the first Job Stream should be executed without creating a global event for the second Job Stream. This is intended a temporary measure that should work without changing the basic configuration.
- Configuration
- A list of individual dates can be added from the GUI.
- A list of weekdays Mon-Sun can be added from the GUI.
- The configuration to prevent global events from being created is assigned the job stream and is not related to jobs.
Dismissal
- This feature is already available to our users considering the following approach:
- Instead of suppressing events for given dates it is preferable to create them for specific dates and not to create the for other dates.
- This can be achieved by a dummy job with the sole purpose of creating a global event that is consumed by Job Streams. The run-time settings allow to run the job for specific dates, weekdays etc.
- Users are free to organize their job that create global events, e.g. by storing them in the same folder or by using a common naming convention.
- In our perspective the ability to suppress global events directly in a Job Stream (instead of a job) does not provide any additional benefit when it comes to flexibility of run-time settings and visibility for which future dates a global event will be created.