My Oracle Support Banner

FAQ: Best Practices For Custom Order Entry Workflow Design (Doc ID 402144.1)

Last updated on APRIL 19, 2024

Applies to:

Oracle Order Management - Version 11.5.2 and later
Information in this document applies to any platform.
 
 


Purpose



These FAQs try to touch upon some best practice considerations while designing Custom Workflows. Most of the questions may be generic but a few of them may be specific to Order Entry module.

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Questions and Answers
 Question 1:  Is it acceptable to modify seeded definitions of workflow process and activities while doing customizations?
 Question 2:  When I make design changes and upload the latest version of custom Workflow definition file to the database using WFLOAD, will the existing open workflow items also automatically reflect to the new changes I did in the workflow builder?
 Question 3:  If my workflow runtime data is huge or voluminous, what could I do to optimize the online or batch performance for Workflow processing?
 Question 4:  What can be the impact of poor (read: infinite loops or low wait time repeated loops) conditional progressing looping logic design ?
 Question 5:  How do we design good customizable workflow wait activities?
 Question 6:  How is an infinite loop situation created for FNDWFBG concurrent program?
 Question 7:  How can we  avoid Infinite loop situations while executing workflow activities in the background?
 Question 8:  What are the other checks and balances best practices that I should integrate for making sure that there is no data corruption or out-of-sync between Workflow or Order management (or any business module being used) situations caused due to poor coding?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.