Why Workflows ?

In the last couple of projects I have used more workflow than scripting.Probably scripting has all possible ways to customize siebel application but it's always not the best way to approach. Here are MY reasons why I would not prefer scripting as my first choice for customization.The points listed below are based on what I learnt from Good Siebel folks out there or from siebel knowledge base
> Scripting impacts performance.
Most of the scripting on Business components ,applets and Business service is to create new records or query for existing records to retireve data and all these can be done from the workflow as well. Workflow or workflow policy program would peform better for these..Invoking OOB Business service from workflow always perform better than invoking it from script.
> Deployment
Any change in server side scripting would require a srf deployment and this makes it hard whenever scripting is part of major release. Usually I have seen it take sometime to staibilize big customization or an upgrade. Since workflow is based on XML, it makes small changes deployment to other environment easy.
> Fusion future.
Saw that escripting will be obsolete in Siebel Fusion version and everything will be based on Java Programming. So if you are part of new implementation less scripting would make the client life much easier.

Cons of Workflow
There are few times that you would opt for scripting and here are few reasons to list atleast off the top of my head.
> Cannot retrive the calculated field value from workflow.
>Requirements that needs to create many to many associations. Siebel has the inbuilt PickRecord() method that would establish Many to Many relationship.Same is possible in wokflow as well by having a BC on intersection table and creating the aassociation. But this is not RECOMMENDED by Siebel.
>Some escript or string functions cannot be used on workflows


That's all for now.Rest in next.. Cannot wait to watch the game this week..My favorite is Colts now that Cowboys are out..Let's see.