Day 1 to 6 : Siebel Configuration

B2B Front End Delivery Section

Sensitivity: Internal & Restricted

Understanding the Siebel Application

Siebel e-Business Application

 These applications are delivered out-of-box with the standard set of screens, views, applets,
Business entities and tables
 All the enterprise data is stored in a central database (3rd- party RDBMS) and it is manipulate
by using a Siebel Application
 Developers can tailor the Siebel screens, views, applets, business entities, column and table in
a limited and controlled manner to better support the user’s business needs.

Siebel Tool
 This Application is used to configure the Siebel Application to exactly meet the users’ business
requirement for:
 User Interface
 Business Logics
 Data Storage
.

Sensitivity: Internal & Restricted

Object Definition
Are data construct that define the elements of the:
 User Interface
 Business Logics
 Data Storage
Are stored in the Siebel repository, a subset of tables in the Siebel Database that contains object
definitions
Are examined, created and edited by using Siebel tools
Are compiled into the repository file (srf) for a configured application

Database
Tools Application
Repository
Data Application Object Manager

Compiled Object
definitions .srf Configured
application

Sensitivity: Internal & Restricted

Siebel Application Architecture 1/3

 Objects are organized by their

characteristics and behavior to
allow for significant application
changes

 A third-party RDBMS holds the

physical schema of the Siebel
Data Model

Sensitivity: Internal & Restricted

Siebel Application Architecture 2/3
Physical User Interface Layer
 Consists of the physical files, Siebel Templates files, style sheets, and other file-based
metadata that render the UI.
 Can be modified by using any HTML or Text Editor

User Interface Objects Layer

 Consists of user interface object definitions that define the visual interface that the
user sees and interacts with in a Web browser.
 There are four principal UI Objects
 Application
 Screen
 View
 Applet

Sensitivity: Internal & Restricted

Siebel Application Architecture 3/3
Business Objects layer
Objects that define business logic and organize data from underlying tables into logical units.
There are two principal objects:
Business Component
Business Object

Business
Object

Business
Component
Data Objects layer
Consists of data object definitions that directly map the data structures from the underlying
physical relational database into Siebel applications
There are two principal object definitions:
Tables
Columns

Sensitivity: Internal & Restricted

 Business Component
 Represents one fundamental business entity in the enterprise
For Example: Contacts, Business Address, Activities, Accounts
Refers to a single base table

Internal
Product (BC) Fields
Name Part # Version

S_PROD_INT Columns
NAME PART_NUM VERSION
(Base Table)

 Represents the logical grouping of data from one or more table.

Internal
Product
(BC) Name Vendor Location Cost Fields

Additional Table

NAME LOC STD_PRI_UNIT Columns

Base table
S_PROD_INT S_ORG_EXT S_PRI_LST_ITEM

Sensitivity: Internal & Restricted

Business Object
 Represents a major functional area of the enterprise
For Example : Account Management
 Provides the foundation for views
 It is a collection of the related Business components.
 Has one business component which serves as the master
 Normally the name of the business object is the name of the master business component
 A business component can be used in many Business Object Contexts

Account Contact BC appears as

master in Contact BO

Account
Contact

Contact
Quote Product Contact

Contact BC appears as child Quote Product Account

in Account BO

Sensitivity: Internal & Restricted

Applet Object Definition
 A portion of a Siebel application window, such as a list or form
 Refers to one business component whose data can be viewed and edited through the list or form
 Consists of multiple list column or textbox control object definitions
 Refers to a field in the applet-referenced business component
 Specifies how the data for the field is displayed in the list or form

Business Contact
component First Name Job Title Email Address

Sensitivity: Internal & Restricted

View Object Definition
 Specifies a view in a Siebel application
 Refers to one business object
 Consists of multiple applet object definitions
 Each applet must reference a business component in that business object

Account

Account

Quote Product Contact

Sensitivity: Internal & Restricted

 Screen Object Definition
 Specifies a screen in a Siebel application
 Is associated with a major functional area of the enterprise
 Consists of multiple view object definitions that usually refer to the same business object
 Administration screens are an exception

Screens

Sensitivity: Internal & Restricted

Application Object Definition
 Specifies a particular collection of screens available in a Siebel application
 Consists of multiple screen object definitions

Sensitivity: Internal & Restricted

Major Objects Definitions
Are related to each other
Are grouped into three layers with different subject matters and purposes
Refer to definitions in the next lower layer and are insulated from those in lower layers

Sensitivity: Internal & Restricted

