Applet :

Applet method menu Item:

It is a child OT of Applet where in we can find default methods like new record,
Edit Record, save record, Delete Record and Undo Record Etc.,
We can also define other methods available in the application by RCNR
Select a Command from available method and give a Display Name.
Applet Toggle:
This also a child OT of Applet, in a single applet if we want to embed another applet
but with the same view , we need to go for Applet Toggle.
Eg: In All Accounts view, Accounts List Applet is there and Account Note Applet is
there, now at a click of a button we should see Account Private Note Applet but the
view should be All Accounts view only.
This we achieve by Querying for Account Note Applet Drilldown OT RCNR
Add another applet Name Account Private Note Applet , compile the Srf and see the
changes.
Drilldown :
Drill down is child OT of Applet, Drill down is used to get more details of that record,
and generally we do drilldown on a particular field, which will take the user to
another screen.
Drilldowns can be configured with in the same BO
Eg: if the user is in Account List Applet , user clicks on Name field , hyper link
navigates him to Account Entry Applet , these 2 applets reference same BO i.e.,
Account BO.
Name

Hyperlink field

Destination View

Drilldown may navigate to another BO

Eg: if the User is in Service Request List Applet (SR BO), User Clicks on Last Name
field , hyper link navigates him Contact Entry applet , which is in Contact BO, so
when the Navigation is between 2 BOs we need to tell the application which record
we are looking for , bcoz of this we need to give Source Field which is nothing but
the Contact Id in the above eg:)
Name

Hyper Link Field

Destination View

Source Field

Force Active
Force Active Property is available at Business component level as well as at field
level. Default is FALSE. When Force Active is TRUE, the field is queried each time the
business component is instantiated, even when the field is not exposed on the user
interface. Force Active should only be set to TRUE when there is a need to script a
field in the active business component and the field is not exposed on the active
applet. Setting this property to TRUE may reduce performance.
Virtual Business Components
Business components based on external data are called virtual business components.
Virtual business components are used when the business component has to obtain
data from a location other than a database table in the Siebel database, but the
information has to be presented in the standard Siebel user interface (applets and
views).
This is typically real-time information from another database, such as from the
Report Encyclopedia in Actuate, or from an SAP table, although
Anything that can supply data in response to an SQL query is a candidate.
Virtual business components allow you to:

Represent external data (for example, data in an SAP R/3 database) as a

virtual business component within a Siebel application. The business
component configuration specifies the DLL to use to access the data

Use business services to transfer data

The following properties of Field objects are supported in virtual business

components:
Calculated
Calculated Value
Currency Code Field
Exchange Date Field
Force Case
Hidden
Internal Pick Applet
Pick List
Precision
Read Only
Required
Scale
Text Length
Type
The following properties of Field objects are not supported in virtual business
components:
Column, Dest Field, Force Active, Join, Link Specification, Multi Value Link, Multi
Valued,No Copy ,Oracle Sequence Object
Siebel Object Types
Field, Post Default Value, Pre Default Value, Use Default Sensitivity, Validation