Your UX is waiting ...interact, engage, explore in Las Vegas at CloudWorld 2023

Learn more
Implementation Tips – Orchestration Process Naming — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Implementation Tips – Orchestration Process Naming

Received Response
edited May 22, 2018 5:20PM in Order Management 1 comment


Implementation 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.

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!