Implementation Tips – Orchestration Process Naming
SummaryImplementation tips on naming a fulfillment orchestration process.
From Oracle Order Management Cloud product team:
Customers are advised not to name user-defined orchestration processes that end with a number.
What are we recommending: If you are defining any new orchestration process as part of your implementation, we suggest not to have the process name ending with a number, like for e.g. CustomDOO_OrderFulfillmentGenericProcess1.
What will customer see if they do not follow this: This may lead to stuck orders because of overlap with process versioning.
1. User creates a new process named ‘CustomDOO_OrderFulfillmentGenericProcess1’ and deploys the process.