Page History

...

• If there is a working day in the Asian region then an order will be created for Workflow 1.
  • If an order is created for the European region for the same date then this order will wait for completion of Workflow 1.
  • If no order is created for the European region for the same date then this does not affect Workflow 1.
• If there is a non-working day in the Asian region then no order is created for Workflow 1.
  • If an order is created for the European region then this will start Workflow 2 without waiting for a notice as there is no posting order from the Asian region available for this date.
  • If no order is created for the European region then neither Workflow 1 nor Workflow 2 will be executed.

...

• 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 posts the required Notice 1.
• 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 - provided that there is no further posting order for Workflow 1 for the same daily plan date.
  • if the lifetime is longer than Day 1 then another pair of Order 1+ and Order 2+ will be started 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 for the previous daily plan date.
• 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 configured 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.

...