My Oracle Support Banner

ActivateField method's proper usage (Doc ID 477947.1)

Last updated on JUNE 01, 2017

Applies to:

Siebel Tools - Version 7.0.4 [14068] and later
Information in this document applies to any platform.
Area(s):Siebel.CRM.Application Development.Scripting and Interfaces
Release(s):V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):GENERIC (All Platforms)
Latest release tested against:V7 (Enterprise)

Checked for relevance on 01-Jun-2017.


Purpose

This Bulletin discusses the proper usage of ActivateField method, the example provided here is in eScript.

ActivateField is normally used when GetFieldValue or SetFieldValue will be performed on the particular field. This method should only be used before a new query is executed on the corresponding business component. Care must be taken with this method when dealing with the currently active business component. In most occasions, the currently active business component refers to the UI Context object. This document explains what to do and what to avoid.

Scope

This document is informational and intended for developers who use Siebel scripting.

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
 1. What is the purpose of ActivateField?
 2. UI context and non-UI context object instances
 2.1 UI context object
 2.2 Non-UI context objects
 3. Fields which don’t need ActivateField in both UI and non-UI context:
 4. Proper usage and improper usage of ActivateFied in UI context
 4.1 Proper usage for UI context objects
 4.2 Improper usage of ActivateField in UI context
 5. Proper usage and improper usage of ActivateFied in non-UI context
 5.1 Proper usage for non-UI context objects
 5.2 Improper usage for non-UI context objects
References

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