Some Workflows Have Inactive Flag Set to Y After Update From Siebel 20.6 Or Previous To Siebel CRM 21.9 Or Later Versions
(Doc ID 2856693.1)
Last updated on MARCH 22, 2022
Applies to:Siebel CRM - Version 21.9 and later
Information in this document applies to any platform.
On this particular scenario customer was updating from Siebel CRM 19.12 to 21.12 version and some workflows in Siebel Repository table (S_WFR_PROC) has the Inactive flags set to Y.
The developers identified that they have some workflows that are been worked and should not have been Inactive set to Y.
The PostInstallDBSetup should only set Inactive=Y for the workflows NOT been used ONLY as per Document:2714523.1 - InactiveWFs Is Not Setting Inactive Property To TRUE For Any Workflows On the Repository, But Repository Has Lots of Unused Workflows
Customer notice that about 554 records in S_WFR_PROC have the Inactive flag set to TRUE (checked or Y on S_WFR_PROC column INACTIVE_FLG) by PostInstallDBSetup process, but some of these 554 are been used on the Development environment and the legacy Version column is not 0 and as indicated on Document 2714523.1 the PostInstallDBsetup should only act over legacy Version column = 0
The issue can be reproduced on customer environment with following steps:
1. Execute an update from Siebel CRM 19.12 to Siebel CRM 21.12 Development environment.
2. After the Update install end with success verify the PostInstallDBSetup reports and confirm no errors show up.
3. Open Siebel Tools and verify the workflows on the Repository, some workflows that are been used has Inactive set to checked and show inactive in Siebel Tools > Object Explorer > Workflow Processes.
Customer update Siebel CRM 19.x to 21.12
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