The Configuration File (cfg)
 The configuration file is a text file and is modifiable by any text editor
 Siebel configuration file contains parameters that indicate:

Repository File

Siebel Application

Application Title

Splash Screen Title

Default Data Sources

Sensitivity: Internal & Restricted

Siebel Tools: Interface

 Object types in Object Explorer (OE)

 Object definitions in Object List Editor (OLE)
Object List
Object Editor
Explorer

Sensitivity: Internal & Restricted

 Object Explorer (OE): Types Tab (default)

Parent Object Definition

OE
OBLE Child Object Definition

Expand parent object types in OE to display contained object types

For selected parent object type in OE, definitions of this type are displayed in Object List Editor
(OBLE)
For selected child object type, parent-child relationship between object definitions
is shown in OBLEs as shown above
In siebel tools it is reperesented as:
 Applet :: Contact Quota Period List Applet | Control :: AppletTitle

Sensitivity: Internal & Restricted

Object Explorer (OE): Details Tab

 Shows top level

object types

 Expanding a
definition displays
child object types

 Expanding child
object type displays
definitions of that type

 Expanding top level object type displays object definitions of that type
 OBLE shows flat list of definitions for selected type

Sensitivity: Internal & Restricted

Object Explorer (OE): Flat Tab

All object types are displayed in flat list (no hierarchy shown)
Selected object type in flat list results in OBLE displaying all definitions of
that type
You can compare same-named definitions with different parent in the
OBLE Child definitions have Parent property in OBLE
 Helps developers to find child object with unknown parent

Sensitivity: Internal & Restricted

 Object Definitions: Properties Window

 The Properties Window displays the object definition

selected in the Object
List Editor (open by selecting View > Windows>
Properties Window)
 Properties are listed in alphabetical order
 The value is shown next to property name and values can
be changed
here also
 The Properties Window does not display Project and
Changed attributes

Sensitivity: Internal & Restricted

Object Definitions: Hyperlinks
 Drill down on a hyperlink to navigate to that object definition
 Applet to business component
 Business component to table Underlined
Note: Users must have the Developer responsibility in blue

Sensitivity: Internal & Restricted

 Object Definitions: Repository Search
 Use Search Repository to find multiple object types at once
 Locate definitions regardless of object type or position in hierarchy

Select one
or more

Double-click to
navigate to
definition

Sensitivity: Internal & Restricted

Columns
Each table has multiple columns to store user and system data
 Defined by the Column child object definitions
Columns determine the data that can be stored in that table
Properties of existing tables and columns should not be edited

Sensitivity: Internal & Restricted

Relationship Between Tables
Siebel database tables are related to one another
Understanding the relationships between tables is important to implementing your
business logic
1:M Relationship are captured using the foreign Key table column in the table on many
side of the relationship.
 Many Foreign Key are named as Suffix _ID

S_PROD_INT
ROW_ID

NAME

Foreign key column for

the 1:M Asset Product
S_ASSET relationship
ROW_ID

ASSET_NUM

PROD_ID

Sensitivity: Internal & Restricted

Relationship Between Tables [Contd..]

M:M Relationship are captured using foreign key table columns in a third table
called the intersection table

Intersection table for M:M

Product Product Line relationship

S_PROD_LN S_PROD_INT

ROW_ID

NAME

PART_NUM

UOM_CD
ROW_ID

NAME

DESC_TEXT

S_PROD_LN_PROD

ROW_ID

PROD_LN_ID

PROD_ID

Sensitivity: Internal & Restricted

1:1 Extension Table
Is a special table that has a 1:1 relationship with a base table
 Foreign key for the relationship:
 Is located in the extension table
 Is named PAR_ROW_ID
Provides additional columns for business components referencing the base table
 A base and extension table can be considered as a single logical table
 Have the name of the base table with suffix _X

Base table S_PROD_INT S_PROD_INT_X Extension table

ROW_ID

NAME

PART_NUM

UOM_CD

ROW_ID

PAR_ROW_ID

ATTRIB_39
Stores the Stock
Level field

Sensitivity: Internal & Restricted

1:M Extension Table

Is a special table for storing child data related to an existing parent table
Allows you to track entities that do not exist in the standard Siebel applications
Contain more than 20 predefined tables that have one-to-many relationships with
base tables
Has name of main table appended with _XM
S_CONTACT S_CONTACT_XM
ROW_ID

FST_NAME

LAST_NAME

EMAIL_ADDR

ROW_ID

PAR_ROW_ID

TYPE

NAME

ATTRIB_01
TYPE column distinguishes
between different types of data
in the table

