Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Add thre orders to the job_chain_expect_orders job chain. For your convenience the orders 1, 2 and 3 are provided with the sample.
    • Each order uses a parameter sequence with a sequential number such as 1, 2, 3.
    • The expect job uses the parameters 
      • control_order_expected_parameter with the value: sequence
      • control_order_expected_default_value with the value: 1
      • control_order_expected_value_function with the value: parseInt(currentValue) + 1
  • Start order 1 that matches the expected value (parameter sequence=1). 
    • The order is processed and moved to the next_job job.
    • A control order control_order_expect is dynamically created and suspended that contains the next expected value (parameter control_order_expect=2)
  • Start order 3 that does not match the expected value (parameter sequence=3).
    • The order is suspended.
    • The control order with the expected value (parameter control_order_expect=2) remains unchanged.
  • Start order 2 that does match the expected value (parameter sequence=2) .
    • Order 2 is processed and moved to the next_job job. 
      • The control order is automatically modified to carry the next expected value (parameter control_order_expect=3).
    • Order 3 is processed and moved to the next_job job.
      • The control order is automatically modified to carry the next expected value (parameter control_order_expect=4).
  • For use with a date sequence instead of a numeric sequence 
    • the orders 1, 2, 3 carry a second parameter business_date with values in an ISO date format. 
    • the expect job carries sample parameters (prefixed with sample_) that can be activated (renamed) to work with the business_date parameter instead of the sequence parameter of the incoming orders .

.