Before we continue to learn how to implement scripts, it is necessary to mention that whenever we write script code in Siebel, there is a high risk that one or more of the following situations might occur:
Similar functionality already exists in the standard Siebel CRM application
Runtime errors or memory leaks negatively affect the application
The performance of the application degenerates
Maintenance and upgrade tasks become more difficult
To avoid any of the preceding things, we should try to fulfill customer requirements with administrative or declarative solutions, which the Siebel application framework provides in abundance, before we resort to scripting.
For example, we can use Siebel Audit Trail to track data changes instead of writing business component scripts, which do the same thing.
The Siebel Workflow framework, discussed in previous chapters, is used intensively by Oracle engineering to implement even the most complex requirements. Whenever additional...
