My Oracle Support Banner

Declarative Alternatives to Using Siebel Scripting (Doc ID 477842.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Siebel Tools - Version 7.0.4 [14068] and later
Information in this document applies to any platform.
Area(s):Siebel VB/eScript/COM
Release(s):V7 (Enterprise), V8 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:scripting, configuration, personalization, state model, workflow
””Checked for Relevance on 27-09-2012””
This document was previously published as Siebel Technical Note 591.

**Checked for relevance on 08-12-2015**

Purpose

There are two approaches to implementing custom business requirements in a Siebel application. The first is to apply scripting; the second is to apply declarative configuration alternatives.

Common reasons for using scripting include:

 

It is recommended that you avoid using scripting where ever possible. Use scripting only when no other configuration alternative is appropriate.

Reasons to avoid scripting include:

Scope

This document is informational and intended for any user.

Details

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
Purpose
Scope
Details
 Data Validation
 Triggering Actions Based on Data Changes
 Resources

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.