High level Workflow Customization Approaches
Approach 1. Preserve the original workflow, with a different name. Then customize the original workflow. Approach 2.Customizing the original (even if you use the appropriate workflow protection) often results in the flow being blown away when patches are applied. It also means that the fact a flow is customised difficult to tell. So where possible we create new top level (runnable processes) by copying them and renaming them and the same for all lower levels that are customised. With the PO approval (and several other flows inc accopunt generator flows) this is the way to go because you can define the startup process in the application. So for reasons of patch protection and clearly visable customisations always create new top level processes. All new or customised functions, notifications etc are also copied and renamed. Approach 3.One other point to consider is there are workflows that you cannot rename. Therefore, you will have to customize the ORIGINAL. Some of these workflows...