History service - log skipped/stopped jobs

Current Situation

• When a workflow job is skipped, the order log contains information only about the executed instructions, not about the skipped jobs.
• When the first workflow job is stopped(suspended) and the order is resumed later, the order log will only contain information about the resumption, but not about the cause of the resumption.

Desired Behaviour

• Skipped jobs:
  • When an job has been skipped, the cause of the skip (manual skip or skip due to addmission time rules) should be enabled in the order log.
    • Introduction of an OrderMoved log line with detailed information about the cause of skipping/moving to another job.
• Stopped jobs:
  • The order log should contain the information about all Stop/Resume operations.

Test Instruction

• Create an deploy a workflow with more than 1 job.
• Skipped jobs:
  • 1) skip all jobs in the Worflow View and check the order log after an order was been executed.
  • 2) skip only one of the jobs ..
  • n) skip/unskip ...
    • Expected result: The order log should contain the information about all skipped jobs.
• Stopped jobs:
  • See the Skip instructions above, but use Stop instead of the Skip operation.
    • Expected result: The order log should contain all skipped (OrderSuspended) and, if a suspended order was resumed, the corresponding resumption operations (OrderResumed).