Sensitivity: Internal & Restricted

Business Component
Is a logical grouping of data
from one or more tables
Consists of single-value fields,
each of which references a single
column in a table ASGN_USR_EXCLD_FLG

One table is considered as a base table which contains the main columns of the Business
component. These fields are typically editable.
Field referencing columns in the joined table are read only.
Column property maps to a column in the base table, if the join property is blank

Opportunity
Name Description Decision Level Sales Stage Sales Stage Phase

S_OPTY S_OPTY_X S_STG

ROW_ID

NAME

DESC_TEXT

CURCY_CD

ROW_ID

NAME

PHASE_CD

STG_ORDER
ROW_ID

PAR_ROW_ID

ATTRIB_01

ATTRIB_09

ATTRIB_39
Base table

Sensitivity: Internal & Restricted Joined table

Join Definition

 Specifies the joined table from which to retrieve data

If the Outer Join flag is set to TRUE, the join returns all records from the base table,
even when there is no related row in the joined table

Name of join
Joined table

Sensitivity: Internal & Restricted

Join Specification Definition
 Specifies how to retrieve the related row from the joined table
 Based on the foreign and primary keys used to relate the base and joined
tables

Opportunity
Name Description Sales Stage Id
Foreign Primary
key key
S_OPTY S_STG field column
ROW_ID

NAME

DESC_TEXT

CURCY_CD

CURR_STG_ID

ROW_ID

NAME

PHASE_CD

STG_ORDER

Sensitivity: Internal & Restricted

1:1 Extension Table

 Base table and extension table columns can be considered to be one logical table
Data from the extension tables is retrieved for the base table for the business
component
Data coming from extension tables can be edited

ATTRIB_01

Columns from
S_OPTY_X

Sensitivity: Internal & Restricted

Party Business Components
 Represents a variety of people and organizational entities
 Person-related entities
 Organization-related entities
 Groupings created for access to master data

Contact Position Account

Employee
Access Group Division

User
User List

Partner Organization

Person –related Organization –

entities Groupings for related entities
Access Control

Sensitivity: Internal & Restricted

S_PARTY
 Is the base table for all party business components
 Stores the party name and party type
Has multiple extension tables that store the business data for the party business
components

Sensitivity: Internal & Restricted

S_PARTY_PER
 S_PARTY_PER
 Is an intersection table that relates two instances of parties
 Used to implement relationship between
 User Lists and Users
 Employees and Positions
 Access Groups and Members
 Accounts and contacts

Sensitivity: Internal & Restricted

Business Objects
 Are a collection of related business components that represent a major area of the business
 One business component is the parent or master
 Other business components are the children
 Provide the foundation for views

Account

Account

Action Opportunity Contact

Sensitivity: Internal & Restricted

 Business Object Component Definition
 Specifies that a business component is to be included in the business object
 Link property specifies the link definition that relates the parent and child business components

Parent BC

Child BCs

Sensitivity: Internal & Restricted

 Links
Link
Specifies the relationship between business Account
components
Specifies which records to retrieve from the child
Account
business component
Supports master-detail views
Specifies the foreign keys to populate when new child
records are created
Action Product Contact
Used with both 1:M and M:M relation between
parent and child data

Account BC Master/Parent/
One
lin
k

Action Detail / Child /

BC Many

Sensitivity: Internal & Restricted

Grand Child Business Components

 Business objects may include grandchild business components

 Used in parent-child-grandchild views

Contact BC

Activity Plan
BC

Activity Plan
Action BC

Sensitivity: Internal & Restricted

Siebel Tools: Projects
 A Standard Siebel Application is delivered with a large number of existing projects
 New projects can be created by
 Selecting the Project object type
 Creating a new record in the Object List Editor (OLE)
Once a new Project is created, it cannot be deleted
 Part of the Siebel change management system to assure that only one developer at a time can be
making changes to a given set of object definitions

Sensitivity: Internal & Restricted

Assigning Object Definitions to Projects
 Every object definition must be assigned to one , and only one project, either:
 A Siebel-supplied Project OR
 A user-created Project
 Top level object definition has a Project property. Child object definitions
belong to parent project and will not have project property

Sensitivity: Internal & Restricted

Viewing Object Definitions by Projects
 Select a project from the Project drop-down list in the Object Explorer
 The Object Explorer displays the object types only if there are definitions of that type in the
selected project
 To see all projects, select **All Projects** from the drop-down list

Sensitivity: Internal & Restricted

Repositories

 Master copy of repository resides on a server database

 Each developer has a copy of the repository on the local developer (client) workstation
 Developers perform all editing on their local repository

