Enable job nodes to specify conditions for execution based on order parameters

Current Situation

• Orders can be specified to
  • proceed from the beginning of a job chain to it's end.
  • proceed between two given job node states by e.g. <order state="100" end_state="500"/> where 100 to 500 are job node states.

Desired Behavior

• Job nodes should be specified to implement conditions that would allow to skip this node.
• Such conditions are implemented by use of a Plugin that allows JavaScript scripting and that can make use of the JobScheduler API.
• Typical uses cases include
  • to process indivdual job node states for orders based on conditions that are controlled by order parameters.
    • An order parameter "pass_states" contains a list of states that an order should pass. If the current job node state were not included in that list then the job node will be skipped and the order proceeds with the next_state of the current node.
    • An order parameter "skip_states" contains a list of states that an order should skip. If the current job node state were included in that list then the current job node will be skipped.
  • to prevent a job node from being executed and to move an order to a different state.

Maintainer Notes

• This feature will be considered with JobScheduler 2.0. It will not be added to the JobScheduler 1.x branch.