|Bookshelf Home | Contents | Index | PDF|
This topic is part of Performance Guidelines for Siebel Scripting.
Often, customers use scripts for data validation, responses to data changes, or other purposes that might best be addressed through declarative means: by defining properties or specifying business service method invocation using Siebel Tools.
Scripting is often unnecessary and must be minimized or avoided because it can introduce performance problems, add risk and complexity, require greater maintenance, and duplicate functionality already available in Siebel Business Applications.
For example, the Validation field property, which allows for common VB expressions and comparison operators, can be used to perform field validation or string manipulation of data entered through the user interface or through Siebel Object Interfaces.
The Force Case field property can also be useful in a data-validation context, such as to ensure that personal names entered have initial capital letters. For more information on supported expressions and operators, see Siebel Developer's Reference.
Setting the Auto Primary property on MVL object definitions can also help you achieve results that you might otherwise use scripting for. For example, if your business requirement is to assign the first record in an MVG as the primary record (for example, primary address or primary owner), then set Auto Primary to the value Default. For more information about using Primary ID fields, see Using Primary ID Fields to Improve Performance and see Configuring Siebel Business Applications.
Functionality such as custom responses to data changes, which can often be handled through scripting, might best be addressed through declarative means. Such mechanisms, many of which can be used in combination, include:
|Siebel Performance Tuning Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|