Server Machine Developer Developer Developer

Workstation Workstation Workstation

Master Local

Sensitivity: Internal & Restricted

Single Object Locking
 This concept has been included from Siebel 7.7 version onward.
 This new functionality allows developers to lock and check out arbitrary groups of
individual objects rather than entire projects

Sensitivity: Internal & Restricted

Locking Projects Locally

 We can lock and unlock projects directly either on local or on server by setting the Locked
property TRUE
 Also thru Tools > Lock Project of menu option

Sensitivity: Internal & Restricted

Locking Projects Locally

 Consider direct local locking when

 Prototyping your ideas without preventing other developers from checking out the project

 Intending to discard (rather than save) your work

 Realize that when you directly lock project locally, you

 Can make and test modifications locally

 Cannot check them into the server repository

 Only projects you have checked out or a newly created project can only be checked in

 Local project’s definitions will get overwritten the next time you get or check out the

project.

Sensitivity: Internal & Restricted

Locking Projects on the Server

 When a developer locks a project directly on the server, other developers cannot check out the

same project. They may Get those object definitions in an incomplete, inconsistent, and untested

state

 In addition the developer loses the ability to cancel check out and restore the original definitions

 Siebel recommends that developers never directly lock Projects on the Server

 Always use check out and modify the object definitions locally

Server Machine Developer

Workstation

Master Local
Sensitivity: Internal & Restricted
 Editing Object Definition
 Select the object definition to edit using the Object Explorer and Object List Editor
 Make sure that project has been locked

Indicates project locked Type in a value Select a value

Sensitivity: Internal & Restricted

Creating a New Object Definition
 Select the desired object type in the Object Explorer
 Create a new record in the Object List Editor

Create a unique name Select a project from picklist Assign values to remaining fields

Locked projects only

Sensitivity: Internal & Restricted

Archive File

Contain object definitions exported from a repository

Available for importing into other repositories
Have .sif extension by default
Are used to share object definitions in multiple repository development
Are used to back up object definitions
Can be version-controlled using source control systems

To export Object Definition To export Project

 Select the object definition(s)  Select the project (or projects) to
 Select Tools > Add to Archive be archived
 Select an existing (or create a  Select Tools > Add to Archive
new) archive file  Select an existing (or create a
 Click Save in the Export to new) archive file
Archive File window  Click Save in the Export to
Archive File window

Sensitivity: Internal & Restricted

Importing Object Definitions
 Object definitions in an archive file can be imported into the local repository on the developer workstation
 Appear in the current active repository
 To import object definitions
 Select Tools > Import from Archive
 Select the archive file
 Indicate how to resolve conflicting object definitions
 Set the default conflict resolution

 Adjust individual resolutions by right-clicking them in the Object differences list

Sensitivity: Internal & Restricted

Compare Objects

Displays differences between selected object definition and another one:

In current local repository
In archive file
In repository on server

To compare object definition to one in

archive or repository
 Select object definition to be compared
 Select Tools > Compare Objects
Select type of comparison

Sensitivity: Internal & Restricted

 Compiling
 Compile to produce an .srf file to test the configuration
 Reads object definitions from repository and creates a flat file representation to be accessed by siebel.exe at run time
 Compile into .srf file located in the objects directory of the client application

Siebel Tools Application

Siebel Application
Object Manager

Compiling .srf Configured

Application

Database

Repository
Data

Sensitivity: Internal & Restricted

Compile Options

 Developers can compile:

 Projects
 Individual object definitions
 Compile Projects
 When starting and at milestones, compile All Projects to generate a new .srf file
 Subsequently, compile only Selected Projects or Locked Projects for an incremental compile
 To compile projects:
 Select Tools > Compile
Projects
 Select project or projects

Compile into client

directory

Run-time behavior when user compiles SRF

 If Web client is running:
At end of compile, browser window
refreshes
User is brought back to view
displayed immediately before
compile
Sensitivity: Internal & Restricted
Form Applet Web Templates
 Define the layout of form applets
The Account Entry
 Button controls applet uses the
 Textbox controls Applet Form Grid
Layout template

The Object Manager

uses the template to
build this familiar
applet

Sensitivity: Internal & Restricted

List Applet Web Templates
 Standard Interactivity clients require two modes:
 Base
 Edit
 High Interactivity clients require one mode:
EditList mode appears as
 EditList – Use Applet List (Base/EditList) an editable list of data

EditList mode supports

