For orders migrated in the past, the order lines are taking old revision of orchestration process
We have a single orchestration definition for our client and have created multiple revisions by modifying the same orchestration and the end date is set. The current active revision is the 9th.
There are orders migrated from a legacy system that have older creation dates and are currently in draft status. When these orders are submitted, they are picking up an older orchestration revision that has been end-dated, instead of the current active revision.
Please note: We did not reject the older revisions.
Our requirement is that all orders—regardless of their creation date (past or present)—should use the latest active orchestration revision when submitted.