Should InactivateWFs be Run Before or After PostInstallDBSetup?
(Doc ID 2713334.1)
Last updated on SEPTEMBER 28, 2020
Applies to:Siebel CRM - Version 20.7 and later
Information in this document applies to any platform.
Starting in the 20.7 Monthly Update, the Workflow Process architecture has changed significantly. Detailed information on the changes can be found in the updated Siebel Bookshelf Business Process Framework - Workflow Guide.
One of the key aspects to the change is that Workflow Processes will only be activated at the repository level, not within the runtime application, if they are needed.
For performance reasons, it is recommended that only the required Workflow Processes be left active in the Design Repository. Inactivation of unneeded Workflow Processes can be done before or after the installation of the 20.7 (or later) release. However, for performance reasons during installation--specifically to reduce the time that PostInstallDBSetup takes to execute--it is recommended that unwanted workflows be inactivated before performing the installation.
NOTE2: The information on this Document applies only to Installation of Updates 20.7 and above being installed on top of existent IP17 environments (17.x, 18.x, 19.x, 20.x)
It does not apply if coming from earlier versions as IP2016 and below to IP2017 which is IRM execution. If coming from versions IP2016 and prior please refer to
How to inactivate unused Workflow Processes in versions prior to IP17 before upgrading to IP17? (Doc ID 2713313.1)
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