querying and data entry
directly in the list
Sensitivity: Internal & Restricted
Applet Modes
 Form Applets will be in two modes i.e. Base and Edit modes where as
 List Applets will be in Base, Edit and Edit List modes .
 The mode can be specified in ‘Applet Web Template” under “Applet” Object

Sensitivity: Internal & Restricted

Major User Interface Object Types

 The major user interface Object are:

 Applet
 View
 Screen
 Application

Some Inputs before customizing the application

 Business Object Layer definitions should exist before creating UI object
definitions
 Views map to Business Objects and Applets to Business Components
 List Columns in ‘List’ Applets and a subset of Controls in ‘Form’ Applets map to
Fields in Business Components

Sensitivity: Internal & Restricted

Mapping UI Layer Definitions to BO Layer Definitions
Application
View’s Business Object property specifies BO used
Applet’s Business Component property specifies BC used
Control’s or List Column’s Field property specifies Field in BC
used Screen

Maps to
BusObj View

Maps to
BusComp1 BusComp2 Applet
….

Maps to List Column

Field1 Field2 Field3
or Control

Sensitivity: Internal & Restricted

Configuring a List Applets

.
1. Create New applet object definition

2. Associate applet template

with applet object definition

3. Bind controls and list columns to

template

• … Or by using the List Applet wizard

Sensitivity: Internal & Restricted

Applet Wizard

Helps to identify all the correct properties and

automatically creates child objects, such as Web
Template Items, etc.

It can be invoked thru File > New Object

 Select List/Form Applet to create the respective
ones
 Applet wizards increases developer productivity

Sensitivity: Internal & Restricted

Web Layout Editor
 Is used to add, remove, and reorder applet Web template items
 Is invoked automatically upon completion of the List Applet wizard
 Can be invoked from the right-click menu
 Edit Web Layout Editor

Right-click to invoke
Edit Web Layout Editor

Sensitivity: Internal & Restricted

Web Layout Editor (Contd..)
 Use the Web Layout Editor to lay out the applet
 Placeholders correspond to item identifiers of Applet Web Template Items

Displays the layout of the

selected mode

Select and right-click

To add, drag and drop to delete columns
items from the
controls/columns window

Sensitivity: Internal & Restricted

List Column Definitions
 It specifies the displayed field. The display name that appears at the top of the list
column may reference a symbolic string

Sensitivity: Internal & Restricted

Symbolic Strings
It is the object type, having a centralized mechanism for storing and managing repository text
strings both in English and other languages
Are stored in the repository containing words and phrases used in UI definitions
 Global dictionary contains commonly used terms
 Symbolic String Locale object type allows language translation. Translatable text strings are defined
once and then referred to by multiple user interface objects.
 Are used by UI such as
 Labels
 List Columns
 Applet Title

Sensitivity: Internal & Restricted

Configuring Views
Consist of one or more applets
Reference a business object that defines the relationships between data in the view
Are associated with a Web template that defines their layout
View Templates are used to render siebel views
 Contains Place holders
 Contains multiple applet tags
 Applet in a view template can be
 Peers
 Parent-Child
 Parent- Child-Grandchild
 Configured in tools by using View Wizard

Sensitivity: Internal & Restricted

View Wizard

 New view can be created by using View Wizard

Select File -> New Object

Sensitivity: Internal & Restricted

Steps for Configuring Views

1. Create New View

Use View Wizard

2. Associate View template
with view object definition

3. Bind applets to view template

4. Configure thread bar

5. Register and assign views

Sensitivity: Internal & Restricted

Screen Definition

 Collection or group of related views

 The screen represents a logical grouping of views pertaining to one business function
 All the views in a screen usually map to a single business object
 Screens are accessed via the Screen Tabs or through Site Map (By Site
 Map icon or Navigate  Site Map)
 The Screen menu and Site Map provide access to a screens are
 defined as part of an Application object definition
 One or both may exist for a given screen
 Screens have bitmap and text properties that are used in the Viewbar area
 Screen definitions specify the default view that appears when a tab is clicked

Sensitivity: Internal & Restricted

Screen Definition [Contd..]

 Screens have a single child object type: Screen View and the list of Views related to that
screen are added in Screen View

Sensitivity: Internal & Restricted

Screen View Property

 Viewbar Text: Defines the text that appears in the UI

 Menu Text: Defines the text that appears in the Site Map
 Type: Defines how users navigate to views within the screen
 Aggregate Category
 May contain aggregate views, detail views, and detail categories
 Do not specify a view
 Aggregate View
 Appear in the link bar or visibility filter drop-down list
 May belong to an aggregate category
 Detail Category
 Appear in the view tab bar
 Belong to an aggregate category
 Group detailed views
 Detail View
 Appear in the view tab bar if the parent category does not specify a detailed category

