How to manage a critical path for job processing

Scope

JobScheduler implements the concept of a "critical path", i.e. the fact that in case of time constraints some less critical jobs should be skipped during daily or nightly processing.
This article introduces the solution for JobScheduler.

Download the attached file: operations.zip
Unzip the archive to your ./config/live/sos folder. All files contained will be unzipped to an operations sub-folder.

The functionality includes job nodes to be skipped for critical path processing. This is achieved by

marking a job node being part of a critical path by prefixing the job node state either with "+" (required) or "-" (skippable).
running a new JITL job "activate_critical_path" that depending on its parameterization would run in one of these processing modes:
- skip the job nodes that are marked as being skippable ("-") (default) or
- skip the job nodes that are not marked as being required ("+").
running a new JITL job "deactivate_critical_path" that would reverse the above operation.

The different processing modes are supported by the following configuration:

Job node states in job chains can be marked to be skipped for critical path processing by prefixing them with a "-" character.
Job node states in job chains can be marked to be required for critical path processing by prefixing them with a "+" character.

tbd