JS-1281 - When a replaced job chain has a new first node then the not yet started permanent orders are repositioned

Known Issue Status

Behavior

• Passed Test Case
  • Starting Situation
    • In a job chain with e.g. three job nodes an order is waiting to run at the top state.
  • Action
    • Adding a new job node and state between the first and the second job node.
  • Behavior
    • The order executes the new job node on the next run.
• Failed Test Case
  • Starting Situation
    • as above
  • Action
    • Adding a job node and state as the first state of the job chain, i.e. making it the top state.
  • Behavior
    • The order ignores the newly added job node until JobScheduler is restarted.
• Explanation
  • When stating that an order is associated to a job chain then technically this means that it is assigned the first job node of the job chain.
  • Adding a new job node to the top of the job chain does not modify the order's assignment to the job node that was the first node at the time when the order was updated the last time.

Requirement

• The order should consider a newly added job node at the top of the job chain and should execute accordingly 

Workaround

• Solution 1: Update the order configuration
  • An updated order configuration file will force JobScheduler to reload the order configuration and to adjust the assignment of the initial state.
• Solution 2: Use start and end nodes
  • We recommend that you use our /sos/jitl/JobChainStart start job as the first node in every job chain and our /sos/jitl/JobChainEnd end job as the last full node. These are dummy jobs without any function of their own. However, they are helpful for fixing orders or pre-/post-processing rules: changes to the names and/or order of states within a job chain do not require a change to the order.