Sensitivity: Internal & Restricted

Register And Assign View

 Views must be administered in the client application to make them available to users
 Register the view
 Assign the view to one or more responsibilities
 Navigate to Site Map > Administration – Application > Views in the client application
 Copy and paste view name from object definition in Tools to the view record

Sensitivity: Internal & Restricted

Register And Assign View (Contd..)
 Navigate to Site Map -> Administration – Application -> Responsibilities in the client application
 Assign the view to developers for unit testing
 Assign the view to users for system testing and production

Sensitivity: Internal & Restricted

Application Definition
 An Application is a collection of screens
 Defines which screens will be accessible through Screen tabs and Site map for an
Application
 It uses container page to display the Siebel Web page
 Specify the Application Level menu.
 Many applications are supported in a single Repository

Container
page

Sensitivity: Internal & Restricted

The Container Page
 Container page specifies the layout of the application

Application-
level menu

Toolbar

Screen tabs

Link bar

View

Sensitivity: Internal & Restricted

Navigation Between Views Using Drilldown

 Drilldowns allow users to click a hyperlink in a field so as to view more information about
that field through another view

 Drilldowns are used in the list applets

 Siebel supports two types of Drilldown:

 Static
 Clicking the hyperlink always navigates to the same target view
 Dynamic
 Clicking the hyperlink navigates to a target view determined by values shown in
the current view

74
Sensitivity: Internal & Restricted
Static Drilldown: Same Business Component
 Drill down to another view, keeping the business component (BC) context

Contact record in
Visible Contacts list
view

Same contact
record in Contact
detail view

75
Sensitivity: Internal & Restricted
Static Drilldown : Same Business Component
 Static drilldowns take the users to the same view under all the circumstances
 To create the new drilldown object, set the Hyperlink Field and View properties to enable static
drilldown

Specifies the BC
field for drilldown

Specifies the
target view

76
Sensitivity: Internal & Restricted
Static Drilldown Different Business Component
 Drill down to another view, changing the business component context

Account field of contact record in

Visible Contacts list view

Related account record

in Account Detail -
Contacts view

77
Sensitivity: Internal & Restricted
Configuring Drilldown to different business component

 Create a new drilldown object for the applet

 Set Hyperlink field and View properties as before
 Set Business Component, Source Field, and Destination Field properties to enable drilldown to a view
based on a different parent record

Specifies master BC
in target view

Foreign Key field in

record pointing to Primary Key field in
target BC the target BC
(default is Id)

78
Sensitivity: Internal & Restricted
Dynamic Drilldown
 Enables hyperlink navigation to multiple views from the same hyperlink field,
depending on the value of a field in the Applet’s current record

For business
Contacts, go to the
Contact Detail View

For Personal
Contacts, go to the
Personal Contact List
View
79
Sensitivity: Internal & Restricted
Matching Conditions
 Identify one or more matching conditions to trigger drilling down to a specific target view
 Used when BC has a field that indicates classification, for example:
 ‘Lead quality’ for an Opportunity
 ‘Primary Industry’ for an Account

 Siebel will check the value for this field in the current record and navigate to the
correct view based on the value
 Personal Contact = Y ====> Personal Contact Detail View
 Personal Contact = N ====> Contact Detail View

80
Sensitivity: Internal & Restricted
Configuring Dynamic Drilldown
Create the drilldown objects for each view
Create a dynamic drilldown destination definition for each condition

Field to Value to
check check for

81
Sensitivity: Internal & Restricted
Thread Bar
 It tracks previous business object and active record
 Provides hyperlinks to previous views
 Updates whenever the user navigates to different business object (View)

Thread bar

82
Sensitivity: Internal & Restricted
Thread Properties
 It specifies the text which appears in the thread bar

Hyperlink to prior active

record in the thread

Specifies the record in the

hyperlink

83
Sensitivity: Internal & Restricted
Business Component Properties
 Capture business logic
 Includes:
 Editing properties (Set the editing properties at the business component level to prevent
deleting, inserting, merging, and updating of records in all applets). The values can be
TRUE / FALSE
 No Delete
 No Insert
 No Merge
 No Update
 Owner Delete (Set the Owner Delete property to TRUE to enable only the owner of a
record to delete it)
 Search Specification
 Sort Specification

84
Sensitivity: Internal & Restricted
Search Specification Property

 Specifies records to be retrieved by the business component

 Typically used when there are multiple business components on the same main
