Accessing UI Context and Non UI Context Object Instances (Doc ID 477419.1)

Last updated on MAY 13, 2022

Applies to:

Purpose

This document describes how Siebel applications instantiate objects to support the user interface (UI) and how these objects can be accessed from a script to implement business functions. It also describes how objects can be created "out of the UI context" to perform actions that are not immediately reflected in the UI.

A good understanding of the difference between UI and non-UI context objects allows developers to instantiate objects in the right way depending on the business needs.

1.    UI Context objects

UI Context object instances are automatically created and destroyed by the Siebel application to support the rendering of a view.

When a view is displayed in the UI, a business object instance is created in the UI context. Business component instances are created in the UI context for each applet in the view.

All operations performed on a UI context object will be immediately reflected in the UI.

For example:

If bc has been instantiated in the UI context, the following eScript code will perform a requery in the current view and the UI will be affected by the query.

     bc.ClearToQuery();
     bc.ExecuteQuery();

An operation like the example listed below will change the field "Name" in the UI and the user will immediately notice that this field has been updated.

     bc.SetFieldValue ("Name","New Name");

Note: Operations that require the UI to be updated need to be performed using UI-context objects.

2.    Non-UI Context objects

Non UI context objects are created by code. The instances are non-visual. That is, they have no associated UI components. When a non UI context object is used to perform certain task, the result is not noticed by the user in the current view.

Non UI context business components are used to perform tasks involving other business components that are not shown in the UI.

When the current record is instantiated and modified in the UI context, a warning message appears which indicates that the current record has been modified by either another user or a process running out of the UI context. In order to see the new values of the fields the user may refresh the record by executing a query.

"The selected record has been modified by another user since it was retrieved."

The following examples require the use of a Non-UI Context business component:

• Invisibly querying a BC that is visible in the UI.
  • Querying data in a BC without the user seeing any change in the applet(s)
  • Process many records in the background

• Using a BC in a different BO context
  A business component is needed that represents the child/detail records for a parent/master other than the current parent/master (Uses a different link)

  	var BO = TheApplication().GetBusObject("Opportunity");
  	var OppBC = BO.GetBusObject("Opportunity");
  	var ActBC = BO.GetBusComp("Action");

  var ActBC = BO.GetBusComp("Action");
  ActBC.ClearToQuery();
  ActBC.ActivateField("Status");
  ActBC.ActivateField("Date Modified");
  …
  ActBC.ExecuteQuery();
  If (ActBC.FirstRecord())
  {
     var sStatus = ActBC.GetFieldValue("Status");
  …
  }

Scope

This document is informational and intended for any user.

Details

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