Siebel Complex Workflows - limits , tips
We are planning to migrate our in house workflows to Siebel. The Inhouse system receives and processes worklow requests from Siebel via middleware using http and xmls requesting the update of Service Requests and creation of Actions. Some of our workflows are quite complex, request the creation of parallel actions, call programs to determine decisions in the WF, involve various status and result codes (some up to 4 Pages in MS Visio). I was wondering if anyone has had experience with complex workflows in Siebel, if they had problems with size and or performance ? Our inhouse system is very modular and changes
0