table

85
Sensitivity: Internal & Restricted
 Search Specification Expressions

 Must contain name of one or more fields and various logical and/or comparison operators
 May contain functions
 Combined syntax creates a conditional expression
 This property exists in Business Component, Applet, Pick List, Link and Report Object.
 Avoid mutually-exclusive search specifications

86
Sensitivity: Internal & Restricted
Search Specification Expressions (Contd...)
 Use double-quotes to enclose strings rather than single quotes
 Single quotes may not be supported in a future release
 Enclose field names within brackets

87
Sensitivity: Internal & Restricted
Business Component Field Properties
Required
Set the Required property to TRUE to prevent user from leaving field blank
Read Only
Set the Read Only property to TRUE to prevent the user from editing the value
Validation
Create a Validation property to ensure that field data is valid.
Is expressed as a combination of logical operators, constants, field names, and predefined
functions
Can refer only to business component fields in the same record
Pre Default
Automatically assigns a value to a field for a new record
Post Default
Assigns a value to a field, if not entered by the user, before the record is inserted into the
database
Force Case
Defines the case for a field value
Valid values are:
 UPPER
 LOWER
 FIRSTUPPER

88
Sensitivity: Internal & Restricted
Calculated Field
 Derive their value from the values in other fields of the business component
 Cannot be stored in the database; therefore, there is no associated column
 Require setting the Calculated property to TRUE (shown as check mark)

Column property
is empty because
calculated fields are not
stored in the database

89
Sensitivity: Internal & Restricted
User Properties

 Are object definitions added as children to an applet, business component, control, field, or list
column
 Use to configure specialized behavior
 Beyond what is configured in the parent object definition's properties
 Add conditional logic to User Property record, instead of scripting
 Some Business Component User Properties are:
 BC Read Only Field
 Field Read Only Field
 On Field Update Set

90
Sensitivity: Internal & Restricted
Picklists
 Picklists allow users to populate one or more single value fields by selecting a value from a list
 The following are its advantages:
 enforces business rules and policies
 makes data entry faster
 reduces errors
 It can be either:
 Static
 Dynamic

91
Sensitivity: Internal & Restricted
Static Picklist
 Static Picklists draws values from the picklist data managed by the administrator
 The values of static picklist doesn’t change during runtime
 A Static “Picklist” provides for the popup display of a list of valid values for a user to select from.
 Can be bounded (must pick a single value from the list) or not bounded (can type in a single value
not in the list).
 Valid values are entered into the S_LST_OF_VAL table
 Can be entered interactively through administration screens or by using Enterprise Integration
Manager (EIM)

Example:

92
Sensitivity: Internal & Restricted
The S_LST_OF_VAL Table
Holds pick list values for all static pick lists
Must Exists in the application database
Has values entered through List Of Values Administration View or by batch Loading
Navigate to Site Map > Administration – Data > List of Values Explorer to administer static
picklist data
 Select an existing picklist or create a new picklist type in the List of Values - Types applet
 Expand the type and select the child Values folder
 Edit the picklist values in the List of Values (LOV) applet

Do not change names of

Siebel-supplied values
93
Sensitivity: Internal & Restricted
PickList Generic Business Component
 Is a Siebel-supplied business component that references the S_LST_OF_VAL table
 Static picklists are based on PickList Generic

94
Sensitivity: Internal & Restricted
Creating a Static PickList
Set Business Component property to
1. Create a New Static Pick List PickList generic
Set the Type Field property to “Type”
Set the Type Value property to match what
was entered in the S_LST_OF_VAL table
2. Add / Identify BC Field That Will Be Set the Bounded property to make the list
Populated restrictive or not

Specify which Pick List should be used to

3. Map the BC Field to the Pick List BC populate which business component field
Field in Contact
Add the Pick Map to define which field
from the PickList Generic BC will be
4. Specify Which Control or List Column copied back to which field on the Contact BC
Will Invoke the Pick List Applet
Set the Runtime property to “TRUE” for
the list column that should pop up the
pick list
> A drop down arrow will be the visual
* The PickList will appear empty until values clue for the user
are entered into the S_LST_OF_VAL table The Pick Applet property does not need
to be set

95
Sensitivity: Internal & Restricted
Dynamic PickList
 Draws values from a business component with records edited by users
 Values displayed in picklist change during run time
 Is used to update joined fields
 Copies foreign key reference to the selected value into destination field
 Reflects the current data in the database
Opportunity: originating
business component

Account: pick business component 96

