Escript Best Practices

There a Golden Rule that every Siebel Developer should follow when it comes to scripting. This golden rule is to never script unless there is no other choice on meeting your requirements. Scripting is the highest level of customization and adds complexity and cost to the configuration. So scripting should be your last resort. So the first practice is to avoid script. So to avoid scripting, below are some configuration methods every developer should think before attempting to work with eScripts

User Properties: This is a major feature in Siebel. An example of this is “On Field Update Set”. This is used instead of scripting on Set Field Value event to change some other value.

Calculated Fields: Calculated fields come very handy when we need to do validation. With the help of Calculated Fields and User properties lot of functional requirements are achieved.

State Models: State models help in restricting transitions from one field value to other. So there is no need to script to check the status change.

Runtime Events: This was introduced in 7.7 and has been of significant help to the developers to on invoking Workflows & Business Services based on events. So avoid Business Component events.

Workflows: Instead of writing a big script, we can break that down to a series of workflow steps. We have steps Like Write, Update, if condition, Sub-Process, Invoke Business Service and lot of other key stuff. Workflows are very efficient and promising.