Page History
...
Dependencies for delayed Order Execution
...
This scenario starts from the above calendar based dependency and handles delayed execution of orders:
- If Order 1 and Order 2 are scheduled for Day 1 but Order 1 cannot proceed in Workflow 1 and remains e.g. in a FAILED or SUSPENDED state for a period longer than Day 1 then Order 2 will wait for Day 2, Day 3 etc. until Order 1 leaves its workflow.
- Users can specify a lifetime for Notice 1:
- if the lifetime is shorter than or equal to Day 1 then Order 2 will start immediately with Notice 1 being expired.
- if the lifetime is longer than Day 1 then another pair of Order 1+ and Order 2+ will become available due to the underlying schedule. As both orders are scheduled for a new daily plan date their dependency is independent from Order 1 and Order 2.
- The desired behavior includes
- the use case to execute Order 1+ and Order 2+ before Order 1 and Order 2 completed. For this use case the lifetime of Notice 1 can be extended for any number of days.
- the use case to execute Order 2 immediately after expiration of Notice 1 at the end of Day 1 or earlier independent from the state of Order 1 being FAILED, COMPLETED or CANCELLED.
Overview
Content Tools