Sensitivity: Internal & Restricted
Toggle Applet

 Toggling allows to configure several applets to share the same place in a view
 Applet toggle identifies one or more alternate applets to use in displaying the data of a business
component

 There are two types of Toggle Applet

 Static Toggle
 do not have to be based on the same business component
 Dynamic Toggle
 must be based on the same business component

 You cannot configure more than one applet toggle in a view.

 Applet toggles cannot be cached and therefore may have a negative affect on performance.
Each time a user navigates to an applet, all available applet toggles are loaded.

97
Sensitivity: Internal & Restricted
Configuring a Static Toggle in an Applet

 Allow users to toggle between applets by selecting the name of the applet from the show
drop-down list.

 An applet may be configured to toggle to a drilldown applet, replacing the originally

displayed applet

 Configured with one or more applet toggle child object definition of an applet object
definition
 The parent applet object definition specifies the first applet to appear in the view

98
Sensitivity: Internal & Restricted
Configuring a Dynamic Toggle in a Applet

 The applet object type has an applet toggle child object type

 One child applet toggle definition is specified for each applet you want to have appear when a
specific condition is met
 All applets must be based on the same business component

 The value contained in a designated BC field determines the applet which will appear

 If all test conditions fail for the applets specified in the applet toggle definitions, the parent
applet is displayed

99
Sensitivity: Internal & Restricted
Primary Foreign Key

 A Primary Foreign Key is a foreign key on the parent-side that points to one “primary” record
on the child -side of a one-to-many relationship
 A primary FK creates a one-to-one relationship between the parent and the child
 A primary FK allows the one initial query to join in one child record per MVG per parent
record and display it

S_ORG_EXT (Account) S_ADDR_ORG (Business Address)

ROW_ID NAME PR_ADDR_ID OU_ID ROW_ID ADDR
A IBM 3333 A 1111 100 Main Street
B Sun 2222 B 2222 55 Elm Drive
A 3333 2200 York Street
one- one-
to- to-
many one

100
Sensitivity: Internal & Restricted
Creating the Custom Extension Column

Make logical changes to the Data layer

 Check out the appropriate project
 Select table to be extended
 Create a new column record with the desired properties
 Name automatically prefixed with X_

101
Sensitivity: Internal & Restricted
Creating a New Table
Use the Table wizard to create a new table
 Select File > New Object > Table

102
Sensitivity: Internal & Restricted
Creating a Standalone table
Table wizard creates a standalone table with:
 Type of Data (Public)
 Seven required system columns
 P1 index on ROW_ID

103
Sensitivity: Internal & Restricted
Creating a 1:1 Extension Table
Select a base table
 Choice restricted to type Data (Public) by default it is Extension
 Multiple extension tables relate directly to base table, and not to each other
Table wizard creates an extension table with:
 Seven required system columns
 PAR_ROW_ID column as foreign key column to base table
 P1 index on ROW_ID
 U1 index on PAR_ROW_ID and CONFLICT_ID

S_PROD_INT CX_PROD_INT_X
ROW_ID

NAME

PART_NUM

UOM_CD

ROW_ID

NEW COLUMN

PAR_ROW_ID
104
Sensitivity: Internal & Restricted
Creating a 1:M Extension Table
Table wizard creates an 1:M extension table with:
 Seven required system columns
 PAR_ROW_ID column as foreign key column to base table
 TYPE and NAME columns
 Type of Data(Public)
 P1 index on ROW_ID
 U1 index on PAR_ROW_ID, TYPE, NAME, and CONFLICT_ID
 M1 index on TYPE and NAME

105
Sensitivity: Internal & Restricted
 Creating a intersection Table
Table wizard creates an intersection table with:
 Seven system columns
 Two foreign key columns as specified
 Type of Data(Intersection)
 P1 index on ROW_ID
 U1 index on two foreign key columns, TYPE, and CONFLICT_ID
 F1 index on foreign key to second parent table

106
Sensitivity: Internal & Restricted
 Apply Changes to Local database
Click Apply/DDL to make the physical database changes
 All database schema changes are made by Siebel Tools
 No separate SQL scripts need to be created or maintained
 Changes are preserved across Siebel application upgrades
Compile relevant projects
Test changes locally before checking projects into server
 Use vendor-supplied utility to query extended tables

107
Sensitivity: Internal & Restricted
Generate DDL
 DDL- SQL statements that can be used either interactively or within programming language
source code to define databases and their components

108
Sensitivity: Internal & Restricted
Thank You!

Sensitivity: Internal & Restricted