Lab Guide

Oracle Internal & Oracle Academy Use Only
Siebel 8.0 Essentials
Volume I • Activity Guide
D46318GC10
Edition 1.0
April 2007
D49912
®
Author Copyright © 2007, Oracle. All rights reserved.
Siebel Curriculum Disclaimer

Development Team
This document contains proprietary information and is protected by copyright and
other intellectual property laws. You may copy and print this document solely for your
Technical Contributors own use in an Oracle training course. The document may not be modified or altered in
any way. Except where your use constitutes "fair use" under copyright law, you may
and Reviewers not use, share, download, upload, copy, print, display, perform, reproduce, publish,
Siebel Review Team license, post, transmit, or distribute this document in whole or in part without the
express authorization of Oracle.
Publisher The information contained in this document is subject to change without notice. If you
find any problems in the document, please report them in writing to: Oracle University,
Joseph Fernandez 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using

the documentation on behalf of the United States Government, the following notice is
applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle

Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
Contents
Volume 1
Lab 0-1 Introduction................................................................................................................................1
Lab 2-1 Navigating the User Interface (UI) (Unguided)..........................................................................3
Solutions 2-1 Navigating the User Interface (UI) (Unguided).................................................................5
Lab 2-1 Navigating the User Interface (UI) (Guided)..............................................................................7
Solutions 2-1 Navigating the User Interface (UI) (Guided)...................................................................10
Lab 3-1 Querying Siebel Data (Unguided) ...........................................................................................11

Solutions 3-1 Querying Siebel Data (Unguided) ..................................................................................13
Lab 3-1 Querying Siebel Data (Guided) ...............................................................................................15
Solutions 3-1 Querying Siebel Data (Guided) ......................................................................................19
Lab 4-1 Exploring Responsibilities and Views (Unguided)...................................................................21
Solutions 4-1 Exploring Responsibilities and Views (Unguided)..........................................................23
Lab 4-1 Exploring Responsibilities and Views (Guided) ......................................................................25
Solutions 4-1 Exploring Responsibilities and Views (Guided)..............................................................29
Lab 5-1 Creating the Company Structure (Unguided)..........................................................................31
Lab 5-1 Creating the Company Structure (Guided)..............................................................................35
Solutions 5-1 Creating the Company Structure (Guided).....................................................................41
Lab 6-1 Exploring View Filters (Unguided)...........................................................................................43
Solutions 6-1 Exploring View Filters (Unguided) ..................................................................................46
Lab 6-1 Exploring View Filters (Guided)...............................................................................................49
Solutions 6-1 Exploring View Filters (Guided)......................................................................................52
Lab 6-2 Exploring Positions (Unguided)...............................................................................................55
Solutions 6-2 Exploring Positions (Unguided) ......................................................................................57
Lab 6-2 Exploring Positions (Guided)...................................................................................................59
Solutions 6-2 Exploring Positions (Guided)..........................................................................................61
Lab 7-1 Creating a Solutions Catalog (Unguided)................................................................................63
Lab 7-1 Creating a Solutions Catalog (Unguided)................................................................................67
Lab 7-1 Creating a Solutions Catalog (Guided) ...................................................................................69
Lab 7-1 Creating a Solutions Catalog (Guided) ...................................................................................74
Lab 8-1 Exploring the Siebel Web Architecture (Unguided).................................................................75
Lab 8-1 Exploring the Siebel Web Architecture (Guided) ....................................................................77
Solutions 8-1 Exploring the Siebel Web Architecture (Guided)............................................................81
Lab 9-1 Exploring Server Components and Parameters (Unguided)...................................................83
Lab 9-1 Exploring Server Components and Parameters (Guided) ......................................................85
Solutions 9-1 Exploring Server Components and Parameters (Guided)..............................................88
iii
Lab 9-2 Enabling and Assigning Component Groups (Unguided) .......................................................91
Solutions 9-2 Enabling and Assigning Component Groups (Unguided) ..............................................92
Lab 9-2 Enabling and Assigning Component Groups (Guided) ...........................................................93
Solutions 9-2 Enabling and Assigning Component Groups (Guided) ..................................................96
Lab 10-1 Exploring Server Management (Unguided)...........................................................................97
Lab 10-1 Exploring Server Management (Guided)...............................................................................99
Solutions 10-1 Exploring Server Management (Guided)....................................................................101
Lab 10-2 Using the Command-Line Server Manager (Unguided)......................................................103
Lab 10-2 Using the Command-Line Server Manager (Guided)..........................................................105
Solutions 10-2 Using the Command-Line Server Manager (Guided).................................................107
Lab 10-3 Invoking and Monitoring Jobs (Unguided)...........................................................................109

Lab 10-3 Invoking and Monitoring Jobs (Guided) ..............................................................................111
Solutions 10-3 Invoking and Monitoring Jobs (Guided)......................................................................113
Lab 11-1 Exploring Siebel Client Types (Unguided) ..........................................................................115
Lab 11-1 Exploring Siebel Client Types (Guided) ..............................................................................117
Solutions 11-1 Exploring Siebel Client Types (Guided) .....................................................................121
Lab 12-1 Securing Access to the Application (Unguided) ..................................................................123
Lab 12-1 Securing Access to the Application (Guided)......................................................................125
Solutions 12-1 Securing Access to the Application (Guided) .............................................................127
Lab 14-1 Exploring Relationships in the Application Architecture (Unguided) ...................................129
Solutions 14-1 Exploring Relationships in the Application Architecture (Unguided) ..........................132
Lab 14-1 Exploring Relationships in the Application Architecture (Guided).......................................135
Solutions 14-1 Exploring Relationships in the Application Architecture (Guided) ..............................139
Lab 15-1 Examining Object Definitions (Unguided) ...........................................................................143
Solutions 15-1 Examining Object Definitions (Unguided)...................................................................146
Lab 15-1 Examining Object Definitions (Guided) ...............................................................................147
Solutions 15-1 Examining Object Definitions (Guided) ......................................................................154
Lab 16-1 Exploring the Data Model (Unguided) .................................................................................155
Solutions 16-1 Exploring the Data Model (Unguided) ........................................................................162
Lab 16-1 Exploring the Data Model (Guided) .....................................................................................167
Solutions 16-1 Exploring the Data Model (Guided) ............................................................................177
Lab 17-1 Examining References Between Applets, Business Components,
and Tables (Unguided) ......................................................................................................................181
Solutions 17-1 Examining References Between Applets, Business Components,
and Tables (Unguided) ......................................................................................................................184
Lab 17-1 Examining References Between Applets, Business Components, and Tables (Guided)...187
Solutions 17-1 Examining References Between Applets, Business Components,
and Tables (Guided) ..........................................................................................................................190
Lab 18-1 Exploring Relationships Between Party Business Components and Tables (Unguided) ...193
iv
Lab 18-1 Exploring Relationships Between Party Business Components and Tables (Guided).......195
Solutions 18-1 Exploring Relationships Between Party Business Components
and Tables (Guided)..........................................................................................................................200
Lab 18-2 Identifying Objects When Using a Party Business Component (Unguided) .......................203
Solutions 18-2 Identifying Objects When Using a Party Business Component (Unguided) ..............205
Lab 18-2 Identifying Objects When Using a Party Business Component (Guided) ...........................207
Solutions 18-2 Identifying Objects When Using a Party Business Component (Guided) ..................209
Lab 19-1 Examining Relationships between Views, Business Objects,
Business Components, and Tables (Unguided)................................................................................211
Solutions 19-1 Examining Relationships between Views, Business Objects,
Business Components, and Tables (Unguided)................................................................................215
Lab 19-1 Examining Relationships between Views, Business Objects,

Business Components, and Tables (Guided)....................................................................................217
Solutions 19-1 Examining Relationships between Views, Business Objects,
Business Components, and Tables (Guided)....................................................................................223
Lab 21-1 Setting Up a Developer (Unguided) ....................................................................................227
Lab 21-1 Setting Up a Developer (Guided) ........................................................................................229
Lab 21-2 Extracting a Local Database (Unguided) ............................................................................233
Lab 21-2 Extracting a Local Database (Guided) ................................................................................235
Solutions 21-2 Extracting a Local Database (Guided) .......................................................................238
Lab 21-3 Populating the Local Developer Database (Unguided).......................................................239
Lab 21-3 Populating the Local Developer Database (Guided)...........................................................241
Lab 22-1 Exploring Projects (Unguided) ............................................................................................245
Solutions 22-1 Exploring Projects (Unguided)....................................................................................248
Lab 22-1 Exploring Projects (Guided) ................................................................................................249
Solutions 22-1 Exploring Projects (Guided) .......................................................................................255
Lab 23-1 Editing and Validating Object Definitions (Unguided) .........................................................259
Solutions 23-1 Editing and Validating Object Definitions (Unguided) ................................................260
Lab 23-1 Editing and Validating Object Definitions (Guided) .............................................................261
Solutions 23-1 Editing and Validating Object Definitions (Guided) ....................................................264
Lab 23-2 Exporting and Importing Object Definitions (Unguided)......................................................265
Solutions 23-2 Exporting and Importing Object Definitions (Unguided) .............................................266
Lab 23-2 Exporting and Importing Object Definitions (Guided)..........................................................267
Solutions 23-2 Exporting and Importing Object Definitions (Guided).................................................270
Lab 23-3 Creating a Custom Repository File (Unguided) ..................................................................273
Solutions 23-3 Creating a Custom Repository File (Unguided) .........................................................276
Lab 23-3 Creating a Custom Repository File (Guided) ......................................................................277
Solutions 23-3 Creating a Custom Repository File (Guided) .............................................................280
Lab 24-1 Exploring Template Files (Unguided)..................................................................................281
Lab 24-1 Exploring Template Files (Guided)......................................................................................283
v
Solutions 24-1 Exploring Template Files (Guided).............................................................................288
Lab 25-1 Modifying a Form Applet (Unguided) ..................................................................................291
Solutions 25-1 Modifying a Form Applet (Unguided)..........................................................................293
Lab 25-1 Modifying a Form Applet (Guided) ......................................................................................295
Solutions 25-1 Modifying a Form Applet (Guided) .............................................................................301
Lab 25-2 Creating a List Applet (Unguided) .......................................................................................303
Solutions 25-2 Creating a List Applet (Unguided) ..............................................................................305
Lab 25-2 Creating a List Applet (Guided) ...........................................................................................307
Solutions 25-2 Creating a List Applet (Guided) ..................................................................................311
Lab 26-1 Creating a View (Unguided) ................................................................................................313
Lab 26-1 Creating a View (Guided) ....................................................................................................317

Lab 27-1 Configuring Drilldowns (Unguided)......................................................................................325
Solutions 27-1 Configuring Drilldowns (Unguided).............................................................................328
Lab 27-1 Configuring Drilldowns (Guided) .........................................................................................329
Solutions 27-1 Configuring Drilldowns (Guided) ................................................................................335
Lab 28-1 Examine Existing Joins (Unguided).....................................................................................337
Solutions 28-1 Examine Existing Joins (Unguided)............................................................................340
Lab 28-1 Examine Existing Joins (Guided) ........................................................................................343
Solutions 28-1 Examine Existing Joins (Guided) ...............................................................................348
Lab 28-2 Adding a Joined Field to a Business Component (Unguided) ............................................351
Lab 28-2 Adding a Joined Field to a Business Component (Guided) ................................................355
Lab 29-1 Configuring Properties of Fields and Business Components (Unguided)...........................363
Solutions 29-1 Configuring Properties of Fields and Business Components (Unguided)..................365
Lab 29-1 Configuring Properties of Fields and Business Components (Guided)...............................367
Solutions 29-1 Configuring Properties of Fields and Business Components (Guided)......................371
Lab 30-1 Using the Standard 1:M Extension Table to Store Supply Plans (Unguided).....................373
Solutions 30-1 Using the Standard 1:M Extension Table to Store Supply Plans (Unguided) ............376
Lab 30-1 Using the Standard 1:M Extension Table to Store Supply Plans (Guided).........................379
Solutions 30-1 Using the Standard 1:M Extension Table to Store Supply Plans (Guided)................385
Lab 30-2 Creating a New List and View (Unguided) ..........................................................................387
Solutions 30-2 Creating a New List and View (Unguided) .................................................................390
Lab 30-2 Creating a New List and View (Guided) ..............................................................................391
Solutions 30-2 Creating a New List and View (Guided) .....................................................................396
vi
Volume 2
Lab 31-1 Creating a Static Picklist (Unguided).......................................................................................1
Solutions 31-1 Creating a Static Picklist (Unguided)..............................................................................4
Lab 31-1 Creating a Static Picklist (Guided) ..........................................................................................5
Solutions 31-1 Creating a Static Picklist (Guided)..................................................................................9
Lab 31-2 Creating a Dynamic Picklist (Unguided)................................................................................11
Solutions 31-2 Creating a Dynamic Picklist (Unguided).......................................................................14
Lab 31-2 Creating a Dynamic Picklist (Guided) ...................................................................................15
Solutions 31-2 Creating a Dynamic Picklist (Guided)...........................................................................20
Lab 32-1 Configuring a Multi-Value Field (Unguided) ..........................................................................23
Solutions 32-1 Configuring a Multi-Value Field (Unguided) .................................................................29

Lab 32-1 Configuring a Multi-Value Field (Guided) ..............................................................................31
Solutions 32-1 Configuring a Multi-Value Field (Guided) .....................................................................38
Lab 33-1 Adding Extension Columns (Unguided) ................................................................................41
Solutions 33-1 Adding Extension Columns (Unguided) .......................................................................43
Lab 33-1 Adding Extension Columns (Guided) ....................................................................................45
Solutions 33-1 Adding Extension Columns (Guided) ...........................................................................48
Lab 33-2 Adding New Fields (Unguided) .............................................................................................49
Lab 33-2 Adding New Fields (Guided) .................................................................................................51
Lab 33-3 Configuration Wrap-Up (Unguided).......................................................................................53
Lab 33-3 Configuration Wrap-Up (Guided) ..........................................................................................57
Lab 34-1 Examining a Business Service (Unguided) ...........................................................................61
Solutions 34-1 Examining a Business Service (Unguided) ..................................................................63
Lab 34-1 Examining a Business Service (Guided)...............................................................................65
Solutions 34-1 Examining a Business Service (Guided)......................................................................67
Lab 34-2 Testing a Business Service (Unguided) ................................................................................69
Solutions 34-2 Testing a Business Service (Unguided) .......................................................................71
Lab 34-2 Testing a Business Service (Guided)....................................................................................72
Solutions 34-2 Testing a Business Service (Guided) ...........................................................................74
Lab 35-1 Building a Siebel Workflow Process (Unguided)...................................................................75
Lab 35-1 Building a Siebel Workflow Process (Guided) ......................................................................79
Lab 35-2 Branching in a Siebel Workflow Process (Unguided) ...........................................................85
Lab 35-2 Branching in a Siebel Workflow Process (Guided) ...............................................................89
Lab 36-1 Testing a Siebel Workflow Process (Unguided)....................................................................93
Lab 36-1 Testing a Siebel Workflow Process (Guided) .......................................................................95
Lab 36-2 Testing Branching in a Siebel Workflow Process (Unguided) ..............................................99
Lab 36-2 Testing Branching in a Siebel Workflow Process (Guided) ................................................101
Solutions 36-2 Testing Branching in a Siebel Workflow Process (Guided) .......................................104
vii
Lab 37-1 Executing a Workflow Process using a Run-time Event (Unguided) ..................................105
Lab 37-1 Executing a Workflow Process using a Run-time Event (Guided) ......................................107
Lab 37-2 Executing a Workflow Process from a Control (Unguided).................................................111
Lab 37-2 Executing a Workflow Process from a Control (Guided).....................................................113
Lab 38-1 Creating a Workflow Policy (Unguided) ..............................................................................117
Lab 38-1 Creating a Workflow Policy (Guided) ..................................................................................119
Lab 38-2 Administering Server Components (Unguided)...................................................................121
Lab 38-2 Administering Server Components (Guided) ......................................................................123
Lab 38-3 Invoking a Workflow Process via Workflow Policy (Unguided) ...........................................127
Lab 38-3 Invoking a Workflow Process via Workflow Policy (Guided)...............................................129
Lab 39-1 Executing a UI Task (Unguided) .........................................................................................131

Lab 39-1 Executing a Task (Guided)..................................................................................................133
Lab 40-1 Creating a UI Task (Unguided)............................................................................................137
Lab 40-1 Creating a Task (Guided) ....................................................................................................143
Lab 40-2 Adding a Summary View (Unguided) ..................................................................................151
Lab 40-2 Adding a Summary View (Guided) ......................................................................................153
Lab 41-1 Adding Branching to a UI Task (Unguided).........................................................................157
Lab 41-1 Adding Branching to a Task (Guided) .................................................................................163
Lab 42-1 Examining Siebel Business Rules (Unguided)....................................................................173
Lab 42-1 Examining Siebel Business Rules (Guided)........................................................................175
Solutions 42-1 Examining Siebel Business Rules (Guided)...............................................................179
Lab 43-1 Creating Siebel Business Rules (Unguided) .......................................................................181
Lab 43-1 Creating Siebel Business Rules (Guided)...........................................................................189
Lab 45-1 Creating Assignment Rules for Sales Data (Unguided)......................................................197
Solutions 45-1 Creating Assignment Rules for Sales Data (Unguided) .............................................200
Lab 45-1 Creating Assignment Rules for Sales Data (Guided)..........................................................201
Solutions 45-1 Creating Assignment Rules for Sales Data (Guided).................................................205
Lab 45-2 Creating Assignment Rules for Service Data (Unguided)...................................................207
Solutions 45-2 Creating Assignment Rules for Service Data (Guided)..............................................211
Lab 45-2 Creating Assignment Rules for Service Data (Guided).......................................................213
Solutions 45-2 Creating Assignment Rules for Service Data (Guided)..............................................218
Lab 46-1 Prioritizing Assignment Rules (Unguided)...........................................................................219
Solutions 46-1 Prioritizing Assignment Rules (Unguided)..................................................................222
Lab 46-1 Prioritizing Assignment Rules (Guided) ..............................................................................223
Solutions 46-1 Prioritizing Assignment Rules (Guided)......................................................................226
Lab 46-2 Using Workload Distribution (Unguided) .............................................................................227
Lab 46-2 Using Workload Distribution (Guided) .................................................................................229
Lab 47-1 Invoking Assignment Manager in Dynamic Mode (Unguided) ............................................231
viii
Solutions 47-1 Invoking Assignment Manager in Dynamic Mode (Unguided) ...................................233
Lab 47-1 Invoking Assignment Manager in Dynamic Mode (Guided)................................................235
Solutions 47-1 Invoking Assignment Manager in Dynamic Mode (Guided).......................................238
Lab 48-1 Creating a Siebel State Model (Unguided) .........................................................................239
Solutions 48-1 Creating a Siebel State Model (Unguided).................................................................242
Lab 48-1 Creating a Siebel State Model (Guided) .............................................................................243
Solutions 48-1 Creating a Siebel State Model (Guided) ....................................................................247
Lab 50-1 Data Mapping: Solutions (Unguided) ..................................................................................249
Solutions 50-1 Data Mapping: Solutions (Unguided) .........................................................................253
Lab 50-1 Data Mapping: Solutions (Guided) ......................................................................................255
Solutions 50-1 Data Mapping: Solutions (Guided) .............................................................................260

Lab 50-2 Data Mapping: Products (Optional).....................................................................................263
Solutions 50-2 Data Mapping: Products (Optional) ............................................................................268
Lab 51-1 Loading EIM Tables with Legacy Data (Unguided).............................................................271
Lab 51-1 Loading EIM Tables with Legacy Data (Guided) ................................................................273
Solutions 51-1 Loading EIM Tables with Legacy Data (Guided)........................................................276
Lab 51-2 Running EIM to Import Solution Data (Unguided)...............................................................277
Solutions 51-2 Running EIM to Import Solution Data (Unguided)......................................................280
Lab 51-2 Running EIM to Import Solution Data (Guided) ..................................................................281
Solutions 51-2 Running EIM to Import Solution Data (Guided)..........................................................285
Lab 51-3 Running EIM to Load Product Data (Optional) ...................................................................287
Solutions 51-3 Running EIM to Load Product Data (Optional)...........................................................289
Lab 53-1 Exporting and Packaging Application Changes (Unguided) ...............................................291
Lab 53-1 Exporting and Packaging Application Changes (Guided) ...................................................293
Solutions 53-1 Exporting and Packaging Application Changes (Guided) ..........................................298
Lab 53-2 Configuring ADM (Unguided) ..............................................................................................299
Lab 53-2 Configuring ADM (Guided)..................................................................................................301
Lab 53-3 Deploying Application Changes (Unguided) .......................................................................305
Lab 53-3 Deploying Application Changes (Guided) ...........................................................................307
Solutions 53-3 Deploying Application Changes (Guided) ..................................................................309
ix
x
Module 0: Introduction
Lab 0-1 Introduction
Goals To describe the differences between Guided and Unguided labs in this lab guide
Time Less than 5 minutes
Guided and Unguided labs:

In this lab book you will find two versions of each lab: First an unguided version and then a guided

version. This introduction will help you decide which of the two lab versions is right for you.
Unguided labs provide as little information as possible while still allowing you to complete the labs.
They do not usually have step-by-step instructions, and instead provide the desired end result and a
few overall steps and parameters to help you achieve this result. A few questions are asked to help
guide you to a result, but typically you are left to work out how to accomplish your goal on your
own. In certain circumstances, such as in exploration labs or in labs where the end result is critical to
several future labs, there is no unguided lab; just an instruction to do the guided lab instead.
Use this format if:

- You want to figure out the details on your own.
- You want more of a challenge.
- You have some prior experience using and configuring Siebel applications.
Guided labs provide step-by-step instructions to achieve your goal, as well as additional content that
may be useful to you, plus questions designed to help you interpret your results. If you have
difficulty with an unguided lab, turn to the guided lab to see the steps required to perform an action.
The numbering in the guided labs does not match the numbering in the unguided labs, so it may take
a moment to orient yourself in the guided lab. If this is your first exposure to the Siebel Customer
Relationship Management (CRM) product, consider doing the guided labs throughout the course.
Use this format if:

- You want step-by-step instructions with additional context.
- You get stuck while doing the Unguided lab.
- You have little or no experience using and configuring Siebel applications.
Siebel 8.0 Essentials 1

Module 0: Introduction
2 Siebel 8.0 Essentials

Module 2: Using the Siebel Client
Lab 2-1 Navigating the User Interface (UI) (Unguided)
Goals To practice navigating in Siebel Call Center.
Time 10 – 15 minutes
Instructions:

In this lab you will practice simple navigation in the Siebel user interface (UI). You have been
provided with a new Siebel installation with a few records added to give you practice with UI
navigation. You will review information on screens frequently visited by an end user of Siebel Call
Center. These screens include Service Request, Accounts, and Contacts.
1. Start Siebel Call Center using the Siebel Web client and log in.
a. Open Internet Explorer and navigate to http://localhost/callcenter_enu.
b. In the login screen, enter these values:
User ID SADMIN
Password SADMIN
c. Click the Arrow button.
2. Examine service requests.

a. Locate service request SR#1-7010, drill down on the record, and answer the following
questions. If necessary, click the Show More button to see all the fields.
i. What is the Work Phone #?
ii. What is the service request Area?
iii. What is the service request’s Reproducible value?
iv. Who is the owner of the SR?
v. What is the Organization?
vi. What is the SR# of the next service request?
vii. What is the name of the person (first and last name) associated with this service
request?

3. Examine contacts.
a. Create a new Contact record with the following information:
Last Name Matthews
First Name Jane
Mr/Ms Ms.
Work Phone # 415-999-5555
Job Title Account Executive
b. Associate the contact with the Cambrian Ventures account.
4. Examine accounts and opportunities.

a. Locate the Cambrian Ventures account and drill down on the Cambrian Ventures

hyperlink.
b. How many opportunities exist for this account?
c. How many contacts are associated with the Eternal Storage 10 TB NAS opportunity?
5. Leave Siebel Call Center open for the next lab.

Solutions 2-1 Navigating the User Interface (UI)

(Unguided)
Answers:
2.a.i. What is the Work Phone #?
(250) 555-1234
2.a.ii. What is the service request Area?

Installation

2.a.iii. What is the service request’s Reproducible value?
Always
2.a.iv. Who is the owner of the SR?

SADMIN
2.a.v. What is the Organization?

Default Organization
2.a.vi. What is the SR# of the next service request?

1-7013
2.a.vii. What is the name of the person (first and last name) associated with this service request?
Jack Hutton
4.b. How many opportunities exist for this account?

2
4.c. How many contacts are associated with the Eternal Storage 10 TB NAS opportunity?
3


Lab 2-1 Navigating the User Interface (UI) (Guided)
Goals To practice navigating in Siebel Call Center.
Instructions:

In this lab you will practice simple navigation in the Siebel user interface (UI). You have been
provided with a new Siebel installation with a few records added to give you practice with UI
navigation. You will review information on screens frequently visited by an end user of Siebel Call
Center. These screens include Service Request, Accounts, and Contacts.
1. You will log in to Siebel Call Center.

a. Select Start > Programs > Internet Explorer.
b. Navigate to http://localhost/callcenter_enu. localhost is the hostname of the Web server,
and callcenter_enu is the application and language. (enu = American English.) The login
screen may take a minute or two to load the first time.
c. In the login screen, enter these values:
User ID SADMIN
Password SADMIN
d. Click the Arrow button.
e. Wait until the application home page has completely loaded before continuing on to the next
step. This will take several seconds.
2. You will examine a service request.

a. Click the Service screen tab.
b. Click the My Service Requests link on the Service Requests Homepage.
c. Click the link for SR# 1-7010.
3. Review the service request details. If necessary, click the Show More button in the upper-right
corner of the Service Request form to see all available fields.
a. What is the Work Phone #?
b. What is the service request Area?
c. What is the service request’s Reproducible value?
d. Who is the owner of the SR?
e. What is the Organization?

4. With SR# 1-7010 still selected, click the More Info view tab below the Service Request form to
navigate to the Service Request More Info View.
a. Click the Next arrow (to the right of the view tabs).
b. What is the SR# of the next service request?
c. What is the name of the person (first and last name) associated with this service request?
5. You will now examine Contacts.

a. Click the Contacts screen tab to navigate to the Contacts screen.
b. Click the Contacts List link in the link bar to display the list of SADMIN’s Contacts.
6. You will add a new contact and examine the behavior of the contact record as you associate it

with an account.
a. Click the New button in the Contacts list or form to enter new contact information.
b. Enter the following information for the new contact:
Last Name Matthews
First Name Jane
Mr/Ms Ms.
Work Phone # 415-999-5555
Job Title Account Executive
c. Now you will associate the contact with an account.
i. In the Account field, click the Select button (or use the F2 key on the keyboard).
ii. From the Accounts window, select the Cambrian Ventures account from the
Available records list on the left.
iii. Click the Add button to add the record to the Selected window on the right.
iv. Click OK.
d. How has the new contact record changed?
7. You will now examine Account records.

a. Click the Accounts screen tab to navigate to the Accounts screen.
b. Click All Accounts from the Frequently Viewed Accounts list.
c. Click the Account Name column header to sort the records in ascending order. You should
see an triangular indicator next to the column name:

8. You will review opportunities for the Cambrian Ventures account.

a. Locate the Cambrian Ventures account and select it by clicking the Cambrian Ventures
account name hyperlink.
b. Navigate to the related opportunities by clicking the Opportunities view tab below the
Account form.
c. How many opportunities exist for this account?
d. Drill down on the opportunity named Eternal Storage 10 TB NAS. What entities are
displayed in the view you navigated to?

e. Which view tab is selected below the Opportunity form?
f. How many contacts are associated with this opportunity?
g. Drill down on the last name Wagoner. What entities are displayed in the view you navigated
to?
h. What information is now visible in the thread bar?
9. Leave Siebel Call Center open for the next lab.

Solutions 2-1 Navigating the User Interface (UI) (Guided)
Answers:
3.a. What is the Work Phone #?
(250) 555-1234
3.b. What is the service request Area?

Installation
3.c What is the service request’s Reproducible value?

Always
3.d. Who is the owner of the SR?

SADMIN
3.e What is the Organization?

Default Organization
4.b. What is the SR# of the next service request?

1-7013
4.c. What is the name of the person (first and last name) associated with this service request?
Jack Hutton
6.d. How has the new contact record changed?

The account name and address fields are automatically populated.
8.c. How many opportunities exist for this account?

2
8.d. Drill down on the opportunity named Eternal Storage 10 TB NAS. What entities are
displayed in the view you navigated to?
The contacts associated with the Eternal Storage 10 TB NAS opportunity
8.e. Which view tab is selected below the Opportunity form?

Contacts
8.f. How many contacts are associated with this opportunity?

3
8.g. Drill down on the last name Wagoner. What entities are displayed in the view you
navigated to?
Contacts and Activities
8.h. What information is now visible in the thread bar?

Account: Cambrian Ventures > Opportunity: Eternal Storage 10 TB NAS > Contact:

Module 3: Working with Siebel Data
Lab 3-1 Querying Siebel Data (Unguided)
Goals To practice querying for data.
Instructions:

In this lab you will create and execute queries and sort the results. Because the classroom application
has very little customer data (Accounts, Opportunities, and so on), you will explore Call Center’s
administrative seed data, which was created during product installation. Several administrative
screens offer large data sets that offer good practice for querying.
1. If necessary, start the Siebel Call Center Web Client and log in as SADMIN/SADMIN.
2. Navigate to the Administration - Data > Zip Code Administration screen.

Note: Zip Code refers to a U.S. postal code.
a. What city has a zip code of 90210?
b. How many ZIP codes are there for Los Angeles, California? The state code for California is
CA. To get a record count, right-click anywhere in the applet and select Record Count.
c. Execute an empty query to refresh the Zip Code list.

d. What city has the northernmost ZIP code (that is, the highest latitude)?
e. Execute a query to return ZIP codes with latitude greater than 49, excluding records with a
state of Alaska (AK).
Note: The western extent of the Canada – U.S. border runs along the 49th parallel of North
latitude.
f. How many ZIP codes outside of Alaska have latitude greater than 49 degrees?
g. Execute a query to locate ZIP codes between 87900 and 87999 using wildcards. How many
valid ZIP codes are in this range?
h. Some ZIP code records were created with zero or null longitude and latitude. Run a query for
these records.

i. How many records are there without geographic coordinates or with coordinates of 0?
3. Get experience querying on multi-value group (MVG) fields. You will execute queries on iHelp
items, a Siebel object used help users with common application tasks.
a. Navigate to Administration - iHelp > All iHelp Items.
Note: Administration - iHelp appears at the end of the list of administration screens because
the sorting is case-sensitive.
b. Use the EXISTS operator to query for iHelp items that contain the word Sales in the
Applications field. What iHelp items are available for sales-like applications?

c. Verify your result by opening the MVG applet for the Applications field of the Create an
iHelp Item record and querying for application names containing the word Sales.
4. Use the query assistant to generate a query and then save that query.
a. Navigate to Administration - Application > Views. This view lists all Siebel application
views.
b. Use the Query Assistant to create the following query: View Name Contains Asset:
c. Save the query as Asset Views. This is a private query – it is only available to you. However,
an administrator can make it available to other users as a predefined query.

Solutions 3-1 Querying Siebel Data (Unguided)
Answers:
2.a. What city has a zip code of 90210?
Beverly Hills
2.a. How many ZIP codes are there for Los Angeles, California? The state code for California
is CA. To get a record count, right-click anywhere in the applet and select Record Count.
99

2.d. What city has the northernmost ZIP code (that is, the highest latitude)?
Barrow, AK (Alaska) at 71.29N latitude
2.f. How many ZIP codes outside of Alaska have latitude greater than 49 degrees?
3
(Note: one of the results, for Eastport, Idaho, appears to have latitude equal to 49, but this
is a result of rounding the result for display in the user interface. The underlying value for
Eastport is 49.0005 degrees, which can be queried directly from the underlying database
table S_ZIPCODE.)
2.g. Execute a query to locate ZIP codes between 87900 and 87999 using wildcards. How many
valid ZIP codes are in this range?
12
2.i. How many records are there without geographic coordinates or with coordinates of 0?
972
3.b. Use the EXISTS operator to query for iHelp items that contain the word Sales in the
Applications field. What iHelp items are available for sales-like applications?
Create an iHelp Item


Lab 3-1 Querying Siebel Data (Guided)
Goals To practice querying for data.
Instructions:

In this lab you will create and execute queries and sort the results. Because the classroom application
has very little customer data (Accounts, Opportunities, and so on), you will explore Call Center’s
administrative seed data, which was created during product installation. Several administrative
screens offer large data sets that offer good practice for querying.
1. If necessary, start Siebel Call Center and log in as SADMIN/SADMIN.

a. Start Internet Explorer.
b. Enter the URL: http://localhost/callcenter_enu. You may want to bookmark this URL.
c. In the login screen, enter these values:
User ID SADMIN
Password SADMIN
d. Click the arrow.
e. Wait until the application has completely loaded before continuing on to the next step.
2. Navigate to the Zip Code Administration screen and query for selected records.
Note: Zip Code refers to a U.S. postal code.
a. Click on the Site Map button on the global toolbar.
b. Click Administration - Data.
c. Scroll down and click Zip Code Administration.
Note: In future labs, these steps will be abbreviated as: Administration – Data > Zip Code
Administration. This notation uses ‘>’ to separate parts of a hierarchical path to be followed
using the Site Map.
d. Select New Query from the applet-level menu (or use the keyboard shortcut ALT+Q).
e. In the ZIP Code field, type 90210.
f. Click the Menu button and select Run Query (or use ALT+ENTER).
g. What value appears in the city column?

h. Query again, this time on two fields: City Los Angeles and State CA. This query will return
records with City = Los Angeles and State = California; that is, a logical AND. How many
ZIP codes are there for Los Angeles? Click the Menu button and select Record Count, or use
CTRL+Shift+3, to find the answer.
3. Create and execute complex queries using the Zip Code seed data.
a. Execute an empty query to refresh the Zip Code list. This is a common technique used to
refresh a list applet so that it lists all visible records.
i. Click Query.
ii. Without entering any query, click Go.
b. Sort the list by latitude in descending order by clicking the Latitude column header until a

down arrow is displayed.
c. What city has the northernmost ZIP code (that is, the highest latitude)?
d. The western extent of the Canada – U.S. border runs along the 49th parallel of North latitude.
Execute a query to return ZIP codes with latitude greater than 49:
i. Click Query.
ii. Type >49 in the Latitude field.
iii. Click Go.
e. Refine your query to exclude records with state equal to Alaska (AK):
i. Select Menu > Refine Query. (Alt+R) Notice that your criterion for latitude appears
in the query form.
ii. Type <>AK in the State field. This will match records where the State is not Alaska.
iii. Execute the query.
iv. How many ZIP codes outside of Alaska have latitude greater than 49 degrees?
f. Execute a query to locate ZIP codes between 87900 and 87999 using wildcards:
i. Execute an empty query to refresh the Zip Code list.
ii. Click Query.
iii. Enter a Zip Code of 879?? and click Go. This query will match 5 digit numbers
starting with 879.
iv. How many valid ZIP codes are in this range?
g. Some ZIP code records were created with blank or null longitude and latitude. Run a query
for these records:
i. Create a new query.
ii. Type IS NULL OR 0 in the Latitude field. This will identify records without an
assigned latitude or with zero latitude. The latter category will catch records where
both the longitude and latitude have been set to zero.

iv. How many records are there without geographic coordinates?
4. Get experience querying on multi-value group (MVG) fields. You will execute queries on iHelp
items, a Siebel object used help users with common application tasks.
a. Use the site map to navigate to Administration - iHelp > All iHelp Items.
b. Examine the Applications field in the lower form applet. What kind of field is it?
c. What query operator can you use to search in this field?

d. Create a query and type EXISTS(“*Sales*”) in the Applications field. This query will match
iHelp items that have at least one value in the Applications MVG that includes the substring
“Sales”. The asterisks are wild cards for any length substring.
e. Execute the query. What iHelp items are available for sales-like applications?
f. If necessary, select the Create an iHelp Item from the list of results by clicking to the left of
the record.
g. Click the MVG select icon in the Applications field. This brings up an MVG applet.
h. Query in this applet for Application *Sales*.
i. Which applications are returned from this last query?
j. Click OK to close the MVG applet.
5. You will navigate to the Views screen and query for application views related to Assets.
a. Navigate to Administration - Application > Views. This view lists all Siebel application
views.
b. Click the Query button.
c. Click the Query Assistant button. This tool simplifies query construction,
and is suitable for less technical users.

d. Execute the following query: View Name Contains Asset:

i. Click the top left-hand dropdown and select View Name.
ii. Click the top center dropdown and select Contains.
iii. Type Asset into the top right-hand text box. The Query Assistant should be identical
to the picture on the next page. Notice that the text box below the dropdown lists
displays a description of the query.
iv. Click Go.

e. How many view records are returned by this query?
6. Save the query you just created so you can use it later.
a. Select Query > Save Query As from the application menu.
b. In the Query Name field, enter Asset Views.
c. Click OK.
d. Notice the query now appears in the Queries drop-down list (in alphabetical order, even
though only one appears for this view) and can be executed by selecting it from the list:
This is a private query – it is only available to you. However, an administrator can make it
available to other users as a predefined query.

Solutions 3-1 Querying Siebel Data (Guided)
Answers:
2.g. What value appears in the city column?
Beverly Hills
2.h. Query again, this time on two fields: City Los Angeles and State CA. This query will
return records with City = Los Angeles and State = California; that is, a logical AND. How
many ZIP codes are there for Los Angeles? Click the Menu button and select Record
Count, or use CTRL+Shift+3, to find the answer.

99
3.c. What city has the northernmost ZIP code (that is, the highest latitude)?
Barrow, AK (Alaska) at 71.29N latitude
3.e.iv. How many ZIP codes outside of Alaska have latitude greater than 49 degrees?
3
(Note: one of the results, for Eastport, Idaho, appears to have latitude equal to 49, but this
is a result of rounding the result for display in the user interface. The underlying value for
Eastport is 49.0005 degrees, which can be queried directly from the underlying database
table S_ZIPCODE.)
3.f.iv. How many zip codes are in this range?

12
3.g.iv. How many records are there without geographic coordinates?

972
4.b. Examine the Applications field in the lower form applet. What kind of field is it?
An MVG field – the icon for an MVG differs from the icon for a dynamic picklist
4.c. What query operator can you use to search this field?
EXISTS( )
4.e. What iHelp items are available for sales-like applications?

Create an iHelp Item
4.i. What applications are returned from this last query?

Siebel Sales Enterprise and Siebel eSales
5. How many view records are returned by this query?

132


Module 4: Responsibilities and Views
Lab 4-1 Exploring Responsibilities and Views

(Unguided)
Goals To explore the relationship between responsibilities and views in the application
To examine the seed responsibilities available in the application
To create and customize a new responsibility
Time 20 - 25 minutes

Instructions:
In this lab, you will explore responsibilities and views first by modifying a user’s responsibilities to
observe which views are available to them, then by creating a new responsibility and observing the
results.
1. Use the Administration - Application > Responsibilities view to explore the seed responsibilities.
In particular, examine the Call Center Representative - SMC responsibility and determine which
users have this responsibility and which views are associated with this responsibility.
a. Which users have the Call Center Representative - SMC responsibility?
b. Query for view names containing the string “Admin”. How many administrative views are
associated with this responsibility?
2. Use a second browser to log in as NBOHR/NBOHR and confirm that he only sees the views
associated with his responsibility.
a. What do you see when you first log in?
b. Does the Home Page View (WCC) appear in the list of views for the Call Center
Representative – SMC Responsibility? Is this what you expected to see?
c. Use File > Log out and close this browser when you are done.
3. Use the Administration - Application > Views view to confirm that the view you found above is
shared by multiple responsibilities. You have now confirmed that one responsibility contains
multiple views, while one view can be associated with multiple responsibilities.
4. Use the Administration - Application > Responsibilities view to locate the Call Center
Representative - SMC responsibility and delete NBOHR as a user for it. You must clear the

responsibility cache for these changes to be immediately visible. Then open a new browser, log
in as NBOHR, and confirm that he does not have access to any screens or views. When you are
done, log out and close the browser.
5. Create a new responsibility named Call Center Representative - Modified by duplicating the
Call Center Representative - SMC responsibility and adding the Home Page View (WCC). Add
NBOHR to this responsibility. Consider making one or more of the views in this responsibility
read-only, or modifying the tabs displayed for this responsibility. You must clear the
responsibility cache for these changes to be immediately visible. Once you are done, log in as
NBOHR, and confirm your changes. Also examine the site map to get a rough idea as to how
many views NBOHR has access to.
6. Add the Call Center Manager responsibility to NBOHR and confirm that he sees the union of
views for the two responsibilities. Do not forget to clear the responsibility cache before logging

back in as NBOHR. Note that the responsibility shown in the administrative applets is his
primary responsibility, but he sees the views from both. Examine the site map and confirm that
NBOHR has access to more views than before.

Solutions 4-1 Exploring Responsibilities and Views

(Unguided)
Answers
1.a. Which users have the Call Center Representative - SMC responsibility?
The Siebel Administrator and Norman Bohr.
1.b. Query for view names containing the string “Admin”. How many administrative views are
associated with this responsibility?

None.
2.a. What do you see when you first log in?

You see an error message that the responsibility of the user does not allow accessing the
Home Page view.
2.b. Does the Home Page View (WCC) appear in the list of views for the Call Center
Representative – SMC Responsibility? Is this what you expected to see?
No; the Home Page view does not appear in the list of views for this responsibility. This is
what you should expect to see when you receive that error message.


Lab 4-1 Exploring Responsibilities and Views (Guided)
Goals To explore the relationship between responsibilities and views in the application
To examine the seed responsibilities available in the application
To create and customize a new responsibility
Instructions:

In this lab, you will explore responsibilities and views first by modifying a user’s responsibilities to
observe which views are available to them, then by creating a new responsibility and observing the
results.
1. If necessary, start the Siebel Call Center Web client and log in as SADMIN/SADMIN.
2. You will first examine the views associated with a responsibility. A responsibility is a set of
views usually corresponding to a specific job function.
a. Navigate to Administration - Application > Responsibilities. The responsibilities shown are
the seed responsibilities for the application. These responsibilities cannot be edited or
deleted. You will learn how to create your own custom responsibilities later in this lab.
b. Query for the Call Center Representative - SMC responsibility. Notice that more than one
view is associated with this responsibility. Which users have this responsibility?
c. In the Views applet, query for view names containing the string “Admin”. Note that no
administrative views are associated with this responsibility.
3. You will next confirm that a user with that responsibility sees only those views.
a. Open a second browser, start the Siebel Call Center Web client, and log in as
NBOHR/NBOHR. Using a second browser will allow you to switch back and forth between
the administrative and user logins without having to log in to and out of the application too
frequently.
b. What do you see when you first log in?
c. Switch back to the Call Center application where you are logged in as SADMIN and query
for Home Page in the view name. Does the Home Page view appear in the list of views for
the Call Center Representative - SMC responsibility? Is this what you expected to see?

4. You will now confirm that a single view may be shared by multiple responsibilities.
a. While still logged in as SADMIN, click the Home tab to return to the home page.
b. Select Help > About View. What is the name of the home page view for Siebel Call Center?
c. Click OK to close the About View window.

d. Navigate to Administration - Application > Views.
e. Query for Home Page. Does the view you found above appear in the list of home page
views?
f. Select the view you found above and confirm that it is included in multiple responsibilities.

You have confirmed that a single responsibility contains multiple views, and that a single
view may be contained in multiple responsibilities.
5. You will next remove Norman Bohr from the list of users with the Call Center Representative -
SMC responsibility. It is unlikely that an administrator would intentionally remove all
responsibilities from a user, but it is quite possible that an administrator might accidentally
remove the user from all responsibilities in the manner shown here.
a. Return to the Siebel Call Center application where you are logged in as NBOHR.
b. Navigate to the Site Map and confirm that NBOHR has access to several views in the
application.
c. Log out of the Siebel Call Center application.
d. Return to the Siebel Call Center application where you are logged in as SADMIN.
e. Navigate to Administration – Application > Responsibilities.
f. Query for the Call Center Representative - SMC responsibility.
g. In the Users applet, select the NBOHR record and click the Delete button.
h. Click OK to confirm the deletion.
i. Click the Clear Cache button near the top of the screen. The responsibilities are cached to
enhance application performance, so it is necessary to clear the cache or restart the server for
the new settings to take effect.
j. Log in to the Siebel Call Center application as NBOHR/NBOHR. What do you notice?
k. Navigate to the Site Map and confirm that NBOHR does not have access to any screens or
views.
l. Log out as NBOHR.
6. You will now create a new responsibility and assign NBOHR to it. A common method of doing
this is to find an existing seed responsibility that closely matches the responsibility you desire,
duplicate it, and modify the new responsibility to have exactly the views you require.
a. Return to the Siebel Call Center application where you are logged in as SADMIN.
b. Select the Call Center Representative - SMC responsibility. Notice that the Delete button is
disabled in the Responsibility pane, and the Add and Delete buttons are disabled in the Views
pane. This shows that this is an application seed responsibility, and cannot be modified.

c. Right-click Call Center Representative - SMC and select Copy Record. A new
responsibility is created containing the same views as Call Center Representative - SMC.
d. Enter Call Center Representative - Modified as the Responsibility name.
e. Enter Custom responsibility as the Description.
f. Click Add in the Views pane. A list of available views is shown.
g. Query for “Home Page View (WCC)”. Note that you cannot query for the full name without
using quotes, as parentheses are illegal search characters.
h. Click OK to add the view. Confirm that the view now appears in the list of views for the
responsibility. When you give this responsibility to NBOHR, he will no longer see the
inaccessible view error message when he logs in.
i. Locate the Service Contact Detail View and mark it as a Read Only view by checking the
checkbox.

j. Click Add in the Users pane. A list of available users is shown.
k. Select Norman Bohr and click OK. He is added as a user to the responsibility.
l. Click the Tab Layout tab. This allows you to customize which screen and view tabs are
available in each application for each responsibility when the user initially logs in. Once the
user has logged in, they can change their personal tab layout to suit their preferences.
m. Query for an application name of Siebel Universal Agent. This is the name of the Siebel
Call Center application. What screen tabs are shown in what order for this application and
this responsibility?
n. Click Clear Cache near the top of the screen.

o. Log in to the Siebel Call Center application as NBOHR/NBOHR. Confirm that you now
have access to the Home Page View (WCC). Notice that not all of the screen tabs you found
above are shown. Why might this be?
Hint: Does NBOHR have access to any of the views under the missing screen tabs?
p. Navigate to Contacts > Contact List.

q. Confirm that you cannot create a new record. This is because you marked this view as Read
Only.
r. Log out as NBOHR.
7. You will finally add a second responsibility to NBOHR, label the Call Center Representative -
Modified responsibility as the primary responsibility, and confirm that NBOHR still sees all of
the views available to either responsibility.
a. Return to the Siebel Call Center application where you are logged in as SADMIN.
b. Navigate to Administration – User > Users. This is the user administration screen, and allows
you to directly edit the responsibilities assigned to a user.
c. Select Norman Bohr. His details are shown in the lower applet.

d. Click the Select icon next to the Responsibility field. Be careful not to select the New
Responsibility field.
e. Query for the Call Center Manager responsibility.
f. Click Add to add it to NBOHR’s responsibilities.
g. Verify that the Primary checkbox next to Call Center Representative - Modified is checked
to mark it as the primary responsibility for NBOHR. This ensures the initial tab layout
NBOHR will see when logging in is the one associated with the modified responsibility.
h. Click OK.
i. Navigate to the Administration - Application > Responsibilities screen.
j. Click the Clear Cache button to clear the Responsibilities cache.
k. Log in to the Siebel Call Center application as NBOHR. Notice the additional tabs; the
Quotes and Sales Orders tabs are now visible because NBOHR has access to views on those

screens.
l. Navigate to Contacts > Contact List and note that the New button is now enabled. Although
NBOHR’s primary responsibility of Call Center Representative - Modified lists this view as
Read Only, his secondary responsibility of Call Center Manager has the same view with
read/write permission. The union of the two responsibilities gives NBOHR the more
permissive permission; that is, he has write access because at least one of his responsibilities
has write access. You can confirm this by returning to the Siebel Call Center application
where you are logged in as SADMIN and examining the Call Center Manager responsibility
to confirm that it contains the Service Contact Detail View with the Read Only flag
unchecked.
8. Log out of the Siebel Call Center application where you are logged in as NBOHR and close the
browser.

Solutions 4-1 Exploring Responsibilities and Views

(Guided)
Answers
2.b. Query for the Call Center Representative - SMC responsibility. Notice that more than
one view is associated with this responsibility. Which users have this responsibility?
The Siebel Administrator and Norman Bohr.
3.b. What do you see when you first log in?

You see an error message that the responsibility of the user does not allow accessing the
Home Page view.
3.c. Switch back to the Call Center application where you are logged in as SADMIN and query
for Home Page in the view name. Does the Home Page view appear in the list of views for
the Call Center Representative - SMC responsibility? Is this what you expected to see?
No; the Home Page view does not appear in the list of views for this responsibility. This is
what you should expect to see when you receive that error message.
4.b. Select Help > About View. What is the name of the home page view for Siebel Call
Center?
Home Page View (WCC).
4.e. Query for Home Page. Does the view you found above appear in the list of home page
views?
Yes.
5.j. Log in to the Siebel Call Center application as NBOHR/NBOHR. What do you notice?
There are no longer any tabs visible at the top of the screen.
6.m. Query for an application name of Siebel Universal Agent. This is the name of the Siebel
Call Center application. What screen tabs are shown in what order for this application and
this responsibility?
Home, Accounts, Contacts, Opportunities, Quotes, Sales Orders, and Service. The rest are
marked as hidden.
6.o. Log in to the Siebel Call Center application as NBOHR/NBOHR. Confirm that you now
have access to the Home Page View (WCC). Notice that not all of the screen tabs you found
above are shown. Why might this be?
Screen tabs only appear if the user’s responsibilities contain at least one view associated
with that screen. Since NBOHR’s responsibility does not include any Quotes or Sales Orders
views, those screen tabs do not appear.


Module 5: Users, Positions, and Organizations
Lab 5-1 Creating the Company Structure

(Unguided)
Goals To implement a division hierarchy including divisions, organizations, positions, and

users
Instructions:

In this lab you will extend an existing division hierarchy. You will implement the company structure
for a fictitious ABC Company, allowing you to explore Access Control in greater detail in later labs.
Because a richer company structure provides better examples of Access Control, some of the
structure has already been created for you in the database. You will implement the following
company structure:
Default Organization (Organization) Already exists as seed data

ABC Company (Division)
CEO (Position): Mark Planck
ABC Western Region (Organization)

VP of Sales - West (Position): Mary West
ABC Northwestern Region (Division)

Sales Rep NW1 (Position): Maxwell Westerly
ABC Southwestern Region (Division)

Sales Rep SW1 (Position): Raj Westerman
ABC Eastern Region (Organization)

ABC VP of Sales - East (Position): Natasha East
ABC Northeastern Region (Division)

ABC Sales Rep NE1 (Position): Catherine Eastman
ABC Southeastern Region (Division)

ABC Sales Rep SE1 (Position): Charles Eastwood
1. Use the Administration - Group > Internal Divisions view to extend the division structure of
ABC Company. The final hierarchy should appear as follows:

Default Organization LEGEND

Division
ABC Company Organization
ABC Western ABC Eastern

Region Region

ABC ABC ABC ABC
Northwestern Southwestern Northeastern Southeastern
Region Region Region Region
2. Use the Administration - Group > Positions view to create positions for the ABC Company.
Unlike responsibilities, the Siebel application comes with only four seed positions, and you must
create the rest to match your company’s structure. Also unlike responsibilities or divisions,
positions, including seed positions, can be deleted. When creating positions, consider:
- Although positions and employees are in a M:M relationship, most positions should contain
only one employee unless their job is completely interchangeable with another. A customer
might not mind working with three different call center representatives on a single problem, but
how would a customer feel about working with three different sales representatives? This is a
question only your company can answer, and it determines whether the three sales
representatives have three different positions, or all share one position.
- Also, data visibility is affected by position, hence unless those three sales representatives
should see the same accounts, they should have different positions.
- Positions do not have to report to parent positions within their organization. For example, if a
sales representative moved from the Western Region to the Eastern region, that sales
representative might still want to report to VP of the Western Region, outside of the sales rep’s
organization.
The final position hierarchy should look as follows. Note that the positions for the Western
organization are not prefixed with “ABC”. This is to help you easily distinguish the positions

you created from those pre-populated for this and other labs in the course:

3. Use the Administration - User > Employees view to create the eastern region employees and
assign positions to them. Use their first initial and last name as their User ID (for example,
NEAST or CEASTWOOD), and leave their responsibilities as Siebel Administrator. Your final
assignments should be as follows:









Lab 5-1 Creating the Company Structure (Guided)
Goals To implement a division hierarchy including divisions, organizations, positions, and

users
Instructions:

In this lab you will explore and extend an existing division hierarchy. You will implement the
company structure for a fictitious ABC Company, allowing you to explore Access Control in greater
detail in later labs. Because a richer company structure provides better examples of Access Control,
some of the structure has already been created for you in the database. You will implement the
following company structure:







1. You will first explore and extend the division structure of ABC Company. The final hierarchy
should appear as follows:

Default Organization LEGEND

Division
ABC Company Organization
ABC Western ABC Eastern

Region Region

ABC ABC ABC ABC
Northwestern Southwestern Northeastern Southeastern
Region Region Region Region
a. If necessary, start Siebel Call Center and log in as SADMIN/SADMIN.

b. Navigate to Administration - Group > Internal Divisions. This view shows all of the existing
organizations and divisions. Those starting with ABC are the pre-populated ABC entries for
this training. Those without an ABC are the seed entities that are created when the Siebel
application is installed. There are three seed entities. What are they?
c. Click Organizations in the link bar near the top of the screen. This view shows only the
organizations. Which of the divisions you found above is an organization?
d. Click Internal Divisions to return to the Internal Divisions view. Because you can enter both
divisions and organizations in this view and it allows you to view the entire company
hierarchy, it is more common to add divisions and organizations from this view.
e. In the Tree applet, click the + sign for Default Organization to expand its hierarchy. The
child divisions of Default Organization are shown. Notice that the explorer tree shows each
division at the top level of the hierarchy for ease of navigation and also shows it within the
correct hierarchy. What are the child divisions of Default Organization?
f. In the Tree applet, expand the ABC Company hierarchy. Notice that the ABC Western
Region has already been entered. Expand the ABC Western Region and confirm that the
ABC Northwestern Region and ABC Southwestern Region have already been entered.

g. Select ABC Western Region in the explorer tree. In the bottom applet, notice that the Parent
Division is now listed as ABC Company. When you create new divisions with ABC Western
Region selected, they will automatically have the same parent. You can also override this, as
you will do below.
h. Click New in the top applet to create a new division.
i. Enter ABC Eastern Region as the division name. Notice that Currency is a required field
that has already been filled in for you in the form applet as the default currency for the
application. Note that divisions may also optionally have addresses and types assigned to
them.
j. Check the Organization Flag. Be very careful when checking this flag; once the record is
saved and the division is marked as an organization, it cannot be undone.
k. Step off the record to save it.
l. Create the ABC Northeastern Region as follows:

i. Click New to create a new division.
ii. Enter ABC Northeastern Region as the division name.
iii. Click the Select button next to Parent Division in the form applet. All of the available
parent divisions are shown.
iv. Select ABC Eastern Region as the parent division and click OK. Notice that the
required Organization Name field is now populated. The organization is the organization
to which the parent division belongs.
v. Ensure that the Organization Flag is not checked.
Note: If you accidentally label one of the divisions an organization, you will need to
rename it and try again, as you cannot delete a division or undo making a division an
organization.
vi. Step off the record to save it.
m. Follow similar steps to create the ABC Southeastern Region division.
n. Refresh the Explorer view by clicking the – sign next to the Divisions folder. Now expand it
by clicking the + sign. You will see the seven ABC Company divisions. Expand ABC
Company to see the division hierarchy. Continue this process to fully expand the ABC
Company division hierarchy. Make sure it matches the picture below. Although you cannot

delete divisions, you can change the parents or rename them if you made an error.

2. You will next explore and create positions for the ABC Company. Unlike responsibilities, the
Siebel application comes with only four seed positions, and you must create the rest to match
your company’s structure. Also unlike responsibilities or divisions, positions, including seed
positions, can be deleted. When creating positions, consider:
- Although positions and employees are in a M:M relationship, most positions should contain
only one employee unless their job is completely interchangeable with another. A customer
might not mind working with three different call center representatives on a single problem, but
how would a customer feel about working with three different sales representatives? This is a
question only your company can answer, and it determines whether the three sales
representatives have three different positions, or all share one position.
- Also, data visibility is affected by position, hence unless those three sales representatives
should see the same accounts, they should have different positions.
- Positions do not have to report to parent positions within their organization. For example, if a
sales representative moved from the Western Region to the Eastern region, that sales
representative might still want to report to VP of the Western Region, outside of the sales rep’s
organization.
The final position hierarchy should look as follows. Note that the positions for the Western
organization are not prefixed with “ABC”. This is to help you easily distinguish the positions

you created from those pre-populated for this and other labs in the course:

a. In the link bar, click Positions. Query for the Siebel Administrator position. How can there
be two positions with the same name?
b. Notice that the position explorer tree lists the primary employee for each position. Who is the
primary employee for the ERM AnonUser position?
c. In the Positions list applet, click New. Create a position record with the following values:
Division ABC Eastern Region
Position ABC VP of Sales, East
Parent Position CEO
d. Similarly, create the following positions:

Division ABC Northeastern Region
Position ABC Sales Rep NE1
Parent Position ABC VP of Sales, East
Division ABC Southeastern Region

Position ABC Sales Rep SE1
Parent Position ABC VP of Sales, East
e. In the Positions list or Explorer view, verify that you have created all of the above positions
correctly. Make any modifications, if necessary.
3. You will now create employees for ABC Company and assign positions to them. As in the
previous steps, the ABC Western Region has been completed for you.
a. Navigate to Administration - User > Employees. Note that there are four seed employees:
Administrator, Employee, Guest, and Queue. The other employees were added for this and
other labs. You will enter the rest of the employees.

b. Click New to create a new employee.

c. Enter East as the employee’s last name.
d. Enter Natasha as the employee’s first name.
e. Enter ABC VP of Sales, East as the employee’s Job Title. Note that Job Title is an optional
field that does not necessarily need to match the employee’s position or any other position. It
should be the employee’s actual job title, whereas the position may be a more generic term or
may even be a code.
f. Enter NEAST as the employee’s user ID. By convention, the user name is in all caps with no
special characters. This supports situations where the user ID may be passed to other
programs such as the database server for authentication purposes, so special characters
should be avoided.
g. Leave the Responsibility as its default Siebel Administrator. In real circumstances you
would change this to limit the views available to the employees. For the sake of this lab, you

will be logging in as several of these employees and you may need access to the entire
application, hence we leave it as its default.
h. Select Natasha East’s position:
i. Click the Select button in the Position field. The available positions are listed. Note
that only a few of them have names associated with them. Those without names are
unfilled positions; no employees have been assigned to them. Those with names list
the name of the primary employee in each position.
ii. Select ABC VP of Sales, East as the position.
iii. Click Add.
iv. Click OK.
i. Leave Natasha East’s organization as the Default Organization. This organization is not used
to determine which records Natasha can access; rather it is used to determine who has access
to her employee record.
j. Step off the record to save it.
k. Add two more employees as shown in the table below:
Last First Job Title User ID Responsibility Position
Name Name
Eastman Catherine ABC Sales Rep NE1 CEASTMAN Siebel ABC Sales Rep NE1
Administrator
Eastwood Charles ABC Sales Rep SE1 CEASTWOOD Siebel ABC Sales Rep SE1
Administrator
4. Log out of Siebel Call Center and leave the browser open on the login screen.
5. You will finally confirm that you successfully added the employees.
a. Log in to Siebel Call Center as CEASTMAN/CEASTMAN. If you cannot log in, log in as
SADMIN/SADMIN and confirm that you entered her User ID correctly.
b. Log out and log in as CEASTWOOD/CEASTWOOD. You should log in successfully.
6. Log out of Siebel Call Center.

Solutions 5-1 Creating the Company Structure (Guided)
Answers:
1.b. Navigate to Administration - Group > Internal Divisions. This view shows all of the
existing organizations and divisions. Those starting with ABC are the pre-populated ABC
entries for this training. Those without an ABC are the seed entities that are created when
the Siebel application is installed. There are three seed entities. What are they?
Default Organization, ERM AnonUser, and Siebel Administration

1.c. Click Organizations in the link bar near the top of the screen. This view shows only the
organizations. Which of the divisions you found above is an organization?
Default Organization is an organization.
1.e. In the Tree applet, click the + sign for Default Organization to expand its hierarchy. The
child divisions of Default Organization are shown. Notice that the explorer tree shows each
division at the top level of the hierarchy for ease of navigation and also shows it within the
correct hierarchy. What are the child divisions of Default Organization?
ABC Company and Siebel Administration.
2.a. In the link bar, click Positions. Query for the Siebel Administrator position. How can there
be two positions with the same name?
Positions are assigned to divisions, hence two positions with the same name can be in two
different divisions. Note that the first Siebel Administrator is part of the Siebel
Administration division, while the other is part of the Default Organization. Hence there is
no conflict.
2.b. Notice that the position explorer tree lists the primary employee for each position. Who is
the primary employee for the ERM AnonUser position?
ERM Guest, one of the seed employees.


Module 6: Controlling Access to Customer Data
Lab 6-1 Exploring View Filters (Unguided)
Goals To understand how view filters use users, positions, and organizations to control user
access to customer data
Instructions:

In this lab, you will explore how access to customer data is controlled using employees, positions,
and organizations. You will explore Opportunities, which are controlled by position and
organization. Each opportunity is associated with a sales team consisting of one or more positions
and is also associated directly with one or more organizations. In each case, you will determine what
you expect to see for a given visibility filter and you will then confirm your expectations.
You will first explore Opportunities from the point of view of an individual user. You will configure
three Opportunities and examine how their visibility is affected by the various view filters. Refer
back to this table when answering visibility questions:
Opportunity Name Sales Team Organization
50 Laptops to ABC Sales Rep SW1: Raj Westerman (Primary) ABC Western Region
CPC ABC Sales Rep NE1: Catherine Eastman
120 Servers to ABC Sales Rep NW1: Maxwell Westerly (Primary) ABC Western Region
ABA
75 Printers to ABC Sales Rep SE1: Charles Eastwood (Primary) ABC Eastern Region
TWA ABC Sales Rep SW1: Raj Westerman
1. You will first configure the Opportunities in the system. Since the primary defaults to the creator
of the record, you will create the 75 Printers to TWA opportunity as CEASTWOOD.
a. Start Siebel Call Center and log in as CEASTWOOD/CEASTWOOD.
Create a new Opportunity named 75 Printers to TWA. Who is the default primary for this
Opportunity?
b. Add Raj Westerman to the sales team for this opportunity.

c. Add Catherine Eastman to the sales team for the 50 Laptops to CPC opportunity.
d. Log out of Siebel Call Center.

2. You will next explore the view filters from the point of view of a position with no reports. Recall
that Raj Westerman holds the position of ABC Sales Rep SW1 and belongs to the ABC
Southwest division, which is part of the ABC Western Region organization:
Name Position Position Position Parent Position
Division Organization
Raj Westerman ABC Sales Rep SW1 ABC ABC Western ABC VP of Sales,
Southwestern Region West
Region
a. Log in to the Siebel Call Center application as RWESTERMAN/RWESTERMAN.
b. Navigate to the Opportunities List view. What is the default view filter for Raj Westerman?

c. What Opportunities should Raj Westerman see in this view? Does he see them?
Hint: Refer back to the table of Opportunities at the beginning of this lab to refresh your
memory.
d. What Opportunities should Raj Westerman see using the My Team’s Opportunities view?
Does he see them?
e. What opportunities should Raj Westerman see using the All Opportunities view? Does he
see them?
f. What opportunities should Raj Westerman see using the All Opportunities Across My
Organizations view? Does he see them?
g. What opportunities should Raj Westerman see using the All Opportunities Across
h. Log out of Siebel Call Center.
3. You will next explore the view filters from the point of view of the ABC Eastern Region
manager, Natasha East. As a reminder, only the 75 Printers to TWA opportunity is assigned the
ABC Eastern Region organization, while Catherine Eastman is on the 50 Laptops to CPC sales
team, but is not the primary.
a. Log in to Siebel Call Center as NEAST/NEAST.
b. Navigate to the Opportunities List view.
c. Confirm that the My Opportunities view contains no records.
d. Confirm that the My Team’s Opportunities view contains only the 75 Printers to TWA
opportunity. Why does it not show the 50 Laptops to CPC opportunity?

e. Confirm that the All Opportunities and All Opportunities Across My Organizations
views show only the 75 Printers to TWA opportunity.
f. Log out of Siebel Call Center.
4. You will finally verify that the company CEO, Mark Planck, sees opportunities from both his
direct reports and their reports as well.
a. Log in to Siebel Call Center as MPLANCK/MPLANCK.
b. Confirm that Mark Planck sees all three opportunities in his My Team’s Opportunities
view. Since his direct reports are not on any of the sales teams, this confirms that Mark
Planck is seeing opportunities from both his direct reports and those who report to them.
c. Confirm that Mark Planck sees only the 5 x Lagerstatte 25 GB SAN and Eternal Storage
10 TB NAS opportunities in his All Opportunities view. His organization is the Default
Organization, which is not associated with any of the opportunities from this lab.

d. Confirm that Mark Planck sees all five opportunities in his All Opportunities Across My
Organizations view. This view includes all of the child organizations of the Default
Organization, including the ABC Eastern Region and ABC Western Region organizations.
e. Log out of Siebel Call Center.

Solutions 6-1 Exploring View Filters (Unguided)
Answers
1.e. Create a new Opportunity named 75 Printers to TWA. Who is the default primary for this
Opportunity?
CEASTWOOD. The default primary team member is the creator of the record.
2.c. Click Opportunities List in the view link bar. What is the default view filter for the
Opportunities list for Raj Westerman?

The My Opportunities view.
2.d. What Opportunities should Raj Westerman see in this view? Does he see them?
He should see the 50 Laptops to CPC and 75 Printers to TWA opportunities, as his
position is on the sales team for both of them. Yes, he sees all opportunities for which his
position is on the sales team.
2.e. Before selecting the next view, answer the following question: What Opportunities should
Raj Westerman see using the My Team’s Opportunities view? Does he see them?
He should see the 50 Laptops to CPC opportunity. Yes, he sees it. The My Team’s
Opportunities view filter shows all opportunities for which Raj Westerman’s position or
one of his direct or indirect reports’ positions is the primary on that opportunity. Since Raj
Westerman has no reports, the view will only show opportunities for which his position is
the primary. Only the 50 Laptops to CPC opportunity satisfies this condition, so only the
50 Laptops to CPC opportunity should be shown.
2.g. What opportunities should Raj Westerman see using the All Opportunities view? Does he
see them?
He should see the 50 Laptops to CPC and 120 Servers to ABA opportunities. Yes, he sees
them. His position is assigned the ABC Western Organization, which includes the 50
Laptops to CPC and 120 Servers to ABA opportunities, but not the 75 Printers to TWA
opportunity. Notice that the 75 Printers to TWA opportunity appears in the My
Opportunities view but not the All Opportunities view.
2.i. What opportunities should Raj Westerman see using the All Opportunities Across My
He should see the 50 Laptops to CPC and 120 Servers to ABA opportunities. Yes, he sees
them. The All Opportunities Across My Organizations view shows all opportunities in his
position’s organization and all its sub-organizations. The ABC Western Region
organization has no sub-organizations, so this view will not differ from the All
Opportunities view.
2.k. What opportunities should Raj Westerman see using the All Opportunities Across
He should see the 50 Laptops to CPC, 120 Servers to ABA, 75 Printers to TWA, 5 x

Lagerstatte 25 GB SAN, and Eternal Storage 10 TB NAS opportunities. He should see all
of the opportunities that are assigned an organization.
3.d. Confirm that the My Team’s Opportunities view contains only the 75 Printers to TWA
It does not show the 50 Laptops to CPC opportunity because Catherine Eastman’s position
is not the primary position of the sales team for that opportunity.


Lab 6-1 Exploring View Filters (Guided)
Goals To understand how view filters use users, positions, and organizations to control user
access to customer data
Instructions:

In this lab, you will explore how access to customer data is controlled using employees, positions,
and organizations. You will explore Opportunities, which are controlled by position and
organization. Each opportunity is associated with a sales team consisting of one or more positions
and is also associated directly with one or more organizations. In each case, you will determine what
you expect to see for a given visibility filter and you will then confirm your expectations.
You will first explore Opportunities from the point of view of an individual user. You will configure
three Opportunities and examine how their visibility is affected by the various view filters. Refer
back to this table when answering visibility questions:
ABA
1. You will first configure the Opportunities in the system. Since the primary defaults to the creator
of the record, you will create the 75 Printers to TWA opportunity as CEASTWOOD.
a. Start Siebel Call Center and log in as CEASTWOOD/CEASTWOOD.
Note: If you cannot log in, confirm that you created Charles Eastwood as an employee in a
previous lab.
b. Click the Opportunities tab.
c. Click Opportunities List in the link bar. The My Opportunities view is shown.
d. Select All Opportunities Across Organizations in the visibility filter drop-down list. The
50 Laptops to CPC and 120 Servers to ABA opportunities should be visible, as well as the
two opportunities from other labs. (5 x Lagerstatte 25 GB SAN and Eternal Storage 10 TB
NAS).
e. Create a new Opportunity named 75 Printers to TWA. Who is the default primary for this
Opportunity?

f. Press the Select button next to Sales Team in the lower applet. The Team Members shuttle
applet is displayed.
g. Select Raj Westerman and click Add to add him to the sales team for this Opportunity.
h. Click OK to close the shuttle applet.
i. Select the 50 Laptops to CPC Opportunity.
j. Using the same steps as above, add Catherine Eastman to the sales team.
Note: If Catherine Eastman does not appear as an available employee, confirm that you
created her in a previous lab.
k. Log out of Siebel Call Center.
2. You will next explore the view filters from the point of view of a position with no reports. Recall
that Raj Westerman holds the position of ABC Sales Rep SW1 and belongs to the ABC
Southwest division, which is part of the ABC Western Region organization:

Name Position Position Position Parent Position
Division Organization
Raj Westerman ABC Sales Rep SW1 ABC ABC Western ABC VP of Sales,
Southwestern Region West
Region
c. Click Opportunities List in the view link bar. What is the default view filter for the
d. What Opportunities should Raj Westerman see in this view? Does he see them?
Hint: Refer back to the table of Opportunities at the beginning of this lab to refresh your
memory.
e. Before selecting the next view, answer the following question: What Opportunities should
Raj Westerman see using the My Team’s Opportunities view?
f. Select the My Team’s Opportunities view from the visibility filter drop-down list and
confirm your result. Note that Raj Westerman has access to all of the visibility filters. This is
because we assigned him the Siebel Administrator responsibility.
g. What opportunities should Raj Westerman see using the All Opportunities view?
h. Select the All Opportunities view from the visibility filter drop-down list and confirm that
you see the opportunities you listed above.
i. What opportunities should Raj Westerman see using the All Opportunities Across My
Organizations view?

j. Select the All Opportunities Across My Organizations view from the visibility filter drop-
down list and confirm your result.
k. What opportunities should Raj Westerman see using the All Opportunities Across
Organizations view?
l. Select the All Opportunities Across Organizations view from the visibility filter drop-
down list and confirm your result.
m. Log out of Siebel Call Center.
3. You will next explore the view filters from the point of view of the ABC Eastern Region
manager, Natasha East. Since you now have some familiarity with the view filters, the steps are
abbreviated here. As a reminder, only the 75 Printers to TWA opportunity is assigned the ABC

Eastern Region organization, while Catherine Eastman is on the 50 Laptops to CPC sales team,
but is not the primary.
a. Log in to Siebel Call Center as NEAST/NEAST.
b. Navigate to the Opportunities List view.
c. Confirm that the My Opportunities view contains no records.
d. Confirm that the My Team’s Opportunities view contains only the 75 Printers to TWA
e. Confirm that the All Opportunities and All Opportunities Across My Organizations
views show only the 75 Printers to TWA opportunity.
f. Log out of Siebel Call Center.
4. You will finally verify that the company CEO, Mark Planck, sees opportunities from both his
direct reports and their reports as well.
a. Log in to Siebel Call Center as MPLANCK/MPLANCK.
b. Confirm that Mark Planck sees all three opportunities in his My Team’s Opportunities
view. Since his direct reports are not on any of the sales teams, this confirms that Mark
Planck is seeing opportunities from both his direct reports and those who report to them.
c. Confirm that Mark Planck sees only the 5 x Lagerstatte 25 GB SAN and Eternal Storage
10 TB NAS opportunities in his All Opportunities view. His organization is the Default
Organization, which is not associated with any of the opportunities from this lab.
d. Confirm that Mark Planck sees all five opportunities in his All Opportunities Across My
Organizations view. This view includes all of the child organizations of the Default
Organization, including the ABC Eastern Region and ABC Western Region organizations.

Solutions 6-1 Exploring View Filters (Guided)
Answers
1.e. Create a new Opportunity named 75 Printers to TWA. Who is the default primary for this
Opportunity?
CEASTWOOD. The default primary team member is the creator of the record.
2.c. Click Opportunities List in the view link bar. What is the default view filter for the
The My Opportunities view.

2.d. What Opportunities should Raj Westerman see in this view? Does he see them?
He should see the 50 Laptops to CPC and 75 Printers to TWA opportunities, as his
position is on the sales team for both of them. Yes, he sees all opportunities for which his
position is on the sales team.
2.e. Before selecting the next view, answer the following question: What Opportunities should
Raj Westerman see using the My Team’s Opportunities view?
He should see the 50 Laptops to CPC opportunity. The My Team’s Opportunities view
filter shows all opportunities for which Raj Westerman’s position or one of his direct or
indirect reports’ positions is the primary on that opportunity. Since Raj Westerman has no
reports, the view will only show opportunities for which his position is the primary. Only
the 50 Laptops to CPC opportunity satisfies this condition, so only the 50 Laptops to CPC
opportunity should be shown.
2.g. What opportunities should Raj Westerman see using the All Opportunities view?
He should see the 50 Laptops to CPC and 120 Servers to ABA opportunities. His position
is assigned the ABC Western Organization, which includes the 50 Laptops to CPC and 120
Servers to ABA opportunities, but not the 75 Printers to TWA opportunity. Notice that the
75 Printers to TWA opportunity appears in the My Opportunities view but not the All
Opportunities view.
2.i. What opportunities should Raj Westerman see using the All Opportunities Across My
Organizations view?
He should see the 50 Laptops to CPC and 120 Servers to ABA opportunities. The All
Opportunities Across My Organizations view shows all opportunities in his position’s
organization and all its sub-organizations. The ABC Western Region organization has no
sub-organizations, so this view will not differ from the All Opportunities view.
2.k. What opportunities should Raj Westerman see using the All Opportunities Across
Organizations view?
He should see the 50 Laptops to CPC, 120 Servers to ABA, 75 Printers to TWA, 5 x
Lagerstatte 25 GB SAN, and Eternal Storage 10 TB NAS opportunities. He should see all
of the opportunities that are assigned an organization.

3.d. Confirm that the My Team’s Opportunities view contains only the 75 Printers to TWA
It does not show the 50 Laptops to CPC opportunity because Catherine Eastman’s position
is not the primary position of the sales team for that opportunity.


Lab 6-2 Exploring Positions (Unguided)
Goals To understand how an employee’s current position affects the data he or she sees
Instructions:
In this lab, you will add the ABC Sales Rep SE1 position to Raj Westerman and observe how it

affects his visibility filters.
Recall these opportunities from the previous lab:

ABA
1. Log in to the Siebel Call Center application as RWESTERMAN/RWESTERMAN and use the
Administration - User > Employees view to add the ABC Sales Rep SE1 position to Raj
Westerman. You will need to log out and log in again to see the change.
2. Explore how this affects the changes to the various view filters.
a. If necessary, log in to Siebel Call Center as RWESTERMAN/RWESTERMAN.
b. Navigate to the Opportunities List view. Note that the My Opportunities view shows the
same opportunities as in the previous lab. These opportunities are those for which Raj
Westerman’s position is on the sales team. This is an important distinction from Raj
Westerman himself being on the sales team, as you will see when you change Raj
Westerman’s current position and observe the effects.
c. Change Raj Westerman’s current position to the ABC Sales Rep SE1 record.
d. Before navigating to the My Opportunities view, answer the following question: What
opportunities will Raj Westerman now see in his My Opportunities view? Why?
e. Navigate to the My Opportunities view and confirm your answer.

f. What opportunities should Raj Westerman now see in the All Opportunities view?

g. Select the All Opportunities view and confirm your answer.

h. What opportunities should Raj Westerman now see in the All Opportunities Across My
Organizations view?
i. Log out of Siebel Call Center.

Solutions 6-2 Exploring Positions (Unguided)
Answers
2.d. Before navigating to the My Opportunities view, answer the following question: What
He will see only the 75 Printers to TWA opportunity. Charles Eastwood’s position of ABC
Sales Rep SE1 is on the sales team for that opportunity, so now that Raj Westerman is in
that position, he will see that record. This shows that whereas a user sees the union of all
of his or her responsibilities, for position-based customer records he or she sees only the

customer records for his or her current position.
2.f. What opportunities should Raj Westerman now see in the All Opportunities view?
Only the 75 Printers to TWA opportunity, as it is the only one assigned the ABC Eastern
Region organization
2.h. What opportunities should Raj Westerman now see in the All Opportunities Across My
Organizations view?
Only the 75 Printers to TWA opportunity. Although Raj Westerman is assigned positions in
both the ABC Western Region and ABC Eastern Region organizations, only his current
position matters.


Lab 6-2 Exploring Positions (Guided)
Goals To understand how an employee’s current position affects the data he or she sees
Instructions:
In this lab, you will add the ABC Sales Rep SE1 position to Raj Westerman and observe how it

affects his visibility filters.
Recall these opportunities from the previous lab:

ABA
1. You will first add the ABC Sales Rep SE1 position to Raj Westerman. He can do it himself
because we gave him the Siebel Administrator responsibility.
b. Navigate to Administration - User > Employees.
c. Select Raj Westerman. You may need to scroll down to see his record.
d. In the form applet, click the select button in the Position field. The Positions Occupied
shuttle applet is shown.
e. Select the ABC Sales Rep SE1 position (with a current primary of Charles Eastwood) and
click Add.
f. Click OK. Raj Westerman is now assigned two positions.
g. Log out of Siebel Call Center. You will need to log out and log in again to see the change.
2. You will next examine the effects of Raj Westerman’s current position on the data that is visible
to him.
a. Log in to Siebel Call Center as RWESTERMAN/RWESTERMAN.
c. Click Opportunities List in the view link bar. Note that the My Opportunities view shows
the same opportunities as in the previous lab. These opportunities are those for which Raj
Westerman’s position is on the sales team. This is an important distinction from Raj
Westerman himself being on the sales team, as you will see when you change Raj
Westerman’s current position and observe the effects.
d. Select Tools > User Preferences.

e. Click Change Position in the view link bar.

f. Select the ABC Sales Rep SE1 record.
g. Click Change Position. The checkbox should now appear next to this record.
h. Before navigating to the My Opportunities view, answer the following question: What
i. Navigate to the My Opportunities view and confirm your answer.

j. What opportunities should Raj Westerman now see in the All Opportunities view?

k. Select the All Opportunities view and confirm your answer.
l. What opportunities should Raj Westerman now see in the All Opportunities Across My
Organizations view?
m. Log out of Siebel Call Center.

Solutions 6-2 Exploring Positions (Guided)
Answers
2.h. What opportunities will Raj Westerman now see in his My Opportunities view? Why?
He will see only the 75 Printers to TWA opportunity. Charles Eastwood’s position of ABC
Sales Rep SE1 is on the sales team for that opportunity, so now that Raj Westerman is in
that position, he will see that record. This shows that whereas a user sees the union of all
of his or her responsibilities, for position-based customer records he or she sees only the
customer records for his or her current position.

2.j. What opportunities should Raj Westerman now see in the All Opportunities view?
Only the 75 Printers to TWA opportunity, as it is the only one assigned the ABC Eastern
Region organization
2.l. What opportunities should Raj Westerman now see in the All Opportunities Across My
Organizations view?
Only the 75 Printers to TWA opportunity. Although Raj Westerman is assigned positions in
both the ABC Western Region and ABC Eastern Region organizations, only his current
position matters.


Module 7: Catalogs and Master Data
Lab 7-1 Creating a Solutions Catalog (Unguided)
Goals To create catalogs, categories, and access groups, and restrict access to master data
contained in categories.
Instructions:

In this lab you will explore catalogs, categories, and access groups by implementing a solution
catalog. This catalog contains links between problem descriptions and Frequently Asked Questions
(FAQ) documents, allowing users to quickly navigate to a FAQ related to their problem. You will
build the following catalog. Note that the contact information is public, while the product
information is private. This could be used to require users to register before giving them access to
product information:
Legend
Public Catalog Master Data
Public Category Master Data
Private Category
eService Catalog
About ABC ABC Products
• How to Contact Us ABC Copiers
• ABC Copier - Low Toner
• ABC Copier - Not Working
ABC Fax Machines
• ABC FAX - Copying Documents
1. Use the Administration - Catalog > Catalog Administration view to create the catalog. Recall
that the catalog acts as a container for categories.
a. Start Siebel Call Center and log in as SADMIN/SADMIN.
Siebel Essentials 8.0 63

b. Create a new catalog with the information below.

Name eService Catalog
Description ABC eService Catalog
Catalog Type eService FAQ
Active TRUE (checked)
c. Navigate to Info Center and confirm that eService Catalog with a description of ABC
eService Catalog now appears in Info Center. Notice that it does not yet have any categories.
2. Add the categories to the catalog. You will first make all of the categories public and confirm
that they are all visible, then you will mark the ABC Products category as private and confirm
that you can no longer see it.
a. Create four new categories for the eService Catalog catalog with the information below.

Name Display Name
About ABC About ABC
ABC Products ABC Products
ABC Copiers ABC Copiers
ABC Fax Machines ABC Fax Machines
b. Demote the ABC Copiers and ABC Fax Machines categories to make them sub categories
of the ABC Products category.
c. Return to Info Center and confirm that the ABC Products and About ABC categories now
appear.
d. Drill down on ABC Products and confirm that the ABC Copiers and ABC Fax Machines
subcategories now appear.
3. Create the solutions to add to your categories. Solutions are text entries that may be used to
provide information or product news to customers viewing the catalog. The FAQ text box is
capable of holding up to 2000 characters. You will enter simple descriptions of what the solution
should contain.
a. Navigate to Administration - Solution > Solutions.
b. Create the following records with the Status Final and Publish Internal and Publish External
boxes both checked.
Name FAQ
ABC Copier - Low Toner How to repair low toner.
ABC Copier – Not Working How to fix copiers.
ABC FAX - Copying a Document How to copy a document.
How to Contact Us How to contact us by phone or
e-mail.
64 Siebel Essentials 8.0

4. Add the solutions you just created to the appropriate categories and confirm your results.
a. Navigate back to the eService Catalog and add the following solutions to the appropriate
category:
Category Solution
About ABC How to Contact Us
ABC Copiers ABC Copier – Low Toner
ABC Copiers ABC Copier – Not Working
ABC Fax Machines ABC FAX – Copying Document
b. Return to Info Center and confirm your results. Verify that each category reflects the
appropriate solution.

5. Mark the ABC Products category as Private, and verify that the ABC Copiers and ABC Fax
Machines categories are now also marked as Private.
6. Navigate to Info Center and confirm the ABC Products category no longer appears.
7. Use the Administration - Group > Access Groups view to explore creating access groups to
access private categories. Recall that child access groups have more access than parent access
groups, rather than less. You will create one parent and one child access group and confirm this
relationship.
a. Create a new access group and name it ABC Access Group.
b. Create a second access group named ABC Child Access Group and set ABC Access Group
as its parent.
c. Click the Access Groups view link under the Categories tab. This is not the same as the
Access Groups tab above the middle applet. Try to associate the ABC Child Access Group
with the ABC Copiers category. What happens? Why?
d. Associate the ABC Access Group with the ABC Products category. Note that the Cascade
button is now enabled. This button would propagate the ABC Access group to all child
categories in the catalog; that is, to ABC Copiers and ABC Fax Machines. You will not
cascade the access group; instead you will add the ABC Child Access Group to the child
categories.
e. Associate the ABC Child Access Group with the ABC Copiers and ABC Fax categories.
f. Add the Siebel Administrator position to the ABC Access Group. You cannot add individual
users as a party to an access group, but you can add positions, organizations, or user lists. To
add an individual user you would make them the sole member of a user list.
g. Return to Info Center and confirm that the ABC Products category is now visible, while the
ABC Copiers and ABC Fax Machines subcategories are not visible.
h. Remove Siebel Administrator’s position from the ABC Access Group and add it to the ABC
Child Access Group. Since child access groups have more access than parent access groups,

Siebel Administrator will still be able to see the ABC Products category even though it is not
explicitly assigned the ABC Child Access Group.
i. Return to Info Center and confirm that Siebel Administrator can now see all of the categories
and solutions, even though his position is only included in the ABC Child Access Group.
8. Log out of Siebel Call Center and close the browser.

Lab 7-1 Creating a Solutions Catalog (Unguided)
Answers:
6.d.vii. Click the Access Groups view link under the Categories tab. This is not the same as the
Access Groups tab above the middle applet. Try to associate the ABC Child Access Group
with the ABC Copiers category. What happens? Why?
An error message is displayed indicating that the access group cannot be added because
the catalog does not contain its parent access group.


Lab 7-1 Creating a Solutions Catalog (Guided)
Goals To create catalogs, categories, and access groups, and restrict access to master data
contained in categories.
Instructions:

In this lab you will explore catalogs, categories, and access groups by implementing a solution
catalog. This catalog contains links between problem descriptions and Frequently Asked Questions
(FAQ) documents, allowing users to quickly navigate to a FAQ related to their problem. You will
build the following catalog. Note that the contact information is public, while the product
information is private. This could be used to require users to register before giving them access to
product information:
Legend
Public Catalog Master Data
Public Category Master Data
Private Category
eService Catalog
About ABC ABC Products
• How to Contact Us ABC Copiers
• ABC Copier - Low Toner
• ABC Copier - Not Working
ABC Fax Machines
• ABC FAX - Copying Documents
1. You will first create the catalog. Recall that the catalog acts as a container for categories.
b. Navigate to Administration - Catalog > Catalog Administration. Note that the application
contains several seed catalogs.

c. In the Catalogs list, create a new catalog with the information below. Catalog type is used to
determine which applets will display the catalog, which is useful when creating catalogs for
customer Web sites. Setting the Active flag means the catalog will immediately be visible in
applets displaying the appropriate catalog type.
Name eService Catalog
Description ABC eService Catalog
Catalog Type eService FAQ
Active TRUE (checked)
d. Use the site map to navigate to Info Center and confirm that eService Catalog with a
description of ABC eService Catalog now appears in Info Center. Notice that it does not yet
have any categories.

2. You will next add the categories to the catalog. Recall that categories are containers for master
data (static, referential data) or other categories. You will first make all of the categories public
and confirm that they are all visible, then you will mark the ABC Products category as private
and confirm that you can no longer see it.
a. Return to the Administration - Catalog > Catalog Administration view.
b. Drill down on the eService Catalog record to navigate to the Categories view.
c. Create four new categories with the information below. Note that they are created in a flat
hierarchy:
Name Display Name
About ABC About ABC
ABC Products ABC Products
ABC Copiers ABC Copiers
ABC Fax Machines ABC Fax Machines
d. With the four records listed in the above order, select the ABC Copiers record and then click
the Demote one level button . Note that there are also Move Down/Move Up buttons so
you can put your categories in the proper order to build the hierarchy.
e. Repeat the above step for the ABC Fax Machines record. Your results should look as
follows:

f. Return to Info Center and confirm that the ABC Products and About ABC categories now
appear.
g. Drill down on ABC Products and confirm that the ABC Copiers and ABC Fax Machines
subcategories now appear.
3. You will next create the solutions to add to your categories. Solutions are text entries that may be
used to provide information or product news to customers viewing the catalog. The FAQ text
box is capable of holding up to 2000 characters. You will enter simple descriptions of what the
solution should contain.
a. Navigate to Administration - Solution > Solutions.
b. Create the following records with the Status Final and Publish Internal and Publish External
boxes both checked (these fields can be found in the form applet). This ensures that these
records will be visible both internally and externally as soon as they are added to a visible

category.
Name FAQ
ABC Copier - Low Toner How to repair low toner.
ABC Copier – Not Working How to fix copiers.
ABC FAX - Copying a Document How to copy a document.
How to Contact Us How to contact us by phone or
e-mail.
4. You will now add the solutions you just created to the appropriate categories and confirm your
results.
a. Navigate back to the Administration - Catalog > Catalog Administration view and drill down
on the eService Catalog to return to the Categories view.
b. Select the About ABC category record and click the Solutions view link in the bottom
applet to navigate to the Solutions view. Note that you may need to use the drop-down list at
the end of the tab bar to locate this view link.
c. Click New to create a new solution record.
d. In the Add Solutions query window, click the Go button. This invokes a list of available
solutions displaying the solutions you created earlier.
e. Select the How to Contact Us record and click OK.
f. Repeat the above steps to associate the categories and solutions shown below. You will need
to expand the ABC Products category to see the ABC Copiers and ABC Fax Machines
subcategories.
Category Solution
ABC Copiers ABC Copier – Low Toner
ABC Copiers ABC Copier – Not Working
ABC Fax Machines ABC FAX – Copying Document
g. Return to Info Center and confirm your results.
i. Drill down on the About ABC category.
ii. Click the Solution link and confirm that the How to Contact Us solution appears.
iii. Click on the How to Contact Us solution and confirm that the text of the FAQ is
shown.

iv. Return to Info Center and explore the ABC Products category hierarchy, including
the ABC Copiers and ABC Fax Machines subcategories, to confirm that the other
three solutions also appear in the appropriate locations.
5. You will now mark a category as private.

a. Return to the list of eService Catalog categories.
b. Mark the ABC Products category as Private and step off the record to save it.
c. Verify that the ABC Copiers and ABC Fax Machines categories are now also marked as
Private. If a parent category is private, the child categories must also be private.
d. Confirm this by unchecking the Private checkbox on ABC Copiers and stepping off the
record. What happens?

e. Click OK to dismiss the error message.
f. Navigate to Info Center and confirm the ABC Products category no longer appears.
6. You will finally explore creating access groups to access private categories. Recall that child
access groups have more access than parent access groups, rather than less. You will create one
parent and one child access group and confirm this relationship.
a. Navigate to Administration - Group > Access Groups. Notice that several seed access groups
already exist.
b. Create a new access group and name it ABC Access Group.
c. Create a second access group named ABC Child Access Group and set ABC Access Group
as its parent.
d. Try to associate the ABC Child Access Group with the ABC Copiers category.
i. Return to the eService Catalog category list.
ii. Expand the ABC Products category.
iii. Select the ABC Copiers category.
iv. Click the Access Groups view link under the Categories tab. This is not the same as
the Access Groups tab above the middle applet.
v. Click New.
vi. Select the ABC Child Access Group.
vii. Click OK. What happens? Why?
viii. Click OK to dismiss the error message.

ix. Click Cancel.
e. Associate the ABC Access Group with the ABC Products category.
i. Select the ABC Products category. Note that the Access Groups applet is still
displayed.
ii. Click New in the bottom applet.
iii. Select the ABC Access Group.

iv. Click OK. Note that there is no error, as the ABC Access Group is not a child access
group. Also note that the Cascade button is now enabled. This button would
propagate the ABC Access group to all child categories in the catalog; that is, to ABC
Copiers and ABC Fax Machines. You will not cascade the access group; instead you
will add the ABC Child Access Group to the child categories.
f. Associate the ABC Child Access Group with the ABC Copiers and ABC Fax categories.
i. Select the ABC Copiers category.
ii. Add the ABC Child Access Group to the ABC Copiers category. Notice that this time
there is no error. Now that the parent access group is associated with the parent
catalog, the child access group may be associated with the child catalog.
iii. Add the ABC Child Access Group to the ABC Fax Machines category.
g. Add the Siebel Administrator position to the ABC Access Group. You cannot add individual
users to an access group, but you can add positions, organizations, or user lists. To add an

individual user you would make them the sole member of a user list.
i. Navigate to Administration - Group > Access Groups.
ii. Select the ABC Access Group record in the upper applet.
iii. Click New in the lower applet.
iv. Select the Siebel Administrator position. Make sure you have selected the position,
not the organization by using the position with a value under Group Type of Position.
v. Click Add.
h. Return to Info Center and confirm that the ABC Products category is now visible
i. Drill down on ABC Products to confirm that the ABC Copiers and ABC Fax Machines
categories are not visible.
j. You will now remove Siebel Administrator’s position from the ABC Access Group and add
it to the ABC Child Access Group. Since child access groups have more access than parent
access groups, Siebel Administrator will still be able to see the ABC Products category even
though it is not explicitly assigned the ABC Child Access Group.
i. Navigate to Administration - Group > Access Groups.
ii. Select the ABC Access Group.
iii. Click Delete in the lower applet to delete the Siebel Administrator record.
iv. Click OK to confirm the deletion.
v. Select the ABC Child Access Group.
vi. Add the Siebel Administrator position to the ABC Child Access Group.
k. Return to Info Center and confirm that Siebel Administrator can now see all of the categories
and solutions, even though his position is only included in the ABC Child Access Group.
7. Log out of Siebel Call Center and close the browser.

Lab 7-1 Creating a Solutions Catalog (Guided)
Answers:
5.d. Confirm this by unchecking the Private checkbox on ABC Copiers and stepping off the
record. What happens?
An error message is displayed indicating that the Private flag cannot be set to false when
the parent category is marked as Private.
6.d.vii. Click OK. What happens? Why?

An error message is displayed indicating that the access group cannot be added because
the catalog does not contain its parent access group.

Module 8: The Siebel Web Architecture
Lab 8-1 Exploring the Siebel Web Architecture

(Unguided)
Goals To examine the locations and settings of the Siebel Web architecture components
Instructions:

Due to the conceptual nature of this lab, there is no Unguided version of it. Please turn the page and
do the Guided version.


Lab 8-1 Exploring the Siebel Web Architecture (Guided)
Goals To examine the locations and settings of the Siebel Web architecture components
Instructions:
In this lab you will explore the Siebel Web architecture, starting with the Siebel Web client, and

moving all the way down to the Siebel database. This will help familiarize you with the components
involved in configuring and running a Siebel application.
1. You will first explore the Siebel Web client. For the high-interactivity (HI) client, an ActiveX
control is required for Internet Explorer. You will confirm the existence of that ActiveX control.
Be aware that when a user first tries to log in to the HI client they will be asked to download this
control.
a. Select Start > Programs > Internet Explorer.
b. Select Tools > Internet Options.
c. Click the Programs tab.
d. Click Manage Add-ons.
e. Confirm that several Siebel ActiveX controls are listed, including controls to display lists,
menus, toolbars, and trees, as well as the High Interactivity client.
f. Click OK to close the Manage Add-ons window.
g. Click OK to close the Internet Options window.
h. Close Internet Explorer.
2. You will next explore the Siebel Web Server Extension. Microsoft Internet Information Services
(IIS) is installed as the Web server on your machine. You will check the virtual directories,
examine the default Web page, and examine the configuration file.
a. Select Start > Programs > Administrative Tools > Internet Information Services.
b. In the left pane, expand your <machine name> and then expand Web Sites and then Default
Web Site.
c. Verify that the callcenter_enu virtual directory exists.
d. Select callcenter_enu.
e. In the right pane, right-click default.htm and select Properties. default.htm is the file users
are directed to when they enter http://<Web Server Name>/callcenter_enu.
f. Click the ASP.NET tab. What is the file location for default.htm?
g. Click Cancel to close the Properties window.

h. Use Notepad to open D:\OUsea\SWEApp\public\enu\default.htm. Note that it is a very

simple HTML file that issues the ‘Start’ Siebel Web Server Extension command. This shows
that it is the Siebel Web Server Extension that is managing the Web server’s interaction with
the client. To open the file using Notepad, right-click the file and select Open With.
i. Close the file, not saving any changes.
j. Close Internet Information Services.
k. View the eapps.cfg file to determine the name of the Siebel Server, Enterprise, and
Application Object Manager for Siebel Call Center. This configuration file is used by the
Siebel Web Server Extension to determine how to connect to the Siebel Enterprise and which
Object Manager to use within that enterprise.
i. Use Notepad to open D:\OUsea\SWEApp\BIN\eapps.cfg.
ii. Select Edit > Find (or press CTRL+F) and search for /callcenter_enu.
iii. Within the connect string, identify the following:

Siebel Server
Enterprise
Call Center Object Manager
iv. Close eapps.cfg, not saving any changes.
l. Verify the information you recorded within the Siebel Call Center using the Web Client.
i. Start Siebel Call Center and log in as SADMIN/SADMIN.
ii. Navigate to Administration - Server Management > Enterprises.
iii. Verify that the Enterprise you found above is shown in the Enterprise Servers list, and
the Siebel Server you found above is shown in the Servers list.
m. Leave Call Center open.
3. You will next identify the critical components of the Siebel Gateway Name Server.
a. Using Windows explorer, navigate to D:\OUsea\gtwysrvr\ADMIN.
b. Confirm the existence of siebns.dat. This is the critical data file maintained by the Gateway
Name Server to keep track of such things as the Enterprise, which Servers are online, which
components on those servers are enabled, and so forth. Do not edit or delete this file!
c. Select Start > Programs > Administrative Tools > Services to open the services window.
d. Confirm that the Siebel Gateway Name Server service exists and is started.
e. Minimize the Services window.
4. You will now determine the name of the Siebel Server and its enabled server components.
a. Return to Siebel Call Center. You should still be on the Administration - Server
Configuration > Enterprises view. Note that most of the component groups are enabled for
this enterprise.
b. Within Administration - Server Configuration, click Servers. What is the name of the Siebel
Server within this Enterprise?

c. Examine the components in the middle applet. Does it look like all of the components from
all of the enabled component groups are enabled on this server?
d. Display the Component Type column.

i. In the Components applet, right-click and select Columns Displayed.
ii. In the Available Columns left pane, select Component Type.
iii. Click the right arrow to move Component Type to the Selected Columns right pane.
iv. Click Save.
e. What type of server component is Call Center Object Manager (ENU)?

5. You will finally examine the other components that make up a Siebel Enterprise: The Siebel
Server service, files related to the Siebel server, the Siebel file system, and the database
connection. Understanding where these files and services are located is important in
implementing a Siebel Enterprise.
a. Return to the Services window and confirm that the Siebel Server [Siebel_OUsrvr] service
exists and is started. This service processes all server requests and manages all sessions; if it
is stopped or crashes, you will no longer be able to log in using the Siebel Web client.
b. Minimize the Services window.
c. Using Windows Explorer, navigate to D:\OUsea\siebsrvr\OBJECTS\ENU. This is the
location of the Siebel Repository File (srf), a compiled binary file containing run-time
information from the server such as data presentation and business rules and logic. It is used
to improve performance by reducing the need for the Siebel Server to access the database.
What is the name of the Siebel Repository File?
d. Navigate to D:\SUsea\siebsrvr\WEBTEMPL. These are the Siebel Web Templates. You will
need to change these to make the Web pages match your company’s “look and feel”.
e. Navigate to D:\siebfile. This is the Siebel File System used to store compressed files such as
attached documents. Note that it is a shared directory.
f. Select Start > Programs > Administrative Tools > Data Sources (ODBC). This is where the
Siebel Server’s connection to the database is defined.
g. Click the System DSN tab.
h. Select Siebel_DSN and click Configure.
i. Note that this class uses an MSSQL database on your local machine. Click Next.
j. Note that this class uses SQL Server authentication. Enter SADMIN as the user name and
SADMIN as the password.
k. Click Next.
l. Note that the default database is siebeldb. (Greyed out). This is the name of the database
used in this class. Click Next.
m. Click Finish.
n. Click Test Data Source. This confirms that you (and therefore the Siebel Server) can
connect to the siebeldb database.

o. Click OK to confirm that the tests completed successfully.

p. Click Cancel three times to close the ODBC Administration tool.

Solutions 8-1 Exploring the Siebel Web Architecture

(Guided)
Answers
2.f. What is the file location for default.htm?
D:\OUsea\SWEApp\public\enu\web.config (default.htm)
2.k.iii. Within the connect string, identify the following:

Siebel Server localhost

Enterprise Siebel
Call Center Object Manager SCCObjMgr_enu
4.b. Within Administration - Server Configuration, click Servers. What is the name of the
Siebel Server within this Enterprise?
OUsrvr.
4.c. Examine the components in the middle applet. Does it look like all of the components from
all of the enabled component groups are enabled on this server?
No. Only components from the CallCenter, SystemAux, and System component groups are
enabled on this server.
4.e. What type of server component is Call Center Object Manager (ENU)?
AppObjMgr (Application Object Manager)
5.c. Using Windows Explorer, navigate to D:\OUsea\siebsrvr\OBJECTS\ENU. This is the

location of the Siebel Repository File (srf), a compiled binary file containing run-time
information from the server such as data presentation and business rules and logic. It is
used to improve performance by reducing the need for the Siebel Server to access the
database. What is the name of the Siebel Repository File?
siebel.srf


Module 9: Server Components and Parameters
Lab 9-1 Exploring Server Components and Parameters

(Unguided)
Goals To explore the Siebel Enterprise using the Enterprise Explorer

To modify parameters within the enterprise

Instructions:


Lab 9-1 Exploring Server Components and Parameters

(Guided)
Goals To explore the Siebel Enterprise using the Enterprise Explorer

To modify parameters within the enterprise

Instructions:
In this lab you will use the Enterprise Explorer to familiarize yourself with the concepts of
component groups, components, and parameters. You will then explore changing a component’s
parameters at multiple levels.
1. Start Siebel Call Center Web client and log in as SADMIN/SADMIN.
2. You will first explore the top level of the Siebel Enterprise using the Enterprise Explorer. This
will give you an overview of the enterprise-level configuration before expanding the tree to
examine it in more detail.
a. Navigate to Administration – Server Configuration > Enterprise Explorer. The explorer tree
is shown in the left pane. The top level of the explorer tree is the enterprise.
b. Click the (+) plus sign next to the enterprise to expand the explorer tree. The folders listed
indicate objects that can be configured or examined at the enterprise level. What objects can
be configured or examined at the enterprise level?
c. Select the Servers folder. Which Siebel Server is contained within the Siebel Enterprise?
d. Select the Component Groups folder. These are the component groups that are enabled for
the enterprise. Component groups must be enabled at the enterprise level to be available for
assignment to individual servers. Recommended practice is to disable those component
groups that you know you will never use on any server.
e. Sort on the Enable State of the component groups. Which component groups are disabled for
the enterprise?
f. Select the Component Definitions folder. Component definitions include the component
type (which can be thought of as the program that will run) and component parameters (input
parameters). Notice that each component definition has a run mode associated with it. What

is the run mode for the Application Deployment Manager Object Manager (ENU)?
g. Select the Parameters folder. These are parameters that are set at the enterprise level. Query
for the ODBC Data Source parameter. This parameter determines the ODBC connection
Siebel servers will use to connect to the database. What is the value of the ODBC Data
Source parameter?
h. Select the System Alerts folder. The system alert components determine whom to e-mail
with system alerts.
i. Select the Profiles folder. These are sets of parameters that can be used by multiple
components. For example, the Server Datasource profile determines how the servers connect

to the database.
3. You will now examine the explorer tree in more detail.

a. Click the + (plus) sign to expand the Servers folder.
b. Expand the OUsrvr object. What objects can be configured or examined at the server level?
c. Expand the Component Groups folder. This lists all of the component groups assigned to
this server. What component groups are currently assigned to this server?
d. Expand the Components folder. This lists all of the components included in the assigned
component groups.
e. Expand the Call Center Manager (ENU) object. This is the Object Manager for the Siebel
Call Center application. Note that you can configure parameters or events on this specific
component on this specific server.
f. Expand the Parameters folder within the Call Center Object Manager (ENU) object. Recall
that you saw the ODBC Data Source parameter at the enterprise level.
g. Query for the ODBC Data Source parameter. This is an example of a component parameter
inheriting its value from the enterprise. What is the current value of the ODBC Data Source
parameter of the Call Center Object Manager (ENU) component?
h. Expand the Parameters folder within OUsrvr object. These are parameters set at the server
level.
i. Expand the Events folder within the OUsrvr object. Here you can set the logging levels for
various events on the server.
j. Continue exploring the explorer tree until you are comfortable with its navigation:
- Component groups contain components.
- Component definitions include a component type and parameters. Notice that for
component definitions, the definition names appear in the right pane, while the types appear

in the left pane. For example, selecting Call Center Object Manager (ENU) in the right pane
shows the Application Object Manager component type in the left pane.
4. You will finally modify a component parameter and examine the effects of the Delete Parameter
Override function.
a. Using the explorer tree, locate the Call Center Object Manager (ENU) component
definition. That is, in the explorer tree select Siebel Enterprise > Siebel > Component
Definitions, and then locate Call Center Object Manager (ENU) in the right pane.
b. Expand the selected Application Object Manager object in the explorer tree. Recall that the
explorer tree shows object definitions by type rather than by name.
c. Expand the Parameters folder.
d. Query for the Log File parameter. What is the current value of the Log File parameter?

e. Using the explorer tree, navigate to Siebel Enterprise > Siebel > Servers > OUsrvr >
Components > Call Center Object Manager (ENU) > Parameters.
f. Query for the Log File parameter. What is the value of the Log File parameter? Where do
you think the default value comes from?
g. Change the Value on Restart value to test and step off the record to save it. What happens?
h. Select the Log File parameter and delete the Value on Restart parameter value, then step off
the record to save it. What happens?
i. Click OK to dismiss the error.

j. Select the Log File parameter, right-click, and select Delete Parameter Override. The value
returns to the inherited value.
5. Remain logged in to Siebel Call Center.

Solutions 9-1 Exploring Server Components and

Parameters (Guided)
Answers
2.b. Click the (+) plus sign next to the enterprise to expand the explorer tree. The folders listed
indicate objects that can be configured or examined at the enterprise level. What objects
can be configured or examined at the enterprise level?
Servers, Component Groups, Component Definitions, Parameters, System Alerts, and
Profiles.

2.c. Select the Servers folder. Which Siebel Server is contained within the Siebel Enterprise?
OUsrvr
2.e. Sort on the Enable State of the component groups. Which component groups are disabled
for the enterprise?
PIM Server Integration.
2.f. Select the Component Definitions folder. Component definitions include the component
type (which can be thought of as the program that will run) and component parameters
(input parameters). Notice that each component definition has a run mode associated with
it. What is the run mode for the Application Deployment Manager Object Manager (ENU)?
Interactive. Object Managers manage user sessions, hence are always interactive.
2.g. Select the Parameters folder. These are parameters that are set at the enterprise level.
Query for the ODBC Data Source parameter. This parameter determines the ODBC
connection Siebel servers will use to connect to the database. What is the value of the
ODBC Data Source parameter?
Siebel_DSN.
3.b. What objects can be configured or examined at the server level?

Component Groups, Components, Parameters, and Events.
3.c. What component groups are currently assigned to this server?

Auxiliary System Management, Siebel Call Center, and System Management.
3.g. Query for the ODBC Data Source parameter. This is an example of a component
parameter inheriting its value from the enterprise. What is the current value of the ODBC
Data Source parameter of the Call Center Object Manager (ENU) component?
Siebel_DSN. This should look familiar, as it is the same value we saw at the Enterprise
level.
4.d. What is the current value of the Log File parameter?

SComm.log.

4.f. What is the value of the Log File parameter? Where does the default value come from?
SComm.log. The component inherits the parameter value from the component definition,
hence the default value is the one specified in the component definition.
4.g. What happens?

Both the Value on Restart value and the default value are set to test. You have overridden
the parameter value at the component level, so it will use this value instead of the value
given in the component definition. This is why the default value becomes test as well.
4.h. What happens?

An error message is shown. You cannot delete the parameter value because it would cause
a null value to be passed to the system.


Lab 9-2 Enabling and Assigning Component Groups

(Unguided)
Goals To enable a component group and assign it to a server

To modify the startup behavior of components within that component group

Instructions:
In this lab you will enable a component group and assign it to a server. You will then modify and
test its startup behavior. You will finally disable it to avoid consuming unnecessary resources.
1. Verify that the Siebel Sales component group is enabled in the enterprise and assigned to the
OUsrvr server, but that it is not enabled on the server.
2. Enable the Siebel Sales component group on the OUsrvr server.
3. Open a second browser and enter an address of http://localhost/sales_enu. You will receive an
error message that the server is busy. Why doesn’t the login screen appear?
4. Restart the Siebel Server service and confirm that you can now access the Siebel Sales login
screen.
5. Use the Administration - Server Configuration > Servers view to set the Sales Object Manager
(ENU) component to Manual Start. Then use the Administration - Server Management >
Components view to shut it down. Although the disabling of the component group does not take
effect until you restart the Siebel Server service, since you shut down the component it is not
taking up your resources, so you can wait to restart the service until you have performed
additional administration in a later lab.

Solutions 9-2 Enabling and Assigning Component

Groups (Unguided)
Answers
3. Open a second browser and enter an address of http://localhost/sales_enu. You will
receive an error message that the server is busy. Why doesn’t the login screen appear?
Enabling or disabling a component group on a server requires a server restart for the
change to take effect.

Lab 9-2 Enabling and Assigning Component Groups

(Guided)
Goals To enable a component group and assign it to a server

To modify the startup behavior of components within that component group

Instructions:
In this lab you will enable a component group and assign it to a server. You will then modify and
test its startup behavior. You will finally disable it to avoid consuming unnecessary resources.
1. You will first verify that the Siebel Sales component group is enabled in the enterprise. You will
then verify that it is assigned to the OUsrvr server. Finally, you will enable it on the server.
Enabling a component group in the enterprise makes it available for assignment to servers.
Assigning a component group to a server makes the component group available on that server.
Enabling it on the server reserves memory on the server for the component group and starts tasks
associated with the component group components when the server starts up.
a. Using the enterprise explorer, locate the Siebel Sales component group. Is the Siebel Sales
component group currently enabled in the enterprise?
b. Open a second browser and enter an address of http://localhost/sales_enu. You will receive
an error message that the server is busy.
c. Close the browser and return to the Siebel Call Center application.
d. Click the Enterprises view link. Note that the Component Groups view tab is selected in the
middle applet and the Siebel Sales component group is selected.
e. Examine the bottom right applet. Is the Siebel Sales component group assigned to OUsrvr?
f. Is the Siebel Sales component group enabled on OUsrvr?
g. Click the Enable button in the lower right applet. This enables the component group on the
server.
Note: At this point you would normally synchronize components to ensure that the
component definitions are registered on the Siebel Gateway Name Server. However, there
are two considerations: First, because the Siebel Sales component group does not contain any
batch components, you will not synchronize here. This will confirm that only batch
components require synchronization. Second, synchronization registers assigned component

groups rather than enabled component groups, so once you have performed an initial
synchronization, enabling a component group does not require an additional synchronization.
h. Click the Servers view link tab.
i. In the middle applet, query for the Sales Object Manager (ENU). Does the Sales Object
Manager (ENU) appear? Why or why not?
j. Log out of Siebel Call Center.
2. You will next restart the Siebel Server service in order for the assignments to take effect.
a. In the Services window, right-click the Siebel Server [Siebel_OUsrvr] service and select
Stop. It takes some time to stop, so this is safer than using the Restart command. If you
receive a timeout error, select Action > Refresh to refresh the view until the service is

completely stopped.
b. Once the Siebel Server service has stopped, right-click the Siebel Server [Siebel_OUsrvr]
service and select Start.
c. Minimize the Services window.
3. You will next test your changes by trying to access Siebel Sales on your local machine. If you
successfully enabled and assigned the component group, you should be able to get to the login
screen. However, remember that the Siebel Server service takes several minutes to start up, so be
patient.
a. Start Internet Explorer.
b. Enter an address of http://localhost/sales_enu. You should get the Siebel Sales login screen.
c. Close Internet Explorer.
4. You will finally modify the startup type for this component and disable it on the server. This is a
somewhat artificial exercise as you would usually do one or the other, but this allows you to
practice both steps at once.
b. Navigate to Administration - Server Configuration > Servers.
c. In the middle applet, locate and select the Sales Object Manager (ENU) component.
d. Click Manual Start. This modifies the component so it does not come online when the
server first starts up, but instead waits for you to manually start it. Combined with the
Component Shutdown feature in server management, this allows you manually start up
certain components only when they are needed and shut them down afterwards, saving
resources on impacted servers.
e. Navigate to Administration - Server Management > Components.
f. Query for Sales Object Manager (ENU).
g. Click Shutdown. This shuts down the component so it no longer accepts new requests.
h. Open a browser and confirm that the address http://localhost/sales_enu no longer brings up a
login screen.
i. Return the Siebel Call Center and click the Enterprises view link.
j. Query for Siebel Sales in the component groups.
k. In the Component Group Assignments applet, click Disable. This disables the component
group on the Siebel Server. The advantage of disabling a component group instead of

unassigning it is that a disabled component group continues to keep track of parameter

overrides, while unassigning a component group removes all parameter overrides.
5. Remain logged in to Siebel Call Center. Although the disabling of the component group does not
take effect until you restart the Siebel Server service, you shut down the component so it is not
taking up your resources, so you can wait to restart the service until you have performed
additional administration in a later lab.

Solutions 9-2 Enabling and Assigning Component

Groups (Guided)
Answers
1.a. Is the Siebel Sales component group currently enabled in the enterprise?
Yes.
1.e. Examine the bottom right applet. Is the Siebel Sales component group assigned to OUsrvr?
Yes.

1.f. Is the Siebel Sales component group enabled on OUsrvr?
No.
1.i. In the middle applet, query for the Sales Object Manager (ENU). Does the Sales Object
Manager (ENU) appear? Why or why not?
It does not appear because you need to restart the Siebel Server and Siebel Gateway Name
Server services in order for any assignment changes to take effect.

Module 10: Server Management
Lab 10-1 Exploring Server Management (Unguided)
Goals To become familiar with the Server Management views
Time 5 - 10 minutes
Instructions:



Lab 10-1 Exploring Server Management (Guided)
Goals To become familiar with the Server Management views
Time 5 - 10 minutes
Instructions:
In this lab you will familiarize yourself with the Server Management views to help you understand

how to monitor a Siebel enterprise.
1. If necessary, start Siebel Call Center using the Web client and log in as SADMIN/SADMIN.
2. You will first examine the Administration – Server Management > Enterprises view. This view
allows you to examine the states of the servers in the enterprise, and components on each server.
a. Navigate to Administration - Server Management > Enterprises.
b. Scroll down to the Components list at the bottom of the view. Note that from this view you
can pause or shut down individual components. What is the current state of the following:
i. Server Manager?
ii. Call Center Object Manager (ENU)?
iii. File System Manager?
iv. Sales Object Manager (ENU)?
3. You will next examine the other views to note the similarities and differences among the various
monitoring views.
a. Click the Servers view link. How is the information displayed here different from the
information displayed in the Enterprises view?
b. Click the Log tab. This shows a list of activities logged by the server.

c. Click the Components view link. Once again you see the states of the components in the
enterprise. What additional information about the components is available here?
d. Click the Tasks view link. This view lists the tasks that are running or have run on the
enterprise. What additional information about tasks is available here?
e. Click the Sessions view link. This view lists user sessions and activity.

f. Select the running instance of the SCCObjMgr_enu component. What is the OM Login for
this instance?
g. Click the State Values view tab in the bottom applet. What is the current value of the Applet
Name state value?
h. Select Help > About View. Does the applet name match what you found above?
i. Click OK to close the About View window.
4. Remain logged in to Siebel Call Center.

Solutions 10-1 Exploring Server Management (Guided)
Answers
2.b.i. Server Manager?
Running.
2.b.ii. Call Center Object Manager (ENU)?

Running.
2.b.iii. File System Manager?

Online.
2.b.iv. Sales Object Manager (ENU)?

Shutdown.
3.a. Click the Servers view link. How is the information displayed here different from the
information displayed in the Enterprises view?
This view shows the component groups assigned to the server, and shows the component
states by component group.
3.c. Click the Components view link. Once again you see the states of the components in the
enterprise. What additional information about the components is available here?
The tasks that are currently running that component, the state values of that component,
and runtime statistics about the component.
3.d. Click the Tasks view link. This view lists the tasks that are running or have run on the
enterprise. What additional information about tasks is available here?
The task logs, parameters, state values, and runtime statistics.
3.f. Select the running instance of the SCCObjMgr_enu component. What is the OM Login
for this instance?
SADMIN
3.g. Click the State Values view tab in the bottom applet. What is the current value of the
Applet Name state value?
Completed: Server Session List Applet (PositionOnRow). This indicates that you just
selected a row on the server session list applet.
3.h. Select Help > About View. Does the applet name match what you found above?
Yes; the name of the applet you found in the previous step appears in the Help > About
View view.


Lab 10-2 Using the Command-Line Server Manager

(Unguided)
Goals To practice using the command-line Server Manager.
Time 5 - 10 minutes

Instructions:
In this lab, you will log in to the command-line server manager and familiarize yourself with its
function. The command-line server manager is useful for scripting server interaction. For more
details on using the command-line server manager, consult the Siebel System Administration Guide.
1. Open a Command Prompt window and enter the command hostname to determine your machine
name.
2. Enter the command below (replacing <Machine Name> with the name you recorded above).
Case is important.
Note: The Server Manager command-line program resides in the E:\OUsea\siebsrvr\BIN
directory. This directory has been added to the PATH environment variable so you do not have
to change directories.
srvrmgr /g <Machine Name> /e Siebel /s OUsrvr /u SADMIN /p

SADMIN
Note: When you are successfully connected to Server Manager, you will see the prompt:
srvrmgr:OUsrvr>
3. Execute the list tasks, list parameters, list component groups, and list servers for component
group Workflow commands to familiarize yourself with the command-line interface.
4. Enter quit to disconnect from the server.
5. Close the Command Prompt window.


Lab 10-2 Using the Command-Line Server Manager

(Guided)
Goals To practice using the command-line Server Manager.

Instructions:
In this lab, you will log in to the command-line server manager and familiarize yourself with its
function. The command-line server manager is useful for scripting server interaction. For more
details on using the command-line server manager, consult the Siebel System Administration Guide.
1. Open the Command Prompt window by selecting Start > Programs > Accessories > Command
Prompt.
2. You will first log in to Server Manager by entering the appropriate values for your machine.
a. Enter the command hostname and record your machine name here:
b. Type the command below (replacing <Machine Name> with the name you recorded above)
and press ENTER. Case is important.
Note: The Server Manager command-line program resides in the D:\OUsea\siebsrvr\BIN
directory. This directory has been added to the PATH environment variable so you do not
have to change directories.
srvrmgr /g <Machine Name> /e Siebel /s OUsrvr /u SADMIN /p

SADMIN
Note: When you are successfully connected to Server Manager, you will see the prompt:
srvrmgr:OUsrvr>
c. View the list of Server Manager commands by entering help at the srvrmgr:OUsrvr>
prompt.
d. Review the commands. Is it possible to start up or shut down a server using these
commands? Why might you want to be able to do this?

3. You will next execute a few list commands to familiarize yourself with the data produced by the
command-line server manager.
a. At the srvrmgr:OUsrvr> prompt, enter list tasks to list the status of current tasks running on
your Siebel Server. Notice that there are several interactive and background tasks running on
your Siebel Server.
b. Enter list parameters to list parameter values for your Siebel Server.
c. Enter list component groups to list the enabled component groups on your Siebel Server.
d. You can create more complex lists as well. To list all servers where the Workflow
component group is enabled, enter list servers for component group Workflow. How many
Siebel Servers are listed?

4. Enter quit to disconnect from the server.
5. Close the Command Prompt window.

Solutions 10-2 Using the Command-Line Server

Manager (Guided)
Answers:
2.d. Review the commands. Is it possible to start up or shut down a server using these
commands? Why might you want to be able to do this?
Yes, you can start up or shut down a server from the command line. You might use this in a
script to assign a component group to a server, enable it, and then restart the server. Many
other answers are possible.

3.i. You can create more complex lists as well. To list all servers where the Workflow
component group is enabled, enter list servers for component group Workflow. How
many Siebel Servers are listed?
One. OUsrvr.


Lab 10-3 Invoking and Monitoring Jobs (Unguided)
Goals To synchronize components with the Gateway Name Server

To create a job template
To invoke and monitor a batch job on the server
Time 10 -15 minutes
Instructions:

In this lab, you will explore creating job templates and invoking and monitoring jobs. During this
process, you will need to perform an initial synchronization between the server and the Gateway
Name Server. This stores the component parameters and assignments on the Gateway Name Server.
Synchronization must be performed after an initial deployment and thereafter every time a
component group containing batch components is enabled or disabled on a server to ensure the
correct parameters for the batch component are stored in the gateway.
1. Use the Administration - Server Configuration > Synchronize view to synchronize components
on the server. This process takes about one minute to complete.
2. Create a job template with the values below. While it is not necessary to create a job template to
run a job, job templates are useful for repeating or frequently-run jobs to avoid having to re-enter
parameters.
Name Administrator Notification Template
Short Name AdmNotify
Component Siebel Administrator Notification Component
Description Sample Template
Note: Because all of the batch components from enabled component groups are available from
the component drop-down list, it is possible to submit a job for a component which is not
enabled on any server. This is intentional; the job will remain queued until a server with that
component enabled becomes available.
3. Add the following parameters to the job template.

Name Value
NotificationHandler AdminEmailAlert
Disable Notification True
The notification handler is the system alert alias used by this component; the Disable
Notification flag ensures that if this job fails, it will not generate an alert.
4. Navigate to Administration - Server Management > Jobs and create and submit a new job using
the job template you just created. Perform empty queries to determine when the job completes.

5. Remain logged in to Siebel Call Center for the next lab.

Lab 10-3 Invoking and Monitoring Jobs (Guided)
Goals To synchronize components with the Gateway Name Server

To create a job template
To invoke and monitor a batch job on the server
Instructions:

In this lab, you will explore creating job templates and invoking and monitoring jobs. During this
process, you will need to perform an initial synchronization between the server and the Gateway
Name Server. This stores the component parameters and assignments on the Gateway Name Server.
Synchronization must be performed after an initial deployment and thereafter every time a
component group containing batch components is enabled or disabled on a server to ensure the
correct parameters for the batch component are stored in the gateway.
1. You will first synchronize components on the server.

a. In Siebel Call Center, navigate to Administration - Server Configuration > Enterprises.
b. Click the Synchronize view tab. Since you have not yet synchronized any components, no
records are displayed.
c. Click the Synchronize button. You will see the clock/timer symbol, indicating that
synchronization is in progress. The process takes about one minute. When this completes,
server components appear in the Synchronize list.
d. Examine the list of components shown in the Synchronize list. Are all of these components
enabled on the server OUsrvr?
2. You will next create a job template to specify parameters for a job. While it is not necessary to
create a job template to run a job, job templates are useful for repeating or frequently-run jobs to
avoid having to re-enter parameters.
a. Click Job Templates in the view link bar.
b. In the Job Templates list, create a new Job Template with the following values. The
component generates database triggers for invoking workflows and other business process
automations. This will have no impact on your system at the moment, so it is an excellent
example you can practice with.
Name Administrator Notification Template
Short Name AdmNotify
Component Siebel Administrator Notification Component
Description Sample Template

Note: Because all of the batch components from enabled component groups are available
from the component drop-down list, it is possible to submit a job for a component which is
not enabled on any server. This is intentional; the job will remain queued until a server with
that component enabled becomes available.
c. In the Job Parameters list, create two new records and enter the following parameters in order
to successfully execute this job. Notice that when you step off the Privileged User Password
record, the password is obscured to protect it.
Name Value
NotificationHandler AdminEmailAlert
Disable Notification True
The notification handler is the system alert alias used by this component; the Disable
Notification flag ensures that if this job fails, it will not generate an alert.

d. Step off the record to save the newly created Job Template.
e. Notice in the Job Templates list that the newly created Job Template is enabled
automatically.
3. You will finally use the job template you just created to execute and monitor a job.
a. Navigate to Administration - Server Management > Jobs.
b. Create a new record. Note that the ID is automatically populated.
c. Click the Select button in the Component/Job field. The Components/Jobs pick applet is
shown. Note that the Administrator Notification Template is the first item listed. Job
templates are shown before components, but here you can select either a component or a job
template.
d. Select the Administrator Notification Template and click OK. Note that the job parameters
at the bottom of the screen are populated using the values from the template. Otherwise you
would have had to populate them manually.
e. Check the Repeating checkbox in the middle applet and step off the checkbox to commit the
change. Notice that you can now specify the repeat unit (seconds, minutes, hours, days,
weeks, months, or years), the repeat interval, and the number of repetitions.
f. Uncheck the Repeating checkbox and step off of it.
g. What is the current status of the job?
h. Click Submit Job to start the job. What is the current status of the job?
i. Perform an empty query. Because the views do not automatically update, you must manually
refresh the view. The job should complete with a status of Success after a few moments.
j. Click the Tasks link. If necessary, query to locate the Administrator Notification task. This is
another location where you can monitor the progress of a job. The Tasks view has the
advantage that it shows more information; for instance: the process ID, start time, and end
time. However, it has the disadvantage that it shows all tasks, not just jobs (tasks run in batch
mode).
4. Remain logged in to Siebel Call Center for the next lab.

Solutions 10-3 Invoking and Monitoring Jobs (Guided)
Answers
1.d. Examine the list of components shown in the Synchronize list. Are all of these components
enabled on the server OUsrvr?
No. Initial synchronization registers all of the components contained in component groups
enabled in the enterprise, so the list contains many more components than are enabled on
our server, OUsrvr.

1.e. What do you think happens when you try to run a job that isn’t registered as available on
any of the available servers?
Two possible answers are: Either you get an error message when you submit the job, or the
job is queued until a server with that component enabled becomes available. In fact, the
latter occurs; you can submit a job for a component that is not enabled on any server, and
the Gateway Name Server will queue that job until a server becomes available.
3.g. What is the current status of the job?

Creating.
3.h. Click Submit Job to start the job. What is the current status of the job?
Queued.


Module 11: Siebel Client Types
Lab 11-1 Exploring Siebel Client Types (Unguided)
Goals To explore the Siebel Web Client, Mobile Web Client, and Developer Web Client
To explore the Sample database
Instructions:



Lab 11-1 Exploring Siebel Client Types (Guided)
Goals To explore the Siebel Web Client, Mobile Web Client, and Developer Web Client
To explore the Sample database
Instructions:

In this lab you will compare the Siebel Web Client to the Siebel Mobile and Developer Web Clients.
The Siebel Mobile Web Client runs a local executable and connects to a local SQL Anywhere
database. The Siebel Developer Web Client runs the same executable as the Mobile Web Client, but
can also connect to the server database.
1. You will first examine some of the features of the Siebel Web client.
a. If necessary, start Siebel Call Center using the Web client and log in as SADMIN/SADMIN.
b. Select Help > Technical Support. What is the connect string for this client?
c. What is the full path to the repository file for this client?
d. Click OK to close the Technical Support window.

e. What is the HTTP address of this client? This is the address shown before the first question
mark.
f. Select File > Log Out to log out of the Siebel Web client and close the browser window.
g. Using Windows Explorer, navigate to D:\OUsea\siebsrvr\bin\enu. This is where the server
configuration files are located.
h. Use Notepad to open uagent.cfg. This is the configuration file for Siebel Call Center. Note
that almost all of the sections are marked as “client-only”, meaning that the parameters are
read from the component definitions.
i. Locate the section that starts with [Preload]. Which views are pre-loaded to improve
performance in the Siebel Call Center application?
j. Close uagent.cfg, not saving any changes.

2. You will next explore the Siebel Developer Web Client. This is a local executable that emulates
the functionality of the Siebel application and which connects to the server database without the
need to go through an object manager on the server. To prove this, you will disable the Siebel
Server service and still use the Developer Web Client.
a. Restore the Services window.
b. Right-click the Siebel Server [Siebel_OUsrvr] service and select Stop.
c. Once the service is stopped, minimize the Services window.
d. Confirm that you can no longer start Siebel Call Center by entering
http://localhost/callcenter_enu in the address bar. You should receive a server error.
e. From the Start menu, right-click Start > Programs > Siebel Web Client 8.0 > Siebel Call
Center – ENU and select Properties. This shortcut is the starting point for both the Siebel
Developer Web Client and the Siebel Mobile Web Client. What is the name of the executable

run by this shortcut?
f. Note that the /c flag passes the full path to the configuration file. What is the full path to the
configuration file? Does this match the path you found above?
g. Click Cancel to close the Properties window.

h. Select Start > Programs > Siebel Web Client 8.0 > Siebel Call Center - ENU to start the local
executable. The Siebel Call Center Mobile or Developer Web Client login screen is
displayed:
Note that it differs from the Siebel Web Client login screen in that it allows you to select a

database to use. The available databases are specified in the configuration file, as you will
see.
i. Enter SADMIN as the User ID.
j. Enter SADMIN as the password.
k. Select the Server database from the drop-down list. This is only available to the Developer
Web Client; the Mobile Web Client only lists the local and sample databases by default.
l. Click OK. After a few seconds, you are logged in to the Developer Web Client. What is the
HTTP address shown in the address bar?
m. Select Help > Technical Support. What is the connect string for this client?

n. What is the full path to the repository file for this client?
o. Click OK to close the Technical Support Window.

p. Navigate to Administration – Server Configuration > Enterprises. You can still enable,
disable, and assign component groups using the Dedicated Web client.
q. Navigate to Administration – Server Management > Servers. What do you notice about the
state of the server?
r. Log out of the Dedicated Web Client.

s. Start the Siebel Server service.
t. Once the Siebel Server service has fully started, log back in to the Dedicated Web Client and
navigate to Administration - Server Management > Servers. The server status is now visible.
u. Log out of the Dedicated Web Client.
3. You will now explore the Siebel Mobile Web Client. This client may be used to connect to any
local Siebel database. Oracle provides a sample Siebel database as part of the installation, so you
will explore it.
a. Select Start > Programs > Siebel Web Client 8.0 > Siebel Call Center – ENU.
b. Enter the following parameters and click OK to log in.
User ID SADMIN
Password SADMIN
Connect to Sample
c. What is the connect string for this client?
Hint: Use Help > Technical Support.
d. What is the full path to the repository file for this client?

e. Explore the client and notice that the database is populated with accounts, contacts,
employees, and a large amount of other data. You will be using the Mobile Web Client with
this database frequently in future labs in order to have some exposure to sample data.
f. Log out of the Siebel Mobile Web Client.

Solutions 11-1 Exploring Siebel Client Types (Guided)
Answers
1.b. What is the connect string for this client?
Siebel_DSN.
1.c. What is the full path to the repository file for this client?
D:\OUsea\siebsrvr\objects\enu\siebel.srf.
1.e. What is the HTTP address of this client?

http://localhost/callcenter_enu/start.swe
1.i. Locate the section that starts with [Preload]. Which views are pre-loaded to improve
performance in the Siebel Call Center application?
The Opportunity List View and the All Service Request List View. If the Siebel QuickStart
agent is enabled, preloaded views are cached the first time the application starts up. In
subsequent application sessions, navigation to a preloaded view is faster. See the Siebel
Performance Tuning Guide for more information.
2.e. What is the name of the executable run by this shortcut?

siebel.exe.
2.f. What is the full path to the configuration file? Does this match the path you found above?
D:\OUsea\Client\Bin\ENU\uagent.cfg. No; it does not mach the path found before. The
siebsrvr directory has been replaced by the Client directory. The Siebel Web Client uses a
different configuration file from that used by the Mobile and Developer Web Clients.
2.l. What is the HTTP address shown in the address bar?

http://localhost:8080/start.swe. This is the fastest way to tell that you are not using the
“plain” Web client. Both the Mobile and Developer Web Clients have a port number in
their HTTP addresses.
2.m. What is the connect string for this client?

SEAW Siebel. The Siebel Developer Web Client uses a different connect string from the
server.
2.n. What is the full path to the repository file for this client?
D:\OUsea\Client\objects\enu\siebel.srf. The Siebel Developer Web Client uses a different
repository file from the server.
2.q. What do you notice about the state of the server?

Its state is unavailable, which makes sense because we shut it down.

3.c. What is the connect string for this client?

D:\OUsea\Client\sample\UTF8\sse_samp.dbf –q –m –x NONE –gp 4096 –c40m –ch60m.
This is a local SQL Anywhere database.
3.d. What is the full path to the repository file for this client?
D:\SUsea\Client\objects\enu\siebel.srf.

Module 12: Securing Access to the Application
Lab 12-1 Securing Access to the Application (Unguided)
Goals To add a login and user to the database
Instructions:
Due to the fact that this lab uses database utilities to update the Siebel database, there is no Unguided

version of it. Please turn the page and do the Guided version.


Lab 12-1 Securing Access to the Application (Guided)
Goals To add a login and user to the database
Instructions:
In this lab, you will add a user using database authentication. Configuring LDAP or ADSI

authentication is beyond the scope of this course.
1. You will now add a user to the database and confirm that this grants the user access to the
application using database authentication.
a. Start Siebel Call Center using the Web client and log in as SADMIN/SADMIN.
b. Navigate to Administration - User > Users.
c. Create a new user with the following values:
Last Name Fermi
First Name Ernest
User ID EFERMI
Responsibility Siebel Administrator
e. Attempt to log in to Siebel Call Center as EFERMI/EFERMI. What happens? Why?
f. Use Notepad to open D:\Labs\Essentials\add login for PPENGUIN.sql.

i. Use Windows Explorer to navigate to D:\Labs\Essentials.
ii. Right-click add login for PPENGUIN.sql and select Open With > Notepad.
iii. If Notepad is not listed, select Open With > Choose Program and select Notepad from
the list of programs.
g. Examine add login for PPENGUIN.sql. This is a SQL script created to add users to the
Microsoft SQL Server database. Based on your RDBMS and or DBA standards, your scripts
may look different.
h. Press CTRL+A to select all of the text in the document.
i. Press CTRL+C to copy all of the text in the document.
j. Close add login for PPENGUIN.sql, not saving any changes.
k. Select Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Express. This is the database management tool used in the classroom. Your company’s
installation will use a different tool.

l. In the Connect to Server window, enter or confirm the following values:

Server Name localhost
Authentication SQL Server Authentication
Login sa
Password sa1
Remember password Checked
m. Click Connect. After a few moments, you should be successfully logged in to Microsoft
SQL Server Management Studio Express.
n. Click the New Query button in the upper left part of the screen. A query pane opens on the
right.
o. Click anywhere within the query pane to select it and then press CTRL+V to paste your

script.
p. Change every instance of PPENGUIN to EFERMI. You should make 4 replacements.
q. Click Execute. The script should execute successfully. If it does not, check your editing and
try again, or contact your instructor.
r. Select File > Exit to close Microsoft SQL Server Management Studio Express.
s. Attempt to log in to Siebel Call Center as EFERMI/EFERMI. What happens? Why?

Solutions 12-1 Securing Access to the Application

(Guided)
Answers
1.e. What happens? Why?
The user ID or password that you entered is incorrect. EFERMI has not yet been given a
database login.
1.s. What happens? Why?

You successfully log in because EFERMI has been added as a database user.


Module 14: Siebel Application Architecture
Lab 14-1 Exploring Relationships in the Application

Architecture (Unguided)
Goals To practice using About View to determine object definitions.

To observe how UI object definitions reference business object definitions.

Instructions:
In this lab, you will gain a better understanding of the nature of the relationships between the user
interface (UI), business, and data layers of the Siebel application. You will map the UI objects to
business objects. As you complete this lab, think about the relationships between screens, views, and
applets at the UI layer, and business objects and business components at the business layer.
1. Identify some of the major application architecture objects being used for the Opportunities
Screen. Enter your responses into this diagram:
a. Open Siebel Call Center using the Siebel Developer Web Client and log in as
JRUBIN/JRUBIN to the Sample database.

b. Navigate to the Opportunities List view use Help > About View to complete the job aid
above.
2. Use Help > About View to identify the views and related business objects for selected contact
views.
Navigation This View. . . . . . references this
Business Object
Contacts Home
Contacts List

Consumers List
Personal Contacts
List
3. Based on your work so far in this lab, how many Business Objects do you think can be displayed
in a view?
One
Many
4. How many views can display the same business object?

One
Many
5. Examine the relationship between applets and business components. Identify the applet and
business components used in the Service Request Calendar view. Applets reference business
components that are contained within a business object.
a. Navigate to Service Requests > Service Request List > Calendar.
b. What are the names of the Applets?
________________________________________________________________________
c. What are the names of the Business Components?
d. Based on your work so far in this lab, how many business components map to an applet?
One
Many

e. How many applets can reference a given business component?

One
Many
6. Log out of all Siebel Call Center sessions.

Solutions 14-1 Exploring Relationships in the

Application Architecture (Unguided)
Answers:
1.

2. Identify the views and related business objects for selected contact views.
Business Object
Contacts Home Contact Screen Homepage Contact
View
Contacts List Visible Contact List View Contact
Consumers List Consumer List View Consumer

Personal Contacts Personal Contact List View Contact(Personal)
List
3. Based on your work so far in this lab, how many Business Objects do you think can be
displayed in a view?
One
4. How many views can display the same business object?

Many
5.b. What are the names of the Applets?

Service Request Detail Applet; eCalendar Monthly Applet Without Employee
5.c. What are the names of the Business Components?

Service Request and Action
5.d. Based on your work so far in this lab, how many business components map to an applet?
One
5.e. How many applets can reference a given business component?

Many


Lab 14-1 Exploring Relationships in the Application

Architecture (Guided)
Goals To practice using About View to determine object definitions.

To observe how UI object definitions reference business object definitions.

Instructions:
In this lab, you will gain a better understanding of the nature of the relationships between the user
interface (UI), business, and data layers of the Siebel application. You will map the UI objects to
business objects. As you complete this lab, think about the relationships between screens, views, and
applets at the UI layer, and business objects and business components at the business layer.
1. In this step, you will identify some of the major application architecture objects being used for
the Opportunities Screen. For each question in this step, enter your response into this diagram:
JRUBIN/JRUBIN to the Sample database.

b. View the application title in Internet Explorer’s banner (located at the top of the browser
window). Enter the Application name into the diagram.
c. Navigate to Opportunities > List.
d. Select Help > About View. Enter the names for Screen, View, Applets, Business Object and
Business Components into the diagram.
e. Click OK to close the About View window.
2. In this step, you will explore the relationship between views and business objects in various
contacts views.
a. Identify the views and related business objects for the selected contact views.
i. Click the Contacts tab.
ii. Use the hyperlinks in the Link bar to select each of the views listed under the Navigation
column in the table, below. For each navigation path, determine the name of the view and

the Business Object it references. For assistance, use About View. Enter your responses
directly into this table:
Business Object
Contacts Home
Contacts List
Consumers List
Personal Contacts
List
b. Based on your work so far in this lab, how many Business Objects do you think can be
One
Many
c. How many views can display the same business object?
One
Many

3. In this step, you will consider the relationship between applets and business components. You
will identify the applet and business components used in the Service Request Calendar view.
Applets reference business components which are contained within a business object.
a. Navigate to Service Requests > Service Request List > Calendar. How many applets are
displayed?
________________________________________________________________________
b. Select Help > About View. What are the names of the Applets?
________________________________________________________________________
c. What are the names of the Business Components?

d. Based on your work so far in this lab, how many business components map to an applet?
One
Many
e. How many applets can reference a given business component?
One
Many
4. In this step, you will explore screen navigation available in the application. Screens are
associated with major functional areas of the enterprise, such as Accounts, Contacts, and
Opportunities. You access screens explicitly through Screen Tabs or the Site Map (you can also
access them implicitly when you drill down on an object that takes you to a view in a different
screen). Screen object definitions specify the default view that appears when a tab is clicked.
Screens group views together to enable users to quickly access the data they require by
navigating to an area of functionality and be taken to the appropriate view.
a. Note the number of screens that appear as screen tabs for JRUBIN.
b. Click the Site Map button to display the Site Map. Approximately how many screens appear
in the Site Map?
15
30
60+
c. Why might the number of screens accessible as screen tabs be less than the number
accessible from the Site Map?
5. In this step, you will examine administration views to observe references to business objects.
Screens may contain one or many views, each of which references a business object. However,
screens themselves do not directly map to business objects.
a. Log out of the Siebel Call Center session where you are logged in as JRUBIN.

b. Start another Siebel Call Center session using the Siebel Developer Web Client and logging
in as SADMIN/SADMIN to the Sample database.
c. Navigate to Administration - Application > State Models. Which business object is
displayed?
d. Navigate to Administration - Application > Responsibilities. Which business object is

displayed?
e. Are different business objects being displayed under the System Administration Screen? If so
why might this be the case?

6. Log out of all Siebel Call Center sessions.

Solutions 14-1 Exploring Relationships in the

Application Architecture (Guided)
Answers:
1.

2.a.ii. Use the hyperlinks in the Link bar to select each of the views listed under the Navigation
column in the table, below. For each navigation path, determine the name of the view and the
Business Object it references. For assistance, use About View. Enter your responses directly
into this table:
Business Object
Contacts Home Contact Screen Homepage Contact
View
Contacts List Visible Contact List View Contact

Consumers List Consumer List View Consumer
Personal Contacts Personal Contact List View Contact(Personal)

List
2.b. Based on your work so far in this lab, how many Business Objects do you think can be
One
2.c. How many views can display the same business object?
Many
3.a. Navigate to Service Requests > Service Request List > Calendar. How many applets are
displayed?
2. Due to your screen resolution, it is possible, that you may only see one applet.
3.b. Select Help > About View. What are the names of the Applets?
Service Request Detail Applet; eCalendar Monthly Applet Without Employee
3.c. What are the names of the Business Components?

Service Request and Action
3.d. Based on your work so far in this lab, how many business components map to an applet?
One
3.e. How many applets can reference a given business component?

Many

4.a. Note the number of screens that appear as screen tabs for JRUBIN.
7
4.b. Click the Site Map button to display the Site Map. Approximately how many screens appear
in the Site Map?
60+
4.c. Why might the number of screens accessible as screen tabs be less than the number
accessible from the Site Map?
The screen tabs typically show only the more commonly used screens. Also, note that the
screen tabs displayed is determined by the responsibilities associated with the user.
5.c. Navigate to Administration - Application > State Models. Which business object is

displayed?
State Model
5.d. Navigate to Administration - Application > Responsibilities. Which business object is

displayed?
Responsibility
5.e. Are different business objects being displayed under the System Administration Screen? If so
why might this be the case?
Yes. Administration screens are the exception in that the screen consists of a collection of
views that reference different business objects. In the case of other screens, the views
reference the same business object to maintain the same data context.


Module 15: Using Siebel Tools to Examine Object Definitions
Lab 15-1 Examining Object Definitions (Unguided)
Goal To practice examining object definitions in the repository.
Instructions:

Siebel Tools is an integrated environment for configuring Siebel applications. You use Siebel Tools
to modify standard Siebel object definitions and create new object definitions to meet your
organization’s business requirements. Siebel Tools is a declarative configuration tool, not a
programming environment. You use Siebel Tools to create and modify the object definitions
(metadata) that define Siebel applications. You do not modify the source code or directly write SQL.
In this lab, you will explore some of the basic Siebel Tools navigation features.
1. Start Siebel tools then log in as SADMIN/SADMIN connecting to the Sample database.
2. Select Application in the Object Explorer (OE). How many application object definitions are
listed in the Object List Editor (OBLE)?
3. Explore child object types.

a. Expand the parent Application object type.
b. How many child object types are listed for the Application object type?
4. Navigate to Screen :: Contacts Screen | Screen View and query for all screen view object
definitions whose names contain the string “Contact Detail”. Your query should return 14
records.

5. From the same view, query for all records whose names contain the string “Contact” AND the
string “View”. Your query should return 16 records.
6. From the same view, query for all records whose names contain the string “Contact” OR the
string “View”. Your query should return 67 records.
7. Use Columns Displayed to reorder columns for the screen views. Reorder columns to place the
Sequence column next to the View column.

8. Query for an object definition that contains special characters by selecting Business Component
in the OE and querying for the name Account (Contact Us).
9. Use the Flat tab to determine the parent screen of the Action Plan View screen view object. Use
the screen shot below as an aid.

10. Click the Types tab to restore the Object Explorer to the hierarchical display mode.
11. Leave Siebel Tools open for the next lab.

Solutions 15-1 Examining Object Definitions (Unguided)
Answers:
2.a. Select Application in the Object Explorer (OE). How many application object definitions
are listed in the Object List Editor (OBLE)?
28.
3.b. How many child object types are listed for the Application object type?
2, Page Tab and Screen Menu Item.

9. Use the Flat tab to determine the parent screen of the Action Plan View screen view object.
The Opportunities Screen.

Lab 15-1 Examining Object Definitions (Guided)
Goal To practice examining object definitions in the repository.
Instructions:

Siebel Tools is an integrated environment for configuring Siebel applications. You use Siebel Tools
to modify standard Siebel object definitions and create new object definitions to meet your
organization’s business requirements. Siebel Tools is a declarative configuration tool, not a
programming environment. You use Siebel Tools to create and modify the object definitions
(metadata) that define Siebel applications. You do not modify the source code or directly write SQL.
In this lab, you will explore some of the basic Siebel Tools navigation features.
1. In this step, you will start Siebel tools then log in as SADMIN connecting to the Sample
database.
a. Select Start > Programs > Siebel Tools 8.0 > Siebel Tools.
b. If necessary, select Agree to Terms in the licensing dialog box.
c. In the login screen, enter the following:
Field Value
User ID SADMIN
Password SADMIN
Connect to Server
The Object Explorer (OE) should be displayed. The Types tab in the OE should be selected
by default. Siebel object definitions are the metadata that define Siebel applications. Object
definitions are stored in a set of database tables called the Siebel Repository. The Siebel
Repository File (SRF) contains compiled object definitions for improved performance. Some
example object types are applets, views, business components, and tables. The Object
Explorer (OE) displays the types, and the Object List Editor (OBLE) displays definitions for
those types. Together, they provide a view into the objects and object definitions in the
repository database tables.
When you select an object type in the OE then create a new record in the OBLE, you are
presented a template in the OBLE for the object type currently selected in the OE. Once you
enter values into the template, you will have created a definition for the object. Hence,
“object definition”.

2. In this step, you will explore the record counter. Many objects in tools are displayed as
individual records in the OBLE. The total number of records currently displayed can be
determined by viewing the record counter, which is visible immediately underneath the OBLE.
a. Select Application in the OE. How many application object definitions are listed in the
Object List Editor (OBLE)?
b. In cases where a large number of records are present, you can cause the record counter to
numerate from the end of the list.
i. Select Table in the OE.
ii. Use the vertical scrollbar at the far right of the OBLE to navigate to the last record.
To do so, select the slider control inside the vertical scrollbar and pull the slider all

the way down to the bottom of the vertical scrollbar.
iii. Slowly scroll up.
iv. Observe the record counter behavior.
3. In this step, you will learn how Tools indicates the active object definition.
a. Select Application in the OE.
b. Select the Siebel Universal Agent object definition in the OBLE by clicking the row tab to
the left of the record. What visual cues indicate that a definition has been selected?
4. In this step, you will explore child object types. Object definitions have hierarchical relationships
called parent-child relationships. For example, when you expand an object type in the OE, such
as Applet, you see child object types, including Applet Method Menu Item, Applet Browser
Script, Applet Server Script, and Applet Toggle. Parent-child relationships between these objects
imply that the child object is in, or belongs to the parent object, but it does not imply inheritance
among objects. The set of properties of a parent object is generally unrelated to the set of
properties of a child object.
The Types tab in the OE shows the object hierarchy. Clicking the plus sign (+) to the left of an
object type displays all the child object types of the top-level object type. Clicking the minus
sign (–) to the left of an object type collapses all its child object types. By default, not all object
types are visible in the Object Explorer. Later in this course you will learn how to show and hide
additional object types.

a. Expand the parent Application object type.
b. How many child object types are listed for the Application object type?

5. In this step, you will query to display all the page tabs that are included in the Siebel Universal
Agent application.
a. Select Application :: Siebel Universal Agent | Page Tab. This notation means to first select
the Application object type in the OE, next select the Siebel Universal Agent record in the
OBLE, and then select the Page Tab child object type in the OE.
b. Perform a null query to ensure that all the Page Tab child object definitions are listed.
i. From the application-level menu, select Query > New Query (or click the New Query
button ).
ii. Select Query > Execute Query (or click the Execute Query button ).
iii. Based on the number of child page tab object definitions displayed, what can you
infer about the object definition’s relationship with the parent Page Tab object type?
There can be zero to many object definitions for a given object type.
There can only be one object definition for a given object type.
6. In this step, you will navigate to Screen :: Contacts Screen | Screen View. Then, you will use a
wildcard to query similar items. A number of common operators are available, such as =, >, <,
<>, LIKE, etc. You can also use AND, OR, and NOT to issue a compound query. By default,
Siebel Tools queries are case sensitive. For more information, reference Using Siebel Tools.
a. Select Screen in the OE.
b. Click anywhere in the OBLE.
c. Click the New Query button.
d. Enter Contacts Screen in the name property.
e. Click the Execute Query button.
f. Expand the Screen object type in the OE.

g. Select Screen View in the OE. Your interface should look similar to this:

h. Query for all screen view object definitions named “Contact Detail”. To run this query,
bracket the string with asterisks. For example *Contact Detail*. Your query should return 14
records.
i. Now use an operator in your query: *Contact* AND *Detail*. Your query should return 16
records. AND returns all strings, even those that are merely concomitant, not contiguous.
j. Use the OR operator. Query *Contact* OR *Detail*. Your query should return 67 records.
k. Query for an object definition that contains special characters.
i. Select Business Component in the OE.
ii. In the Name property of the OBLE, query for 'Account (Contact Us)'. Ensure you
bracket the query with single quotes.
7. In this step, you will use Columns Displayed to reorder columns. When working in Tools, it is
often useful to display and reorder columns to only display properties you seek, or to move
desired properties into the immediately viewable area of the OBLE.
a. Reorder columns to place the Sequence column next to the View column.
i. Right-click anywhere in the Screen Views window.
ii. Select Columns Displayed.

iii. Select Sequence in the Displayed columns dialog box, and use the arrows to move it
to follow immediately after View.

iv. Click OK.
v. Observe the change in the OBLE. You should see the Sequence property immediately
to the right of the View property. If necessary, use the OBLE’s horizontal scroll bar.
8. In this step, you will use Siebel Tools hyperlinks to quickly navigate between related objects. For
example, the UI layer Account Entry Applet references the business layer Account business
component, which in turn references the data layer S_PARTY table. In Tools, these references
are manifested as hyperlinks.
a. Select Applet :: Account Entry Applet. Querying for a specific object definition is a quick
way to access and isolate it (rather than scrolling). What is the value of the Business
Component property?
b. Drill down to the Account business component by clicking the Account hyperlink.
c. Identify the value of the table property. When working with a frequently viewed property,
such as Table, use Columns Displayed to move the property into the immediately viewable
area of the OBLE, thus avoiding horizontal scroll bar use. Additionally, you can drag and
drop column headers to re-order them. What is the value of the Table property?
d. Drill down on the Table property. Note that you have now navigated from the UI layer,
through the business layer to the data layer via hyperlinks.

e. Click the back arrow to return to the Account business component.
9. In this step, you will use Flat tab to display object types (parent and child) in a single,
alphabetically-arranged list, without displaying the parent-child relationship. When Flat tab is
used, if the object selected is the child in a parent/child relationship, additional parent
information is included in the OBLE that is not present when the Type tab is used. For example,
the Screen View object is the child of the Screen object type. In flat tab, the Parent Screen
property provides direct hyperlink access to the parent:

In this screen print, you can also see that if there are multiple parents that reference the same
child, then the child is repeated in flat view for each parent that references it. That is why the
screen view A Account Partner View has more than one entry in the list.
The Flat tab is particularly helpful in finding a child object with an unknown parent. For
example, if you created a new field but do not remember what business component it is in, you
can select the Field object type in the Flat tab and search the Name property for the field name in
question.
a. Select the Flat tab in the OE.
b. Select the Screen View object type. When you use the Flat tab, you may notice a slight delay
before the list of objects is displayed in the OBLE. This is due to that fact that all objects in
the repository of the type you select, such as Screen View, are displayed. This is significantly
different compared to when objects are viewed via Types tab, where the parent/child
relationship greatly reduces the number of object definitions to be retrieved and displayed.
c. In the OBLE, query for the screen view object definition named Action Plan View. What
screen is its parent (look for the Parent Screen property)?

d. Click on the Opportunities Screen hyperlink in the Parent Screen property of the OBLE.
What happens in the OE?
e. What happens in the OBLE?
f. Identify a Screen View that is referenced by multiple parent Screens.

i. Select the Screen View object type in the OE.
ii. Query for a screen view named Account List. Your query should return four object
definitions, each referenced by a different parent screen.
g. Click the Types tab to restore the Object Explorer to the hierarchical display mode.

10. Leave Siebel Tools open for the next lab.

Solutions 15-1 Examining Object Definitions (Guided)
Answers:
2.a. Select Application in the OE. How many application object definitions are listed in the
Object List Editor (OBLE)?
28
3.b. Select the Siebel Universal Agent object definition in the OBLE by clicking the row tab to
the left of the record. What visual cues indicate that a definition has been selected?

An active record indicator appears at the far left, and the record is highlighted in color.
4.b How many child object types are listed for the Application object type?
2, Page Tab and Screen Menu Item
5.b.iii. Based on the number of child page tab object definitions displayed, what can you infer about
the object definition’s relationship with the parent Page Tab object type?
There can be zero to many object definitions for a given object type.
8.a. Select Applet :: Account Entry Applet. Querying for a specific object definition is a quick
way to access and isolate it (rather than scrolling). What is the value of the Business
Component property?
Account
8.c. Identify the value of the table property. When working with a frequently viewed property,
such as Table, use Columns Displayed to move the property into the immediately viewable
area of the OBLE, thus avoiding horizontal scroll bar use. Additionally, you can drag and
drop column headers to re-order them. What is the value of the Table property?
S_PARTY
9.c. In the OBLE, query for the screen view object definition named Action Plan View. What
screen is its parent (look for the Parent Screen property)?
Opportunities Screen
9.d. Click on the Opportunities Screen hyperlink in the Parent Screen property of the OBLE.
What happens in the OE?
The Screen object type is automatically selected.
9.e. What happens in the OBLE?

The Opportunities Screen object definition is displayed.

Module 16: The Siebel Data Model
Lab 16-1 Exploring the Data Model (Unguided)
Goal To examine some of the tables, indexes, user keys, and foreign keys that
make up the Siebel Data Model.
Instructions:

In this lab, you will investigate the Siebel Data Model. You will gain a better understanding of the
relationships between the user interface, business and data layers. First, you will navigate Tools to
determine how a user interface object references an object in the business layer and how that object
references an object in the data layer. Next, you will explore Tools to gain a better understanding of
various table properties and system columns. You will then explore user keys and indexes for a
table. You will finally review the different extension tables and their parent/base tables.
1. Identify some of the major application architecture objects being used for the Opportunities
Screen. Determine the data table and column that map to the Opportunity Name list column in
the Opportunities List Applet. To assist with this task, you will use the job aid, below. Enter your
responses into the job aid, as directed.
Layer Object You’re
Step Tip for Finding Information Enter Value Here
looking For
Look for text label

User • List applet: column heading above
Interface 1 Display Name field in question
Objects
• Form applet: control label next to
field
2 Applet Name In UI: Help > About View
Business
3 In UI: Help > About View
Business Component
Objects
a. In Tools: <applet name> | List :: List |
List Column.
Business
4 Component b. Query Display Name for <display
Field name>.
c. Value you need is the Field property.


looking For
In Tools: Business Component :: <BC

name>| Field :: <field name>
IF Join property is empty
Enter base table name
Data 5 Table Name ELSE
Objects Enter value in Join property
Note: if query fails, Field property is

calculated. Try this: query Calculated
Value for *<field name>*

Table Column
6 name>| Field :: <field name>. Value in
Name
Column property.
a. If necessary, open Siebel Call Center using the Siebel Web Client and log in as
SADMIN/SADMIN.
b. Navigate to the opportunities list and enter the display name (for the opportunity name),
name of the list applet, and business component of the list applet into the job aid.
c. If necessary, start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample
database.
d. Enter the field corresponding to the Opportunity Name list column displayed in the applet
into the job aid.
e. Enter the table name and table column name for this field into the job aid.

2. Use Siebel Tools to inspect some important table properties, such as Required, Physical Type,
Length, and Default, for columns in the S_SRV_REQ table.
a. Select Table :: S_SRV_REQ | Column.
b. Examine the Type property. What two column types are included in this table?
c. Review the system columns that are representative of the columns that appear in all tables.
Of these system columns, which one is the primary key for this table?
d. Query the table for all columns that have Physical Type of Date Time. What column in
S_SRV_REQ has a Physical Type of Date Time?

3. Examine how user keys can enforce uniqueness when records are created. The user key is a
column or set of columns on a Siebel table that uniquely identifies a row.
a. Expose the User Key Column in Object Explorer.

b. Select Table :: S_OPTY | User Key :: S_OPTY _U1 | User Key Column. Identify which
columns make up this user key. Enter your answer directly into the diagram, below.
S_OPTY
ROW_ID

S_OPTY _U1
User Key
c. Open Siebel Call Center using the Siebel Developer Web Client and log in as
SADMIN/SADMIN to the Sample database.
d. Create a new opportunity record using the values in the table, below. Use Columns Displayed
to expose the Organization column. When adding the Organization via the shuttle applet, set
Capital Systems to the Primary, then remove Default Organization.
Property Value
Opportunity Name A Big Deal
Account Bay Builders
Organization Capital Systems
e. Create another new record with exactly the same values. Save it. What happens? Why?
f. Now, change Organization to ABC Reseller. You should be able to now step off the record
and save it since both records are unique.
g. Delete the records.
h. Log out of the Call Center application.
4. Use Siebel Tools to examine indices.

a. In Siebel Tools, select Table :: S_OPTY | Index to display the indexes for the table. How
many indices are defined for the S_OPTY table?
More than 10
More than 40

b. Select Table :: S_OPTY | Index :: S_OPTY_P1 | Index Column. Which column(s) make up
this index?
c. Which column(s) make up the S_OPTY_U1 index?
5. Practice locating foreign key columns. You will use this skill while exploring the Siebel Data
Model and in configuring the Siebel application.
a. Select Table :: S_SRV_REQ | Column to display the columns in the S_SRV_REQ table.
b. What is the Foreign Key Table for the AGREE_ID column? Enter your answer into the table
header on the right-hand side of the diagram.

S_SRV_REQ
ROW_ID
AGREE_ID
ROW_ID
FK PK
c. What column(s) serve(s) as a foreign key to S_PROD_INT? Enter your answer into the table
on the left-hand side of the diagram. Draw line(s) between the tables to indicate FK/PK
relationship(s).
S_SRV_REQ S_PROD_INT
ROW_ID
ROW_ID

6. Examine a 1:1 extension table to see how it relates to its base table.
a. Select Table :: S_SRV_REQ_X.
b. View the Type property. What is the type of the table?
c. What is the Base Table to S_SRV_REQ_X?
d. What is the value of the foreign key Column Name for the foreign key to S_SRV_REQ in the
S_SRV_REQ_X extension table?
e. Enter the column name into the table on the right-hand side of the diagram, above.

f. Draw a line between the tables to indicate the FK/PK relationship.
7. Identify any pre-built intersection tables that support the M:M relationship between project and
contacts. The query below works by selecting tables with foreign keys for either S_PROJ or
S_CONTACT.
a. Select the Flat tab and then select Column in the Object Explorer (OE).
b. Execute a compound query with the following values:
Property Value
User Key Sequence 1 OR 2
Foreign Key Table S_PROJ OR S_CONTACT
c. Sort the results of the query in ascending order for both the Parent Table list column and the
User Key Sequence list column.
d. Look for a Parent Table that appears in two adjacent rows where the Foreign Key Table
property is S_PROJ in one row and S_CONTACT in the other row. Note that the parent table
name has a _CON suffix. Which table satisfies these criteria?

e. Complete the diagram, below.

i. Enter the names of the two data tables that have a M:M relationship.
ii. Enter the name of the intersection table.
iii. Enter the names of the two FK columns in the intersection table.
Intersection
Data Table Table Data Table
S_PROJ S_CONTACT
ROW_ID
ROW_ID
ROW_ID

PK PK
FK FK
f. Select the Types tab to restore the Object Explorer to the hierarchical display mode.

Solutions 16-1 Exploring the Data Model (Unguided)
Answers:
1.
Job Aid: Identify Table Column That Supplies Data for an Applet Control
looking For
Look for text label

Opportunity Name

Objects • Form applet: control label next to
field

Opportunity List
Applet
Business
Business Component Opportunity
Objects
Name
List Column.
Business
Field name>.

name>| Field :: <field name> S_OPTY


Table Column NAME
Name
Column property.

2.b. Examine the Type property. What two column types are included in this table?
Data(Public) and System.
2.c. Of these system columns, which one is the primary key for this table?
ROW_ID.
2.d. What column in S_SRV_REQ has a Physical Type of Date Time?

POST_MORTEM_RVW_DT.
3.b. Select Table :: S_OPTY | User Key :: S_OPTY_U1 | User Key Column. Identify which
columns make up this user key. Enter your answer directly in to the diagram, below.
S_OPTY
BU_ID
NAME
ROW_ID
PR_DEPT_OU_ID

S_OPTY _U1
User Key
3.e. Create another new record with exactly the same values. Save it. What happens? Why?
The new record cannot be saved because a record with the same name, account, and
organization already exists. BU_ID stores a unique value to identify the business unit, in
this case, Bay Builders under Account. NAME stores Opportunity Name, in this case, A Big
Deal. PR_DEPT_OU_ID stores a unique value for the Organization. When an attempt is
made to save the record, a check is made against the S_OPTY _U1 user key. If all three
fields are identical, that is, the user key matches, the save is disallowed.
4.a. In Siebel Tools, select Table :: S_OPTY | Index to display the indexes for the table. How
More than 10
4.b. Select Table :: S_OPTY | Index :: S_OPTY_P1 | Index Column. Which column(s) make up
this index?
ROW_ID.
4.c. Which column(s) make up the S_OPTY_U1 index?

BU_ID, CONFLICT_ID, NAME, PR_DEPT_OU_ID

5.b. What is the Foreign Key Table for the AGREE_ID column? Enter your answer into the
table header on the right-hand side of the diagram.
S_SRV_REQ
ROW_ID S_ENTLMNT
AGREE_ID
FK ROW_ID PK
5.c. What column(s) serve(s) as a foreign key to S_PROD_INT? Enter your answer into the

table on the left-hand side of the diagram. Draw line(s) between the tables to indicate
FK/PK relationship(s).
PRDINT_ID
ROW_ID
ROW_ID
FK PK
6.b. View the Type property. What is the type of the table?
Extension.
6.c. What is the Base Table to S_SRV_REQ_X?

S_SRV_REQ.
6.d. What is the value of the foreign key Column Name for the foreign key to S_SRV_REQ in
the S_SRV_REQ_X extension table?
PAR_ROW_ID.
6.f. Draw a line between the tables to indicate the FK/PK relationship.
(see diagram, above).
7.d. Look for a Parent Table that appears in two adjacent rows where the Foreign Key Table
property is S_PROJ in one row and S_CONTACT in the other row. Note that the parent
table name has a _CON suffix. Which table satisfies these criteria?
S_PROJ_CON.

7.e. Complete the diagram, below.

Intersection
S_PROJ S_CONTACT
ROW_ID
ROW_ID
S_PROJ_CON
PROJ_ID
ROW_ID
CON_ID
PK PK

FK FK


Lab 16-1 Exploring the Data Model (Guided)
Goal To examine some of the tables, indexes, user keys, and foreign keys that
make up the Siebel Data Model.
Instructions:

In this lab, you will investigate the Siebel Data Model. You will gain a better understanding of the
relationships between the user interface, business and data layers. First, you will navigate Tools to
determine how a user interface object references an object in the business layer and how that object
references an object in the data layer. Next, you will explore Tools and gain a better understanding
of various table properties and system columns. You will then explore user keys and indexes for a
table. You will then review the different extension tables and their parent/base tables.
1. In this step, you will identify some of the major application architecture objects being used for
the Opportunities Screen. You will determine the data table and column that maps to the UI
Opportunity Name list column in the Opportunities List Applet. To assist with this task, you will
use the job aid, below. Enter your responses into the job aid, as directed.
looking For
Look for text label

Objects
• Form applet: control label next to
field
Business
Business Component
Objects
List Column.
Business
Field name>.


looking For



Table Column
Name
Column property.
a. If necessary, Open Siebel Call Center using the Siebel Web Client and log in as
SADMIN/SADMIN.
b. Navigate to Opportunities > List.
c. Locate the display name for the left-most column in the list applet. Enter your response into
the job aid.
d. Enter the Applet Name being used to display this list into the job aid.
e. Enter the Business Component into the job aid.
f. If necessary, start Siebel Tools and log in as SADMIN connecting to the Sample database.
g. Enter the Business Component Field into the job aid.
h. Enter the Table Name into the job aid. Remember to use Columns Displayed to move the
table property into the immediately viewable area of the OBLE.
i. Enter the Table Column Name into the job aid.

2. In this step, you will diagram some of the objects you just identified. The objects you identified
in an earlier lab are already completed for you in the diagram, below. The diagram illustrates
how data in a table column is used by a list column in an applet. The Opportunity business
component references a base table, which in turn contains many columns. One of these columns
contains data referenced by a business component field called Name. This field, in turn, is
referenced by the applet’s list column, and the data is displayed. Base tables will be covered in
more detail later in this course.
Refer to the job aid completed in the previous step to complete the values in the empty boxes.

3. In this step, you will inspect some important table properties, such as Required, Physical Type,
Length, and Default, for columns in the S_SRV_REQ table. The Table object type is metadata
about the physical tables in the underlying database management system. The column child
object type is metadata about the columns in those physical tables. As you have discovered with
objects at the UI layer and business layer, objects at the data layer are also represented in the OE
as object types with their definitions displayed in the OBLE.
a. Select Table :: S_SRV_REQ | Column. Most table columns in Siebel applications are data
columns. Sometimes called base columns, data columns provide the data for fields, or serve
as foreign keys that point to rows in other tables. You cannot modify the properties of data
columns.
b. Examine the Type property.
i. To simplify viewing, lock the Name property column in place by double-clicking the
Name property column heading

ii. Scroll to the Type property and note that the Name property remains in place. What
two column types are included in this table?
c. Review the system columns that are representative of the columns that appear in all tables.
i. Right-click anywhere in the lower window of the OBLE
ii. Click Sort Order.
iii. Sort by Type, descending.
iv. Of these system columns, which one is the primary key for this table? For assistance,
view the Primary Key property.
d. Query the Required property for True (checked). Is MODIFICATION_NUM a required

column?
Yes
No
e. Review the Physical Type and Length properties. There are several options for physical type
and length.
i. From the Tools application-level menu, select View > Windows > Properties
Window to open the Properties Window.
ii. Click the push-pin to auto-hide the properties window.

f. Query the table for all columns that have Physical Type of Date Time. What column in
S_SRV_REQ has a Physical Type of Date Time?
4. In this step, you will examine how user keys can enforce uniqueness when records are created.
The user key is a column or set of columns on a Siebel table that uniquely identifies a row. This
is in addition to the ROW_ID column, which is also unique. Below, you will see how the three
columns displayed under User Key Columns make up the S_OPTY_U1 user key.
a. Expose the User Key Column in Object Explorer.
i. Select View > Options > Object Explorer.
ii. Scroll down to Table and expand the Table object type.
iii. Expand the User Key object type and ensure User Key Column has a checkmark.

iv. Click OK.
v. Select Table :: S_OPTY | User Key to display the user keys for the table. When
querying for S_OPTY, ensure you query the Name property, not the Base Table
property. Which user keys are defined?

b. Select Table :: S_OPTY | User Key :: S_OPTY _U1 | User Key Column. Identify which
S_OPTY
ROW_ID

S_OPTY _U1
User Key
c. Log out of your current Call Center session.
d. Open Siebel Call Center using the Siebel Developer Web Client and log in as
e. Navigate to Opportunities > My Opportunities.
f. Create a new opportunity record using the values in the table, below. Use Columns Displayed
to expose the Organization column. When adding the Organization via the shuttle applet, set
Capital Systems to the Primary, then remove Default Organization.
Property Value
Opportunity Name A Big Deal
Account Bay Builders
Organization Capital Systems

g. Create another new record with exactly the same values. Save it. What happens? Why?
You should have received an error message similar to this:

h. Click OK to dismiss the warning.
i. Now, change Organization to ABC Reseller. You should be able to now step off the record
and save it since both records are unique.
j. Delete the record.
k. Log out of the Call Center application.
5. In this step, you will use Siebel Tools to examine indices. Index object definitions are metadata
representations of physical indices in the underlying database management system. Siebel
applications include a set of standard indices.
a. In Siebel Tools, select Table :: S_OPTY | Index to display the indexes for the table. How
More than 10
More than 40
b. Select Table :: S_OPTY | Index :: S_OPTY_P1 | Index Column. Which column(s) make up
this index?
c. Which column(s) make up the S_OPTY_U1 index?
6. In this step, you will practice locating foreign key columns. You will use this skill while
exploring the Siebel Data Model and in configuring the Siebel application.
a. Select Table :: S_SRV_REQ | Column to display the columns in the S_SRV_REQ table.

b. What is the Foreign Key Table for the AGREE_ID column? For assistance, use Columns
Displayed or the Properties window. Enter your answer into the table header on the right-
hand side of the diagram.
S_SRV_REQ
ROW_ID
AGREE_ID
ROW_ID

FK PK
c. Query the Foreign Key Table property for S_PROD_INT. What column(s) serve(s) as a
foreign key to S_PROD_INT? Enter your answer into the table on the left-hand side of the
diagram. Draw line(s) between the tables to indicate FK/PK relationship(s).
ROW_ID
ROW_ID
7. In this step, you will examine a 1:1 extension table to see how it relates to its base table. Base
tables and extension tables maintain a primary key / foreign key relationship. Extension tables
have a foreign key that references the primary key of its base table. PAR_ROW_ID reads as
“parent row ID”.
a. Select Table :: S_SRV_REQ_X.
b. View the Type property. What is the type of the table?

c. What is the Base Table to S_SRV_REQ_X?
d. What is the value of the foreign key Column Name for the foreign key to S_SRV_REQ in the
S_SRV_REQ_X extension table?
e. Select Table :: S_SRV_REQ_X | Column :: PAR_ROW_ID.

f. Enter the column name into the table on the right-hand side of the diagram, above.
g. Draw a line between the tables to indicate the FK/PK relationship.
8. In this step, you will identify any pre-built intersection tables that support the M:M relationship
between project and contacts. The query below works by selecting tables with foreign keys for

either S_PROJ or S_CONTACT.
a. Select the Flat tab and then select Column in the Object Explorer (OE).
b. Use Columns Displayed in the OBLE to move the Parent Table, Name, Foreign Key Table,
and User Key Sequence columns to the left side of the OBLE.
c. Execute a compound query with the following values:
Property Value
User Key Sequence 1 OR 2
Foreign Key Table S_PROJ OR S_CONTACT
d. Sort the results of the query in ascending order for both the Parent Table list column and the
User Key Sequence list column.
i. Right-click in the OBLE and select Sort Order.
ii. In the Sort Order dialog box select the Sort by field.
iii. Select Parent Table from the drop-down list.
iv. In the Then by field click the drop-down arrow and select User Key Sequence.
v. Accept the default Ascending for both fields.
vi. Click OK.
e. Look for a Parent Table that appears in two adjacent rows where the Foreign Key Table
property is S_PROJ in one row and S_CONTACT in the other row. Note that the parent table
name has a _CON suffix. Which table satisfies these criteria?

f. Complete the diagram, below.

i. Enter the names of the two data tables that have a M:M relationship.
ii. Enter the name of the intersection table.
iii. Enter the names of the two FK columns in the intersection table.
Intersection
S_PROJ S_CONTACT
ROW_ID
ROW_ID
ROW_ID

PK PK
FK FK
g. Select the Types tab to restore the Object Explorer to the hierarchical display mode.

Solutions 16-1 Exploring the Data Model (Guided)
Answers:
1.
Job Aid: Identify Table Column That Supplies Data for an Applet Control
looking For
Look for text label

Opportunity Name

Objects • Form applet: control label next to
field

Opportunity List
Applet
Business
Objects
Name
List Column.
Business
Field name>.

name>| Field :: <field name> S_OPTY


Table Column NAME
Name
Column property.

2.

3.b.ii. Scroll to the Type property and note that the Name property remains in place. What two
column types are included in this table?
Data(Public) and System
3.c.iv. Of these system columns, which one is the primary key for this table? For assistance, view
the Primary Key property.
ROW_ID.
3.d. Query the Required property for True (checked). Is MODIFICATION_NUM a required
column?
Yes
3.f. What column in S_SRV_REQ has a Physical Type of Data Time?

POST_MORTEM_RVW_DT.
4.a.v. When querying for S_OPTY, ensure you query the Name property, not the Base Table
property. Which user keys are defined?
S_OPTY_II, S_OPTY_U1.

4.b. Select Table :: S_OPTY | User Key :: S_OPTY _U1 | User Key Column. Identify which
S_OPTY
BU_ID
NAME
ROW_ID
PR_DEPT_OU_ID
S_OPTY _U1
User Key

4.g. Create another new record with exactly the same values. Save it. What happens? Why?
The new record cannot be saved because a record with the same name, account, and
organization already exists. BU_ID stores a unique value to identify the business unit, in
this case, Bay Builders under Account. NAME stores Opportunity Name, in this case, A Big
Deal. PR_DEPT_OU_ID stores a unique value for the Organization. When an attempt is
made to save the record, a check is made against the S_OPTY _U1 user key. If all three
fields are identical, that is, the user key matches, the save is disallowed.
5.a. In Siebel Tools, select Table :: S_OPTY | Index to display the indexes for the table. How
More than 10
5.b. Select Table :: S_OPTY | Index :: S_OPTY_P1 | Index Column. Which column(s) make up
this index?
ROW_ID.
5.c. Which column(s) make up the S_OPTY_U1 index?

BU_ID, CONFLICT_ID, NAME, PR_DEPT_OU_ID.
6.b. What is the Foreign Key Table for the AGREE_ID column? For assistance, use Columns
Displayed or the Properties window. Enter your answer into the table header on the right-
hand side of the diagram.
S_SRV_REQ S_ENTLMNT
ROW_ID
AGREE_ID
ROW_ID
FK PK

6.c. Query the Foreign Key Table property for S_PROD_INT. What column(s) serve(s) as a
foreign key to S_PROD_INT? Enter your answer into the table on the left-hand side of the
diagram. Draw line(s) between the tables to indicate FK/PK relationship(s).
PRDINT_ID
ROW_ID
ROW_ID
FK PK

7.b. View the Type property. What is the type of the table?
Extension.
7.c. What is the Base Table to S_SRV_REQ_X?

S_SRV_REQ.
7.d. What is the value of the foreign key Column Name for the foreign key to S_SRV_REQ in
the S_SRV_REQ_X extension table?
PAR_ROW_ID.
7.g. Draw a line between the tables to indicate the FK/PK relationship.
(see diagram, above).
8.e. Look for a Parent Table that appears in two adjacent rows where the Foreign Key Table
property is S_PROJ in one row and S_CONTACT in the other row. Note that the parent
table name has a _CON suffix. Which table satisfies these criteria?
S_PROJ_CON.
8.f. Complete the diagram, below.

Intersection
S_PROJ S_CONTACT
ROW_ID
ROW_ID
S_PROJ_CON
PROJ_ID
ROW_ID
CON_ID
PK PK
FK FK

Module 17: Siebel Business Components
Lab 17-1 Examining References Between Applets,

Business Components, and Tables (Unguided)
Goal To describe the key relationships between business components, fields, columns, and
tables in the Siebel Application Architecture.

Instructions:
In this lab, you will use the same method used in previous labs to identify all the major objects
involved in getting data from the data layer to the UI layer. This lab focuses on the business
component. You will navigate both the application and Tools in order to document the architectural
relationships for a business component called Internal Product.
1. Identify the table column name that provides data for the Product column in the Internal Product
List applet by filling out the job aid, below.
a. If necessary, open Siebel Call Center using the Siebel Developer Web Client and log in as
SADMIN/SADMIN connecting to the Sample database.
b. Navigate to Products > Internal Product List. Notice the Product column in the list applet.
c. Enter the display name, applet name, and business component name into the job aid, below.
d. If necessary, start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample
database.
e. Enter the business component field, table name, and table column into the job aid, below.

Job Aid: Identify Table Column Supplying Data for Applet Control
looking For
Look for text label

• List applet: column heading above
User 1 Display Name field in question
Interface • Form applet: control label next to
Objects field

Business

Component
Business
Objects
a. In Tools: <applet name> | List :: List
| List Column.
Business
b. Query Display Name for <display
4 Component
name>.
Field
c. Value you need is the Field
property.

Table Name
Data 5 ELSE


Table Column
Name
Column property.

2. Use Tools’ visualization feature to verify some of the mappings between business components
and tables you just identified. This feature provides a way to view relationships between entities
graphically, similar to the way entities are represented in an Entity Relationship Diagram (ERD).
a. Select Business Component :: Internal Product.
b. From the Tools application-level menu bar, select View > Visualize > View Details. Scroll
down slowly, then select the Name field in the left column. What table and column does it
reference?
c. What columns do the Part # and Unit of Measure fields reference?

d. Close the visualization window.

Solutions 17-1 Examining References Between Applets,

Business Components, and Tables (Unguided)
Answers:
1. Job Aid: Identify Table Column Supplying Data for Applet Control

looking For
Look for the text label:

Product
User • In a list applet, column heading
Interface 1 Display Name above the field in question
Objects • In a form applet, control label next

to the field
•
2 Applet In UI: Help > About View

Product List Applet
Business
Component Internal Product
Business
Objects a. In Tools: <applet name> | List :: List |
List Column. Name
4 Field
name> (from step 1).
Value you need is the Field property.

name>| Field :: <field name> S_PROD_INT
Data 5 Table ELSE
Note: if query for field fails, Field

property is calculated. Try this: query
Calculated Value for *<field name>*

6 Table Column name>| Field :: <field name>. Value in NAME
Column property.
2.b. From the Tools application-level menu bar, select View > Visualize > View Details. Scroll
reference?
S_PROD_INT table, NAME column

2.c. What columns do the Part # and Unit of Measure fields reference?
PART_NUM and UOM_CD columns


Lab 17-1 Examining References Between Applets,

Business Components, and Tables (Guided)
Goal To describe the key relationships between business components, fields, columns, and
tables in the Siebel Application Architecture.

Instructions:
In this lab, you will use the same method used in previous labs to identify all the major objects
involved in getting data from the data layer to the UI layer. This lab focuses on the business
component. You will navigate both the application and Tools in order to document the architectural
relationships for a business component called Internal Product.
1. In this step, you will identify the table column name that provides data for the Product column in
the Internal Product List applet. As you complete each step, use the instructions under the Tip for
Finding Information column of the job aid, below.
a. If necessary, open Siebel Call Center using the Siebel Developer Client and log in as
b. Navigate to Products > Internal Product List. Notice the Product column in the list applet.
c. Enter the Display Name in the job aid, below.
d. Select Help > About View.
e. Enter the Applet Name into the job aid, below.
f. Enter the Business Component Name into the job aid, below.
g. If necessary, start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample
database.
h. Using the UI Display Name that you identified earlier, enter the business component field
that the user interface references and enter the value of the Field property for this object
definition into the job aid, below.
i. Identify the Table Name for the data source then enter it into the job aid.
j. The value in the Column property in Tools is the table column referenced by the business
component. Enter this value into the job aid, below.

Job Aid: Identify Table Column Supplying Data for Applet Control
looking For
Look for text label

• List applet: column heading above
User 1 Display Name field in question
Interface • Form applet: control label next to
Objects field

Business

Component
Business
Objects
d. In Tools: <applet name> | List :: List
| List Column.
Business
e. Query Display Name for <display
4 Component
name>.
Field
f. Value you need is the Field
property.

Table Name
Data 5 ELSE


Table Column
Name
Column property.

2. In this step, you will use Tools’ visualization feature to verify some of the mappings between
business components and tables you just identified. This feature provides a way to view
relationships between entities graphically, similar to the way entities are represented in an Entity
Relationship Diagram (ERD).
a. Select Business Component :: Internal Product.
i. From the Tools application-level menu bar, select View > Visualize > View Details.
Scroll down slowly, then select the Name field in the left column. What table and
column does it reference?
ii. What columns do the Part # and Unit of Measure fields reference?

iii. Close the visualization window.
iv. If the Properties Window is open, close it now. To dock or close the Properties
Window, right-click in the properties window and select either Docked or Hide.
v. In Call Center, close About View.

Solutions 17-1 Examining References Between Applets,

Business Components, and Tables (Guided)
Answers:
1. Job Aid: Identify Table Column Supplying Data for Applet Control

looking For

User Product
• In a list applet, column heading
Interface 1 Display Name above the field in question
Objects • In a form applet, control label next

to the field
2 Applet In UI: Help > About View

Product List Applet
Business
Component Internal Product
Business
Objects a. In Tools: <applet name> | List :: List |
List Column. Name
4 Field
name> (from step 1).

name>| Field :: <field name> S_PROD_INT
Data 5 Table ELSE
Note: if query for field fails, Field

property is calculated. Try this: query
Calculated Value for *<field name>*

6 Table Column name>| Field :: <field name>. Value in NAME
Column property.
2.a.i. From the Tools application-level menu bar, select View > Visualize > View Details. Scroll
reference?
S_PROD_INT table, NAME column

2.a.ii. What columns do the Part # and Unit of Measure fields reference?
PART_NUM and UOM_CD columns


Module 18: Siebel Party Business Components
Lab 18-1 Exploring Relationships Between Party

Business Components and Tables (Unguided)
Goal To examine how person-related and organization-related business components store their
fields in S_PARTY and related tables.

Instructions:
Due to the question-and-answer nature of this lab, there is no Unguided version of it. Please turn the
page and do the Guided version.


Lab 18-1 Exploring Relationships Between Party

Business Components and Tables (Guided)
Goal To examine how person-related and organization-related business components store their
fields in S_PARTY and related tables.

Instructions:
At the beginning of this lab, you will examine two person-related party business components to
determine which tables they use to store their main data. You will examine this general structure:
Person-Related Party Business Component
Field X Field X Field X Field X
S_PARTY S_CONTACT S_USER S_EMP_PER

ROW_ID
PAR_ROW_ID
PAR_ROW_ID
PAR_ROW_ID
PK FK FK FK
Base Table Extension Tables – Record Data Stored Here
You will see how multiple party business components reference the same column in the same base
table. You will also see that extension tables contain most of the data needed by the party business
component. Since business component fields reference extension table fields directly, you may not
see S_PARTY in object definitions or properties. Rather, you will see the S_PARTY extension
table.
1. In this step, you will explore how a person-related party business component called Contact
references its extension tables. If necessary, start Siebel Tools and log in as SADMIN
connecting to the Sample database.
a. Select Business Component :: Contact.
b. Select View > Visualize > View Details. Scroll down slowly until you find First Name in the
left column and select it. What table and column does it reference?

c. About how many fields in the Contact party business component reference columns in the
S_CONTACT table? Pick one choice from the following three options.
Zero
One to ten
Greater than ten
d. Scroll down slowly until you find the S_EMP_PER table in the right column. Are there any
fields in the Contact business component that reference columns in the S_EMP_PER table?
If yes, list them.
e. Scroll down slowly until you find the S_USER table in the right column. Are there any fields

in the Contact business component that reference columns in the S_USER table? If yes, list
them.
f. Close the visualization window.
2. In this step, you will explore how a person-related party business component called Employee
references its extension tables. Note that both this party business component, Employee, and
Contact, the party business component you studied in the previous step, have S_PARTY as their
base table and, in many cases, reference the same extension table for their data.
a. Select Business Component :: Employee.
b. Select View > Visualize > View Details. Scroll down slowly until you find First Name in the
left column and select it. What table and column does it reference?
c. How many fields in the Employee business component reference columns in the
Zero
One to ten
Greater than ten
d. Scroll down slowly until you find the S_EMP_PER table in the right column. Are there any
fields in Employee that reference columns in the S_EMP_PER table?
e. Scroll down slowly until you find the S_USER table in the right column. Are there any fields
in Employee that reference columns in the S_USER table?

3. In this step, you will observe how some organization-related party business components use the
S_ORG_EXT table. As with person-related party BCs, here you will observe that organization-
related party BCs also reference the same column in the same extension tables to gather their
data, and that the extension tables contain most of the data. Use the Visualize technique you
followed in the previous steps to answer the questions, below. You will examine this general
structure:
Organization-Related Party Business Component
Field X Field X
S_PARTY S_ORG_EXT
ROW_ID
PAR_ROW_ID

PK FK
Base Table Extension Tables
a. Does the Organization party business component use the INT_ORG_FLG column in the
S_ORG_EXT table?
b. Does the Organization party business component use the NAME and LOC columns in the
S_ORG_EXT table?
c. Does the Account party business component use the INT_ORG_FLG column in the
S_ORG_EXT table?
d. Does the Account party business component use the NAME and LOC columns in the
S_ORG_EXT table?
4. In this step, you will examine how party business components reference S_PARTY.
a. Select Business Component :: Account. What is the base Table for the Account business
component?

b. Use the visualization tool to examine references from the Account fields to tables and
columns. About how many columns in the S_PARTY table are referenced?
Less than five

More than five
c. Consider the Party Type Code field in the Account business component. What column in
S_PARTY does it reference?
d. Which field references ROW_ID in S_PARTY? Note that Id is a predefined field for every

business component. It serves as the primary key field. Since it is predefined you will not
find it in the single value field object definitions for a business component, but you will be
able to refer to it and use it during configuration.
e. Verify that the Contact and Organization party business components also use S_PARTY as
their base table. Do they use roughly the same S_PARTY columns as the Account business
component?
5. In this step, you will inspect single value field object definitions to determine the referenced
columns.
a. Select Business Component :: Account | Single Value Field :: Party Name. What is the value
of the Column property?
i. Which table contains this column?
b. Select Business Component :: Account | Single Value Field :: Location. What is the value of
the Column property? What is the value of the Join property?

6. In this step, you will examine how the S_CONTACT and S_CONTACT_X tables are related to
the S_PARTY table. Note that, since multiple business components may reference the same base
table, it is critical that you be able to distinguish between how business components reference
tables, and the various extension tables that are referenced.
a. Select Table :: S_CONTACT. What is the type of the table?
b. What base table does this party table reference?

c. Select Table :: S_CONTACT_X. This is the standard 1:1 extension table for the
S_CONTACT table. What base table does this party extension table reference?
d. Determine which S_CONTACT_X column is the FK to S_PARTY.

i. Select Table :: S_CONTACT_X | Column.
ii. Query the Foreign Key Table property for S_PARTY. Which S_CONTACT_X
column is the FK to S_PARTY?
7. Leave Tools open.

Solutions 18-1 Exploring Relationships Between Party

Business Components and Tables (Guided)
Answers:
1.b. Select View > Visualize > View Details. Scroll down slowly until you find First Name in
the left column and select it. What table and column does it reference?
The FST_NAME column in the S_CONTACT table
1.c. About how many fields in the Contact party business component reference columns in the

Greater than ten
1.d. Scroll down slowly until you find the S_EMP_PER table in the right column. Are there any
If yes, list them.
Yes: Work Phone Extension and Share Home Phone Flag
1.e. Scroll down slowly until you find the S_USER table in the right column. Are there any
fields in the Contact business component that reference columns in the S_USER table? If
yes, list them.
Yes: Challenge Answer, Challenge Question, and Login Name
2.b. Select View > Visualize > View Details. Scroll down slowly until you find First Name in
the left column and select it. What table and column does it reference?
The FST_NAME column in the S_CONTACT table.
2.c. How many fields in the Employee business component reference columns in the
Greater than ten
2.d. Scroll down slowly until you find the S_EMP_PER table in the right column. Are there any
If yes, list them.
Yes, there are many fields (>10).
2.e. Scroll down slowly until you find the S_USER table in the right column. Are there any
fields in the Contact business component that reference columns in the S_USER table? If
yes, list them.
Yes, there are several fields.
3.a. Does the Organization party business component use the INT_ORG_FLG column in the
S_ORG_EXT table?
Yes

3.b. Does the Organization party business component use the NAME and LOC columns in the
S_ORG_EXT table?
It uses both NAME and LOC.
3.c. Does the Account party business component use the INT_ORG_FLG column in the
S_ORG_EXT table?
Yes
3.d. Does the Account party business component use the NAME and LOC columns in the
S_ORG_EXT table?
It uses both NAME and LOC.
4.a. Select Business Component :: Account. What is the base Table for the Account business
component?

S_PARTY
4.b. Use the visualization tool to examine references from the Account fields to tables and
columns. About how many columns in the S_PARTY table are referenced?
More than five
4.c. Consider the Party Type Code field in the Account business component. What column in
S_PARTY does it reference?
PARTY_TYPE_CD
4.d. Which field references ROW_ID in S_PARTY? Note that Id is a predefined field for every
business component. It serves as the primary key field. Since it is predefined you will not
find it in the single value field object definitions for a business component, but you will be
able to refer to it and use it during configuration.
Id
4.e. Verify that the Contact and Organization party business components also use S_PARTY as
their base table. Do they use roughly the same S_PARTY columns as the Account business
component?
Yes, they do.
5.a. Select Business Component :: Account | Single Value Field :: Party Name. What is the
value of the Column property?
NAME
5.a.i. Which table contains this column

S_PARTY
5.b. Select Business Component :: Account | Single Value Field :: Location. What is the value
LOC
5.b. What is the value of the Join property?

S_ORG_EXT

6.a. Select Table :: S_CONTACT. What is the type of the table?

Extension (Siebel)
6.b. What base table does this party table reference?

S_PARTY
6.c. Select Table :: S_CONTACT_X. This is the standard 1:1 extension table for the
S_CONTACT table. What base table does this party extension table reference?
S_PARTY
6.d.ii. Query the Foreign Key Table property for S_PARTY. Which S_CONTACT_X column is
the FK to S_PARTY?
PAR_ROW_ID

Lab 18-2 Identifying Objects When Using a Party

Business Component (Unguided)
Goal To examine how the elements of a party business component are represented in the
application architecture.

Instructions:
In this lab, you will identify the major objects involved in getting data from the data layer to the UI
layer for a standard business component that uses an explicit join to pull data from a party extension
table.
1. If necessary, open Siebel Call Center using the Siebel Web Client and log in as
SADMIN/SADMIN.
2. Navigate to Assets > List and use Columns Displayed to display the Account column in the list
applet. Enter the display name, applet name, and business component name for account data into
the job aid, below.
3. Verify that an applet references only one business component.

a. In Tools, select Applet :: <applet name from previous step>
b. Compare the business component property for this applet against what you entered into the
job aid, below.
4. Identify whether the business component is standard or party by examining its base table.
5. Identify the field that the display name references and enter the value into the job aid.
6. Identify the table name and enter the value into the job aid.
7. Verify that this table is an S_PARTY extension table by examining the base table property of
Table :: S_ORG_EXT.

Job Aid: Identifying Objects When Using a Party Business Component

Layer Part You’re Source Where Information About The
Step Enter Value Here
looking For Object Can Be Found
User • In a list applet, column heading above
Interface Display the field in question
1
Objects Name • In a form applet, control label next to
the field
2 Applet Name
In UI: Help > About View
Business In UI: Help > About View

3
Component

In Tools: Applet <applet name>. Drill down
on BC property. Party
Business
IF BC’s base table (table property) is
Business Component Standard
4 S_PARTY
Objects Type
It’s a party BC
ELSE
It’s a standard BC
a. In Tools: <applet name> | List :: List | List

Column.
b. Query Display Name for <display name>
5 Field (from step 1).
Data a. In Tools: Business Component :: <BC

Objects name> | Field :: <field name>.
6 Table b. Enter value under Join property

Solutions 18-2 Identifying Objects When Using a Party

Business Component (Unguided)
Answers:
Job Aid: Identifying the Parts of a Party Business Component
• In a list applet, column heading above
Account

User Display the field in question
Interface 1
Name • In a form applet, control label next to
Objects the field
2 Applet Name
Asset Mgmt - Asset List
Applet
3
Component Asset Mgmt – Asset
⌧
Business
4 S_PARTY
Objects Type
It’s a party BC
ELSE

Column.
b. Query Display Name for <display name> Account Name

b. Enter value under Join property S_ORG_EXT
6 Table


Lab 18-2 Identifying Objects When Using a Party

Business Component (Guided)
Goal To examine how the elements of a party business component are represented in the
application architecture.

Instructions:
In this lab, you will identify the major objects involved in getting data from the data layer to the UI
layer for a standard business component that uses an explicit join to pull data from a party extension
table.
1. If necessary, open Siebel Call Center using the Siebel Web Client and log in as
SADMIN/SADMIN.
a. Navigate to Assets > List.
b. Display the Account column for the list applet.
i. From the application-level menu, select View > Columns Displayed. As a shortcut, right-
click then select Columns Displayed, or press CTRL+SHIFT+K.
ii. Use the shuttle applet to move Account from Available Columns to Selected Columns.
iii. Use the up arrow to move Account to the top of the list.
iv. Click Save.
c. Enter the Display Name for account data into the job aid, below.
2. Identify the Applet Name and business component.

a. Select Help > About View.
b. Enter the applet name into the job aid, below.
c. Enter the business component name into the job aid, below.
3. Verify that the applet references only one business component.

a. In Tools, select Applet :: <applet name from previous step>
b. Compare the business component property for this applet against what you entered into the
job aid.
4. Identify whether the business component is standard or party.

5. Identify the field name that the display name references.

a. In Tools, select Applet :: <applet name> | List :: List | List Column.
b. Select the List Column object definition whose Display Name property is Account. Enter the
value of the Field property for this record into the job aid.
6. Identify the Table Name for the data source. Select Business Component :: <business component
name>| Field :: <field name, from previous step>. You can also access this business component
by drilling down on the applets business component property in the OBLE.
a. Enter the value under the join property into the job aid. If this value is empty, the data source
is from the base table. Otherwise, it is from a join table. Since we know this is a standard BC
referencing data from a party BC, we know a join is involved.
b. Verify this table is an S_PARTY extension table. Select Table :: S_ORG_EXT. If the value

of the Base Table Name property is S_PARTY, it is an S_PARTY extension table. Note that
most of the data resides in the extension table, not the base table. Thus, the extension table is
the source of the data.
Job Aid: Identifying Objects When Using a Party Business Component
User • In a list applet, column heading above
Interface Display the field in question
1
Objects Name • In a form applet, control label next to
the field
2 Applet Name

3
Component
Business
4 S_PARTY
Objects Type
It’s a party BC
ELSE

Column.
b. Query Display Name for <display name>

6 Table b. Enter value under Join property

Solutions 18-2 Identifying Objects When Using a Party

Business Component (Guided)
Answers:
6.b.
Job Aid: Identifying the Parts of a Party Business Component

• In a list applet, column heading above
User Account
Display the field in question
Interface 1
Name • In a form applet, control label next to
Objects the field
2 Applet Name
Asset Mgmt - Asset List
Applet
3
Component Asset Mgmt – Asset
⌧
Business
4 S_PARTY
Objects Type
It’s a party BC
ELSE

Column.
b. Query Display Name for <display name> Account Name

b. Enter value under Join property S_ORG_EXT
6 Table


Module 19: Siebel Business Objects
Lab 19-1 Examining Relationships between Views,

Business Objects, Business Components, and Tables
(Unguided)
Goal To explore Business Object and Link definitions in Siebel Tools.

Instructions:
Recall that business objects are used to focus data presented in views depending on the context in
which the data is accessed, and that any given view references one, and only one business object.
Business objects also organize business components into a major business area, such as Accounts,
Opportunities, Contacts and Actions. In this lab, you will examine how business objects relate to
other objects in the Siebel repository.
1. Examine references for the Opportunities business object. Views reference a single business
object and business objects reference multiple business components.
a. Open Siebel Call Center using the Siebel Call Center Developer Web Client and log in as
b. Drill down on any opportunity from the opportunities list applet.

c. Enter the name of the view, the name of the business object, and the names of the two
business components into this diagram:

d. In Siebel Tools, navigate to the view object definition you found above and confirm that its
business object property matches the one you found above.
e. Navigate to the business object object definition you found above and confirm that the
business component you found above is one of the business object’s business object
components.

2. Identify references between fields and business components for a 1:M link referenced by the
Opportunity business object where many opportunity records may be associated with a single
revenue record. Enter your answers directly into this diagram:
a. Select Business Object :: Opportunity | Business Object Component :: Revenue.
b. Drill down on the link property to identify the parent and child business components. Add the
link, parent BC, and child BC to the diagram above.
c. Enter the name of the base table for the parent into the diagram.
d. Enter the name of the base table for the child into the diagram.
e. Use the properties of the link to identify the primary and foreign key references; that is, the
source field of the parent BC and the destination field of the child BC.
f. Identify the column name in the child base table that holds the foreign key.

3. Identify references between fields and business components for a M:M link used by the
Opportunity business object where there could be multiple opportunity records that have
relationships with multiple contact records. Enter your responses directly into the diagram
below:
a. Select Business Object :: Opportunity | Business Object Component :: Contact.
b. Enter the business object name into the diagram.
c. Enter the link name into the diagram.
d. Inspect the Link definition to verify the relationship between opportunities and contacts is
M:M and enter the value of the Inter Table property into the top of the intersection table in
the diagram.
e. Identify the parent and child business components and their base tables and enter them into
the diagram

f. Identify the primary key / foreign key mappings and enter them into the diagram. Note that
the Inter Parent Column property holds the value for the intersection table FK column that
maps to the parent base table while the Inter Child Column property holds the value for the
intersection table FK column that maps to the child base table.
4. Exit Siebel Tools and log out of Siebel Call Center.

Solutions 19-1 Examining Relationships between Views,

(Unguided)
Answers:
1.c.

2.

3.

Lab 19-1 Examining Relationships between Views,

(Guided)
Goal To explore Business Object and Link definitions in Siebel Tools.

Instructions:
Recall that business objects are used to focus data presented in views depending on the context in
which the data is accessed, and that any given view references one, and only one business object.
Business objects also organize business components into a major business area, such as Accounts,
Opportunities, Contacts and Actions. In this lab, you will examine how business objects relate to
other objects in the Siebel repository.
1. In this step, you will examine references for the Opportunities business object. Views reference a
single business object and business objects reference multiple business components.
a. Open Siebel Call Center using the Siebel Call Center Developer Web Client and log in as
b. Navigate to Opportunities > List. If no records appear in the list, execute a blank query to
populate the list.
c. Drill down on any opportunity from the list applet.

d. Select Help > About View. Enter the name of the view, the name of the business object, and
the names of the two business components into this diagram:

e. If necessary, start Siebel Tools and log in as SADMIN connecting to the Sample database.
f. Select View:: Opportunity Detail - Contacts View. Check the value you entered into the
diagram for View. It should match the value of the Business Object property in Tools.
g. Explore the relationship between business objects and business components.
i. Select Business Object :: Opportunity | Business Object Component. The Bus Comp
property displays all business components used for this business object. Peruse the
list.
ii. Now execute a null query in the Name property of the OBLE upper window. The
query should return a list of all business objects in the repository.
iii. With the cursor positioned in the Name property, use the down arrow to slowly scroll
through 15 or 20 business objects. As you scroll, observe changes in the OBLE’s
lower window.
iv. What can you infer about the relationship between business objects and business
components?
A given business object references one or more business components
A given business object only references one business component

2. In this step, you will identify references between fields and business components for a 1:M link
referenced by the Opportunity business object where many opportunity records may be
associated with a single revenue record. Enter your answers directly into this diagram:

a. Identify the parent and child business components and their base tables.
i. Select Business Object :: Opportunity | Business Object Component :: Revenue.
ii. Drill down on the Link property.
iii. Enter the names of the business object, the parent business component, the child
business component, and the link into the diagram.
iv. Drill down on the Parent Business Component property.
v. Enter the name of the base table for the parent into the diagram.
vi. Click the back arrow.
vii. Drill down on the Child Business Component property.
viii. Enter the name of the base table for the child into the diagram.
b. Identify the primary key references.
i. Navigate back to the object definition for the Opportunity/Revenue link.
ii. View the values in the Properties window.
iii. In the structure diagram, enter the value that maps the Source Field to the parent base
table. Note that the Source Field property defaults to the primary key ROW_ID for
the parent base table. This appears as Id in the Source Field property.
c. Identify the foreign key references.
i. View the values in the Properties window to identify the Destination Field.
ii. Enter this value into the diagram. Note that the Destination Field property points to a
field in the child business component, which in turn has a column property that
identifies the table column.
d. Identify the column name in the child base table that holds the foreign key:
i. Drill down on the child business component.

ii. Select Business Component :: Revenue | Field.

iii. In the name property, query for the Destination Field you identified in the previous
step.
iv. The column name that this field maps to is displayed under the Column property.
Enter this value into the child base table in the diagram. Note that you are now
viewing definitions for the data layer.
3. In this step, you will identify references between fields and business components for a M:M link
used by the Opportunity business object where there could be multiple opportunity records that
have relationships with multiple contact records. This example illustrates how the link focuses
the data while the intersection table resolves the M:M relationship. Enter your responses directly
into this diagram:

a. Inspect the Link definition to verify the relationship between opportunities and contacts is
M:M.
i. Select Business Object :: Opportunity | Business Object Component :: Contact.
ii. Enter the business object name specified under the Name property into the diagram.
iii. Enter the link name specified under the Link property into the diagram.
iv. Drill down on the Opportunity/Contact link.
v. Set a bookmark:
vi.
vii. Enter the value of the Inter Table property into the top of the intersection table in the
diagram.
b. Identify the parent and child business components and their base tables.

i. Enter the name of the parent business component into the diagram. In Tools, it is the
value of the Parent Business Component property for the link object definition.
ii. Enter the name of the child business component into the diagram. It is the value of the
Child Business Component property for the link object definition.
iii. To identify the name of the base table for the parent, drill down on the parent
business component. Enter the value for the parent base table into the diagram. Note
that the table property listed for the business component is always the base table.
c. Identify the name of the base table for the child.
i. Use the bookmark to navigate back to the link object definition:
ii. Drill down on the child business component.
iii. Enter the value for the child business component’s base table into the diagram.
iv. Use the bookmark to navigate back to the link object definition:

d. Identify the primary key / foreign key mapping.
i. Open the properties window.
ii. The Inter Parent Column property holds the value for the intersection table FK
column that maps to the parent base table. Enter the foreign key for the parent base
table into the diagram.
iii. The Inter Child Column property holds the value for the intersection table FK column
that maps to the child base table. Enter the foreign key for the child base table into the
diagram.
4. In this step, you will examine the relationship for several more parent/child business
components.
a. Verify that the Account-Business Address relationship is one-to-many (1:M) by inspecting
the link definition.
i. Select Business Object :: Account | Business Object Component :: Business Address.
What link is used?
ii. Drill down on the Account/Business Address (w/Primary) link. What is the value of
the Inter Table property?
iii. What does this convey about the form of the Account – Business Address relationship?
b. In the Account/Position link, how can you verify that the form of the relationship between
Account and Position is M:M?

c. In the Account/Contact link, what is the form of the relationship between Account and
Contact?
d. In the Service Request/Product Defect link, which intersection table supports the M:M
relationship between Service Request and Product Defect?
5. Log out and close Siebel Tools.

Solutions 19-1 Examining Relationships between Views,

(Guided)
Answers:
1.d.

1.g.iv. What can you infer about the relationship between business objects and business
components?
A given business object references one or more business components

2.

3.
4.a.i. Select Business Object :: Account | Business Object Component :: Business Address. What
link is used?
Account/Business Address (w/Primary).
4.a.ii. Drill down on the Account/Business Address (w/Primary) link What is the value of the
Inter Table property?
The field is blank.

4.a.iii. What does this convey about the form of the Account – Business Address relationship?
It is a one-to-many (1:M) relationship.
4.b. In the Account/Position link, how can you verify that the form of the relationship between
Account and Position is M:M?
Inspect the Account/Position link (which has a value for the Inter Table property).
4.c. In the Account/Contact link, what is the form of the relationship between Account and
Contact?
The Inter Table property is not null, so the relationship is M:M.
4.d. In the Service Request/Product Defect link, which intersection table supports the M:M
relationship between Service Request and Product Defect?
S_SR_DEFECT.


Module 21: The Configuration Process
Lab 21-1 Setting Up a Developer (Unguided)
Goal To set up a developer on your configuration team.
Instructions:

Due to the critical nature of this lab, there is no Unguided version of it. Please turn the page and do
the Guided version.


Lab 21-1 Setting Up a Developer (Guided)
Goal To set up a developer on your configuration team.
Instructions:

In this lab you will create an employee record for a developer, Pat Penguin. In future labs, you will
create a local database for Pat to use for Siebel application configuration. The tasks you will do in
this lab are:
• Create a position for Pat Penguin
• Create a responsibility associated with views that Pat will use
• Add Pat Penguin as an employee
• Create a mobile client, needed to create a local database for Pat
• Add Pat as a database user and login to allow access to the server database
1. Open the Siebel Web client and log in to Siebel Call Center as SADMIN/SADMIN.
2. You will create a position for Pat Penguin.

a. Navigate to Administration – Group > Positions.
b. Create a new position with the following values:
Division Default Organization
Position ABC Developer
3. Next, you will create the ABC Developer responsibility that will be assigned to Pat Penguin.
a. Navigate to Administration – Application > Responsibilities.
b. Create a new responsibility record named ABC Developer.
c. You will add the required application views to the ABC Developer responsibility. Two types
of views will be added to this responsibility: all views that will be used in this course, as well
as all repository views. Instead of associating one view at a time to the new responsibility,
you will use a provided text file to speed the process.
i. Using Windows Explorer, navigate to D:\Labs\Essentials and open ABC Developer
views.txt. This file contains a query that you execute to select the views for the ABC
Developer responsibility.
ii. Select Edit > Select All.
iii. Select Edit > Copy to copy the text in the file.
iv. Switch to the Siebel Call Center window.

v. Click Add in the Views applet to create a new record. The application will display a list
applet entitled Add Views.
vi. Click Query.
vii. In the View Name field, paste the query string copied from ABC Developer views.txt.
viii. Click Go. 45 views will be returned.
ix. Press CTRL+A to select all 45 views. Click OK to add them. Verify that 45 views were
added to the responsibility.
x. Close ABC Developer views.txt.
d. You will add the required repository views to the ABC Developer responsibility.
i. In Siebel Call Center, click Add in the Views list to create a new record. The
application will display the Add Views association applet.
ii. Find all views beginning with the word Repository. Enter Repository in the “Starting

with” field and click Go. Scroll to the bottom of the list to verify 122 view records
matched the query. These views are used by Siebel Tools, where they allow drilldown
access to objects, such as the ability to drill down on the Table property in a business
component definition.
iii. Press CRTL+A to select all records.
iv. Click OK to add them. Verify that you now have 167 views added to the ABC
Developer responsibility.
v. Make sure the Local Access field is checked for each view. This will allow you to
access these views while connected to a local database. There should be five views with
Local Access flag unchecked. Check the flag for each of them.
All Accounts across Organizations
All Contacts across Organizations
All Service Requests across Organizations
Asset Mgmt – Assets View
Contact List View
Note: To query for views with Local Access unchecked, check the Local Access flag in
your query, then uncheck it.
e. In the Responsibilities applet, click Clear Cache to ensure that the ABC Developer
responsibility is not cached.
4. You will create Pat Penguin as an ABC developer by creating an employee record.
a. Navigate to Administration – User > Employees.
b. Create a new employee record using the position you just created:
Last Name Penguin
First Name Pat
User ID PPENGUIN
Responsibility ABC Developer (use the
shuttle applet to add this
responsibility and remove
the Siebel Administrator
responsibility for
PPENGUIN )
Position ABC Developer

c. Verify that PPENGUIN has only the ABC Developer responsibility before proceeding.
5. You will add a corresponding database login for Pat Penguin.

a. Select Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Express.
b. Click Connect.
c. Select File > Open > File.
d. Select the file D:\Labs\Essentials\add login for PPENGUIN.sql.
e. Click Connect. The script you see was created by modifying grantusr.sql. It contains the
statements to create a user login and assign that user a default database and a role. The syntax
is specific to MS SQL Server. In a real-world implementation, the database administrator on
your team would create these scripts for you.
f. Click Execute.

g. The results should state:
Command(s) completed successfully.
h. Exit SQL Server Management Studio Express.
6. You will register Pat Penguin as a mobile client. This will allow you to run a database extract
job and create a local database for Pat, as you will do later in this lab.
a. In Siebel Call Center, navigate to Administration - Siebel Remote > Mobile Clients.
b. In the Mobile Clients list, create a new record with the following values:
Mobile Client PPENGUIN
User ID PPENGUIN
Routing Model MOBILE CLIENT - STANDARD
c. Save the record.
7. You will configure Siebel Remote security preferences by disabling password expiration,
password syntax checking and remote user lockout. These security features are important, but are
unnecessary in the classroom environment.
a. Click the Remote System Preferences link.
b. Uncheck three check boxes in the Remote System Preferences applet:
Enable Mobile Password Expiration
Enable Mobile Password Syntax Check
Enable Mobile Web Client Lockout
c. Click Save.
8. Finally, you will verify your work.

a. Log out of Siebel Call Center.
b. Start Siebel Call Center using the Web client and log in as PPENGUIN/PPENGUIN.
c. You should see five screen tabs: Home, Accounts, Contacts, Opportunities, Service.
Note: If the login was not successful or you do not see the proper screens, do not continue.
Speak with your instructor. You must be able to log in as PPENGUIN to continue.


Lab 21-2 Extracting a Local Database (Unguided)
Goal To execute server tasks to generate a database template and extract a local database for
Pat Penguin.
Instructions:

the Guided version.


Lab 21-2 Extracting a Local Database (Guided)
Goal To execute server tasks to generate a database template and extract a local database for
Pat Penguin.
Instructions:

Before you create a local database to be used by the developer, you need to run two server jobs.
First, you must generate a database template that represents the Siebel schema. Second, you must run
a database extract on the server for mobile user PPENGUIN. This extracted data will be used to
build Pat Penguin’s local database.
1. Start Siebel Call Center using the Web client and log in as SADMIN/SADMIN.
2. You will enable the Siebel Remote component group.

a. Navigate to Administration – Server Configuration > Enterprises > Component Groups.
b. In the Component Groups child applet, query for the component group Siebel Remote.
c. Locate the grandchild applet titled Component Group Assignments. You will see a single
record for server OUsrvr. If the Enabled on Server checkbox is not checked, click Enable.
d. If necessary, synchronize components with the Gateway Name Server. It should not be
necessary, as you synchronized all assigned component groups in a previous lab.
i. Click the Synchronize view tab.
ii. Query for the Database Extract component. This is one of the components from the
Siebel Remote component group.
iii. If this component is not found, click the Synchronize button. Synchronization will take
1-2 minutes.
3. You will restart the Siebel Server so that it will reflect the new configuration.
a. If necessary, select Start > Programs > Administrative Tools > Services.
b. Locate the Siebel Server [Siebel_OUsrvr] service. Right-click on it and select Stop. Your
Siebel Server may take a few minutes to completely shut down, and sometimes the Service
Control dialog box will generate a warning that it could not stop this service. However, click
OK and update the status for the Siebel Server service by selecting Action > Refresh
periodically. Within a minute or so, you should see this service’s status change from
Stopping to blank.
c. Right-click on Siebel Server [Siebel_OUsrvr] and select Start. Right-click on an empty
part of the Windows task bar and select Task Manager. Monitor CPU usage until percentage
used drops to near 0% and remains there.

d. Start Siebel Call Center using the Web client and log in as SADMIN/SADMIN.
4. You will verify that the Siebel Remote server components are online, and synchronize
component definitions with the Siebel Gateway. These steps are prerequisites for running the
server jobs to create a local database.
a. Navigate to Administration > Server Management > Components.
b. In the Components list applet, locate Database Extract, Generate New Database, and
Synchronization Manager. Make sure these three components have state Online. If any of
these components is not online, notify your instructor.
c. Navigate to Administration – Server Configuration > Enterprises > Synchronize.
d. In the Synchronize child applet, click Synchronize. Synchronization will take 1-2 minutes to
complete, and will be done when your cursor returns to normal from hourglass form.

5. Next, you will submit a job to start a Generate New Database server task.
a. Navigate to Administration – Server Management > Jobs.
b. In the Jobs list, click New.
c. In the Component/Job field, select Generate New Database from the Components/Jobs
applet and click OK.
d. Scroll down to the bottom of the page, and in the Job Parameters list, click New.
i. In the Name field, select Client Db Type.
ii. Verify that the default parameter value, Sql Anywhere, is entered in the Value field.
e. In the Jobs list, what is the status of the job?
f. Click the Submit Job button to run the task.

g. What is the status of the job?
6. You will monitor the Generate New Database task.

a. Click Servers in the link bar.
b. Select the Tasks view link.
c. Locate the Generate New Database task in the Tasks list. Monitor the task for a few minutes.
The best way to refresh a list in Siebel applications is to run a null query.
i. Click the Query button.
ii. Leave all the fields blank.
iii. Click the Go button.
d. Record the task number of the Generate New Database task:
e. Monitor the task until it completes by executing the query periodically. On the Tasks list, the
Status field will have value Completed successfully.
f. Select the Generate New Database task to view the Task Information Log in the lower
portion of the screen. No records appear if the task executed successfully.

7. You will verify the existence of the database template file.

a. Navigate to D:\OUsea\siebsrvr\DBTEMPL.
b. There should be a subdirectory with a name similar to “db43r105” Verify that it contains four
files.
8. Now you will run a Database Extract job to build a local database for Pat Penguin that contains
the user data visible to Pat.
a. Click Jobs in the link bar.
c. In the Component/Job field, select Database Extract.
d. Scroll down to the bottom of the page, and in the Job Parameters list, enter the following job
parameters:

Name Value
Client Database encryption method None (don’t leave
blank)
Client Name PPENGUIN
Encrypt client Db password False
e. In the Jobs list applet at the top of the page, click Submit Job.
f. In the Jobs list applet, click Query, and then click Go (to execute a null query to refresh the
view). The status for the Database Extract job should change from “Queued” to “Active.”
g. Click on Tasks in the link bar to view the task.
h. Query for Component = Database Extract. Monitor the status of the task until completion
by re-querying the applet. The State field will be set to Completed when the database extract
is done. This should be within 5-10 minutes after you submitted the job.
9. Finally, you will verify your work.

a. Navigate to D:\OUsea\siebsrvr\docking.
b. Verify that there is a PPENGUIN directory.
i. In the PPENGUIN directory, verify that there is a file called dobjinst.dbf and
subdirectories called inbox and outbox.
ii. Verify that the outbox subdirectory contains several files. There should be at least one
with each of the following extensions: .uaf, .dat, and .toc.
c. Select File > Log Out to close the Siebel Call Center application, and then close the Internet
Explorer window.

Solutions 21-2 Extracting a Local Database (Guided)
Answers:
5.e. In the Jobs applet, what is the status of the job?
Creating
5.g. What is the status of the job?

Queued

Lab 21-3 Populating the Local Developer Database

(Unguided)
Goal To initialize and populate the local developer database.

Instructions:
the Guided version.


Lab 21-3 Populating the Local Developer Database

(Guided)
Goal To initialize and populate the local developer database.

Instructions:
Before you create Pat Penguin’s local database, you will need to check configuration files and
ODBC connection settings. The last step in creating the local database is to start Siebel Tools
connected to the local database. Because this database doesn’t exist yet, Tools will create it, using
the database extract files that you generated in the last lab.
1. You will verify that Tools is correctly configured to connect to the server and local databases.
a. In Windows Explorer, navigate to D:\OUsea\tools\BIN\ENU.
b. Double-click tools.cfg to open it with Notepad.
c. Scroll down and find the [Local] section.
i. Verify that the ConnectString parameter is set to:
D:\OUsea\tools\local\sse_data.dbf –q –m –x NONE –gp 4096 –c256m –ch256m
ii. Set the DockConnString parameter to localhost.
d. Scroll down and find the [ServerDataSrc] section.
i. Verify that the FileSystem parameter is set to D:\siebfile.
ii. Set the GatewayAddress parameter to localhost.
iii. Verify that the EnterpriseServer parameter = Siebel.
e. Save and close tools.cfg.
2. Next, you will verify or update the ODBC data source for Tools, connecting to the server.
a. Select Start > Programs > Administrative Tools > Data Sources (ODBC).
b. In the ODBC Data Source Administrator dialog box, click the System DSN tab.
c. Select SSD default instance and click Configure.
d. In the first dialog box of the Microsoft SQL Server DSN Configuration wizard, verify the
following entries:
Name SSD default instance
Description Siebel MS SQL Database
Server localhost
e. Click Next.
f. Select With SQL Server authentication.

g. Select Connect to SQL Server and enter the following values:

Login ID PPENGUIN
Password PPENGUIN
h. Click Next.
i. Select the Change the default database to option and, if necessary, select siebeldb from the
drop-down menu and click Next.
j. Click Finish.
k. Click the Test Data Source button in the ODBC Microsoft SQL Server Setup dialog box.
l. You should see the message “TESTS COMPLETED SUCCESSFULLY!” in the SQL Server
ODBC Data Source Test dialog box. Click OK to close the dialog box.
m. Click OK to close the ODBC Microsoft SQL Server Setup dialog box.

n. Click OK to close the ODBC Data Source Administrator dialog box.
3. You will initialize the sse_data.dbf SQL Anywhere local database using Siebel Tools. In this
step the local database is populated.
a. Start Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the Local database.
b. In the siebdev dialog box window that appears, click Yes to initialize the local database.
c. In the Siebel Remote Parameters dialog box that appears, enter the following values:
Client Name PPENGUIN
User Name PPENGUIN
Password PPENGUIN
Confirm Password PPENGUIN
d. Click Continue.
e. The Siebel Upgrade wizard will be started and a progression window will show the status of
the initialization process. This process will take 3 to 5 minutes to complete.
4. When initialization completes, Siebel Tools will open. You will verify the local login.
a. Select Help > Technical Support.
b. Verify the User name = PPENGUIN
c. Verify the Connect string = D:\OUsea\tools\local\sse_data.dbf –q –m –x
d. Verify the Table owner = SIEBEL
Note: If Siebel Tools did not open successfully, or you do not see the proper information, do
not continue. Speak with your instructor. You must be able to log in as PPENGUIN to
continue with the labs.
e. Click OK.
5. Now you will verify the ODBC Data Sources in Siebel Tools.
a. Select View > Options.
b. Select Check In/Out.
c. Click the Change button next to Data Sources: Server.

d. Verify the ODBC data source for the server:

Client Name SSD default instance (There are two spaces
between “SSD” and “default instance”.)
User Name PPENGUIN
Password not verifiable, as it is not visible
Table Owner dbo
e. Click OK to close the Change Data Source window.
f. Click the Change button next to the Client Data source.
g. Verify the ODBC data source for the client:
Client Name SSD Local Db default instance
User Name PPENGUIN

Password not verifiable, as it is not visible
Table Owner SIEBEL
h. Click OK to close the Change Data Source window.
i. Click OK to close the Development Tools Options window.
6. You will test the local database login.

a. Close Siebel Tools
b. Start Siebel Tools and log in as SADMIN/SADMIN connecting to the Local database.
Note: You should receive an error. This is expected. The local database is initialized for a
given user, PPENGUIN. Other users, such as SADMIN, do not have access.
c. Click OK.
7. Populate the local database with object definitions from the repository.
a. Start Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the Local database.
b. Select Applet in the Object Explorer. You should not see any object definitions, since you
have not populated the repository tables yet.
c. Select Tools > Check Out.
d. Click All projects.
e. Click the Get button (not Check Out).
Note: This process will run for 45 minutes to an hour. You will learn about this dialog in the
next module.


Module 22: Managing Object Definitions
Lab 22-1 Exploring Projects (Unguided)
Goals To explore how projects work in Siebel Tools.

To perform project and object-level check outs.
Instructions:

In this lab, you will modify the Asset Mgmt – Assets View object definition. To do this, you need to
determine the proper project, check it out from the server, and then change the object definition.
1. Open Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the Local database.
2. Explore what needs to be done to modify an object definition. You will use the Asset Mgmt -
Asset business component for this step.
a. Select Business Component :: Asset Mgmt – Asset. Note that you cannot modify it because
you have not yet locked the project to which it belongs.
b. The Project property specifies the project to which the object definition belongs. What is the
value of the Project property?
3. Determine what other object definitions you will be able to edit when you check out the project.
a. Select Asset Management from the Project drop-down list at the top of the Object Explorer
window. After you check out the Asset Management project, will another team member be
able to edit the Asset Mgmt – Account Pick Applet object definition? Why or why not?
b. Reset your OE display so that you have an unrestricted list of all the projects. Select ** All
Projects ** at the top of the Project drop-down list in the Object Explorer window.
4. Enable project checkout for the Asset Management project, as well as other projects you will
modify during this course.
a. Start a new Tools session and log in as SADMIN/SADMIN to the Server database.
b. Toggle Allows Object Locking to FALSE for the Asset Management project.

c. Toggle Allows Object Locking to FALSE for the following projects:

Account
Account (SSE)
Contact
Contact (SSE)
Service
Service (SSV)
Table Asset.
5. In the Siebel Tools session where you are logged in as PPENGUIN/PPENGUIN, check out the
Asset Management project.
Note: Use Help > Tech Support if you have trouble determining which session is which.
6. Return to the Siebel Tools session where you are logged in as SADMIN/SADMIN and confirm

that the project has been checked out by PPENGUIN.
7. In the Siebel Tools session where you are logged in as PPENGUIN/PPENGUIN, perform an
object-level check out of the User List business component.
8. Return to the Siebel Tools session connected to Server as SADMIN. What signs are there that
the User List object is checked out?
9. Exit from SADMIN’s Siebel Tools session. Leave PPENGUIN’s session open. Log out of
Siebel Call Center.
10. Return to Siebel Tools and observe the visual cues that indicate whether object definitions are a
part of a locked or unlocked project.
b. Examine Asset Management Screen and Asset Management Screen (eService) in the
OBLE.
c. What differences do you notice between the two screen definitions?

11. One of your colleagues noticed that a developer could invoke Tools > Lock Project to lock the
project locally and make the definitions available for editing. What are the consequences of
doing this to edit the Asset Management Screen object definition?
12. Select Tools > Check In. What appears in the check in list and why?

13. Check in the Asset Management project while maintaining the lock.
Note: You will use the technique in this step as you continue through the configuration labs. Get
into the habit of checking your work in to the server at the end of the labs, but maintaining your
locks to avoid unnecessary additional check outs.

Solutions 22-1 Exploring Projects (Unguided)
Answers:
2.b. The Project property specifies the project to which the object definition belongs. What is
the value of the Project property?
Asset Management
3.a. Select Asset Management from the Project drop-down list at the top of the Object
Explorer window. After you check out the Asset Management project, will another team
member be able to edit the Asset Mgmt – Account Pick Applet object definition? Why or

why not?
No. When you check out a project from the server, it locks the project on the server, thus
preventing other developers from modifying it, and the Asset Mgmt – Account Pick Applet
is part of this project.
8. Return to the Siebel Tools session connected to Server as SADMIN. What signs are there
that the User List object is checked out?
The Object Locked property is TRUE (checked), and Object Locked By is PPENGUIN.
10.c. What differences do you notice between the two screen definitions?
(1) The “W” (for writeable) column has a pencil icon in the Asset Management Screen, but
not in the Asset Management Screen (eService).
(2) When you select one of the fields in the Asset Management Screen, the background is
white and you can edit the field. When you select one of the fields in the Asset Management
Screen (eService), the background is gray and you cannot edit the field.
11. One of your colleagues noticed that a developer could invoke Tools > Lock Project to lock
the project locally and make the definitions available for editing. What are the
consequences of doing this to edit the Asset Management Screen object definition?
They will be able to create and edit the object definitions, but they will not be able to check
them into the server. In addition, another developer can check out the Asset Management
project from the server and make a different set of changes.
12. Select Tools > Check In. What appears in the check in list and why?
Asset Management is the only locked project you have checked out, and is therefore the
only project that you can check in. User List appears with type Business Component,
because you did an object check out.

Lab 22-1 Exploring Projects (Guided)
Goals To explore how projects work in Siebel Tools.

To perform project and object-level check outs.
Instructions:

In this lab, you will modify the Asset Mgmt – Assets View object definition. To do this, you need to
determine the proper project, check it out from the server, and then change the object definition.
1. Open Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the Local database.
2. You will now explore what needs to be done to modify an object definition. You will use the
Asset Mgmt - Asset business component for this step.
a. Select Business Component :: Asset Mgmt - Asset.
b. Click the Comments property in the Object List Editor (OBLE) for the Asset Mgmt - Asset
object definition. You will probably have to scroll to the far right of the window to find the
Comments property. You may want to right-click in the OLBE and select Columns
Displayed and then move the Comments column so that it appears in the first few columns
displayed.
i. Can you change its value?
ii. What visual cues reinforce this?
iii. What must you do before you can edit the Asset Mgmt - Asset business component
object definition?
iv. The Project property specifies the project to which the object definition belongs.
What is the value of the Project property?

v. If you do not see the Properties window, select View > Windows > Properties
Window. Does the Project property appear in the Properties window?
vi. Right-click the Properties window and select Hide to hide it.
c. Verify that the project is, in fact, not already locked:
i. Select Project in the OE.
ii. Query for Name = Asset Managment. Is the project locked?
iii. Query for Locked=checked. Are any projects locked at this point?

3. Select View : Asset Mgmt – Assets View in the Object Explorer. Which project will you need to
check out to be able to modify the Asset Mgmt - Assets View object definition?
4. Before you check out a project, you might want to know what other object definitions you will
be able to edit when you check out the project.
a. Select Asset Management from the Project drop-down list at the top of the Object Explorer
window. Do you see more or fewer object types displayed in the OE?
b. After you check out the Asset Management project, will another team member be able to edit
the Asset Mgmt – Account Pick Applet object definition? Why or why not?
c. Reset your OE display so that you have an unrestricted list of all the projects. Select ** All
Projects ** at the top of the Project drop-down list in the Object Explorer window.
5. Next, you will check out the Asset Management project from the server so you are prepared to
make changes to the Asset Mgmt - Assets View object definition.
a. Select Tools > Check Out.
b. Select Asset Management from the list. Can you check out this project?
c. What do you have to do first?
d. Click Cancel to close the window.

e. Now you will enable project checkout for the Asset Management project, as well as other
projects you will modify during this course.
i. Start a new Tools session and log in as SADMIN/SADMIN to the Server database.
ii. Select Project :: Asset Management.
iii. Right-click and select Toggle Allows Object Locking.
iv. Verify the change by querying for projects with Allow Object Locking equals FALSE
(unchecked). Do this by checking and then unchecking the check box in the query.
Asset Management should be one of the projects returned by this query.
v. Before you exit from Tools as SADMIN, you will unset Allow Object Locking for
several other projects that you will use later. Refresh the project list, and right-click
and select Toggle Allows Object Locking for the following projects:
Account
Account (SSE)

Contact
Contact (SSE)
Service
Service (SSV)
Table Asset
vi. Verify your changes by querying for projects with Allow Object Locking equals
FALSE (unchecked) and Changed is TRUE (checked).
vii. Exit SADMIN’s Siebel Tools session.
f. You will check out the Asset Management project.
i. Return to the other Siebel Tools session, where you are logged on as PPENGUIN
connected to the local database.
ii. Cancel the previous Check Out.
iii. Select Tools > Check Out and select Asset Management from the project list.
iv. Click Check Out. Observe the communication between the server and the local
database displayed in the dialog box. Notice that the OBLE disappears towards the
end of the checkout. The check out will take several minutes.
g. Observe what other developers see when you have the Asset Management project checked
out.
i. Start a second instance of Siebel Tools as SADMIN/SADMIN and connect to the
Server database.
iii. Will other developers know PPENGUIN has the project locked? Why or why not?
iv. Attempt to lock the project and confirm that you get an error message.
v. Click OK to close the error dialog.
vi. Leave this session of Tools open and return to where you are logged in to Siebel
Tools as PPENGUIN, connected to the Local database.
h. Verify that the checkout was successful.

ii. Query for Locked = TRUE

iii. Do you have any projects locked?
iv. What is the value of the Locked By Name property for the Asset Management
project?
6. This step will allow you to test object-level check out and check in. In the rest of the course you
will only perform project check outs, not object-level check outs.
a. In the OE, select Business Component :: User List.
b. What project does this object belong to?

c. Right-click and select Check Out Object.
d. Click Check Out.
e. Return to the Siebel Tools session connected to Server as SADMIN.
f. Select Project in the OE and query for locked projects in the OBLE. What project(s) are
locked?
g. Select Business Component :: User List in the OE. What signs are there that this object is
checked out?
Hint: Scroll to the right.
h. Exit from SADMIN’s Siebel Tools session. Leave PPENGUIN’s session open.
7. When you check out a project, a local copy of the project, called an archive file, is also created in
the tools\TEMP directory. You will learn about archive files in a later module.
a. Use Windows Explorer to navigate to the D:\OUsea\Tools\TEMP\Projects directory. What is
the name of the file located in this directory?
Note: If you need extra drive space during the configuration process, you may delete these
.sif files. Do not delete this file now!
b. Navigate to D:\OUsea\Tools\TEMP\Objects. What file appears in this directory?
8. Return to Siebel Tools and observe the visual cues that indicate whether object definitions are a
part of a locked or unlocked project.

b. Examine Asset Management Screen and Asset Management Screen (eService) in the
OBLE.
c. What differences do you notice between the two screen definitions?

9. One of your colleagues noticed that a developer could invoke Tools > Lock Project to lock the
project locally and make the definitions available for editing. What are the consequences of
doing this to edit the Asset Management Screen object definition?
10. Now you will explore which projects can be used to assign new object definitions.
b. You want to add a new Screen object definition.
i. Right-click in the OBLE and select New Record to add a new screen object
definition.
ii. Click the drop-down arrow to open the Project picklist in the newly created record.
Why is Asset Management the only project listed?
iii. Click Close to close the Project picklist window.

iv. Right-click and select Undo Record to delete the newly created record.
11. Imagine you have implemented changes to the Asset Mgmt - Assets View object definition,
tested them locally, and they work. These modified definitions can stand alone, and you want to
make certain that the next set of changes will not affect the Asset Mgmt - Assets View object
definition. You decide to check the project into the server to save the snapshot (milestone) before
continuing with the next set of changes.
a. Select Tools > Check In. What appears in the check in list and why?

b. Select Asset Management.

c. Check the Maintain lock check box, because you still need to make more changes. You will
still be using this project, and this will allow you to modify object definitions in the Asset
Management project without checking it out again.
d. Click Check In. Observe how the status is displayed during check-in.
e. Check in the User List business component.
i. Select Tools > Check In.
ii. Select User List in the Check In dialog box.
iii. Select the Maintain lock check box.
iv. Click Check In.
f. Verify the results of the project check-in.

ii. Query for Locked = TRUE. You should still see that you have the Asset Management
project locked. If not, then repeat the checkout.
Note: You will use the technique in this step as you continue through the configuration labs. Get
into the habit of checking your work into the server at the end of the labs (with the lock
maintained as directed by the project development plan).

Solutions 22-1 Exploring Projects (Guided)
Answers:
2.b.i. Can you change its value?
No
2.b.ii. What visual cues reinforce this?

(1) The background of the field appears gray.
(2) The “W” field, which indicates whether the record is writeable, is null (blank).

2.b.iii What must you do before you can edit the Asset Mgmt - Asset Business Component object
definition?
Best practice is to check out the object or its project from the server. Checking an object
or project out from the server prevents other developers from modifying it and allows
checking back to the server. You can also lock the project locally to edit the object
definition. This should only be considered when prototyping or intending to discard
changes. Locking projects locally prevents the developer from checking them in to the
server repository, so be careful when using this option!
2.b.iv. The Project property specifies the project to which the object definition belongs. What is
the value of the Project property?
Asset Management
2.b.v. If you do not see the Properties window, select View > Windows > Properties Window.
Does the Project property appear in the Properties window?
No
2.c.ii. Query for Project = Asset Management. Is the project locked?

No
2.c.iii. Are any projects locked at this point? (Hint: Query for Locked=checked.)
Yes – ABC WF
3. Select View : Asset Mgmt – Assets View in the Object Explorer. Which project will you
need to check out to be able to modify the Asset Mgmt - Assets View object definition?
You will need to check out Asset Management.
4.a. Select Asset Management from the Project drop-down list at the top of the Object
Explorer window. Do you see more or fewer object types displayed in the OE?
Fewer (there are ten displayed).

4.b. After you check out the Asset Management project, will another team member be able to
edit the Asset Mgmt – Account Pick Applet object definition? Why or why not?
No. When you check out a project from the server, it locks the project on the server, thus
preventing other developers from modifying it, and the Asset Mgmt – Account Pick Applet
is part of this project.
5.b. Select Asset Management from the list. Can you check out this project?
No. The Check Out button remains grayed out.
5.c. What do you have to do first?

Set Allow Object Locking to FALSE for the Asset Management project on the Server. This
can only be done by a user with administrative privileges (such as SADMIN). This will
allow project-level check out for PPENGUIN.

5.g.iii. Will other developers know you have the project locked? Why or why not?
Yes, because the Locked property is true, and the Locked By Name property shows
PPENGUIN’s user ID.
5.h.iii. Do you have any projects locked?

Yes, the Asset Management project is now locked, as well as the ABC WF project.
5.h.iv. What is the value of the Locked By Name property for the Asset Management project?
PPENGUIN
6.b. What project does this object belong to?

Division
6.f. Select Project in the OE and query for locked projects in the OBLE. What project(s) are
locked?
Asset Management and ABC WF
6.g. Select Business Component :: User List in the OE. What signs are there that this object is
checked out?
Hint: Scroll to the right.
The Object Locked property is TRUE (checked), and Object Locked By is PPENGUIN.
7.a. Use Windows Explorer to navigate to the D:\OUsea\Tools\TEMP\Projects directory. What

is the name of the file located in this directory?
Asset_Management.sif
7.b. Navigate to D:\OUsea\Tools\TEMP\Objects. What file appears in this directory?

Business_Component_User_List.sif

8.c. What differences do you notice between the two?

(1) The “W” (for writeable) column has a pencil icon in the Asset Management Screen, but
not in the Asset Management Screen (eService).
(2) When you select one of the fields in the Asset Management Screen, the background is
white and you can edit the field. When you select one of the fields in the Asset Management
Screen (eService), the background is gray and you cannot edit the field.
9. One of your colleagues noticed that a developer could invoke Tools > Lock Project to lock
the project locally and make the definitions available for editing. What are the
consequences of doing this to edit the Asset Management Screen object definition?
They will be able to create and edit the object definitions, but they will not be able to check

them into the server. In addition, another developer can check out the Asset Management
project from the server and make a different set of changes.
10.b.ii. Click the drop-down arrow to open the Project picklist in the newly created record. Why
is Asset Management the only project listed?
Asset Management is the only project locked by PPENGUIN, and you can only add object
definitions to a project locked by the current user. ABC WF is also locked, but it is locked
by SADMIN, so PPENGUIN cannot use it.
11.a. Select Tools > Check In. What appears in the check in list and why?
Asset Management is the only locked project you have checked out, and is therefore the
only project that you can check in. User List appears with type Business Component,
because you did an object check out.


Module 23: Editing and Compiling Object Definitions
Lab 23-1 Editing and Validating Object Definitions

(Unguided)
Goal To practice using Siebel Tools for editing and validating object definitions.

Instructions:
You will practice modifying object definitions in Siebel Tools in this lab. You will verify your
changes using Tools’ Validation tool. These definition changes will be examined and archived in
the next lab.
1. If necessary, open Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the Local
database.
2. Change the Visibility Applet and Comments properties for the Asset Mgmt - Assets View.
Which properties change is not important; in this and the next steps you will see how Siebel
Tools tracks changes to objects and projects, and how you can validate object definitions.
a. Blank out the Visibility Applet property of the Asset Mgmt - Assets View.
b. Use the properties window to set the Comments property column of the Asset Mgmt -
Assets View record to “Deleted visibility applet”.
3. Explore the Inactive property. Each object definition has a property called Inactive. If Inactive is
set, the object definition will not be referenced by Siebel applications.
a. Mark View :: Asset Mgmt - Assets View as inactive and observe the results.
b. Reset the view to active.
4. Validate the Asset Mgmt - Assets View object definition. Which rule number was violated?
5. Deactivate that rule by clicking Options, then selecting it and clicking Ignore.
6. Rerun the validation and confirm that it no longer generates any errors.
7. Reset the rule so that it is once again enforced.

Solutions 23-1 Editing and Validating Object Definitions

(Unguided)
Answers:
4. Validate the Asset Mgmt - Assets View object definition. Which rule number was
violated?
Rule number 7.

Lab 23-1 Editing and Validating Object Definitions

(Guided)
Goal To practice using Siebel Tools for editing and validating object definitions.

Instructions:
You will practice modifying object definitions in Siebel Tools in this lab. You will verify your
changes using Tools’ Validation tool. These definition changes will be examined and archived in
the next lab.
1. If necessary, open Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the Local
database.
2. You will start this lab by changing the value of properties in both the Object List Editor (OBLE)
and the Properties window. You will change the Visibility Applet and Comments properties for
Asset Mgmt – Assets View. Which properties change is not important, but in this and the next
steps you will see how Siebel Tools tracks changes to objects and projects, and how you can
validate object definitions.
a. Select View :: Asset Mgmt – Assets View.
b. In the OBLE, tab over to the Visibility Applet property column and delete the field contents
so that it is blank (or null). Be careful not to click the drilldown to the Asset Mgmt – Asset
List Applet. Step off the record to commit your change.
c. Click the Properties tab to the left side of the OE. (If it is not there, select View > Windows
> Properties Window, then right-click on the Properties window display bar and select Auto-
Hide.)
d. In the Properties window, click the Comments property column of the Asset Mgmt – Assets
View record and enter Deleted visibility applet. Step off the record to commit your change.
3. You will now observe that some properties have picklists and some do not.
b. Double click the column header of the Name property to lock the Name column in place.
Scroll right and find the Thread Field property. Type in “Asset Tag” rather than using the
dropdown list. Tab out of the field. What happens?
c. Click Close.

4. Each object definition has a property called Inactive. If Inactive is set, the object definition will
not be referenced by Siebel applications.You will now explore this property.
a. Make sure View :: Asset Mgmt – Assets View is selected.
b. Click the Inactive column in the OBLE (this will toggle the setting of a TRUE/FALSE
value). Aside from the checkmark, what visual indication appears?
c. Look in the Properties window and verify that the Inactive property is set to TRUE; if not, set
it to TRUE.
d. Reset the Inactive property to FALSE and tab out of the column.

Note: You will use these techniques to edit property values throughout the configuration labs.
Be careful where you click, because you might set a property to TRUE or FALSE in the
OBLE by mistake. You might find it safer to use the tab key when moving from one column
to another in the OBLE.
5. Next, you will practice using the Validate option to verify your changes.
a. With View :: Asset Mgmt – Assets View selected in the OBLE, right-click and select
Validate.
b. Click Start to validate the Asset Mgmt – Assets View object definition. Wait a few moments
for the validation to complete.
i. Select the error listed and inspect the details listed in the Details box. Which rule
number was violated?
ii. Click Save As to save the details in a log file.

iii. Click Save.
c. Click Options to examine the rules that are checked during validation.
i. Click the Object column heading to sort the rules list by object type.
ii. Which rule numbers are specific to View objects?
iii. Which two rules apply to all objects?
iv. Select Rule 7.

v. Click Ignore to deactivate the rule. If necessary, scroll right to find the Enforce
column. Notice that its value is now No.
vi. Click OK.

d. Click Start to rerun your validation. Were any errors listed in the errors list? Why or why
not?
e. Click Load to examine the original validation error message. Click Open to view the former
log file.
f. Click Options to reactivate the screen rule.
i. Select Rule 7.
ii. Click Enforce to reactivate the rule. Notice the Enforce column value changes to
Yes.

iii. Click OK.
g. Click Cancel to close the dialog box.
Note: Validating your work frequently is a recommended practice.

Solutions 23-1 Editing and Validating Object Definitions

(Guided)
Answers:
3.b. Double click the column header of the Name property to lock the Name column in place.
Scroll right and find the Thread Field property . Set the value to Asset Tag. Tab out of the
field. What happens?
The value you entered disappeared and a pick applet showing a list of available fields
appears. Because Tag Asset isn’t a value that appears in the drop-down list, and this field

doesn’t accept any such values, Siebel Tools disallows this entry.
4.b. Click the Inactive column in the OBLE (this will toggle the setting of a TRUE/FALSE
value). Aside from the checkmark, what visual indication appears?
The color of the text for this record changes to red.
5.b.i. Select the error listed and inspect the details listed in the Details box. Which rule number
was violated?
Rule number 7
5.c.ii. Which rule numbers are specific to View objects?

Rule numbers 3, 5, 6, 7, 10, 11, 97, 118
5.c.iii. Which two rules apply to all objects?

Rule numbers 1 and 61
5.d. Click Start to rerun your validation. Were any errors listed in the errors list? Why or why
not?
No errors were detected, because the relevant error check has been deactivated.

Lab 23-2 Exporting and Importing Object Definitions

(Unguided)
Goal To explore the use of the Diff and Archive options in Siebel Tools.

Instructions:
In this lab you will walk through the following scenario:
You are unclear what changes you have made to the Asset Mgmt - Assets View object definition,
and you want to compare your local version to the version on the server. Having compared them,
you decide that you would like to keep the changes you have made to Asset Mgmt - Assets View.
However, the changes are not complete, so you do not want to check them in to the server yet. You
decide to use an archive file to save your version of the Asset Mgmt - Assets View object definition.
Later, you decide you want to delete your changes, but you cannot access the server. You decide to
import the original archive file that was created when you checked out the project.
1. Select Tools > Check In and select the Asset Management project. Use the Diff feature to
compare the object definitions you checked out, with those in the repository.
2. Add the Asset Mgmt - Assets View to an archive. Keep the archive window open.
3. Add the Asset Mgmt - Asset List Applet to the same archive and save it as myasset.sif.
4. Open myasset.sif using Notepad++ and examine the file. What does this file appear to contain?
5. Practice importing modified object definitions from an archive file. After further testing you
decide to start configuration again. You could check out the project again from the server, but
you are traveling and do not have access to the server. You decide to import the original archive
file that was created when you checked out the project.
a. Import the file Asset_Management.sif. This is the entire Asset Management project.
Replace the definitions in your repository.
b. Inspect the imported definition of View :: Asset Mgmt - Assets View and confirm that it is
back to its original form; that is, that it has a visibility applet specified.
6. Check in the original version of the project to release the local lock and the server lock.

Solutions 23-2 Exporting and Importing Object

Definitions (Unguided)
Answers:
4. Open myasset.sif using Notepad++ and examine the file. What does this file appear to
contain?
XML data with object definition information

Lab 23-2 Exporting and Importing Object Definitions

(Guided)
Goal To explore the use of the Diff and Archive options in Siebel Tools.

Instructions:
In this lab you will walk through the following scenario:
You are unclear what changes you have made to the Asset Mgmt – Assets View object definition,
and you want to compare your local version to the version on the server. Having compared them,
you decide that you would like to keep the changes you have made to Asset Mgmt – Assets View.
However, the changes are not complete, so you do not want to check them in to the server yet. You
decide to use an archive file to save your version of the Asset Mgmt – Assets View object definition.
Later, you decide you want to delete your changes, but you cannot access the server. You decide to
import the original archive file that was created when you checked out the project.
1. You will start by using the Diff feature to compare the object definitions you checked out, stored
in an archive file, with those in the repository.
a. Select Tools > Check In. The Check In dialog box will appear.
b. Select Asset Management and click the button marked Diff…
Note: Diff uses the local archive file to assist with the comparison.
c. In the left-hand Compare Objects window, expand Asset Management. Notice how the
right-hand window mirrors this action.
d. Examine the folder icon next to each node in the tree. Blue indicates no difference between
server and local definitions of an object or type. Pink indicates a difference. What object
type is marked with pink in the tree?
e. Expand the View type.

f. Scroll through the list of views in the Asset Management project. Which view has a
definition in the local database that differs from its definition on the server?
g. Select Asset Mgmt – Assets View.

h. Inspect the differences listed in the Properties window in the lower part of the dialog box.
Are there any differences?

i. Click Close.
j. Click Cancel.
2. Now you will practice saving modified object definitions to an archive file.
b. Select Tools > Add to Archive. Do not close the Export to Archive File window. You will be
adding more objects to the archive, and closing the window creates the archive file. Move the
window out of your way if necessary by dragging and dropping it to the side of the OBLE.
What is the default name of the archive file?
c. Select Applet :: Asset Mgmt – Asset List Applet to select the second definition you wish to
include. You have not changed this definition, but this technique shows you how to include

multiple object definitions in a single archive file.
d. Right-click the Asset Mgmt – Asset List Applet record and select Add to Archive. What do
you observe?
e. In the Archive file field, change the name of the archive file to
D:\OUsea\Tools\objects\myasset.sif.
f. Click Save.
3. Verify the archive file was created in the directory.

a. In Windows Explorer, navigate to D:\OUsea\Tools\OBJECTS.
b. Verify that it contains a myasset.sif file.
c. Right-click the myasset.sif file and select Open.
d. Select Select the program from a list and click OK.
e. In the Open With dialog box, select Notepad++. Click OK.
f. Observe the structure of the file. Do not make any changes.
g. What does this file appear to contain?
h. When you are finished, close the WordPad application.
4. Now, you will practice importing modified object definitions from an archive file. After further
testing you decide to start configuration again. You could check out the project again from the
server, but you are traveling and do not have access to the server. You decide to import the
original archive file that was created when you checked out the project.
a. In Siebel Tools, select Tools > Import from Archive.

b. Navigate to the D:\OUsea\Tools\TEMP\Projects directory in the Select Archive to Import

window and select Asset_Management.sif.
c. Click Open.
d. Inspect the list. It displays all the object definitions that are part of the archive. This is the
entire Asset Management project.
e. Click the Overwrite the object definition in the repository radio button to replace the
definition in your repository.
Note: Notice that you could also merge the definition from the file with the changes you
made in your repository.
f. Click Next. You may need to wait a few moments while the contents of the wizard screen are
generated. Notice that the display you see is somewhat similar to the Diff window. Select and
then expand the objects in the left-hand window. What appears in the right-hand window?

g. Click Next. Notice the summary information that informs you what will be changed.
h. Click Yes to proceed. Notice that the OBLE disappears as the import archive operation
completes.
i. Click Finish to close the Import Wizard Summary window.
5. Inspect the imported definition.

b. What is the value of the Visibility Applet property?
6. Check in the original version of the project to release the local lock and the server lock.
a. Select Tools > Check In.
b. Select Asset Management. Make sure Maintain Lock is not checked.
c. Click Check In.
7. When you check in the local version of the project (called an archive file), it is deleted from the
TEMP directory.
a. Navigate to D:\OUsea\Tools\TEMP\Projects.
b. Are there any files in the directory? Do you think releasing the lock on the project makes a
difference?
Note: You will use these techniques throughout the configuration labs. You should get into
the habit of using the Diff option if you cannot remember what you changed.

Solutions 23-2 Exporting and Importing Object

Definitions (Guided)
Answers:
1.d. Examine the icon next to each node in the tree. Blue indicates no difference between
server and local definitions of an object or type. Pink indicates a difference. What object
type is marked with pink in the tree?
View – the folder icon next to this type has a pink diamond on it, unlike the folder icon for
other object types.

1.f. Scroll through the list of views in the Asset Management project. Which view has a
definition in the local database that differs from its definition on the server?
1.h. Inspect the differences listed in the Properties window. Are there any differences?
Yes – two differences. The client (local) version of the view has its Comment property
equal to the string you entered in the first part of this lab, and the server version has its
visibility applet property set.
2.b. Select Tools > Add to Archive. Do not close the Export to Archive File window. You will
be adding more objects to the archive, and closing the window will create the archive file..
Move the window out of your way if necessary by dragging and dropping it to the side of
the OBLE. What is the default name of the archive file?
D:\OUsea\Tools\objects\objects.sif
2.d. Right-click the Asset Mgmt – Asset List Applet record and select Add to Archive. What
do you observe?
The second object definition selected appears in the list of objects to archive.
3.g. What does this file appear to contain?

XML data with object definition information
4.f. Click Next. You may need to wait a few moments while the contents of the wizard screen
are generated. Notice that the display you see is somewhat similar to the Diff window.
Select and then expand the objects in the left-hand window. What appears in the right-hand
window?
When you select an object that has been modified, the differences between the file and the
repository attributes are displayed, as well as a proposed resolution to the conflict. This
resolution has a value of File or Repository, and can be set by right-clicking on the
Resolution column.
5.b. What is the value of the Visibility Applet property?

The value is now Asset Mgmt – Asset List Applet. In an earlier lab, you deleted this field
value. As a result of importing the archive file, the field value was overwritten.

7.b. Are there any files in the directory? Do you think releasing the lock on the project makes a
difference?
No, as the Maintain Lock is not checked. If the Maintain Lock is checked the file(s) will not
be removed as the lock indicates that further work will be done with the project.


Lab 23-3 Creating a Custom Repository File (Unguided)
Goal To create a custom.srf file, which you will use in the remaining configuration labs.
Time 45 minutes
Instructions:

1. It is generally recommended that you use Compile All Projects to create a brand new .srf file to
build your configuration upon. You would not need to do this until you wished to test your first
configuration change. However, you are doing so now in preparation for labs in the coming
modules.
a. In which directory should siebel.srf be located?
b. In Windows Explorer, navigate to D:\OUsea\client\OBJECTS\ENU and rename siebel.srf to

siebel_back.srf. This file will be a backup in case the compile fails.
c. You should still be logged in to Siebel Tools as PPENGUIN connected to the Local database.
Note: You might wish to resize your window so that it does not take up the whole desktop.
The window will be frozen after you start compiling.
i. Select Tools > Compile Projects.
ii. Click Browse. Click the directory drop-down to see the full directory structure. What
directory are you in?
iii. Navigate to the D:\OUsea\client\OBJECTS\ENU directory and enter siebel.srf.

iv. Click Save.
v. Select All Projects.
vi. Click Compile.
Note: This might take 20 minutes. Continue with the next steps.
2. Edit D:\OUsea\client\bin\ENU\uagent.cfg to modify the application title for the ABC Call
Center application that you will be creating, to use the appropriate ODBC connection, and to set
the connection string to point at the local database.
a. Open uagent.cfg with Notepad and set the following parameter:
Application Title ABC Call Center
b. Scroll down and find a line that starts with “LocalDbODBCDataSource”. Change the value
of this parameter from SEAW Local Db default instance to SSD Local Db default
instance. An ODBC data source stores information how to connect to a data source, and
includes parameters such as the database file location(s) and the executable to access the
database. The first ODBC data source, starting with SEAW, describes a database in the

client subdirectory. The second, starting with SSD, refers to a database in the tools
subdirectory. Because you first initialized the local database using Siebel Tools, the local
database file was created in D:\OUsea\tools\LOCAL. Because of its location in the tools
subdirectory, this data source is described by the SSD Local Db default instance.
c. Find the line that reads “[Local]”. Below this, change the ConnectString parameter to read:
D:\OUsea\tools\local\sse_data.dbf –q –m –x NONE –gp 4096 –c15p –ch25p
Note: You will probably only need to change the word “Client” to “Tools”. You are
changing this connect string to point to the local database (sse_data.dbf).
d. Set the DockConnString parameter to localhost.
e. Save the changes and exit the uagent.cfg file.
3. When the compile you started earlier is complete, verify your work.
a. Navigate to the D:\OUsea\Client\OBJECTS\ENU directory and verify the directory contains

siebel.srf with a recent Date Modified.
b. Select Start > Programs > Siebel Web Client 8.0 > Siebel Call Center – ENU and log in as
PPENGUIN/PPENGUIN to the Local database.
c. Select Help > Technical Support. Verify the parameters are as follows:
User ID PPENGUIN
ConnectString D:\OUsea\tools\local\sse_data.dbf –q –m –x NONE –gp
4096 –c15p –ch25p
Table Owner SIEBEL
Repository File D:\OUsea\client\objects\enu\siebel.srf
d. Exit the application.
4. You will now make some changes to Tools options to make modifying and testing your
application easier.
a. First you will set up Tools so that you can launch the Siebel Developer Web Client directly
from Siebel Tools.
i. From the application View menu, select Options > Debug, and then enter the values
in the table below. These parameters will be used to start up the modified Siebel Call
Center application directly from Siebel Tools.
IMPORTANT: Click the ellipsis buttons to locate the file names for CFG and
Browser.
Executable D:\OUsea\client\BIN\siebel.exe
CFG file D:\OUsea\client\BIN\ENU\uagent.cfg
Browser D:\Program Files\Internet Explorer\IEXPLORE.exe
Working directory D:\OUsea\client\BIN
Arguments /h
User name PPENGUIN
Password PPENGUIN
Data source Local
ii. Click OK.

b. Verify in Siebel Tools that you can modify Web templates using the Web Layout editor.
i. In the Target Browser field of the Configuration Context toolbar, select Target
Browser Config.
Note: If Target Browser Config does not appear in your toolbars, from the application
View menu, select Toolbars > Configuration Context and add it.
ii. In the Selected browsers: field, verify that IE 6.0 appears in the list. If it does not,
select IE 6.0 in the Available browsers: field and click the right-arrow to move IE
6.0 into the Selected Browsers field.
iii. Click OK.
iv. Select IE 6.0 in the Target Browser drop-down list.
c. Test your work.
i. Select Debug > Start (or press the F5 key on your keyboard).

ii. If the application does not start, check the values you typed above. If this does not
work, ask your instructor for assistance.
iii. Log out of Siebel Call Center.

Solutions 23-3 Creating a Custom Repository File

(Unguided)
Answers:
1.a. In which directory should siebel.srf be located?
D:\OUsea\client\OBJECTS\ENU. The .srf file should be in the OBJECTS\ENU
subdirectory of the directory where you install the Siebel client software.
1.c.ii. Click Browse. Click the directory drop-down to see the full directory structure. What

D:\OUsea\tools\OBJECTS\ENU

Lab 23-3 Creating a Custom Repository File (Guided)
Goal To create a custom.srf file, which you will use in the remaining configuration labs.
Time 45 minutes
Instructions:

1. It is generally recommended that you use Compile All Projects to create a brand new .srf file to
build your configuration upon. You would not need to do this until you wished to test your first
configuration change. However, you are doing so now in preparation for labs in the coming
modules.
a. In which directory should siebel.srf be located?
b. In Windows Explorer, navigate to D:\OUsea\client\OBJECTS\ENU and rename siebel.srf to

siebel_back.srf. This file will be a backup in case the compile fails.
c. You should still be logged in to Siebel Tools as PPENGUIN connected to the Local database.
Note: You might wish to resize your window so that it does not take up the whole desktop.
The window will be frozen after you start compiling.
ii. Click Browse. Click the directory drop-down to see the full directory structure. What
iii. Navigate to the D:\OUsea\client\OBJECTS\ENU directory and enter siebel.srf.

iv. Click Save.
v. Select All Projects.
vi. Click Compile.
Note: This might take 20 minutes. Continue with the next steps.
2. Edit D:\OUsea\client\bin\ENU\uagent.cfg to modify the application title for the ABC Call
Center application that you will be creating, to use the appropriate ODBC connection, and to set
the connection string to point at the local database.
a. Open uagent.cfg with Notepad and set the following parameter:
Application Title ABC Call Center
b. Scroll down and find a line that starts with “LocalDbODBCDataSource”. Change the value
of this parameter from SEAW Local Db default instance to SSD Local Db default
instance. An ODBC data source stores information how to connect to a data source, and
includes parameters such as the database file location(s) and the executable to access the
database. The first ODBC data source, starting with SEAW, describes a database in the

client subdirectory. The second, starting with SSD, refers to a database in the tools
subdirectory. Because you first initialized the local database using Siebel Tools, the local
database file was created in D:\OUsea\tools\LOCAL. Because of its location in the tools
subdirectory, this data source is described by the SSD Local Db default instance.
c. Find the line that reads “[Local]”. Below this, change the ConnectString parameter to read:
D:\OUsea\tools\local\sse_data.dbf –q –m –x NONE –gp 4096 –c15p –ch25p
Note: You will probably only need to change the word “Client” to “Tools”. You are
changing this connect string to point to the local database (sse_data.dbf).
d. Set the DockConnString parameter to localhost.
e. Save the changes and exit the uagent.cfg file.
3. When the compile you started earlier is complete, verify your work.
a. Navigate to the D:\OUsea\Client\OBJECTS\ENU directory and verify the directory contains

siebel.srf with a recent Date Modified.
b. Select Start > Programs > Siebel Web Client 8.0 > Siebel Call Center – ENU and log in as
c. Select Help > Technical Support. Verify the parameters are as follows:
User ID PPENGUIN
ConnectString D:\OUsea\tools\local\sse_data.dbf –q –m –x NONE –gp
4096 –c15p –ch25p
Table Owner SIEBEL
Repository File D:\OUsea\client\objects\enu\siebel.srf
d. Exit the application.
4. You will now make some changes to Tools options to make modifying and testing your
application easier.
a. First you will set up Tools so that you can launch the Siebel Developer Web Client directly
from Siebel Tools.
i. From the application View menu, select Options > Debug, and then enter the values
in the table below. These parameters will be used to start up the modified Siebel Call
Center application directly from Siebel Tools.
IMPORTANT: Click the ellipsis buttons to locate the file names for CFG and
Browser.
Executable D:\OUsea\client\BIN\siebel.exe
CFG file D:\OUsea\client\BIN\ENU\uagent.cfg
(or wherever you have IEXPLORE installed)
Working directory D:\OUsea\client\BIN
Arguments /h
User name PPENGUIN
Password PPENGUIN
Data source Local
ii. Click OK.

b. Verify in Siebel Tools that you can modify Web templates using the Web Layout editor.
i. In the Target Browser field of the Configuration Context toolbar, select Target
Browser Config…
Note: If Target Browser Config… does not appear in your toolbars, from the
application View menu, select Toolbars > Configuration Context and add it.
ii. In the Selected browsers: field, verify that IE 6.0 appears in the list. If it does not,
select IE 6.0 in the Available browsers: field and click the right-arrow to move IE
6.0 into the Selected Browsers field.
iii. Click OK.
iv. Select IE 6.0 in the Target Browser drop-down list.
c. Test your work.
i. Select Debug > Start (or press the F5 key on your keyboard).

ii. If the application does not start, check the values you typed above. If this does not
work, ask your instructor for assistance.
iii. Log out of Siebel Call Center.

Solutions 23-3 Creating a Custom Repository File

(Guided)
Answers:
1.a. In which directory should siebel.srf be located?
D:\OUsea\client\OBJECTS\ENU. The .srf file should be in the OBJECTS\ENU
subdirectory of the directory where you install the Siebel client software.
1.c.ii. Click Browse. Click the directory drop-down to see the full directory structure. What

D:\OUsea\tools\OBJECTS\ENU

Module 24: UI Layer Configuration - Web Templates
Lab 24-1 Exploring Template Files (Unguided)
Goal To practice using the Web Template Explorer and to examine the relationship between
views and applets, and their associated templates.
Instructions:

Due to the exploratory nature of this lab, there is no Unguided version of it. Please turn the page and


Lab 24-1 Exploring Template Files (Guided)
Goal To practice using the Web Template Explorer and to examine the relationship between
views and applets, and their associated templates.
Instructions:

Siebel applications are specified by a set of physical UI files that determine how the logical UI will
be physically rendered in a browser. These files are not composed of object definitions and are the
main focus of this module. In this lab, you will use Tools to explore various template files.
1. In this step, you will practice using the Web Template Explorer to examine the contents of Web
template files. Web Template Explorer is a template browser that allows you to examine the
contents of template files without having to open them directly. It functions very similarly to the
OE and the OBLE. Templates are displayed in a parent / child relationship, with the child
template files available for viewing by clicking the parent file in the tree.
a. If necessary, start Siebel Tools and log in as PPENGUIN connecting to the Local database.
b. From the application-level menu, select View > Windows > Web Templates Window to view
the Web Template Explorer.
c. Scroll down until you locate CCPopupContainer. Select CCPopupContainer to display the
contents of the template file.
d. Examine the first line in the file. What is the full name of the template file?
e. What is the name of the first file that is included in this template file?
f. Expand CCPopupContainer by clicking the + (plus) sign. Expanding the CCPopupContainer

parent web template exposes all child template files included within the parent. How many
template files are included in the CCPopupContainer template file?
g. Click the child CCStylesChoice template. What did you observe in the pane that displays the
contents?
h. Close the Web Template File window and the Web Template Explorer.

2. In this step, you will examine how multiple views can use the same template.
a. Select the Flat tab in Object Explorer.
b. Select View Web Template.
c. Execute a query to select View Web Templates where Web Template property = View
Detail. This query displays all views that use the View Detail web template. When using Flat
Tab, the associated view appears under the Parent View property. About how many views
use this template (10; 100; 500 or more)? Depress the down arrow in the vertical scrollbar of
the OBLE until you are comfortable answering the question.
d. Click the Types tab to restore the Object Explorer to the hierarchical display mode.

3. In this step, you will examine how views map to templates and how applets in views map to
swe:applet tags in the corresponding template file. Web Template Item is a child object of the
applet. It defines mappings between controls and list columns to placeholder tags or locations in
the Web template file. They contain the name of a control or list column as well as an identifier
of a template placeholder. At run time, the placeholder determines the position of the control or
list column in the Web page. For more information, reference the Configuring Screens and
Views chapter in Configuring Siebel eBusiness Applications.
a. Select View :: Account List View | View Web Template :: Base. What is the name of the
Web Template associated with the Account List view?
b. Select View :: Account List View | View Web Template :: Base | View Web Template Item.
Which applets are listed and what is the corresponding Item Identifier?
c. Next, determine the file name for View Detail (Parent with Pointer). Select Web Template ::
View Detail (Parent with Pointer) | Web Template File. If you are querying for the template,
recall that you must bracket the object name with single quotes when the query includes
special characters, such as parentheses: ( ). What is the Filename of the Web Template File?
Ensure you write the name in the blank space provided, below. You will reference this later
in the lab.
4. In this step, you will explore the Item Identifier property. The Web Template Item property Item
Identifier specifies a unique numeric identifier for each control. The value is used in the markup
language tag that specifies the corresponding control in a template, binding the control to a
specific position on the page. It does not impose a hierarchy or priority of web template items.
a. Open the Web Template Explorer.
Tip: Select View > Windows > Web Templates Window to view the Web Template
Explorer.
b. Select the CCViewDetail_ParentPntr.swt template file.

c. Peruse the Main Content Area to locate the swe:applet tag with id=1. Look for the following:
Note the Item Identifier property in the View Web Template Items window. You may need to
re-position the template file window or navigate to Account List View | View Web Template
:: Base | View Web Template Item.
d. Compare the item identifier in the View Web Template Items window to the HTML
“Applet” id value. You can also view the HTML hintText value. In this case, its value is
“Parent Applet”. The diagram, below, illustrates the mapping.

e. Which applet is bound to Item Identifier 1?
f. Close the Web Template File window and the Web Template Explorer.
5. In this step, you will examine how applets map to templates and how controls in applets map to
swe:control tags in the corresponding template file. You will do this for the Contact Service
Request List Applet (eService), which has been configured for use in a standard interactivity
application.
a. Select Applet :: Contact Service Request List Applet (eService) | Applet Web Template.
b. View the Web Template property. What are the names of the Web Templates for the list
applet?
c. Next, you will observe individual Web templates and see how Controls map to Web
Template Item Identifiers.
i. Select Applet :: Contact Service Request List Applet (eService) | Applet Web
Template:: Query | Applet Web Template Item. Be sure to select Query in the Applet

Web Template window. Notice the number of web template items displayed and their
names.
ii. Compare Query mode to Edit Mode. Select Applet :: Contact Service Request List
Applet (eService) | Applet Web Template:: Edit | Applet Web Template Item. Notice
the number of web template items displayed and their names. How do web template
items vary when using query mode versus edit mode?
iii. Think about the level of user interaction when querying versus editing. Typically,
editing interactions are more involved. When comparing Query against Edit mode,
why are there differences in the controls that are rendered in the applet?

d. Now you will examine the template file used for query mode. Select Web Template ::
DotCom Applet Form 1-Column | Web Template File. It is the file used for both Edit and
Query modes for the Contact Service Request List Applet (eService). What is the Filename
of the Web template file?
6. In this step, you will identify which controls in the Web template map to the Item Identifier
property in Tools.
a. Open the Web Template Explorer.
b. Select the dCCAppletForm1Col template file. Note that this file includes additional
template files.
c. Expand the template file and click dCCForm1Col.
d. In the bottom window, scroll down to the first purple colored tag.
e. Locate the following swe for-each tag.
<swe:for-each count=”6” startValue=”1300” iteratorName=

”currentId”

f. This tag starts with an ID of 1300 and iterates six times, incrementing the ID value by one
each time. The screen print, below, displays the Applet Web Template Items for the DotCom
Applet Form 1-Column web template. Draw directly on the screen print, below, to indicate
which controls will be rendered by the SWE tag, above.

Solutions 24-1 Exploring Template Files (Guided)
Answers:
1.d. Examine the first line in the file. What is the full name of the template file?
CCPopupContainer.swt.
1.e. What is the name of the first file that is included in this template file?
CCStylesChoice.swt.
1.f. Expanding the CCPopupContainer parent web template exposes all child template files

included within the parent. How many template files are included in the
CCPopupContainer template file?
1, CCStylesChoice.swt.
1.g. Click the child CCStylesChoice template. What did you observe in the pane that displays
the contents?
The HTML code window displays both parent and child templates in a split view. The
upper pane displays the contents of the parent template file while the lower pane displays
the child template.
2.c. Execute a query to select View Web Templates where Web Template property = View
Detail. This query displays all views that use the View Detail web template. When using
Flat Tab, the associated view appears under the Parent View property. About how many
views use this template (10; 100; 500 or more)?
Over 500 views use the View Detail template.
3.a. Select View :: Account List View | View Web Template :: Base. What is the name of the
Web Template associated with the Account List view?
View Detail (Parent with Pointer).
3.b. Select View :: Account List View | View Web Template :: Base | View Web Template
Item. Which applets are listed and what is the corresponding Item Identifier?
Account List Applet (1) and Account Entry Applet (2).
3.c. Next, determine the file name for View Detail (Parent with Pointer). Select Web Template
:: View Detail (Parent with Pointer) | Web Template File. If you are querying for the
template, recall that you must bracket the object name with single quotes when the query
includes special characters, such as parentheses: ( ). What is the Filename of the Web
Template File?
CCViewDetail_ParentPntr.swt.
4.e. Which applet is bound to Item Identifier 1?

The Account List Applet (the parent applet in the Account List view) is bound to tag 1.

5.b. View the Web Template property. What are the names of the Web Templates for the list
applet?
DotCom Applet List Tabbed and DotCom Applet Form 1-Column
5.c.ii. Compare Query mode to Edit Mode. Select Applet :: Contact Service Request List Applet
(eService) | Applet Web Template:: Edit | Applet Web Template Item. Notice the number
of web template items displayed and their names. How do web template items vary when
using query mode versus edit mode?
The number and type of web template item varies depending on the mode. For example,
edit mode includes items not present with query mode, such as Cancel, HelpText, and
WriteRecord. Conversely, query mode includes items not present with edit mode, such as
CancelQuery and ExecuteQuery.
5.c.iii. Think about the level of user interaction when querying versus editing. Typically, editing

interactions are more involved. When comparing Query against Edit mode, why are there
differences in the controls that are rendered in the applet?
They are used in different contexts: one for querying and one for editing. In this case, more
fields are required when the applet is used for editing.
5.d. Now you will examine the template file used for query mode. Select Web Template ::
DotCom Applet Form 1-Column | Web Template File. It is the file used for both Edit and
Query modes for the Contact Service Request List Applet (eService). What is the Filename
of the Web template file?
dCCAppletForm1Col.swt.

6.f. This tag starts with an ID of 1300 and iterates six times, incrementing the ID value by one
each time. The screen print, below, displays the Applet Web Template Items for the
DotCom Applet Form 1-Column web template. Draw directly on the screen print, below, to
indicate which controls will be rendered by the SWE tag, above.

Module 25: UI Layer Configuration - Applets
Lab 25-1 Modifying a Form Applet (Unguided)
Goal To modify a form applet by removing and adding controls.
Instructions:

In this lab, you will update an applet to display a few changes that your business requires. To meet
some of your business requirements, you will remove the Manufactured Date field that appears on
the Asset Management – Asset Detail Applet. You will then add a Status field named “ABC Code”
to the applet.
1. Determine which applet you need to modify.

a. If necessary, start Siebel Tools and log in as PPENGUIN/PPENGUIN connecting to the
Local database.
b. Open Siebel Call Center using the Siebel Developer Web Client and log in as
c. Navigate to Assets > List.
d. Inspect the form applet for the manufactured date that will be removed from the display:
e. What is the name of the form applet in this view?
f. What is the name of the view?

2. Perform the configurations necessary to be able to modify symbolic strings.

a. Verify that tools.cfg parameters are set to allow string creation. To be able to create symbolic
strings or string override fields, EnableToolsConstrain must be set to FALSE.
i. Use Notepad to open D:\OUSea\tools\bin\enu\tools.cfg and verify or set the
EnableToolsConstrain parameter.
b. Create and lock a new ABC Strings project to hold your symbolic string. There is an existing
Symbolic String project, but it is very large, so recommended practice is to create a new
project and store all new or modified strings in that project.
c. Expose the Symbolic String object type in the OE. Recall that the OE has the ability to
display many object types.
d. Create a new symbolic string that will be used to display the ABC status code. After you
have defined the string object once, you can reference it anywhere in the application. Any

change you wish to make to this string can be made a single time in Tools, and the resulting
change will appear wherever it is referenced in the application.
Note: The X_ prefix is automatically generated to differentiate new from existing strings.
Property Value
Name X_ASSET_CODE
Current String Value ABC Code
Project ABC Strings
3. Modify the Asset Mgmt - Asset Detail Applet to match the requirements detailed above.
a. Remove the Manufactured control and label from the applet.
b. In the Object Explorer, select Applet :: Asset Mgmt - Asset Detail Applet | Control :: Status
c. Change the Caption - String Reference property of the Status control to
X_ASSET_CODE. This will cause the Status Label to display the new ABC Code string.
Changing String Reference to X_ASSET_CODE also sets the Caption to the reference’s
associated string you created earlier, ABC Code. .
d. Add the Status text control to where the Manufactured text control previously appeared.
4. Use the Format menu to format the form applet.
5. Compile and check your work. Verify that the Status field is displayed in the form applet where
Manufactured previously appeared. It should look like this:

Solutions 25-1 Modifying a Form Applet (Unguided)
Answers:
1.e. Select Help > About View. What is the name of the form applet in this view?
Asset Mgmt - Asset Detail Applet
1.f. What is the name of the view?

Asset Mgmt - Assets View


Lab 25-1 Modifying a Form Applet (Guided)
Goal To modify a form applet by removing and adding controls.
Instructions:

In this lab, you will update an applet to display a few changes that your business requires. To meet
some of your business requirements, you will remove the Manufactured Date field that appears on
the Asset Management – Asset Detail Applet. You will then add a Status field named “ABC Code”
to the applet.
1. In this step, you will determine which applet you need to modify.
Local database.
b. Open Siebel Call Center using the Siebel Developer Web Client and log in as
PPENGUIN/PPENGUIN to the Local database. As an alternative, to quickly launch the
Developer Web Client from Tools, select Debug > Start or press F5.
d. Inspect the form applet for the manufactured date that will be removed from the display:
e. Select Help > About View. What is the name of the form applet in this view?
f. What is the name of the view?
g. Click OK to close the About View dialog box.

2. In this step, you will verify tools.cfg parameters are set to allow string creation. To be able to
create symbolic strings or string override fields, EnableToolsConstrain must be set to FALSE.
This parameter determines the constrain mode. When set to TRUE, you must choose from a list
of string references in order to enter values for translatable text strings, such as an Applet Title,
and you cannot create new symbolic strings. When FALSE, you can override the string reference
using the string override property, and you can create new symbolic strings.
a. Log out and close Siebel Tools.
b. Use Notepad to open D:\OUSea\tools\bin\enu\tools.cfg.
c. Verify the following parameter under the [Siebel] section:
Parameter Value
EnableToolsConstrain = FALSE

d. If necessary, save any changes, then close tools.cfg.
e. Start Siebel Tools then log in as PPENGUIN/PPENGUIN to the Local database.
3. In this step, you will create a new project to hold your symbolic string. There is an existing
Symbolic String project, but it is very large. Due to its size, checking in or checking out the
entire project can be very time consuming. Thus, it is not recommended that you check out the
entire Symbolic String Project. Instead, create a new project and store all new or modified strings
in that project. When you want to add or work on new strings you can then use this new project.
a. In the Object Explorer, select Project.
b. Create a new record with the following values:
Property Value
Name ABC Strings
Locked True (Checked)
Note: You can use strings from the Siebel repository (denoted by the “SBL_” prefix in the
Symbolic String Name property) by selecting the strings you wish to modify and changing
their Project property to your new project.
4. In this step, you will expose the Symbolic String object type in the OE. Recall that the OE has
the ability to display many object types. To simplify usage, you can show or hide these types as a
group or individually.
a. From the Tools application-level menu, select View > Options.
b. Click the Object Explorer tab.
c. Click the checkbox next to the Symbolic String object. The checkbox should have a
checkmark with a white background. This will expose the Symbolic String object type and
its child object in the Object Explorer.
d. Click OK to return to Siebel Tools.
5. In this step, you will create a new symbolic string that will be used to display the ABC status
code. After you have defined the string object once, you can reference it anywhere in the
application. Any change you wish to make to this string can be made a single time in Tools, and
the resulting change will appear wherever it is referenced in the application.
a. In the OE, select Symbolic String.

b. Click anywhere in the OBLE then enter CTRL+N to create a new record.
c. Set the properties for this new symbolic string object definition using values from the table,
below.
Property Value
Name X_ASSET_CODE
Current String Value ABC Code
Project ABC Strings
6. In this step, you will modify the Asset Mgmt - Asset Detail Applet.
a. Select Applet :: Asset Mgmt - Asset Detail Applet. Note that it is currently read-only. What
must be done to make this object definition editable?

b. To which project does the Asset Management – Asset Detail Applet belong?
c. Select Tools > Check Out.

d. Select Asset Management from the list.
e. Click Check Out. If Check Out is not available, you must disable object locking for the
project:
i. Start Siebel Tools and log in as SADMIN/SADMIN connecting to the Server
database.
iii. Right-click and select Toggle Allows Object Locking.
iv. Exit Siebel Tools.
f. Click OK.
Note: Instead of checking out an entire project, you could check out a single object, such as
the Asset Detail Applet. Checking out individual objects allows multiple developers to work
on objects within a single project, improves check-out and check-in times, and reduces
network traffic. However, there could be some additional management overhead in checking
out objects instead of projects (more items to track and keep synchronized across
developers). An administrator enables or disables Allow Object Locking on the project in
which the object resides. This feature is enabled by default. For more information, reference
Using Siebel Tools.
g. Select Applet :: Asset Mgmt - Asset Detail Applet. Right-click and select Edit Web Layout.
h. In the Controls/Columns window, ensure the Mode: field is set to 1: Edit. If not, set it now.
Applet modes determine how a given applet is rendered at run time. In this case, you want to
allow users to edit records, create new records, and query records in a form applet. Edit mode
enables this usage.
i. In the Controls/Columns window, increase the width of the Mapped column until it is
sufficiently wide to read. Note that fields have a Mapped value of Y or N (yes or no).
Mapped indicates whether a given control is mapped in the selected applet.
j. In the Controls/Columns window, ensure Show unmapped controls only has a checkmark.
Any given applet can incorporate the use of a large number of controls. You can limit the

controls visible in the Controls / Columns window to display only those controls that are
unmapped in the currently selected applet.
k. At your discretion, you may choose to auto-hide the OE, Controls / Columns, and Palettes
windows in order to make more room for the Web Layout Editor.
7. In this step, you will remove the manufactured control and label from the applet.
a. In the Web Layout editor, select the Manufactured control:
b. Right-click and select Delete.

c. Select the Manufactured label.

d. Right-click and select Delete. Note that the Manufactured text control and label you just
removed from the applet now appear in the Controls / Columns window as an unmapped
control.
e. Select File > Save to save the applet.
f. Close the applet using File > Close.
8. In this step, you will edit the Status Label to show the caption ABC Code that was created
above.
a. In the Object Explorer, select Applet :: Asset Mgmt - Asset Detail Applet | Control :: Status
b. In the OBLE, change the property Caption – String Reference to X_ASSET_CODE. This
will cause the Status Label to display the new ABC Code string. Changing String Reference
to X_ASSET_CODE also sets the Caption to the reference’s associated string you created
earlier, ABC Code.
9. In this step, you will add a control to the form Applet.

a. In the OBLE, right-click the Asset Mgmt – Asset Detail Applet and select Edit Web Layout.
b. In the Controls/Column window, ensure mode is set to 1:Edit.
c. To provide enough space for the web layout editor to fully display in the viewable area, auto-
hide the Palette and Object Explorer windows.
d. In the Controls/Columns window, find the StatusLabel control. Drag and drop it onto the
form applet where the Manufactured label previously appeared. Note that the StatusLabel
control is now labeled “ABC Code:”.
e. In the Controls/Columns window, find the Status text control. Drag and drop it onto the form
applet where the Manufactured text control previously appeared. Note that the Status text
control now displays “ABC Code”.
10. In this step, you will format the form applet.

a. Hold down the Shift key and select the Status text control. Do not select the label.
b. Continue to hold the Shift key down, and select the Shipped text control. Both controls
should now be selected. When selecting multiple items, any format changes you make will
conform to the format of the last item selected. Ensure the Shipped text control was selected
last or the next steps in this lab will not work properly.

c. Siebel Tools includes an application-level menu that allows you to perform a number of
formatting tasks. From the application-level menu, select Format > Make Same Size > Both.
This will make the Status text control the same size as Shipped.
d. Select Format > Align > Lefts. This will align the left edges of the controls so they appear in

a single column.
e. Click in the gray area of the applet to unselect all controls.
f. Select the Status text control (not the label).
g. Shift+click the Product control.
h. Select Format > Align > Bottoms. This will align the bottom edges of the controls so they
appear in a single row.
i. Click in the gray area of the applet to unselect all controls.
j. Repeat these steps for the labels that appear next to the text controls.
k. Close the Layout Editor. When prompted, ensure you save your changes.
11. Compile your work.

a. If necessary, navigate to Applet :: Asset Mgmt - Asset Detail Applet.
b. In the OBLE, right-click Asset Mgmt - Asset Detail Applet and select Compile Selected
Objects.
c. In the dialog box, ensure the path for the Siebel repository file is set to
D:\OUsea\client\OBJECTS\ENU\siebel.srf. For these labs, since you are working as a local
developer you will be compiling into D:\OUsea\client\OBJECTS\ENU\siebel.srf. When
compiling, Tools defaults to D:\OUsea\tools\OBJECTS\ENU\siebel.srf, which is also the srf
Tools runs against. Therefore, to avoid overwriting the SRF file used by Siebel Tools and
save the changes to the client application, you must compile to
D:\OUsea\client\OBJECTS\ENU\siebel.srf.
d. Check the box marked “Auto Start Web Client”.
e. Click Compile.
12. Check your work.

a. In the Siebel client, navigate to Assets > List.

b. Verify that the Status field is displayed in the form applet where Manufactured previously
appeared. It should look like this:

Solutions 25-1 Modifying a Form Applet (Guided)
Answers:
1.e. Select Help > About View. What is the name of the form applet in this view?
Asset Mgmt – Asset Detail Applet
1.f. What is the name of the view?

6.a Select Applet :: Asset Mgmt - Asset Detail Applet. Note that it is currently read-only. What

must be done to make this object definition editable?
Either the project or the object must be checked out.
6.b. To which project does the Asset Management – Asset Detail Applet belong?
Asset Management


Lab 25-2 Creating a List Applet (Unguided)
Goal To create a list applet.
Instructions:

In this lab, you will create an applet to display some of the most important data about assets for use
by field service representatives.
1. Create a project to contain the new applets you will build for your application. You could use an
existing project for your applet, but we’ll create a new project for new items we create.
Property Value
Name ABC New Applets
Locked TRUE
2. Use the List Applet Wizard to create the ABC Asset Characteristics list applet.
a. In the General dialog box of the List Applet Wizard, set the properties to the values shown in
the table, below. To ensure field properties are set correctly, use dropdown lists to populate
fields, when available.
Property Value
Project ABC New Applets
Name ABC Asset Characteristics List Applet
Display Title Characteristics
Business Component Asset Mgmt – Asset
Upgrade Behavior Preserve
b. In the top list of the wizard, select the templates for Base and Edit List modes using the
values in the table, below.
Field Value
Template for Base read-only mode Applet List (Base/EditList)
Template for Edit List mode Applet List (Base/EditList)
Note: the Web Layout – General wizard screen lets you select among a variety of potential
web templates. To assist in selecting the most appropriate template for your display
requirements, consider doing the following: In the UI, find an existing applet with a layout
similar to the display you require, then use About View and Siebel Tools to find out which
template is used.

c. In the bottom dialog box of the wizard, select the template for Edit mode:
Field Value
Template for Edit mode Applet List Edit (Edit/New/Query)
d. In the Web Layout – Fields dialog box of the wizard, add the fields that will be in the applet.
Sequence Field Name
1 Asset Number
2 Serial Number
3 Asset Description
4 Product Name
5 Product Part Number

6 Product Description
7 Status
e. Click Next to accept the defaults in the Web Layout – Fields dialog box.
f. Click Finish in the Finish dialog box.
3. Preview the wizard output.
4. Set up the Product Name field so that it enables the end-user to select from a list of available
products using the Asset Mgmt - Internal Product Pick Applet.
5. Validate the applet you created then compile your changes into the client .srf file. Can you view
the new customization in your application now? Why, or why not?

Solutions 25-2 Creating a List Applet (Unguided)
Answers:
5.c. Can you view the new customization in your application now? Why, or why not?
No, because the applet has not been added to a view visible in the application.


Lab 25-2 Creating a List Applet (Guided)
Goal To create a list applet.
Instructions:

In this lab, you will create an applet to display some of the most important data about assets for use
by field service representatives.
1. In this step, you will create a project to contain the new applets you will build for your
application. You could use an existing project for your applet, but we’ll create a new project for
new items we create. This way, applets associated with the existing project remain available to
other developers. Since locking the project ensures other developers cannot access it or any of its
objects, the Project then becomes available to the developer to make associations to it in other
settings, such as in Wizards, as you’ll see later in this lab.
Local database.
b. Select Project in the Object Explorer. Add a new project record with the following values:
Property Value
Name ABC New Applets
Locked TRUE
c. Why can you not check the project out?
2. In this step, you will use the List Applet Wizard to create the ABC Asset Characteristics list
applet. It is highly recommended you use wizards, where possible. In this example, the List
Applet Wizard helps you identify all the correct properties and automatically creates the list
applet; child objects, such as the Web Template and Web Template Items; the list; the list
column; and controls. The wizard also relates the applet to a business component. Alternatively,
you create applets manually by defining all the necessary properties and child objects.
a. To start the wizard, select File > New Object.
b. Click the Applets tab in the New Object Wizards dialog box.
c. Select List Applet.
d. Click OK.
e. In the General dialog box of the List Applet Wizard, set the properties to the values shown in
the table, below. To ensure field properties are set correctly, use dropdown lists to populate

fields, when available. This prevents typographical errors. It also ensures any required hidden
characters or spaces are included.
When specifying the Project property, only locked projects will appear as an option in the
wizard. This is also true for the Project property in the OBLE on any applet. A project must
be locked before it can be related to an object. If the project is not locked, it won’t appear as
a selectable option in the project property in the OBLE.
Upgrade Behavior determines whether a UI object can be preserved during an upgrade. In

general, we set it to Preserve, which makes the object available for Incorporate Custom
Layout (ICL) when performing a repository merge. Upgrade Behavior is defined on screens,
views, and applets. At each release, Oracle sets the value of Upgrade Behavior for UI
objects. Do not change these values. For more information, reference Siebel Database

Upgrade Guide.
Property Value
Name ABC Asset Characteristics List Applet
Display Title Characteristics
Business Component Asset Mgmt – Asset
f. Click Next.
g. In the top list of the wizard, select the templates for Base and Edit List modes using the
values in the table, below. The wizard prompts you to select templates for three different
modes: Base (displays fields in read-only mode.), Edit List (allows users to edit records,
create new records, and query in a list applet), and Edit. Applet List (Base/EditList) is used
here for the first two modes since: 1), it most closely mirrors display requirements for your
application; 2), it combines both Base and Edit mode requirements. For additional
information about edit modes, reference Configuring Applets, Configuring Siebel eBusiness
Applications.
Field Value
Template for Base read-only mode Applet List (Base/EditList)
Template for Edit List mode Applet List (Base/EditList)
Note: the Web Layout – General wizard screen lets you select among a variety of potential
web templates. To assist in selecting the most appropriate template for your display
requirements, consider doing the following. In the UI, find an existing applet with a layout
similar to the display you require, then use About View and Siebel Tools to find out which
template is used. Another method to explore various template designs is to navigate to Select
Web Templates in the OE, click a familiar template name, right-click, and select View Web
Layout.

h. In the bottom dialog box of the wizard, select the template for Edit mode:
Field Value
Template for Edit mode Applet List Edit (Edit/New/Query)
i. Click Next.
j. In the Web Layout – Fields dialog box of the wizard, add the fields that will be in the applet.
i. Select Asset Number in the Available Fields window.
ii. Click the right arrow to move this field to the Selected Fields window.
iii. Select Serial Number in the Available Fields window. When using a dialog box in
Tools that includes a long pick list, type the first letter of the object you seek into the
prompt box. This will place the active selection in close alphabetical proximity to the
field you seek. For example, click anywhere in the Available Fields window, then
type “S”. Scroll to select the field you seek.

iv. Click the right arrow to move this field to the Selected Fields window.
v. Repeat these steps to move the fields in the order listed in the table below from the
Available Fields to the Selected Fields window. This list represents the sequence in
which the fields will appear in the list applet in the user interface. Add these
individually to ensure proper display sequence.
Sequence Field Name
1 Asset Description
2 Product Name
3 Product Part Number
4 Product Description
5 Status
k. You should now have seven fields in the Selected Fields window, starting with Asset
Number and ending with Status. Click Next.
l. The Web Layout – Fields dialog box allows you to add controls to the applet. By default, all
controls have been selected for you. Click Next to accept the default.
m. In the Finish dialog box, click Finish. Siebel wizards often provide a Finish dialog that lists
your configuration settings. This dialog provides a quick way to verify your configuration
settings.
3. In this step, you will preview wizard output. Upon exiting the wizard, Tools will automatically
start the Web Layout Editor.
a. Right-click anywhere on the grid in the Web Layout Editor and select Preview to view a
close approximation of how the new applet will appear in the interface.
b. Right-click and deselect Preview to return to the Web Layout Editor’s edit mode.

4. In this step, you will set up the Product Name field so that it enables the end-user to select from a
list of available products.
a. Select the Product Name list column in the Web Layout Editor.
i. If the Properties window is in auto-hide mode, reveal it now by rolling the mouse
over the Properties window tab on the far left side of the Tools interface. If the
Properties window is closed, right-click and select View Properties Window.
ii. In the Properties window, Set the Pick Applet property to Asset Mgmt - Internal
Product Pick Applet. In a later module, you will assign a pick applet to the Product

Name field. When the user selects a field with a pick applet, a dropdown list appears
and the user picks from this list of predefined items. The Pick Applet property you
specify here determines the applet to be used for that dropdown display.
iii. Ensure the Runtime property is set to True (checked). When you configure this
column with a pick applet in a later module, that applet will have a button tht is used
to invoke the pick applet. The Runtime property determines whether or not that
button is active at runtime.
b. Select File > Save to save your changes.
c. Close the Web Layout Editor.
5. In this step, you will validate the applet you created then compile your changes.
a. Validate your work.
i. In the OBLE, Select Applet :: ABC Asset Characteristics List Applet.
ii. Right-click the ABC Asset Characteristics List Applet and select Validate.
iii. Click Start to begin the validation process.
iv. Review the results. If the previous lab steps were followed correctly, the dialog will
display Total tests failed: 0.
v. Click Cancel to close the validation dialog.
b. Compile your changes.
ii. Make sure Selected Projects is selected.
iii. Ensure Auto-start web client is not selected.
iv. In the Projects window, select ABC New Applets.
v. Click Compile. You must specify an .srf file in which to compile. Local developers
should compile into an srf in the client\objects\enu directory. In this case, enu was set
during installation (enu for US English). This directory could change based on the
languages installed. For this lab, use OUsea\client\OBJECTS\ENU\siebel.srf.
c. Can you view the new customization in your application now? Why, or why not?
Note: You will create a view to display this applet in a later lab.

Solutions 25-2 Creating a List Applet (Guided)
Answers:
1.c Why can you not check the project out?
When you create a new project on the local database, there is no project on the server to
check out.
5.c Can you view the new customization in your application now? Why, or why not?
No, because the applet has not been added to a view visible in the application.


Module 26: UI Layer Configuration - Applications, Screens, and Views
Lab 26-1 Creating a View (Unguided)
Goals To create a view with several applets.
Instructions:

In the previous lab you created list applets that will display service-oriented data about customer
assets. Now, you need to create a view to display these applets. They will be displayed as children,
and an existing account form applet will act as the parent. You will then add the view to a screen.
You will implement the following:
1. Create the ABC New Views project. You may have noticed that, in these labs, you frequently
create new projects. This is done for several reasons. It reduces the amount of time required to
check in and check out. If you used one big project for all your development work, the time
required to complete check in and check out would increase. It also provides a way to minimize
the number of objects locked on the server, freeing up those resources so other developers can
work on them.
Property Value
Name ABC New Views
Locked TRUE

2. Create the ABC Account Asset View.

a. In the New View dialog, specify the following:
Property Value
Project ABC New Views
Name ABC Account Asset View
Title ABC Account Asset View
Business Object Account
b. Associate the view with the View Detail (Parent with Pointer) Web template.
c. In the Web Layout - Applets dialog, add the Account Form Applet and ABC Asset

Characteristics List Applet. The Account Form Applet will allow end users to enter data,
and the ABC Asset Characteristics List Applet will allow users to view an asset list.
d. Preview the view. It should look similar to this:
3. Make the child applet by changing its Applet Mode property to Edit List. Edit List mode renders
list applets as persistently editable.
4. Add the view to the Accounts Screen. Type and Parent Category together determine where the
screen view appears in the user interface. Recall that there are four types of views:
Detail View is the only view that allows users to interact directly with data. All other views are
groups or categories of views and appear as tabs, links or in drop-down lists. Since the part of the
application you are working on requires data entry, Detail View is used.
Parent Category allows you to specify which view is the parent. For example, when you drill
down on a record in the Account List aggregate category, it displays a detail form applet and

detail categories that appear below the form applet on the tab bar. These detail categories are
child categories of the parent, Account List.
Add a new screen view to the Account Screen with the values shown in the table, below. When
specifying either the Menu Text - String Reference or the Viewbar Text - String Reference,
locate Assets in the pop-up dialog then click Pick. At that point, the property should populate
with a direct reference to the string, such as SBL_ASSETS-1004224605-1C1.
Property Value
View ABC Account Asset View
Type Detail View
Parent Category Account List
Menu Text – String Reference Assets

Viewbar Text – String Reference Assets
5. Compile your changes to the Accounts Screen to the client .srf.
6. Administer the view in the application. You must specify the correct view exactly as it appears in
Tools and then add it to one or more responsibilities. In this case, add it to the ABC Developer
responsibility.
7. Verify you can see the ABC Account Asset View in the application.


Lab 26-1 Creating a View (Guided)
Goals To create a view with several applets.
Instructions:

In the previous lab you created list applets that will display service-oriented data about customer
assets. Now, you need to create a view to display these applets. They will be displayed as children,
and an existing account form applet will act as the parent. You will then add the view to a screen.
You will implement the following:
1. In this step, you will create the ABC New Views project. You may have noticed that, in these
labs, you frequently create new projects. This is done for several reasons. It reduces the amount
of time required to Check in and Check out. If you used one big project for all your development
work, the time required to complete Check In and Check Out would increase. It also provides a
way to minimize the number of objects locked on the server, freeing up those resources so other
developers can work on them.
Local database.
b. In the Object Explorer, select Project.
c. Add a new project with the following values:
Property Value
Name ABC New Views
Locked TRUE

2. In this step, you will create the ABC Account Asset View. Recall that a view is a collection of
applets that present data referenced from one, and only one, business object. Views can contain
lists, forms, charts, and other types of applets. The applets in the view reference business
components in the business object.
a. Use the View wizard to create a new view. Select File > New Object.
b. Under the General Tab, select View.
c. Click OK.
d. In the New View dialog, specify the following:
Property Value
Name ABC Account Asset View

Title ABC Account Asset View
e. Click Next.
f. Associate the view with a Web template. This makes the web template available to the view,
which can then be used to specify data display. In the View Web Layout - Select Template
dialog, specify the following:
Property Value
Web Template View Detail (Parent with Pointer)
g. Click Next.
h. In the Web Layout - Applets dialog, add the applets to the view that are listed in the table,
below. The Account Form Applet will allow end users to enter data, and the ABC Asset
Characteristics List Applet will allow users to view an asset list. Note the slight delay that
occurs immediately before this dialog is displayed. This is due to the fact that the business
object you selected in the wizard in a previous dialog box influences the applets displayed.
The business object should have the master business component that matches the top or
driving applet in the view.
Property Value
Applet Account Form Applet
Applet ABC Asset Characteristics List Applet
i. Click Next.
j. Click Finish. The wizard will create the view object definition and its child objects. It will
also open the Web Layout Editor with the parent and child applets already added to the web
template. The first applet you specify in the wizard is placed in the parent position on the
template. Subsequent applets are placed in subordinate positions, such as Child Applet.

3. In this step, you will verify wizard output. In a typical development environment it is not
necessary to verify wizard output. You are doing so here to gain a full understanding of the tasks
the wizard performs.
a. Navigate to the ABC Account Asset View object definition. Select View :: ABC Account
Asset View, or use the navigation tabs to toggle between the Web Layout Editor and the
OBLE:

Toggle
b. In the OBLE, verify the business object property is Account. When you created the ABC
Account Asset View you associated it to the Account business object.
c. Navigate to View :: ABC Account Asset View | View Web Template :: Base | View Web
Template Item. Verify Account Form Applet and ABC Asset Characteristics List Applet
have been added as web template items.
d. Toggle back to the Web layout editor via the Tools navigation tab.
e. Click the form applet in the Web Layout Editor. It will be activated, as indicated by a blue
outline around the form applet.
f. Right-click in the activated applet and select View Properties Window. Verify, via the
properties window, that the Applet property is Account Form Applet.

g. Verify the form applet is in the parent position on the template, above the list applet.
Temporarily drag and drop the form applet to the empty top placeholder. The Parent Applet
placeholder should become exposed, as shown below.

Form applet temporarily moved up to
expose Parent Applet placeholder
h. Move the form applet back into the Parent Applet position.
i. Click the list applet and verify the Applet property is ABC Asset Characteristics List Applet.
j. Verify the list applet is in the Child Applet position on the web template by temporarily
moving it to a vacant placeholder, in similar fashion as you did with the form applet.
k. Right-click anywhere in the layout editor and select Preview. It should look similar to this:
l. Right-click anywhere in the layout editor and select Preview again to close Preview.
4. In this step, you will make the child applet editable. In the scenario for this lab, the child applet is
used to allow data entry into the record, such as asset number, serial number, and so forth. Since
the default Applet Mode property is set to Base when the applet is created, it must be changed to
allow editing.
a. In the Web Layout Editor, click the ABC Asset Characteristics List Applet.

b. Note how the applet is represented in the layout editor. It displays list columns that cannot be
edited.
c. In the Properties window, note that Applet Mode is set to Base.
d. In the Properties window, Set the Applet Mode property to Edit List. Note how the
appearance of the list applet in the layout editor changes: list columns are now represented as
editable. Edit List mode renders list applets as persistently editable. The purpose of an
editable list applet is to allow users to modify the records in a list applet without switching to
an edit page.
e. Close the edit window. Save changes when prompted.
5. In this step, you will add the view to a screen. Type and Parent Category together determine
where the screen view appears in the user interface. Recall that there are four types of views:

Detail View is the only view that allows users to interact directly with data. All other views are
groups or categories of views and appear as tabs, links or in drop-down lists. Since the part of the
application you are working on requires data entry, Detail View is used.
Parent Category allows you to specify which view is the parent. For example, when you drill
down on a record in the Account List aggregate category, it displays a detail form applet and
detail categories that appear below the form applet on the tab bar. These detail categories are
child categories of the parent, Account List.
a. Check out the Account (SSE) project.

b. Select Screen :: Accounts Screen | Screen View.
Add a new screen view with the values shown in the table, below. When specifying either the
Menu Text - String Reference or the Viewbar Text - String Reference, locate Assets in the
pop-up dialog then click Pick. At that point, the property should populate with a direct
reference to the string, such as SBL_ASSETS-1004224605-1C1.
Property Value
View ABC Account Asset View
Type Detail View
Parent Category Account List
Menu Text – String Reference Assets
Viewbar Text – String Reference Assets
c. In the Screens window in the OBLE, right-click Accounts Screen and select Edit Screen
View Sequence
d. Position the view.
i. Click Detail View - ABC Account Asset View to select it (about the fourth item
down).

ii. Right-click the same view, then notice that the view is currently in the highest
Position. This would cause the View to appear at the far left of the Viewbar in the
Accounts screen. You will move the View so it appears between Contacts and ESP in
the Viewbar tab.
iii. Select Move to Next Lower Position. Notice that the View moves down in sequence.
iv. Use the keyboard shortcut Ctrl+Down (the Control key and the Down arrow key).
Notice that the View moves down in sequence again.
v. Repeat until the new view appears directly below the Detail View - Account Detail –
Contacts View and directly above the Detail Category – ESP.
e. Save your changes.
f. Close the editor.
g. Right-click anywhere in the Screen Views window in the OBLE.

h. Sort on the Sequence property in ascending order.
i. Note that ABC Account Asset View appears before Detail Category – ESP, and after
Account Detail – Contacts View.
6. Compile your changes to the Accounts Screen.

a. From the application-level menu, select Tools > Compile Projects.
b. Select Locked Projects.
c. Ensure Auto-start web client is enabled.
d. Click Compile.
7. In this step, you will administer the view. You must specify the correct view exactly as it appears
in Tools. Otherwise, it will not be recognized in your application. One way to ensure the correct
view is specified is to copy the view name from Tools then paste it into the proper field in your
application’s Administration screen. This procedure is detailed, below.
a. Copy the view name.
i. Return to Siebel Tools.
ii. Select View :: ABC Account Asset View.
iii. In the OBLE, tab into the Name property.
iv. Press Ctrl+C to copy it to the clipboard.
v. Return to Siebel Call Center.
b. Add the view.
i. Navigate to Administration – Application > Views.
ii. Click New.
iii. In the View Name field, press Ctrl+V to paste the view name ABC Account Asset
View.
iv. In the Description field, enter “Used to display service data about customer assets”
v. Ensure Default Local Access flag is checked. Each view and each responsibility has
a Local Access flag. Together, these settings determine whether views can be
accessed by Mobile Web Client users. The setting of the Local Access flag does not
affect access to a view for users using either the Siebel Web Client or Siebel
Developer Web Client connecting to the Server database. When Local Access is
checked, all users with the view in one of their responsibilities can access the view
when using the Siebel Mobile Web Client (connected to the Local database). When

Local Access is unchecked, users cannot access the view when using Mobile Web
Client.
c. Assign responsibilities to the new view. Recall that, in order for a view to be visible to a
given user, the user’s responsibility must be assigned to the view.
i. In the Responsibilities list applet (toward the bottom of the page), click the New
button.
ii. Select the ABC Developer responsibility and click OK.
iii. Navigate to Administration – Application > Responsibilities.
iv. Select the ABC Developer responsibility in the Responsibilities list applet.
v. In the Views applet, verify that ABC Account Asset View appears.
vi. Click Clear Cache.
8. In this step, you will verify you can see the ABC Account Asset View.

a. Log out of Siebel Call Center. You must close and re-open the application to allow the cache
to refresh.
b. Start the Developer Web Client from within Tools.
c. Navigate to Accounts > Accounts List.
d. Verify the Asset view tab is visible.
i. If there are no account records in the list, create a new record now.
ii. Drill down on a record in the Account Name field of the Accounts list applet.
iii. There should be an Assets tab. Click it.
iv. Use Help > About View to verify the view is ABC Account Asset View and the
applet is the ABC Asset Characteristics List Applet.
v. Click OK to close About View.
vi. Create a new record in the ABC Asset Characteristics List Applet.
vii. Confirm your new view appears as expected. It should look similar to the screen
print, below.


Module 27: UI Layer Configuration - Drilldowns
Lab 27-1 Configuring Drilldowns (Unguided)
Goal To configure drilldowns and the thread bar.
Instructions:

In your custom application, your users have a need to drill down on a service request number to see
the Service Request Related SR View, and drill down on the product name in the ABC Account
Asset Characteristics List Applet to see the product. In this lab you will configure object definitions
to enable this desired drilldown behavior.
First, you will configure a drilldown so that clicking the service request number field (in certain
views) will display the Service Request Related SR View for that service request. Then you will
configure a drilldown in the ABC Asset Characteristics List Applet so that drilling down on the
product name hyperlink field will display the Product Detail Key Features View.
1. In Siebel Tools, modify the drilldown object definition of the Service Request List Applet to
enable drilling down on SR # to get to the Service Request Related SR View and compile the
project. Verify your results in the application by drilling down on an SR # and confirming that
you are navigated to the Service Request Related SR View. Compare your view against the
screen print, below:

2. Use Siebel Call Center to identify the view used when drilling down on the Product field of the
asset list.
a. What applet is used to display the asset list?
b. Drill down on the Product field of an asset record in the list. What view appears?
3. Gather the information required to configure the ABC Asset Characteristics List Applet so that
users can drill down on the Product Name field in the applet in order to see product details. This
drilldown involves going from an asset record to a product record and requires additional
configuration. This is because you are drilling down to a different business component than were

you started. Enter the information you gather into the diagram below.
a. Use Siebel Tools to determine the name of the drilldown object used to drill down on the
Product field of the Asset Mgmt - Asset List Applet.
b. Identify the source business component from which you are drilling down and enter it into
the diagram.
c. Identify the destination business component to which you are drilling and enter it into the
diagram.
d. Identify the source field that serves as the foreign key field to the destination business
component and enter it into the diagram.
e. Identify the destination field that serves as the primary key field and enter it into the diagram.
Recall that the Id field is used by default when a field is blank
Source Business Component:
Source Field:
FK PK
Destination Business Component:
Destination Field:
4. Use the diagram above to configure a new drilldown on the ABC Asset Characteristics List
Applet that allows users to drill down on the Product to get to the Product Detail Key Features
View.
5. Compile the ABC Asset Characteristics List Applet.

6. Enable the ABC Account Asset View to support the thread bar using the properties shown
below:
Property Value
Thread Applet Account Form Applet
Thread Field Name
Thread Title – String Reference Account
7. Compile the ABC Account Asset View.
8. Add the Product Detail Key Features View to the ABC Developer responsibility and test your
drilldown and your thread bar. They should look similar to the screen shots below:

Drilling down should take you to this view:

Solutions 27-1 Configuring Drilldowns (Unguided)
Answers:
2.a. What applet is used to display the asset list?
Asset Mgmt - Asset List Applet
2.b. Drill down on the Product field of an asset record in the list. What view appears?
Product Detail Key Features View
3.a. Use Siebel Tools to determine the name of the drilldown object used to drill down on the

Product field of the Asset Mgmt - Asset List Applet.
ProductToProductKeyFeatures.
4.

Lab 27-1 Configuring Drilldowns (Guided)
Goal To configure drilldowns and the thread bar.
Instructions:

In your custom application, your users have a need to drill down on a service request number to see
the Service Request Related SR View, and drill down on the product name in the ABC Account
Asset Characteristics List Applet to see the product. In this lab you will configure object definitions
to enable this desired drilldown behavior.
First, you will configure a drilldown so that clicking the service request number field (in certain
views) will display the Service Request Related SR View for that service request. Then you will
configure a drilldown in the ABC Asset Characteristics List Applet so that drilling down on the
product name hyperlink field will display the Product Detail Key Features View.
1. In this step, you will begin by examining the drilldown behavior in the standard Siebel
application. As you complete the step, notice the differences between the Service Request Detail
View and the Service Request Related SR View. The first view you access will display the
standard list applet on top with its related detail form applet below. The second view displays the
detail form applet on top with detail categories below. You will modify this behavior in this lab
so that the user drills down to the Service Request Related SR View.
a. In your application, navigate to Service Requests > Service Request List.
b. If necessary, add a service request record.
c. Drill down on SR #. What view does it take you to?
d. From the Site Map, navigate to Service Requests > Service Request List > Related SRs.
Which view appears?
e. Log out of your application.

2. In this step, you will modify the drilldown object definitions to enable drilling down from the
Service Request List Applet to the Service Request Related SR View.
a. In Siebel Tools, select Applet :: Service Request List Applet | Drilldown Object. Scan the
Hyperlink Field property for a value of SR Number. Which view is listed for the SR
Number? Select the record without (SCW) in the View field.
b. What project must be checked out to modify the Service Request List Applet?
c. Check out the project.

d. Modify the view to reflect the new drilldown.

i. Select Applets: Service Request List Applet | Drilldown Object :: Original.
ii. Change the View property to Service Request Related SR View.
e. Compile the Service Request List Applet.
i. Right-click the Service Request List Applet and select Compile Selected Objects.
ii. Click Service Request List Applet in the window of the Object Compiler dialog box.
iii. Click Compile. Ensure Auto-start web client is enabled.
f. In Siebel Call Center, navigate to Service > Service Request List.
i. Drill down on an SR #.
ii. Do you see the Service Request Related SR View? To verify, compare your view
against the screen print, below.
g. Log out of Siebel Call Center.

3. In this step, you will identify the view used when drilling down on the asset list.
b. Navigate to Assets > List.
c. What applet is used to display the list?
d. Drill down on the Product field of an asset record in the list. What view appears?
e. Log out of the Call Center application.
4. In this step, you will gather the information required to configure the ABC Asset

Characteristics List Applet so that users can drill down on the Product Name field in the applet
in order to see product details. This drilldown involves going from an asset record to a product
record and requires additional configuration. This is because you are drilling down to a different
business component than were you started. Enter the information you gather into this diagram:
Source Business Component:
Source Field:
FK PK
Destination Business Component:
Destination Field:
a. In Tools, select Applet :: Asset Mgmt - Asset List Applet | List :: List | List Column.
b. In the Display Name property, query for Product. This is the list column that contains the
drilldown object you just used in the client. Note that the value in the Field property is
Product Name, which is the business component field the list column references.
c. Select Applet :: Asset Mgmt - Asset List Applet | Drilldown Object.
d. Query the Hyperlink Field property for Product Name. The query should return a drilldown
object whose name property is ProductToProductKeyFeatures.
e. Identify the source business component from which you are drilling down. It is displayed in
the Business Component property of the Asset Mgmt - Asset List Applet. Enter it into the
diagram.
f. Identify the destination business component to which you are drilling. It is displayed in the
Business Component property of the ProductToProductKeyFeatures drilldown object. Enter
it into the diagram.
g. Identify the source field that serves as the foreign key field to the destination business
component. It is displayed in the Source Field property of the ProductToProductKeyFeatures
drilldown object. Enter it into the diagram.

h. Identify the destination field that serves as the primary key field. It is displayed in the
Destination Field property of the ProductToProductKeyFeatures drilldown object. Recall that
the Id field is used by default when a field is blank
5. In this step, you will configure the drilldown. Note that the information you entered in the
diagram, above, is used to configure the properties represented in the table, below.
a. Select Applet :: ABC Asset Characteristics List Applet | Drilldown Object.
b. Add a new drilldown object definition using the property values in the table, below.
Hyperlink Field specifies the list column or control that has hyperlink capabilities. View
specifies the destination view when the hyperlink is clicked. Sequence specifies the order in
which drilldown objects are activated when using dynamic drilldowns. In this case, we assign
1 since there are no other drilldown object definitions for this applet. For additional
information, reference About Drilldowns, Configuring Siebel Business Applications.

Property Value
Name Product
Hyperlink Field Product Name
View Product Detail Key Features View
Source Field Product Id
Business Component Internal Product
Sequence 1
c. Compile the ABC Asset Characteristics List Applet. In the compile dialog, ensure the Auto-
start web client box is not checked.
6. In this step, you will enable the ABC Account Asset View to support the thread bar, which
assists user navigation among views.
a. Select View :: ABC Account Asset View.
b. Set the properties as shown in the table, below. The Thread Applet property specifies which
of the applets appearing in the view will supply data for the thread field. Thread Field is the
name of the field whose data is included in the arrow box, following Thread Title. Thread
Field is in the business component related to the applet identified via Thread Applet. Thread
Title is the text used in the thread to identify the view. To select the Thread Title value
shown in the table, enter Account into the Starting with window in the pop-up pick list.
Then select the first record in the list.
Property Value
Thread Applet Account Form Applet
Thread Field Name
Thread Title – String Reference Account (Select the first one in the list.)
7. Compile the ABC Account Asset View. In the compile dialog, ensure Auto-start web client is
checked.

8. In this step, you will add the Product Detail Key Features View to the ABC Developer
responsibility.
a. Navigate to Administration – Application > Responsibilities.
b. Add the Product Detail Key Features View to the ABC Developer responsibility to ensure
PPENGUIN can see this view when testing the application.
c. Ensure the Local Access flag is checked.
d. Click Clear Cache.
e. Close the Call Center application.
9. Test your work.

a. Start your application from within Tools.
b. In your application, navigate to Accounts > Accounts List.

c. Create an Account record.
d. Drill down on Account Name.
e. Click the Assets view tab.
f. Create an asset record.
i. Select the Product Name field.
ii. Click the MVG button.
iii. Click the Go button.
iv. Click the OK button to select the first record in the list.
v. Step off the record to save it.
g. Is the Product Name field hyperlinked? To verify, compare your view against the screen
print, below. It should look similar. If the Product Name field appears but values in the field
are not hyperlinked, ensure you added Product Detail Key Features View to Penguin’s
responsibility.

i. Drill down on the product name.

ii. Do you see the Product Detail Key Features View? Your view should look similar to
the screen print, below.

h. Log out of Siebel Call Center.

Solutions 27-1 Configuring Drilldowns (Guided)
Answers:
1.c. Drill down on SR #. What view does it take you to?
Service Request Detail View
1.d. From the Site Map, navigate to Service Requests > Service Request List > Related SRs.
Which view appears?
Service Request Related SR View

2.a. In Siebel Tools, select Applet :: Service Request List Applet | Drilldown Object. Scan the
Hyperlink Field property for a value of SR Number. Which view is listed for the SR
Number? Select the record without (SCW) in the View field.
Service Request Detail View
2.b. What project must be checked out to modify the Service Request List Applet?
The Service (SSV) project. Service Request Related SR View is the view you need to relate
to the SR Number Hyperlink Field. By navigating to the view’s object definition via the
Object Explorer, you can see that this view’s project property is set to Service (SSV).
3.c. What applet is used to display the list?

Asset Mgmt - Asset List Applet
3.d. Drill down on the Product field of an asset record in the list. What view appears?
4.


Module 28: Business Layer Configuration - Joins
Lab 28-1 Examine Existing Joins (Unguided)
Goals To examine existing joins in a business component.
Instructions:

In this lab you will examine references between fields and columns in the base and joined tables.
This exercise will assist you in understanding how joins are structured.
1. Examine how the Commit Time single value field object definition in the Service Request
business component references a database table and column when a join is not present. Use
Siebel Tools to complete the following diagram, including the business component, field, base
table, and column:

2. Examine how the Account single value field object definition in the Service Request business
component maps to database tables and columns when a join is present. Use Siebel Tools to
complete the following diagram, including the business component, field, base table, joined
table, primary key, foreign key, and column. Do not forget to examine the join and join
specification object definitions to help you complete your work.

3. Examine several fields for the Service Request business component. This activity provides
practice in mapping the column and table referenced by a business component. Complete the
following table for the Service Request business component.
Service Request Business Component
Field Join Column Table
Contact Last Name
Owner
Resolution Code
Serial Number

Status

Solutions 28-1 Examine Existing Joins (Unguided)
Answers:
1.

2.

3.
Contact Last Name S_CONTACT LAST_NAME S_CONTACT
Owner Owner-S_USER LOGIN S_USER
Resolution Code RESOLUTION_CD S_SRV_REQ
Serial Number S_ASSET SERIAL_NUM S_ASSET
Status SR_STAT_ID S_SRV_REQ


Lab 28-1 Examine Existing Joins (Guided)
Goals To examine existing joins in a business component.
Instructions:

1. In this step, you will examine how a Single Value Field object definition in the Service Request
business component references a database table and column when a join is not present. For each
question in this step, enter your response into this diagram:

a. In Siebel Tools, Select Business Component :: Service Request.

b. Recall that the Table property for the business component displays the base table. Enter the
business component name and its base table into the diagram.
c. Select Business Component :: Service Request | Single Value Field :: Commit Time.
d. Enter the field name into the diagram.
e. Enter the value of the column property into the base table in the diagram. As indicated in the
diagram, note that this field references a single column in the base table. What is the value of
the Join property?
f. What does a null Join property tell you about the database table that contains the column?

g. Verify EXP_CLOSE_DT references the base table in the diagram you just completed, above.
Select Table :: S_SRV_REQ | Column :: EXP_CLOSE_DT. Does such a column exist in the
S_SRV_REQ table?

2. In this step, you will examine how a Single Value Field object definition in the Service Request
business component maps to database tables and columns when a join is present. For each
question, enter your response into this diagram:

a. Select Business Component :: Service Request.
b. Enter the business component name and base table name.
c. Select Business Component :: Service Request | Single Value Field :: Account.
i. Enter the field name into the diagram.
ii. Enter the joined table name into the diagram. The value displayed in the Join property
is the joined table name. When a join property is not null, its value specifies the
joined table.
iii. Enter the joined table column name that contains the data. The value of the Column
property for the Single Value Field displays the joined table column name that
contains data to be brought into this business component.

d. Determine the name of the column in the base table that serves as the foreign key to the
joined table.
i. Select Business Component :: Service Request | Join.
ii. Query for the record in which the Alias is S_ORG_EXT.
iii. In the OE, select Join Specification.
iv. What is the value of the Source Field?
e. Determine the Column that the Source Field references.

i. Select Business Component :: Service Request | Single Value Field :: Account Id.
ii. What is the value of the Join property?

iii. What is the value of the Column property?
iv. Enter the name of the Column into the base table’s FK column in the diagram.
f. Determine the name of the column in the joined table that serves as the primary key.
i. Select Table :: S_ORG_EXT | Column.
ii. Query for Primary Key = TRUE.
iii. In the diagram, enter the name of the primary key column into the joined table’s PK
column. Recall that most Siebel tables use ROW_ID as their primary key.
3. In this step, you will examine several fields for the Service Request business component. This
activity provides practice in mapping the column and table referenced by a business component.
Since the join property may or may not have a value, you will gain exposure in mapping fields
that either reference the base table or a joined table.
a. Select Business Component :: Service Request | Single Value Field.
b. Use Columns Displayed to arrange the SVF join and column properties into the immediately
viewable area of the OBLE.
c. Bookmark the SVF window.
d. Query for the field, then enter the values for the join and column properties.
e. Drill down on the join hyperlink to determine the table property.
f. Use the bookmark to return to the SVF window.

g. Fill in the table with your observations for each field.

Contact Last
Name
Owner
Resolution
Code
Serial Number

Status

Solutions 28-1 Examine Existing Joins (Guided)
Answers:
1.

1.e. Enter the value of the column property into the base table in the diagram. As indicated in
the diagram, note that this field references a single column in the base table. What is the
value of the Join property?
It is blank.
1.f. What does a null Join property tell you about the database table that contains the column?
A blank Join property indicates that the column maps to the base table (S_SRV_REQ).
Since the column references directly to the base table, there is no need for a join.
1.g. Does such a column exist in the S_SRV_REQ table?

EXP_CLOSE_DT column does exist in S_SRV_REQ table. Commit time does indeed
reference a column in the base table.

2.

2.d.iv. What is the value of the Source Field?
Account Id.
2.e.ii. What is the value of the Join property?

Blank. The field is blank because the Account Id field references a column in the base table
(S_SRV_REQ) of the Service Request business component.
2.e.iii. What is the value of the Column property?

CST_OU_ID.
3.g. Fill in the table with your observations for each field.
Contact Last Name S_CONTACT LAST_NAME S_CONTACT
Owner Owner-S_USER LOGIN S_USER
Resolution Code RESOLUTION_CD S_SRV_REQ
Serial Number S_ASSET SERIAL_NUM S_ASSET
Status SR_STAT_ID S_SRV_REQ


Lab 28-2 Adding a Joined Field to a Business

Component (Unguided)
Goals To add fields from a related table to an existing business component.

Instructions:
Your application has a requirement to display the original order number for a piece of equipment
and, if available, the purchase order number given by the customer who purchased or leased it. To
make this possible, you will need to add fields to the Asset Mgmt - Asset business component to
capture these numbers.
A colleague has determined that the business component where this information is stored in the
Order Entry - Orders business component, and the underlying table is S_ORDER. In addition, she
has determined that the column containing the original order number is ORDER_NUM, and the
column containing the customer’s purchase order number is ACCNT_ORDER_NUM. She used the
same technique you used in previous labs to identify table columns at the data layer that supply data
for controls at the UI layer.
In the remainder of this lab you will construct Join and Join Specification object definitions that
allow you to create new fields in the Asset Mgmt - Asset business component that reference columns
in the S_ORDER table. You will then create Original Order Number and Customer PO Number
fields in the Asset Mgmt - Asset business component. Finally you will expose these new fields on
the Asset Mgmt - Asset Detail Applet (no title) applet.
1. Examine the existing Join definitions of the Asset Mgmt business component to see if the
required join already exists. In order to display the original order number and the purchase order
number, the business component must establish a join between S_ASSET (the base table for the
Asset Mgmt - Asset business component) and S_ORDER (the table that contains the purchase
order number).

2. Since there is no existing Join to S_ORDER, you will need to construct the appropriate Join
Definition and Join Specification. Complete the following diagram with your join requirements,
including the business component, base table, joined table, primary key, and foreign key.
Examine the base table to find the foreign key column to the joined table.

3. Inspect the business component to determine if it has a field that maps to the foreign key column.
The join specification uses the name of the foreign key field in the business component that
references the foreign key column. When you configure a join specification you will need to
create the foreign key field if it does not already exist.
4. Complete the diagram by entering the name of the foreign key field into the diagram. Optionally,
add the columns in the joined table that you will be accessing.
5. Create the join definition to add the joined table to the Asset Mgmt - Asset business component.
Set the alias to Order Information and the Outer Join Flag to True.
6. Create the join specification. It identifies the foreign key field in the business component and the
primary key column in the joined table the foreign key points to.

7. Create a new field that references the order number column from the joined table. Recall that the
required column is ORDER_NUM. Set the Name property to Original Order Number. This
property is used in the business component to display the order number. Recall that our scenario
requires display of both the original order and the customer’s purchase order number.
8. Create a new field that references the customer purchase order column from the joined table.
Recall that the required column is ACCNT_ORDER_NUM. Set the Name property to Customer
PO Number.
9. Compile the Asset Mgmt - Asset business component.
10. Display these new fields in the ABC Asset Characteristics List Applet by adding them as two
list columns with the properties shown below. Do not forget to add them to the applet Web
templates.

Property Value
Name Original Order Number
Field Original Order Number
Display Name – String Override Original Order #
Property Value
Name Customer PO Number
Field Customer PO Number
Display Name – String Override Customer PO #
11. Compile the ABC Asset Characteristics List Applet.
12. Verify your work. Make sure that the new fields, Original Order # and Customer PO #, appear in
the ABC Asset Characteristics List Applet with their proper display names. Your view should
look like something like this:
New Fields From

Joined Table

Solutions 28-2 Adding a Joined Field to a Business

Component (Unguided)
Answers:
2.

Lab 28-2 Adding a Joined Field to a Business

Component (Guided)
Goals To add fields from a related table to an existing business component.

Instructions:
Your application has a requirement to display the original order number for a piece of equipment
and, if available, the purchase order number given by the customer who purchased or leased it. To
make this possible, you will need to add fields to the Asset Mgmt – Asset business component to
capture these numbers.
A colleague has determined that the business component where this information is stored in the
Order Entry - Orders business component, and the underlying table is S_ORDER. In addition, she
has determined that the column containing the original order number is ORDER_NUM, and the
column containing the customer’s purchase order number is ACCNT_ORDER_NUM. She used the
same technique you used in previous labs to identify table columns at the data layer that supply data
for controls at the UI layer.
In the remainder of this lab you will construct Join and Join Specification object definitions that
allow you to create new fields in the Asset Mgmt – Asset business component that reference
columns in the S_ORDER table. You will then create Original Order Number and Customer PO
Number fields in the Asset Mgmt – Asset business component. Finally you will expose these new
fields on the Asset Mgmt – Asset Detail Applet (no title) applet.
1. In this step, you will examine the existing Join definitions to see if the required join already
exists. In order to display the original order number and the purchase order number, the business
component must establish a join between S_ASSET (the base table for the Asset Mgmt – Asset
business component) and S_ORDER (the table that contains the purchase order number). If such
a join exists, S_ORDER will display in the Table property.
a. Select Business Component :: Asset Mgmt - Asset | Join.
b. Inspect the Table property. Is there a join defined for the S_ORDER table?

2. Since there is no existing Join to S_ORDER, you will need to construct the appropriate Join
Definition and Join Specification. Use the diagram, below, to record your answers in this section
of the lab. The diagram is provided as a learning tool. If you encounter difficulties during this lab
you should, at your discretion, feel free to view the solutions section for assistance.

a. Identify the base table name for the Asset Mgmt – Asset business component. View the
business component’s Table property. Enter it into the diagram.
b. The join definition specifies the joined table. Enter the name of the joined table into the
diagram. It is the table your colleague identified as containing the required data.
Tip: Refer to the introduction for an explanation of what your colleague is looking for.

3. In this step, you will determine the names of the columns that serve as foreign key and primary
keys. The join specification specifies the foreign key(s) used to retrieve the relevant record(s)
from the joined table.
a. Determine the name of the column in the base table that serves as the foreign key to the
joined table.
i. Drilldown on the table property for the Asset Mgmt – Asset business component
(S_ASSET) in the OBLE.
ii. Select Table :: S_ASSET | Column.
iii. Query the Foreign Key Table property for S_ORDER. Due to your colleague’s work,
you know S_ORDER contains the required information. Querying for S_ORDER in
the Foreign Key Table property returns all columns in S_ASSET that are foreign keys
which map to S_ORDER.

iv. Enter the name of the column into the base table’s FK column in the diagram.
b. Determine the name of the column in the joined table that serves as the primary key.
i. Select Table :: S_ORDER | Column.
ii. Query the Primary Key property for TRUE (checked).
iii. Enter the name of the primary key column into the joined table’s PK column in the
diagram.
4. In this step, you will inspect the business component to determine if it has the required foreign
key field. The join specification uses the name of the foreign key field in the business component
that references the foreign key column of ORIG_ORDER_ID. When you configure a join
specification you will need to create the foreign key field if it does not already exist.
a. Select Business Component :: Asset Mgmt – Asset | Single Value Field.
b. Check to see if there is an existing reference. Query the Column property for
ORIG_ORDER_ID.
c. Since there is an existing reference between the ORIG_ORDER_ID column and a business
component field, you do not need to add a new single value field. Instead, complete your
diagram by entering the name of the single value field into the diagram. Next, you can refer
to this diagram when creating the join in Tools.
5. In this step, you will create a join definition to add the joined table to the Asset Mgmt - Asset
business component. Note that the join definition specifies the joined table from which to
retrieve data. The join specification, covered in the next step, 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.
a. Select Business Component :: Asset Mgmt - Asset | Join.
b. Add a join definition object definition.
i. Create a new join definition.
ii. Set the Table property to S_ORDER.
iii. Set the Alias property to Order Information. The alias makes it possible for a
business component to have more than one join with the same destination table. In the
example here, you could have an additional join that brings in, say, tax amount data
for this order. Therefore, it is important that the Alias property be distinct even

though the destination table is the same.
Important: It is usually not a good practice to use the table name as the Alias name,
even though this is common in the standard repository. This is because implicit joins
will use the table name as the Alias to make sure that the explicit join name is not
used instead. To make sure that no conflict exists, you should always give the join a
distinct and custom alias name.
iv. Set the Outer Join Flag property to True (checked).

v. Set the Comments property to Join to bring Order Information into Asset Mgmt -
Asset BC. Entering information in Comments is optional. Thoroughly documenting
your work can simplify application creation, maintenance, and troubleshooting.

6. In this step, you will create the join specification. It identifies the foreign key field in the
business component and the primary key column in the joined table the foreign key points to.
a. Select Business Component :: Asset Mgmt - Asset | Join :: Order Information | Join
Specification.
b. Add a new join specification object definition.
i. Set the Name property to Original Order Id. Note that you can assign any random
string to the Name field. To assist application creation, choose a name that reflects the
nature of the join. Since this specification is bringing original order ID data into the
business component, that is the name we give it here.
ii. Set the Destination Column property to ROW_ID. Destination Column identifies the
primary key column in the joined table.
iii. Set the Source Field property to Original Order Id.
c. What would happen at run time if you added the join, but forgot to add the join specification?
7. In this step, you will create a new field that references the order number column from the joined
table. At this point you have created a join between S_ASSET and S_ORDER, and you are ready
to add fields to the Asset Mgmt - Asset business component that reference columns which
contain data in S_ORDER, the joined table.
You know from your colleague’s work that the column containing the original order number is
ORDER_NUM, and the column containing the customer’s purchase order number is
ACCNT_ORDER_NUM.
a. Enter ORDER_NUM into the diagram in the joined table next to ROW_ID.
b. Enter ACCNT_ORDER_NUM into the diagram in the joined table in the next available
column.
c. Select Business Component :: Asset Mgmt - Asset | Single Value Field.
d. Add a new single value field object definition.
i. Set the Name property to Original Order Number. This property is used in the
business component to display the order number.

ii. Set the Join property to Order Information, which is the name of the join you just
created.
iii. Set the Column property to ORDER_NUM, which is the name of the column in
S_ORDER that contains the order number information you need to display in the UI.
The columns made available to you in the pop-up list are all from S_ORDER (the
joined table).
iv. Verify the Type property is DTYPE_TEXT.
e. Why must you set the Join property before you set the Column property?

8. In this step, you will create a new field that references the customer purchase order column from
the joined table. Recall that our scenario requires display of both the original order and the
customer’s purchase order number.
a. Add a new Single Value Field to the Asset Mgmt - Asset business component. Set the
following properties:
Property Value
Join Order Information
Column ACCNT_ORDER_NUM
Type DTYPE_TEXT
b. Compile the Asset Mgmt - Asset business component. Ensure Auto-start web client is not
checked.
9. In this step, you will display these new fields in the ABC Asset Characteristics List Applet.
(Recall that in an earlier lab, you created this applet).
a. Add list columns to the applet.
i. Select Applet :: ABC Asset Characteristics List Applet | List :: List | List Column.
ii. Add a new list column object definition.

iii. Set properties to the values in the table, below. The Name property can be any
descriptive text. For Display Name, consider the many strings that already exist in the
repository. Using existing strings can reduce maintenance efforts. Before creating a
string override, query the Display Name – String Reference property to determine if
the desired string exists. If a string reference does not exist, you will have to use the
Display Name – String Override property and create a string override. Notice that
when you enter a value into the String Override property, the property’s value is
duplicated in the Display Name property immediately upon tabbing out of the
override property or stepping off the record.
Property Value
Name Original Order Number
Field Original Order Number

Display Name – String Override Original Order #
iv. Add a second list column object definition.
v. Set the following properties:
Property Value
Field Customer PO Number
Display Name – String Override Customer PO #
10. In this step, you will add the columns to the applet template.
a. Select Applet :: ABC Asset Characteristics List Applet.
b. Right-click and select Edit Web Layout.
c. Verify the Mode: field in the Web Controls toolbar is 1: Base. To simplify navigation, auto-
hide the Palette and Object Explorer windows.
d. Drag and drop the Original Order # field from the Control / Columns window to an
available field in the applet. To view an available field, scroll-right in the Web Template
Layout Editor window. You will see a series of available fields that look like this:
e. Repeat this step for the Customer PO # field.

f. Preview the applet. Verify that the fields appear where you put them.
g. Deselect Preview (right-click then deselect the preview option).
h. In the Mode: field of the Web Controls toolbar, select 2: Edit.
i. Drag and drop the Original Order # field from the Control/Columns window to an available
field in the applet. The FormSection field immediately below the existing controls will
suffice. Available fields in Edit mode have this appearance:

j. Drag and drop the Customer PO # field from the Control/Columns window to an available
field in the applet.
k. Preview the applet. Verify that the fields appear where you put them. After you have
reviewed the applet, close the preview mode.
l. Deselect Preview.
m. In the Mode: field of the Web Controls toolbar, select 3: Edit List.
n. Drag and drop the Original Order # field from the Control / Columns window to an
available field in the applet.
o. Drag and drop the Customer PO # field from the Control / Columns window to an available
field in the applet.
p. Preview the applet. Verify that the fields appear where you put them.
q. Close the Web Layout editor. Click Yes to save changes.

r. Compile the ABC Asset Characteristics List Applet. Ensure auto-start is enabled.
11. Test your work.

a. In the application, navigate to Accounts > Accounts List > Assets.
b. Verify that the new fields, Original Order # and Customer PO #, appear in the ABC Asset
Characteristics List Applet with their proper display names. Your view should look like
something like this:
New Fields From

Joined Table
c. Log out of the Siebel Call Center.

Solutions 28-2 Adding a Joined Field to a Business

Component (Guided)
Answers:
1.b. Inspect the Table property. Is there a join defined for the S_ORDER table?
No.
2. Since there is no existing Join to S_ORDER, you will need to construct the appropriate
Join Definition and Join Specification. Use the diagram, below, to record your answers in

this section of the lab.
6.c. What would happen at run time if you added the join, but forgot to add the join
specification?
The application would use a default join specification of ROW_ID = ROW_ID. Since row
IDs are unique, the resulting query would return no records.
7.e. Why must you set the Join property before you set the Column property?
If the Join property is blank, the columns available on the Column property are base table
columns (in this case, S_ASSET). The ORDER_NUM column is located on S_ORDER, not
S_ASSET. In order to get the pop-up list to display the correct columns, you must first
specify the join so that the pop-up list is populated with S_ORDER columns Try an
experiment: change the value in the join property to another value, then notice how values
in the column property change.

Module 29: Business Layer Configuration - Existing Business Components and Fields
Lab 29-1 Configuring Properties of Fields and Business

Components (Unguided)
Goal To configure field and business component properties.
Instructions:

In this lab, you will incorporate additional business logic into your application by configuring
several properties in field and business component object definitions. You will observe how
validation properties can be used to prevent unwanted data from being entered into the database.
You will see how default values for data can be specified and how user properties can be set to
incorporate business logic into the application.
As a result of your work in this lab:

• Users should not be able to enter a negative value for the original cost of an asset
• The Source of new Service Requests should default to Phone
• When an owner is assigned to an asset, the sub-status should be changed to Assigned.
1. Add a validation to the Original Cost field of the Asset Mgmt - Asset business component so
that negative values cannot be entered into the database and compile the Asset Mgmt - Asset
business component.
2. Use a Post Default Value to ensure that the Source field of the Service Request business
component defaults to Phone. Right now, your application only accepts new service requests
over the phone. As such, setting phone as the default value will enable call center agents to take
service requests over the phone more quickly by reducing the amount of data entry. If your
application accepted new service requests over the Web or other channels, the call center agent
would have to ensure the source was set appropriately. Using Post Default Value ensures the
value you specify, such as Phone, will be populated after the user saves the record only if the
user has not entered a value.
3. Expose the Business Component User Prop object type in the Object Explorer.
4. Configure an “On Field Update Set n” user property on the business component. You would like
the application to change the SR Sub-Status to Assigned when an SR Owner is assigned. You
will accomplish this by configuring a user property.
a. Add a new user property to the Service Request business component. Set the Name property
to On Field Update Set 5. This user property allows you to set the value of a field in the
business component when another field is updated. When there is more than one instance of
this user property, each instance is executed sequentially by number (for example, On Field

Update Set 1, then On Field Update Set 2, and so forth). You used Set 5 because there are
already several other instances of this user property in the Service Request business
component.
b. Set the Value property to “Owned By Id”, “Sub-Status”, “Assigned”. Pay careful attention
to the spaces between the words, the use of double quotes, and the hyphen in Sub-Status. The
value of this user property consists of three quoted parameters separated by a comma and a
space: the field to check (in this case Owned By Id), the field to set (in this case Sub-Status),
and the value to assign to that field (in this case Assigned). At run-time, Sub-Status is set to
Assigned when Owned By Id is updated. For additional information about user properties,
consult Siebel Developer’s Reference.
c. Compile the Service Request business component.
5. Test your changes.

a. Create or modify an asset record and enter a negative number in the Original Cost field to
confirm that your validation works correctly. If you do not see the Original Cost field in the
list applet, use Columns Displayed to display it.
b. Create a new service request record, tab into the owner field and delete the value there. Do
not tab out of the field nor step off the record.
i. What value appears in the Source field in the form applet?
ii. What are the current values of the Owner and Substatus fields?
iii. In the Owner field, click the Select button and select PPENGUIN as the new Owner
for the Service Request. Now what are the values of the Owner and Substatus fields?
Why?
iv. Save the record. What is the new value of the Source field? Why?
6. For an additional challenge, set validation for the Email Address field in the Contact business
component so that the email address entered must contain an “at” sign (@) and a period (.). You
can also check that the user enters at least one character for each of the text strings that surround
the @ sign and two characters after the period (.). Compile and test the customization in your
application.

Solutions 29-1 Configuring Properties of Fields and

Business Components (Unguided)
Answers
5.b.i. What value appears in the Source field in the form applet?
No value. It is empty.
5.b.ii. What are the current values of the Owner and Substatus fields?
The Owner field is set to the login ID for the current user, PPENGUIN if logged in as Pat

Penguin, and the Substatus is Unassigned.
5.b.iii. In the Owner field, click the Select button and select PPENGUIN as the new Owner for
the Service Request. Now what are the values of the Owner and Substatus fields? Why?
The Owner field is PPENGUIN and the Substatus is Assigned. The User Property you
created (On Field Update Set) was configured to update the Substatus to Assigned
whenever the Owner field is updated.
5.b.iv. Save the record. What is the new value of the Source field? Why?
The new value is Phone. The Source field had a Post default value, so the value is not
updated until after the record is saved.
6. F or an additional challenge, set validation for the Email Address field in the Contact
business component so that the email address entered must contain an “at” sign (@) and a
period (.). You can also check that the user enters at least one character for each of the text
strings that surround the @ sign and two characters after the period (.).
First, check out the Contact project. Then, set the Validation property for the Single Value
Field Email Address on the Contact business component as follows:
Validation *?@?*.*??
Note: The wildcard (*) can match zero or more characters. The question marks in the
expression ensure that there is at least one character in each text string. The “at” symbol
(@) and period are literals.)


Lab 29-1 Configuring Properties of Fields and Business

Components (Guided)
Goal To configure field and business component properties.
Instructions:

In this lab, you will incorporate additional business logic into your application by configuring
several properties in field and business component object definitions. You will observe how
validation properties can be used to prevent unwanted data from being entered into the database.
You will see how default values for data can be specified and how user properties can be set to
incorporate business logic into the application.
As a result of your work in this lab:

• Users should not be able to enter a negative value for the original cost of an asset
• The Source of new Service Requests should default to Phone
• When an owner is assigned to an asset, the sub-status should be changed to Assigned.
1. In this step, you will add validation to the Original Cost field of the Asset Mgmt - Asset business
component so that negative values cannot be entered into the database.
a. If necessary, start Siebel Tools and log in as PPENGUIN connecting to the Local database.
b. Select Business Component :: Asset Mgmt - Asset | Single Value Field :: Original Cost.
c. Set the following properties:
Property Value
Validation >=0
Validation Message – The Original Cost field must have a
String Override value that is greater than or equal to
zero.
Message Display Mode User Msg with Error Code Only
d. Compile the Asset Mgmt - Asset business component. Ensure the Auto-start web client
option is not checked.
2. In this step, you will use Post Default Value to ensure a field is not empty after record creation is
completed. On the Service Request business component, you would like the Source field to
default to Phone. Right now, your application only accepts new service requests over the phone.
As such, setting phone as the default value will enable call center agents to take service requests
over the phone more quickly by reducing the amount of data entry. If your application accepted
new service requests over the Web or other channels, the call center agent have to ensure the

source was set appropriately. Using Post Default Value ensures the value you specify, such as
Phone, will be populated after the user saves the record and before it is saved to the database.
a. If necessary, check out the Service project.
b. Select Business Component :: Service Request | Single Value Field :: Source.
c. Navigate back to the Source single-value field for the Service Request business component.
d. Set the Post Default Value property to Phone.
3. In this step, you will expose the Business Component User Property object type in the Object
Explorer.
a. In the Tools Menu Bar, select View > Options.
b. Click the Object Explorer tab.
c. Expand Business Component.

d. Select the checkbox next to Business Component User Prop. This will cause the Business
Component User Property object type to appear in the Object Explorer.
e. Click OK to accept the change and close the Development Tools Options dialog.
4. In this step, you will configure a User Property on the business component. You would like the
application to change the SR Sub-Status to Assigned when an SR Owner is assigned. You will
accomplish this by configuring a User Property. A Business Component User Property is an
object definition added as a child to the business component. You can use it to configure
specialized behavior beyond what is configured in the parent object definition's properties.
a. Select Business Component :: Service Request | Business Component User Prop.
b. Add a new Business Component User Prop object definition.
c. Set the Name property to On Field Update Set 5. On Field Update Set n is one of the many
user properties available with Siebel. It allows you to set the value of a field in the business
component when another field is updated. When there is more than one instance of this user
property, each instance is executed sequentially by number (for example, On Field Update
Set 1, then On Field Update Set 2, and so forth). We used Set 5 because there are already
several other instances of this user property in the Service Request business component.
d. Set the Value property to “Owned By Id”, “Sub-Status”, “Assigned”. Pay careful attention
to the spaces between the words, the use of double quotes, and the hyphen in Sub-Status. The
value of this user property consists of three quoted parameters separated by a comma and a
space: the field to check (in this case Owned By Id), the field to set (in this case Sub-Status),
and the value to assign to that field (in this case Assigned). At run-time, Sub-Status is set to
Assigned when Owned By Id is updated. For additional information about user properties,
consult Siebel Developer’s Reference.
e. View another instance of this user property in the Service Request business component. In
the Name property, query for On Field Update Set 3. For this user property, what role does
Entitlement Id play?

f. What role does Billable Flag play?
g. Compile the Service Request business component. Ensure the Auto-start web client option is
checked.

a. In Siebel Call Center, navigate to Assets > List.
b. Create a new Asset record.
i. In the Product field, click the Select button.
ii. Select a product from the Pick Product list and click OK.

iii. Find the Original Cost field. If you do not see it in the list applet, use Columns
Displayed to make it visible.
iv. Enter a negative number in the Original Cost field.
v. Save the record. What happens?
vi. Click OK.

vii. Enter a positive value in the Original Cost field. Click Save Record again. What
happens now when you attempt to save the record?
c. Navigate to Service Requests > Service Request List.

i. Create a new service request record.
ii. Tab into the owner field and delete the value there. Do not tab out of the field nor step
off the record. What value appears in the Source field in the form applet?
iii. What are the current values of the Owner and Substatus fields?
iv. In the Owner field, click the Select button and select PPENGUIN as the new Owner
for the Service Request. Now what are the values of the Owner and Substatus fields?
Why?

v. Save the record. What is the new value of the Source field? Why?
6. If you would like a challenge, set validation for the Email Address field in the Contact business
component so that the email address entered must contain an “at” sign (@) and a period (.). You
can also check that the user enters at least one character for each of the text strings that surround
the @ sign and two characters after the period (.).
a. Compile and test the customization in your application.
b. See solutions, below, for assistance.

Solutions 29-1 Configuring Properties of Fields and

Business Components (Guided)
Answers
4.e. View another instance of this user property in the Service Request business component. In
the Name property, query for On Field Update Set 3. For this user property, what role does
Entitlement Id play?
Entitlement Id is the trigger that initiates the user property action. When Entitlement Id is
updated, the user property logic is executed.

4.f. What role does Billable Flag play?
Billable Flag is the acted-upon field. When the user property logic is executed, Billable
Flag is set to the value of the user property’s third parameter. In this case, that parameter
is a conditional statement: "IIF ([Entitlement Id] IS NULL, ""N"", [Billable Flag])”.
5.b.v. Save the record. What happens?

You should receive an error message similar to the following:
5.b.vii. Enter a positive value in the Original Cost field. Click Save Record again. What happens
now when you attempt to save the record?
The record saves without error, because the Original Cost does not violate its validation
rule.
5.c.ii. What value appears in the Source field in the form applet?
No value. It is empty.
5.c.iii. What are the current values of the Owner and Substatus fields?
The Owner field is set to the login ID for the current user, PPENGUIN if logged in as Pat
Penguin, and the Substatus is Unassigned.
5.c.iv. In the Owner field, click the Select button and select PPENGUIN as the new Owner for
the Service Request. Now what are the values of the Owner and Substatus fields? Why?
The Owner field is PPENGUIN and the Substatus is Assigned. The User Property you
created (On Field Update Set) was configured to update the Substatus to Assigned
whenever the Owner field is updated.

5.c.v. Save the record. What is the new value of the Source field? Why?
The new value is Phone. The Source field had a Post default value, so the value is not
updated until after the record is saved. After saving the record, your view should look
something like this:
Owner changed?

Updates to
“Assigned” after
Updates to “Phone”
Owner is changed
after record is saved
6. I f you would like a challenge, set validation for the Email Address field in the Contact
business component so that the email address entered must contain an “at” sign (@) and a
period (.). You can also check that the user enters at least one character for each of the text
strings that surround the @ sign and two characters after the period (.).
First, check out the Contact project. Then, set the Validation property for the Single Value
Field Email Address on the Contact business component as follows:
Validation *?@?*.*??
Note: The wildcard (*) can match zero or more characters. The question marks in the
expression ensure that there is at least one character in each text string. The “at” symbol
(@) and period are literals.)

Module 30: Business Layer Configuration - New Business Components and Fields
Lab 30-1 Using the Standard 1:M Extension Table to

Store Supply Plans (Unguided)
Goal To create a new business component using a standard 1:M extension table.

Instructions:
Many customers rely on your company to provide a variety of supplies (consumable goods) for their
durable assets. A given asset may require a variety of different supplies at a variety of different
times. For example, a copier might require paper frequently, toner less frequently, and lubricant
occasionally. For each asset that consumes supplies, your company creates a supply plan, consisting
of a list of supplies, stocking level, and frequency of stocking.
In this lab you will create a new business component, ABC Asset Supply Plan, which is related to
the Asset Mgmt - Asset business component. Each record will identify a supply, stocking level, and
stocking frequency. Since the records for these new components will have a many-to-one
relationship with asset records, you can use the standard 1:M extension table for the Asset Mgmt -
Asset business component.
1. Determine data storage requirements.

a. The asset-to-supply plan relationship is 1:M, so you decide to use the 1:M extension table for
the Asset Mgmt - Asset business component. Note that the 1:M extension table has the name
of the parent table appended with _XM. What is the name of the 1:M extension table you
should use?
b. Identify the columns in which to store supply plan data. Which column in S_ASSET_XM
table is a foreign key to S_ASSET?
c. A supply plan specifies the name of the supply, the stocking level and stocking frequency.
Which column looks like it should hold the name of the item being supplied?

d. The stocking frequency field should be able to store at least 20 characters. Which columns
will serve this need most efficiently?
e. The stocking level field should be a number. Which columns will serve this need?
2. Determine if a business component already exists that can be used to store supply plan data in
the S_ASSET_XM table. Are there any existing business components that use this table?

3. Create a new project named ABC New Bus Comps to contain your new business component.
Recall that you are using a separate project to hold each object type. This is done to facilitate
managing the development environment.
4. Use the business component wizard to create a new business component, ABC Asset Supply
Plan, based on the S_ASSET_XM table, which will be capable of storing multiple supply plans
for each asset.
a. Create single value fields that reference the required user key columns and additional
ATTRIB columns you will need from the S_ASSET_XM table.
Column Name
PAR_ROW_ID Asset Id
NAME Supply
TYPE Type
ATTRIB_03 Stocking
Frequency
ATTRIB_14 Stocking Level
5. Set the Search Specification property for the business component you just created to [Type] =
‘SP’.
6. Add the three fields that make up the user key: Asset Id, Supply, and Type. The user key is
specified in the base table, and adding these columns as fields in the business component ensure
that users gain full advantage of the user key. Make these fields required.
7. Set the Predefault Value for Type to SP.

8. Specify the fields that store the data. Set and verify the properties listed for each field in the
table, below.
Name Column Predefault Required Type
Value
Stocking Frequency ATTRIB_03 DTYPE_TEXT
Stocking Level ATTRIB_14 DTYPE_NUMBER
9. Gather the information required to configure a new link to support the 1:M relationship between
Asset Mgmt - Asset and ABC Asset Supply Plan. Enter your responses directly into this
diagram, including parent business component, child business component, source field, and
destination field:

10. Use the diagram above to create the link between the two business components. Create the link
in the ABC New Bus Comps project. Validate the link once you have created it.
11. Add the ABC Asset Supply Plan business component to the Asset Management business object
using the link you just created. You will compile and test your changes in the next lab.

Solutions 30-1 Using the Standard 1:M Extension Table

to Store Supply Plans (Unguided)
Answers:
1.a. The asset-to-supply plan relationship is 1:M, so you decide to use the 1:M extension table
for the Asset Mgmt - Asset business component. Note that the 1:M extension table has the
name of the parent table appended with _XM. What is the name of the 1:M extension table
you should use?
S_ASSET_XM.

1.b. Identify the columns in which to store supply plan data. Which column in S_ASSET_XM
PAR_ROW_ID. To find out, navigate to Table :: S_ASSET_XM / Column. Query the
Foreign Key Table property for S_ASSET.
1.c. A supply plan specifies the name of the supply, the stocking level and stocking frequency.
NAME.
1.d. The stocking frequency field should be able to store at least 20 characters. Which columns
ATTRIB_03 through ATTRIB_07 are Varchar columns and have a length over 20. Other
columns, such as ATTRIB_01, have the correct data type but have a value in the Length
property that is much longer than what is required for this field.
1.e. The stocking level field should be a number. Which columns will serve this need?
ATTRIB_14 through ATTRIB_25. These columns have a Physical Type of number.
2.b. Are there any existing business components that use this table?
No.

5. In this step, you will gather information required to configure a new link to support the
1:M relationship between Asset Mgmt - Asset and ABC Asset Supply Plan. Enter your
responses directly into this diagram:


Lab 30-1 Using the Standard 1:M Extension Table to

Store Supply Plans (Guided)
Goal To create a new business component using a standard 1:M extension table.

Instructions:
Many customers rely on your company to provide a variety of supplies (consumable goods) for their
durable assets. A given asset may require a variety of different supplies at a variety of different
times. For example, a copier might require paper frequently, toner less frequently, and lubricant
occasionally. For each asset that consumes supplies, your company creates a supply plan, consisting
of a list of supplies, stocking level, and frequency of stocking.
In this lab you will create a new business component, ABC Asset Supply Plan, which is related to
the Asset Mgmt - Asset business component. Each record will identify a supply, stocking level, and
stocking frequency. Since the records for these new components will have a many-to-one
relationship with asset records, you can use the standard 1:M extension table for the Asset Mgmt -
Asset business component.
Since you have already explored fields and business components in previous labs, the steps in this
lab focus on creating a new business component.
1. In this step, you will determine data storage requirements.

a. The asset-to-supply plan relationship is 1:M, so you decide to use the 1:M extension table for
the Asset Mgmt - Asset business component. Note that the 1:M extension table has the name
of the parent table appended with _XM. What is the name of the 1:M extension table you
should use?
b. Identify the columns in which to store supply plan data. Which column in S_ASSET_XM
c. A supply plan specifies the name of the supply, the stocking level and stocking frequency.

d. The stocking frequency field should be able to store at least 20 characters. Which columns
e. The stocking level field should be a number. Which columns will serve this need?
2. In this step, you will determine if a business component already exists that can be used to store
supply plan data in the S_ASSET_XM table.
a. Select Business Component in the OE.
b. Query for Table = S_ASSET_XM. Are there any existing business components that use this

table?
3. In this step, you will create a new project to contain your new business component. Recall that
you are using a separate project to hold each object type. This is done to facilitate managing the
development environment.
a. Select Project in the OE.
b. Add a new object definition with the following values:
Property Value
Name ABC New Bus Comps
Locked TRUE
4. In this step, you will use the business component wizard to create a new business component,
ABC Asset Supply Plan, which will be capable of storing multiple supply plans for each asset.
a. Select File > New Object.
i. Select BusComp under the General tab.
ii. Click OK.
b. In the New Business Component dialog box, enter the following:
Property Value
Project ABC New Bus Comps
Name ABC Asset Supply Plan
Table S_ASSET_XM
c. Click Next.

d. Create single value fields that reference the required user key columns and additional
ATTRIB columns you will need from the S_ASSET_XM table. Use the wizard’s Single
Value Fields dialog box to create each of the following fields:
Column Name
PAR_ROW_ID Asset Id
NAME Supply
TYPE Type
ATTRIB_03 Stocking
Frequency
ATTRIB_14 Stocking Level

e. Click Finish.
f. In the OBLE, set the Search Specification property for the business component you just
created to [Type] = ‘SP’. The Search Specification specifies that when this BCs Type single-
value field = ‘SP’, the record will be retrieved. SP, in this case, stands for Supply Plan.
g. Specify fields that make up the user key. The three fields, Asset Id, Supply, and Type,
together make up the user key. DTYPE_ID references the data as the primary key
automatically generated by the application. Specifying TRUE in the Required property
ensures the user enters data for the Supply field in the UI. The user will not be able to
proceed without either entering data into the Supply field or undoing the record. Setting SP
as the Predefault Value for Type causes the Type field to automatically populate with SP
when the user creates a new record in the UI. This provides a way to flag every record
created in this business component as a supply plan record. Then, when the BC needs to
retrieve its records, it uses the value in the required TYPE column to determine which
records to bring up from the data layer.
i. Query for the Asset Id field then set the field’s values to those shown in the table,
below. Dock the Properties window to quickly view and change property values.
ii. Query for then set values for the Supply field, as shown in the table, below.
iii. Query for then set values for the Type field, as shown in the table, below.
Single Value Field Column Predefault Required Type
Name Value
Asset Id PAR_ROW_ID DTYPE_ID
Supply NAME TRUE DTYPE_TEXT
Type TYPE SP DTYPE_TEXT

h. Specify fields that store the data. Use the OBLE to set and verify the properties listed for
each field in the table, below.
Name Column Predefault Required Type
Value
Stocking Frequency ATTRIB_03 DTYPE_TEXT
Stocking Level ATTRIB_14 DTYPE_NUMBER
5. In this step, you will gather information required to configure a new link to support the 1:M
relationship between Asset Mgmt - Asset and ABC Asset Supply Plan. Enter your responses
directly into this diagram:

a. What is the parent business component?
b. What is the child business component?
c. What field in the child is the foreign key field to the parent?
d. What field in the parent is the primary key field? Recall that Id is a Siebel-supplied field in
all business components that refers to ROW_ID in the base table. However, you will not find
the Id field when you examine the single value fields for a business component.

6. In this step, you will create the link.

a. Select Link in the OE.
b. Add a new object definition and set the following properties:
Property Value
Parent Business Component Asset Mgmt - Asset
Child Business Component ABC Asset Supply Plan
Source Field Asset Id
Destination Field Asset Id
c. What happened to the Name property of the link you just created?

d. Examine pop-up list behavior. Similar to behavior you’ve observed elsewhere in Tools,
choices displayed in the pop-up list for Source Field are context-sensitive. In this case, the
pop-up list displays all fields in Asset Mgmt - Asset, the business component you just
specified for the Parent Business Component property. The same context-sensitivity is true
for the Child Business Component property. When creating new objects in Tools, it is
important to remain cognizant of how pop-up lists are populated.
i. Try an experiment. Create a new link object definition. Leave the Parent Business
Component property empty, then view the Source Field pop-up list. What fields are
available?
ii. Close the pop-up list. Now specify Asset Mgmt - Asset as the Parent Business
Component. Are the fields available different?
iii. Right-click and select Undo Record.
7. In this step, you will verify your work.

a. Right-click the Asset Mgmt - Asset/ABC Asset Supply Plan link object definition and
select Validate.
b. Click Start to begin the validation process.
c. Wait for the validation to complete. If the previous lab steps were followed correctly, you
should not have any errors.
d. Click Cancel to close the validate dialog box.
8. In this step, you will establish a relationship between the new business component, the new
business component’s link, and the Asset Management business object.
a. Select Business Object :: Asset Management | Business Object Component.

b. Add a new object definition and set the following properties:

Property Value
BusComp ABC Asset Supply Plan
Link Asset Mgmt - Asset/ABC Asset Supply Plan
c. If you compiled now, would you be able to test your changes? Why or why not?

Solutions 30-1 Using the Standard 1:M Extension Table

to Store Supply Plans (Guided)
Answers:
1.a. The asset-to-supply plan relationship is 1:M, so you decide to use the 1:M extension table
for the Asset Mgmt - Asset business component. Note that the 1:M extension table has the
name of the parent table appended with _XM. What is the name of the 1:M extension table
you should use?
S_ASSET_XM.

1.b. Identify the columns in which to store supply plan data. Which column in S_ASSET_XM
PAR_ROW_ID. To find out, navigate to Table :: S_ASSET_XM / Column. Query the
Foreign Key Table property for S_ASSET.
1.c. A supply plan specifies the name of the supply, the stocking level and stocking frequency.
NAME.
1.d. The stocking frequency field should be able to store at least 20 characters. Which columns
ATTRIB_03 through ATTRIB_07 are Varchar columns and have a length over 20. Other
columns, such as ATTRIB_01, have the correct data type but have a value in the Length
property that is much longer than what is required for this field.
1.e. The stocking level field should be a number. Which columns will serve this need?
ATTRIB_14 through ATTRIB_25. These columns have a Physical Type of number.
2.b. Are there any existing business components that use this table?
No.

5. In this step, you will gather information required to configure a new link to support the
1:M relationship between Asset Mgmt - Asset and ABC Asset Supply Plan. Enter your
responses directly into this diagram:

6.c. What happened to the Name property of the link you just created?
It automatically populated to Asset Mgmt - Asset/ABC Asset Supply Plan.
6.d.i. Try an experiment. Create a new link object definition. Leave the Parent Business
Component property empty, then view the Source Field pop-up list. What fields are
available?
Created, Created By, Id, Updated, Updated By.
6.d.ii. Now specify Asset Mgmt - Asset as the Parent Business Component. Are the fields
available different?
Yes. The fields available in the Source Field pop-up list are the fields in the business
component specified in Parent Business Component.
8.c. If you compiled now, would you be able to test your changes? Why or why not?
No. There are no user interface objects (views or applets) in which the new business
component is displayed. You will create them in the next lab.

Lab 30-2 Creating a New List and View (Unguided)
Goal To create a new list applet that displays the ABC Supply Plan business component data,
and a view that displays the applet.
Instructions:

In this lab you will create a new applet to display supply plans. The applet will be based on the ABC
Asset Supply Plan business component you have created. You will also create a new master-detail
view that includes the new list applet. You will use wizards to build the applets.
1. Create a new list applet called ABC Asset Supply Plan List Applet in project ABC New Applets
to display the data from the ABC Asset Supply Plan business component.
a. In the General dialog box, enter the following:
Property Value
Name ABC Asset Supply Plan List Applet
Title Supply Plans
Business Component ABC Asset Supply Plan
b. Select the applet for each edit mode.
i. Select Applet List (Base/EditList) for the Base read-only mode.
ii. Select Applet List (Base/EditList) for the Edit List mode.
iii. Select Applet List Edit (Edit/New/Query) for the Edit mode.
c. In the Web Layout - Fields dialog box, add Supply, Stocking Frequency, and Stocking
Level.
d. Accept the default controls.

2. Create a new view called ABC Asset Supply Plan List View that displays the Asset Mgmt -
Asset Detail Applet on the top and the ABC Asset Supply Plan List Applet on the bottom.
a. In the New View dialog box enter the following:
Property Value
Name ABC Asset Supply Plan List View
Title Supply Plans
Business Object Asset Management
b. Select View Detail in the View Web Layout dialog box.

c. In the Web Layout - Applets dialog box, add the Asset Mgmt - Asset Detail Applet and then
the ABC Asset Supply Plan List Applet. Make sure Asset Mgmt - Asset Detail Applet is on
the top and ABC Asset Supply Plan List Applet is immediately below it.
d. Ensure the configuration allows users to add and edit supply plans directly in the list applet.
i. Select View :: ABC Asset Supply Plan List View | View Web Template :: Base |
View Web Template Item :: ABC Asset Supply Plan List Applet and change the
Applet Mode property to Edit List.
ii. Select View :: ABC Asset Supply Plan List View | View Web Template :: Base |
View Web Template Item :: Asset Mgmt - Asset Detail Applet and verify that the
Applet Mode property was set to Edit by the View Wizard.
3. Add the ABC Asset Supply Plan List View you just created to the Asset Management Screen
using the properties below:
Property Value
View ABC Asset Supply Plan List View
Type Detail View
Parent Category Asset Management List
Viewbar Text – String Override Supply Plans
Menu Text – String Override Supply Plans
4. Set the view sequence so that the Detail View - ABC Asset Supply Plan List View appears
immediately after the Detail View - Asset Mgmt - Assets View (Detail).
5. Compile all Locked projects.
6. Administer the ABC Supply Plan List View and add it to the ABC Developer responsibility.


a. Add two Asset records to the assets list.
b. Add supply plan record sto the assets you created.Your view should look similar to this:

c. In the asset form applet, move between the asset records: click Next Record or Previous
Record. Test your link by verifying the supply plan shows up for one and not the other. How
was the foreign key on the supply plan record set?
d. If you were to see the same supply plan records for both assets, what would you need to fix
in Siebel Tools?

Solutions 30-2 Creating a New List and View (Unguided)
Answers:
6.h. In the asset form applet, move between the asset records: click Next Record or Previous
Record. Test your link by verifying the supply plan shows up for one and not the other.
How was the foreign key on the supply plan record set?
The Link object definition updated the foreign key. The Link specifies that, when a Supply
Plan is created, the Asset Id is set to the Id of the Asset for which it was created.
6.i. If you were to see the same supply plan records for both assets, what would you need to fix

in Siebel Tools?
If you can scroll from Asset to Asset, and the list of related supply plans does not change, it
means the Link is not being used. You would need to add the Link to the ABC Asset Supply
Plan business object component of the Asset Management business object.

Lab 30-2 Creating a New List and View (Guided)
Goal To create a new list applet that displays the ABC Supply Plan business component data,
and a view that displays the applet.
Instructions:

In this lab you will create a new applet to display supply plans. The applet will be based on the ABC
Asset Supply Plan business component you have created. You will also create a new master-detail
view that includes the new list applet. You will use wizards to build the applets.
1. In this step, you will create a new list applet called ABC Asset Supply Plan List Applet in
project ABC New Applets to display the data from the ABC Asset Supply Plan business
component.
b. Click the Applets tab.
c. Select List Applet.
d. Click OK.
e. In the General dialog box, enter the following:
Property Value
Name ABC Asset Supply Plan List Applet
Title Supply Plans
Business Component ABC Asset Supply Plan
f. Click Next.
g. Select the applet for each edit mode. For each mode, ensure the displayed thumbnail is
similar to how the applet should appear in the application. In the Web Layout - General
dialog box:
i. Select Applet List (Base/EditList) for the Base read-only mode.
ii. Select Applet List (Base/EditList) for the Edit List mode.
iii. Select Applet List Edit (Edit/New/Query) for the Edit mode.
iv. Click Next.
h. In the Web Layout – Fields dialog box:
i. Double-click Supply in the Available Fields list. Notice how it moved to the Selected
Fields list.
ii. Select Stocking Frequency in the Available Fields list.

iii. Click the right arrow to move it to the Selected Fields list.
iv. Select Stocking Level in the Available Fields list.
v. Click the right arrow to move it to the Selected Fields list.
vi. Click Next.
i. In the Web Layout - Fields dialog box, click Next to accept the default selected controls (all
controls available).
j. In the Finish dialog box, review the Applet properties displayed and click Finish. The Web
Layout Editor will appear.
2. In this step, you will verify wizard output.

a. Ensure the list applet is laid out properly. The fields should be arranged left to right, in this
order: Supply, Stocking Frequency, Stocking Level. If they do not appear in this order, re-
arrange the columns as necessary.

b. Close the Web Layout Editor window. If the Confirm dialog box appears, click Yes to save
your changes.
c. Inspect the object definitions created by the List Applet wizard.
i. Select Applet :: ABC Asset Supply Plan List Applet | List :: List | List Column. What
object definitions were created? List them, according to the value in the Name
property.
ii. Select Applet :: ABC Supply Plan List Applet | Control. Some controls must be
present for a list applet to operate properly. If you configure an applet manually, you
must remember to include these controls. One major benefit of the wizard is that the
controls are configured automatically for you. How many Control object definitions
were created?
3. In this step, you will create a new view called ABC Asset Supply Plan List View that displays
the Asset Mgmt - Asset Detail Applet on the top and the ABC Asset Supply Plan List Applet on
the bottom.
i. Under the General tab, select View.
ii. Click OK.
b. In the New View dialog box enter the following:
Property Value
Name ABC Asset Supply Plan List View
Title Supply Plans
Business Object Asset Management
i. Click Next.

c. In the View Web Layout dialog box:

i. Select View Detail.
ii. Check to make sure that the displayed thumbnail looks like how you expect the view
to look in the application.
iii. Click Next.
d. In the Web Layout - Applets dialog box:
i. In the Available Applets window, double-click Asset Mgmt - Asset Detail Applet.
ii. In the Available Applets window, double-click ABC Asset Supply Plan List Applet.
iii. In the Selected Applets window, ensure Asset Mgmt - Asset Detail Applet is on the
top and ABC Asset Supply Plan List Applet is immediately below it.
iv. Click Next.
e. Review the properties displayed in the Finish window. If you are satisfied with the values,

click Finish.
f. The Web Layout Editor for your view will open. Right-click and select Preview.
g. Confirm that the layout looks as you expected.
h. Close the layout window. If asked, click Yes to save your changes.
i. Ensure the configuration allows users to add and edit supply plans directly in the list applet.
i. Select View :: ABC Asset Supply Plan List View | View Web Template :: Base |
View Web Template Item :: ABC Asset Supply Plan List Applet.
ii. Change the Applet Mode property to Edit List.
iii. Select View :: ABC Asset Supply Plan List View | View Web Template :: Base |
View Web Template Item :: Asset Mgmt - Asset Detail Applet.
iv. Verify the Applet Mode property was set to Edit by the View Wizard.
4. In this step, you will add the ABC Asset Supply Plan List View you just created to the Asset
screen.
a. Select Screen :: Asset Management Screen | Screen View.
b. Add a new object definition.
c. Set the properties for the new object definition to those listed in the table, below. Recall that
a screen references one or more views. In this case, you are creating a reference from the
Asset Management Screen to the ABC Asset Supply Plan List View.
Property Value
View ABC Asset Supply Plan List View
Type Detail View
Parent Category Asset Management List
Viewbar Text – String Override Supply Plans
Menu Text – String Override Supply Plans
d. Set the view sequence.
i. Right-click on the Asset Management Screen object definition in the OBLE’s upper
window.
ii. Select Edit Screen View Sequence. The Detail View - ABC Asset Supply Plan List
View should appear immediately after the Detail View - Asset Mgmt – Assets View
(Detail). If it does not, move it into the correct position.

e. Close the sequence editor. Save your changes, when prompted.

f. Compile all Locked projects. Ensure auto-start web client is enabled.
5. In this step, you will administer the ABC Supply Plan List View.
a. In the application, navigate to Administration – Application > Views.
b. Add the ABC Asset Supply Plan List View. To ensure the record you create in the
application matches exactly the record you create in Tools, copy and paste the view name
from Tools.
c. Add the following description: Used for supply plan Stocking Frequency and Stocking
Level data entry.
d. Click the Responsibilities list at the bottom of the view.
e. Add the ABC Developer responsibility to the ABC Supply Plan List View.
f. Click Responsibilities on the link bar.

g. Click Clear Cache.
h. Log out of your application.

a. Start the Developer Web Client from Tools.
b. In the application, navigate to Assets > Supply Plans. Click the link for Supply Plans.
Troubleshooting Tips: If you do not see the new view, did you administer the view properly?
Did you add the view to the screen? Did you set the proper text properties? Did you add the
view to the ABC Developer responsibility?
c. Select Assets > List.

d. Add two Asset records. Ensure you fill in any required fields.
e. Navigate to Assets > List > Supply Plans.
f. Notice the Supply Plan view tab is highlighted.

g. Add a Supply Plan record to the asset you created. Set the Supply to Toner, Stocking
Frequency to Weekly, and Stocking Level to 3. Your view should look similar to this:

h. In the asset form applet, move between the asset records: click Next Record or Previous
Record. Test your link by verifying the supply plan shows up for one and not the other. How
was the foreign key on the supply plan record set?
i. If you were to see the same supply plan records for both assets, what would you need to fix
in Siebel Tools?
j. Log out of Siebel Call Center.

Solutions 30-2 Creating a New List and View (Guided)
Answers:
2.c.i. Select Applet :: ABC Asset Supply Plan List Applet | List :: List | List Column. What
object definitions were created? List them, according to the value in the Name property.
Stocking Frequency, Stocking Level, Supply.
2.c.ii. Select Applet :: ABC Supply Plan List Applet | Control. Some controls must be present for
a list applet to operate properly. If you configure an applet manually, you must remember
to include these controls. One major benefit of the wizard is that the controls are configured

automatically for you. How many Control object definitions were created?
14.
6.h. In the asset form applet, move between the asset records: click Next Record or Previous
Record. Test your link by verifying the supply plan shows up for one and not the other.
How was the foreign key on the supply plan record set?
The Link object definition updated the foreign key. The Link specifies that, when a Supply
Plan is created, the Asset Id is set to the Id of the Asset for which it was created.
6.i. If you were to see the same supply plan records for both assets, what would you need to fix
in Siebel Tools?
If you can scroll from Asset to Asset, and the list of related supply plans does not change, it
means the Link is not being used. You would need to add the Link to the ABC Asset Supply
Plan business object component of the Asset Management business object.

Module 31: Configuring Picklists
Lab 31-1 Creating a Static Picklist (Unguided)
Goal To create a static picklist.
Instructions:

ABC’s analysts have determined that they can increase the effective productivity of the service reps
who stock customers’ equipment by creating regular stocking routes. To accomplish this, they wish
to give customers the option of stocking twice weekly, weekly, biweekly, or monthly (every four
weeks).
You will use the Pick List wizard to create a bounded, static picklist to populate the stocking
frequency field in the ABC Asset Supply Plan business component. You will use
ABC_STOCK_FREQ for the S_LST_OF_VAL TYPE to identify this new picklist.
1. Inspect the existing Stocking Frequency list column to verify that it does not use a picklist.
a. Start the Siebel Call Center Developer Web Client and log in as PPENGUIN/PPENGUIN
connecting to the Local database.
b. Navigate to Assets > List > Supply Plans.
c. Add a new supply plan record using any supply, and set the value of Stocking Frequency to
Fortnightly. Verify that the stocking frequency does not use a picklist.
2. Use the Pick List wizard to build the new static picklist for Stocking Frequency. The wizard will
create the Pick List definition, attach the picklist to the field, and populate the administrative data
in the S_LST_OF_VAL table. Use the ABC New Bus Comps project for this picklist.
a. Enter ABC Stocking Frequency Picklist for the Name of the Pick List.
b. Create a new List of Values named ABC_STOCK_FREQ and enter the following four
values: Twice Weekly, Weekly, Biweekly, Monthly (4 wks).
c. Enter Regular stocking period for an asset as the Comment and make sure the Bounded Pick
List check box is checked.
3. Inspect the picklist that you created using the wizard and ensure it has the following properties:
Name ABC Stocking Frequency Picklist
Bounded TRUE
Business Component PickList Generic
Type Field Type
Type Value ABC_STOCK_FREQ

4. Verify that the picklist was attached properly to the Stocking Frequency field by examining the
PickList property of that field. You may need to re-query the business component to refresh the
UI.
5. If necessary, set Runtime to TRUE on the proper control or list column in order to make the
picklist available to the user through the applet.
6. Compile the ABC New Bus Comps, ABC New Applets, and Asset Management projects.
7. Test your work.

a. Add a new supply plan. Verify that you can invoke the Stocking Frequency picklist and that
you can see all four values. Can you enter any other value?

b. Edit the supply plan you created at the beginning of this lab. Can you save the record without
changing the value (Fortnightly) in the Stocking Frequency field?
c. Why or why not?
8. Modify the picklist to add a new value, Quarterly, to the choices for Stocking Frequency. You
can administer the picklist from the Siebel Call Center application. Static picklist administration
can also be performed in Siebel Tools by using the Screens > System Administration > List of
Values menu item, but you will use the Siebel client here.
a. Select Administration - Application > Responsibilities.
b. Add the List of Values View to the ABC Developer responsibility.
c. Click Clear Cache.
d. Log out and restart Siebel Call Center so you can use the List of Values View.
e. Navigate to Administration - Data > List of Values.
f. Verify that ABC_STOCK_FREQ has the four values you entered.
g. Add the new value, Quarterly.
h. In the List of Values list, click Clear Cache. Siebel applications use caching to increase
efficiency of functions like Lists of Values. To make sure the new value appears in the List
of Values, you need to clear the cache.
i. Return to a supply plan record. Is the new value for Stocking Frequency available?

j. Suppose at some time in the future, you were directed to change the picklist value from
Biweekly to Fortnightly. What would happen to the Stocking Frequency field in all those
records with a value of Biweekly?

Solutions 31-1 Creating a Static Picklist (Unguided)
Answers:
7.a. Add a new supply plan. Verify that you can invoke the Stocking Frequency picklist and
that you can see all four values. Can you enter any other value?
No.
7.b. Edit the supply plan you created at the beginning of this lab. Can you save the record
without changing the value (Fortnightly) in the Stocking Frequency field?
Yes.

7.c. Why or why not?
The picklist limits the values you can add to the field, but the values are static. The
application does not force you to change values that are already present.
8.i. Return to a supply plan record. Is the new value for Stocking Frequency available?
Yes.
8.j. Suppose at some time in the future, you were directed to change the picklist value from
Nothing, these are static values. If you change the list of values after records are entered,
the existing records are not changed. The new values will only be enforced if a user tries to
edit the value in the Stocking Frequency field.

Lab 31-1 Creating a Static Picklist (Guided)
Goal To create a static picklist.
Instructions:

ABC’s analysts have determined that they can increase the effective productivity of the service reps
who stock customers’ equipment by creating regular stocking routes. To accomplish this, they wish
to give customers the option of stocking twice weekly, weekly, biweekly, or monthly (every four
weeks).
You will use the Pick List wizard to create a bounded, static picklist to populate the stocking
frequency field in the ABC Asset Supply Plan business component. You will use
ABC_STOCK_FREQ for the S_LST_OF_VAL TYPE to identify this new picklist.
1. If necessary, start Siebel Tools and log in as PPENGUIN/PPENGUIN to the Local database.
2. You will inspect the existing Stocking Frequency list column to verify that it does not use a
picklist.
a. Start the Siebel Call Center Developer Web Client from Tools.
b. Use the Site Map to navigate to Assets > List > Supply Plans.
c. Add a new supply plan record using any supply, and set the value of Stocking Frequency to
Fortnightly.
d. Log out of the ABC application.
3. You will use the Pick List wizard to build the new static picklist for Stocking Frequency. The
wizard will create the Pick List definition, attach the picklist to the field, and populate the
administrative data in the S_LST_OF_VAL table.
a. In Siebel Tools, select File > New Object.
i. Under the General tab, select Pick List.
ii. Click OK.
b. In the Pick List dialog box fill in the following values:
i. For Project, select ABC New Bus Comps.
ii. For Business Component, select ABC Asset Supply Plan.
iii. For Field, select Stocking Frequency.
iv. Click Next.
c. In the Pick List Type dialog box:
i. Verify that the Stocking Frequency list column appears in the upper list with the
Locked column set to Yes.
ii. Select Static.

iii. Click Next.

d. In the Pick List Definition dialog box:
i. Select Create new Pick List.
ii. Click Next.
e. In the next Pick List Definition dialog box:
i. Enter ABC Stocking Frequency Picklist for the Name of the Pick List.
ii. Select Create new List of Values.
iii. Click Next.
f. In the List of Values dialog box:
i. Enter ABC_STOCK_FREQ for the name for the List of Values.
ii. Enter Twice Weekly in the Enter a value field.
iii. Click Enter.

iv. Repeat the previous steps to enter three additional values: Weekly, Biweekly,
Monthly (4 wks).
v. Verify the values in the Current values list.
vi. Click Next.
g. In the Pick List Definition dialog box:
i. Leave the Search Specification empty.
ii. Enter Regular stocking period for an asset as the Comment.
iii. Check the Bounded Pick List check box.
iv. Click Next.
h. Review the Picklist properties displayed in the Finish dialog box. If you are satisfied with the
values, then click Finish.
4. You will inspect the picklist that you created using the wizard.
a. Select Pick List :: ABC Stocking Frequency Picklist.
b. View the properties.
Name ABC Stocking Frequency Picklist
Bounded TRUE
Type Field Type
Type Value ABC_STOCK_FREQ
5. You will verify that the picklist was attached properly to the Stocking Frequency field.
a. Select Business Component :: ABC Asset Supply Plan | Single Value Field :: Stocking
Frequency.
b. Verify PickList = ABC Stocking Frequency Picklist.
c. Do you need to create a Pick applet to display this data to the user at run time?

6. You will set Runtime to TRUE on the proper control or list column in order to make the picklist
available to the user through the applet.
a. Select Applet :: ABC Asset Supply Plan List Applet | List :: List | List Column :: Stocking
Frequency.
b. Set Runtime = TRUE (if not already set by default).
7. Compile the ABC New Bus Comps, ABC New Applets, and Asset Management projects with
the Auto-start web client check box selected.
8. Next you will test your work.

a. In the application, use the Site Map to navigate to Assets > List > Supply Plans.
b. Add a new supply plan. Verify that you can invoke the Stocking Frequency picklist and that
you can see all four values. Can you enter any other value?

c. Edit the supply plan you created at the beginning of this lab. Can you save the record without
changing the value (Fortnightly) in the Stocking Frequency field?
d. Why or why not?
9. At this point you will modify the picklist values to add a new value, Quarterly, to the choices for
Stocking Frequency. You can administer the picklist from the Siebel Call Center application.
Static picklist administration can also be performed in Siebel Tools by using the Screens >
System Administration > List of Values menu item, but you will use the Siebel client here.
a. Select Administration – Application > Responsibilities.
b. Add the List of Values View to the ABC Developer responsibility.
c. Click Clear Cache.
d. Log out and restart Siebel Call Center so you can use the List of Values View.
e. Navigate to Administration - Data > List of Values.
f. Does ABC_STOCK_FREQ appear?
g. Verify that ABC_STOCK_FREQ has the four values you entered.

h. Add the new value, Quarterly.
i. Select Monthly (4 wks)
ii. Click the Menu button and select Copy Record.

iii. In the newly created record set the following properties:

Display Value Quarterly
Language Independent Code Quarterly
Order 4
iv. Step off the record to save it.
i. In the List of Values list, click Clear Cache. Siebel applications use caching to increase
efficiency of functions like Lists of Values. To make sure the new value appears in the List
of Values, you need to clear the cache.
j. Use the Site Map to navigate to Assets > List > Supply Plans and edit a record. Is the new
value for Stocking Frequency available?

k. Suppose at some time in the future, you were directed to change the picklist value from

Solutions 31-1 Creating a Static Picklist (Guided)
Answers:
5.c. Do you need to create a Pick applet to display this data to the user at run time?
No. Since this is a static picklist, the application will automatically generate one at run
time.
8.b. Add a new supply plan. Verify that you can invoke the Stocking Frequency picklist and
that you can see all four values. Can you enter any other value?

No
8.c. Edit the supply plan you created at the beginning of this lab. Can you save the record
without changing the value (Fortnightly) in the Stocking Frequency field?
Yes
8.d. Why or why not?

The picklist limits the values you can add to the field, but the values are static. The
application does not force you to change values that are already present.
9.f. Does ABC_STOCK_FREQ appear?

Yes
9.j. Use the Site Map to navigate to Assets > List > Supply Plans and edit a record. Is the new
value for Stocking Frequency available?
Yes
9.k. Suppose at some time in the future, you were directed to change the picklist value from
Nothing, these are static values. If you change the list of values after records are entered,
the existing records are not changed. The new values will only be enforced if a user tries to
edit the value in the Stocking Frequency field.


Lab 31-2 Creating a Dynamic Picklist (Unguided)
Goal To create a dynamic picklist.
Instructions:

In this lab you will create a Currency field in the Contact business component. You will display this
field in a control on the Contact Form Applet. Finally, you will add a dynamic picklist to the control
to enable users to update the contact’s preferred currency.
1. Gather the information you need to create the Currency field.

a. Start the Siebel Call Center Developer Web Client and log in as SADMIN/SADMIN
b. Use the Site Map to navigate to Administration - Data > Currencies.
i. Which business components are displayed in this view?
ii. Which applets are displayed in this view?
iii. What is the header of the list column displaying the name of the currency?
2. Now you will get information about currencies in Siebel Tools.

a. What table and column store the currency name you found above?
b. Are there any existing joins from the Contact business component to this table?
3. Find the information necessary to build a join to this table on the Contact business component.
a. What column acts as the primary key for this table?
b. Which column on S_CONTACT is defined as a foreign key to this table?

c. Which field in the Contact business component is based on this column?
4. Use Siebel Tools to evaluate whether to create a new picklist or use an existing picklist. Query
for picklists with for Business Component = Currency. Are there any dynamic picklists based
on this business component that you can use?
5. Evaluate whether to create a new pick applet or use an existing pick applet. Query for applets
where Business Component = Currency and Type = Pick List. Are there any pick applets
based on the Currency business component?

6. Create a join for the Contact business component that brings in data from the S_CURCY table.
Name it Contact Currency and make it an outer join. Do not forget to add the join specification.
7. Create a single value field on the Contact business component with the properties below. Accept
the default length.
Name Currency Name
Join Contact Currency

Column NAME
Type DTYPE_TEXT
PickList PickList Currency
8. Create the necessary pick maps for the Currency Name field. These will map fields between the
originating business component (Contact) and the pick business component (Currency).
a. Select Business Component :: Contact | Single Value Field :: Currency Name | SVF Pick
Map.
b. Add a new record and set the following properties:
Field Income Currency Code
Pick List Field Currency Code
c. Add another new record and set the following properties:
Field Currency Name
Pick List Field Name
d. Why are you attaching pick maps to the Currency Name field and not the Income Currency
Code field?

9. Add the Currency Name field to the Contact Form Applet by creating a control with the
following properties. Do not forget to edit the Web layout to add the control and a label for it:
Name Currency
Caption Currency
Field Currency Name
HTML Type Field
Pick Applet Currency Pick Applet
Runtime TRUE
10. Save and compile your changes. Because you changed many object definitions, be sure to

compile all locked projects.
11. Test your work. Navigate to the Contacts list and, if necessary, create a record. Verify that the
currency control appears in the form applet with a select button, and that you can invoke the pick
applet and select a currency from the list. Requery the contacts for the record and confirm that
the value was stored correctly.

Solutions 31-2 Creating a Dynamic Picklist (Unguided)
Answers:
1.b.i. Which business components are displayed in this view?
Currency.
1.b.ii. Which applets are displayed in this view?

Currency List Applet, Currency Entry Applet.
1.b.iii. What is the header of the list column displaying the name of the currency?

Name.
2.a. What table and column store the currency name you found above?
The table is S_CURCY; the column in this table is NAME.
2.b. Are there any existing joins from the Contact business component to this table?
No.
3.a. What column acts as the primary key for this table?
CURCY_CD. This is a rare example of a table that does not use ROW_ID as its primary
key.
3.b. Which column on S_CONTACT is defined as a foreign key to this table?

ANNL_INCM_CURCY_CD.
3.c. Which field in the Contact business component is based on this column?
Income Currency Code.
4. Use Siebel Tools to evaluate whether to create a new picklist or use an existing picklist.
Query for picklists with for Business Component = Currency. Are there any dynamic
picklists based on this business component that you can use?
Yes, there are two: PickList Currency, PickList Currency - CPG. You will use PickList
Currency.
5. Evaluate whether to create a new pick applet or use an existing pick applet. Query for
applets where Business Component = Currency and Type = Pick List. Are there any
pick applets based on the Currency business component?
Yes, the Currency Pick Applet is based on the Currency business component.
8.d. Why are you attaching pick maps to the Currency Name field and not the Income Currency
Code field?
Currency Name is the field behind the control that is visible to the user on the applet. Since
the Income Currency Code field is not displayed to the user, it would not make sense to
place the picklist on this field. The user would not be able to invoke it.

Lab 31-2 Creating a Dynamic Picklist (Guided)
Goal To create a dynamic picklist.
Instructions:

In this lab you will create a Currency field in the Contact business component. You will display this
field in a control on the Contact Form Applet. Finally, you will add a dynamic picklist to the control
to enable users to update the contact’s preferred currency.
The instructions will concentrate on the new information and give more general instructions for
some tasks that are familiar by now. If you need to refer back to earlier labs to accomplish some
tasks, please do so.
1. First, you will gather the information you need to create the Currency field.
a. Start the Siebel Call Center Developer Web Client and log in as SADMIN/SADMIN
b. Use the Site Map to navigate to Administration - Data > Currencies.
i. Which business components are displayed in this view?
ii. Which applets are displayed in this view?
iii. What is the header of the list column displaying the name of the currency?
iv. Log out of the Call Center application.
2. Now you will get information about currencies in Siebel Tools.

a. In Siebel Tools, select Applet :: Currency List Applet | List :: List | List Columns
b. Find the List Column that has a Display Name of Name. What is the value of the Field
property?
c. Select Business Component :: Currency. What is the value of the Table property?

d. Select Business Component :: Currency | Single Value Field :: Name. What is the value of
the Column property?
e. Select Business Component :: Contact | Join. Are there any existing joins from the Contact
business component to S_CURCY?
3. You will find the information necessary to build a join to S_CURCY on the Contact business
component.
a. Select Table :: S_CURCY | Column and query for the primary key property. What column
acts as the primary key for this table?

b. Which column on S_CONTACT is defined as a foreign key to this table?
c. Which field in the Contact business component is based on this column?
4. You will evaluate whether to create a new picklist or use an existing picklist.
a. Select Picklist in the Object Explorer. In the OBLE, query for Business Component =
Currency. Are there any dynamic picklists based on this business component that you can
use?
Hint: the Static property will be unchecked for a dynamic picklist.
b. Based on the properties of the picklists, you decide to use PickList Currency.
5. Now you will evaluate whether to create a new pick applet or use an existing pick applet.
a. Select Applet in the Object Explorer.
b. Query for Business Component = Currency and Type = Pick List.
c. Are there any pick applets based on the Currency business component?

6. You will create the Currency field.

a. Check out the projects Contact and Contact (SSE).
b. Select Business Component :: Contact | Join and create a new record:
Table S_CURCY
Alias Contact Currency
Outer Join Flag TRUE
c. Select Business Component :: Contact | Join :: S_CURCY | Join Specification and create a
new record:
Name Currency
Destination Column CURCY_CD

Source Field Income Currency Code
d. Select Business Component :: Contact | Single Value Field and create a new record:
Name Currency Name
Join Contact Currency

Column NAME
Type DTYPE_TEXT
PickList PickList Currency
e. Why are you attaching the picklist to Currency Name and not Income Currency Code?
7. You will create pick maps for the Currency Name field. These will map fields between the
originating business component (Contact) and the pick business component (Currency).
a. Select Business Component :: Contact | Single Value Field :: Currency Name | SVF Pick
Map.
b. Add a new record and set the following properties:
Field Income Currency Code
Pick List Field Currency Code

c. Add another new record and set the following properties:

Field Currency Name
Pick List Field Name
d. Why are you attaching the pick maps to the Currency Name field and not the Income
Currency Code field?

8. Next, you will add the Currency Name field to the Contact Form Applet.
a. Select Applet :: Contact Form Applet | Control.
b. Create a new record with the following properties:
Name Currency
Caption – String Override Currency
Field Currency Name
HTML Type Field
Pick Applet Currency Pick Applet
Runtime TRUE
c. Right-click the Contact Form Applet in the OLBE and select Edit Web Layout. Add the
Currency control and its label to the Edit mode template.
9. Save and compile your changes with the Auto-start web client checkbox selected. Because you
changed many object definitions, be sure to compile locked projects.
10. Finally, you will test your work.

a. Select Contacts > Contacts List.
b. Create a record if necessary.
c. Does the Currency control appear in the form with a Select button?
d. Can you invoke the pick applet and select a currency from the list?

e. Try entering some word that is not a currency—for example, the word “rosebud”—in the
Currency field. What happens when you attempt to save this?

Solutions 31-2 Creating a Dynamic Picklist (Guided)
Answers:
1.b.i. Which business components are displayed in this view?
Currency.
1.b.ii. Which applets are displayed in this view?

Currency List Applet, Currency Entry Applet.
1.b.iii. What is the header of the list column displaying the name of the currency?

Name.
2.b. Find the List Column that has a Display Name of Name. What is the value of the Field
property?
Name.
2.c. Select Business Component :: Currency. What is the value of the Table property?
S_CURCY.
2.d. Select Business Component :: Currency | Single Value Field :: Name. What is the value of
the Column property?
NAME.
2.e. Select Business Component :: Contact | Join. Are there any existing joins from the Contact
business component to S_CURCY?
No.
3.a. Select Table :: S_CURCY | Column and query for the primary key property. What column
acts as the primary key for this table?
CURCY_CD.
3.b. Which column on S_CONTACT is defined as a foreign key to this table?

ANNL_INCM_CURCY_CD.
3.c. Which field in the Contact business component is based on this column?
Income Currency Code.
4.a. Select Picklist in the Object Explorer. In the OLE, query for Business Component =
Currency. Are there any dynamic picklists based on this business component that you can
use?
Yes, there are two: PickList Currency, PickList Currency - CPG.
5.c. Are there any pick applets based on the Currency business component?
Yes, the Currency Pick Applet is based on the Currency business component.

6.e. Why are you attaching the picklist to Currency Name and not Income Currency Code?
Currency Name is the field behind the control that is visible to the user on the applet. Since
the Income Currency Code field is not displayed to the user, it would not make sense to
place the picklist on this field. The user would not be able to invoke it.
7.d. Why are you attaching the pick maps to Currency Name and not Income Currency Code?
Currency Name is the field that has the picklist attached, and from which the user invokes
the list. You must pick back Income Currency Code, since this is the value that is actually
stored on the record. You do this by adding multiple pick maps.
10.c. Does the Currency control appear in the form with a Select button?
Yes.
10.d. Can you invoke the pick applet and select a currency from the list?

Yes.
10.e. Try entering some word that is not a currency—for example, the word “rosebud”—in the
Currency field. What happens when you attempt to save this?
The change is lost and the pick applet appears.


Module 32: Configuring Multi-Value Groups
Lab 32-1 Configuring a Multi-Value Field (Unguided)
Goal To configure primary records, multi-value fields (MVFs), multi-value links (MVLs), and multi-
value group (MVG) applets.
Instructions:

ABC Company stores many notes about a contact. You determine that the best way to do this is with
a business component that will store public and private notes about contacts. You will display this
information as a multi-value field on the form applet.
1. Examine the Call Center application and find how notes are already stored.
a. Start the Siebel Call Center Web client and log in as SADMIN/SADMIN.
b. Navigate to the Contacts list and drill down on the first contact’s Last Name. Then click the
Notes tab, and then the Public Notes hyperlink.
i. What is the bottom business component?
ii. What is the bottom applet?
iii. What is the caption of the list column that stores the note text?
c. Click the Private Notes link. What is the bottom business component?
2. Gather the information you need to create a multi-value group applet that shows all public notes
and your private notes about this contact.
a. In Siebel Tools, examine the list columns for the applet you found above. Find the column
that has Description in the Display Name property. What field does this list column map to?
b. Query for the two business components you noted earlier using an OR operator. Other than
the names, what one property is different between these business components? What are the
values?

c. What table and column is used to store the contact note information for these business
components?
3. Create a new business component that represents a combination of the two business components
you just explored: Contact Note and Contact Private Note. Create it by copying the Contact Note
business component and setting the following parameters::
Name ABC Contact Note
Search Private = ‘N’ or Private IS NULL or (Private = ‘Y’ AND Created By = LoginId())
Specification
It is important that the search specification match the above exactly. Notice that there are spaces

between the words, and that the expression uses single quotes.
4. What field in your new business component appears to be a foreign key to S_CONTACT?
5. Create a link from the Contact business component to the ABC Contact Note business
component using the following properties:
Name Contact/ABC Contact Note
Parent Business Component Contact
Child Business Component ABC Contact Note
Source Field Id
Destination Field Contact Id
Cascade Delete Delete
6. Create a single-value field that points to the primary note. Using the primary improves
performance.
a. Which column in the S_CONTACT table acts as a foreign key to S_NOTE_CON?
b. Does the Contact business component have a primary foreign key field to S_ NOTE_CON;
that is, a field corresponding to the column you just found?
c. Create a new single value field to reference that column:

Name Primary Note Id
Join S_CONTACT
Column PR_NOTE_ID
Type DTYPE_ID

7. Create the multi-value link and multi-value field using the MVG Wizard.
a. In the General dialog box, fill in the following properties:
Project Contact
Master Business Component Contact
b. In the next dialog box, fill in the following properties:
Detail Business Component ABC Contact Note
Multi-Value Link ABC Contact Note
c. In the Direct Links dialog box, select a link:
Source Field Id

d. In the Primary Id Field dialog box, set these properties:
i. Leave the Primary Id field blank. You will manually set the primary ID field for the
multi-value link created by the wizard.
ii. Verify that Auto Primary is set to Default. This setting will cause the first record
entered in the MVG to become the primary by default.
iii. Check the Use Primary Join check box.
iv. Leave the Check No Match check box unchecked.
e. In the Multi-Value Link dialog box, confirm that all properties are blank (unchecked). You
do not want to restrict these properties for this applet.
f. In the Multi-Value Fields dialog box, select Note for the field in the destination business
component of the multi-value link. Enter Contact Note MVF as the name of the multi-value
field.
g. Review the settings and click Finish. The MVG Applet wizard should start immediately. If it
does not, select File > New Object > Applets > MVG Applet. (Note the General dialog box
should display automatically after File > New Object is selected.)
8. Create the MVG applet. This applet will appear when the user clicks the MVG icon in the Notes
field, which you will create later in this lab.
Project Contact (SSE)
Name ABC Contact Note MVG
Applet
Display Title Notes
Business Component ABC Contact Note
Note: The Contact project contains generic Contact-related objects, while Contact (SSE),
Contact (SSV), and Contact (SCW) contain UI object definitions for different Siebel
applications. Contact (SSE) contains UI elements used by Siebel Call Center.
b. In the Web Layout – General dialog box, select the Popup List MVG template for both base
and edit modes.

c. In the Web Layout – Fields dialog box, add each of these fields to the MVG applet in the
order listed below. These are the fields you have chosen to appear in the MVG applet.
SSA Primary Field
Private
Note Type
Note
d. Accept the default controls.
9. Modify the MVG applet created by the wizard.

a. Select the SSA Primary Field list column in the Applet window. This list column was
generated by the wizard and uses a special field to display the primary check box.
b. Right-click SSA Primary Field and select View Properties Window.

c. Set the following properties for the SSA Primary Field:
Display Name – String Primary
Override
HTML Icon Map CHECK
d. Select the Private list column and set the HTML Icon Map property to CHECK. This will
cause this list column to be represented by a check box.
10. Add an OK button to the applet. The MVG applet created by the MVG wizard does not have a
control that can be bound to the OK button, because the control is not included in the Popup List
MVG web template you specified in the wizard. You will add this control and bind it to the
button.
a. Create a new control for the ABC Contact Note MVG Applet with the following properties:
Caption OK
HTML Display Mode DontEncodeData
HTML Type MiniButton
Method Invoked CloseApplet
Name CloseApplet
Sort FALSE
Visible - Language Override TRUE
Note: These parameters are appropriate for a button that will display the caption OK and will
execute the CloseApplet method when invoked.
b. From the Mode drop-down in the Controls/Columns window, select 2: Edit List.
c. At the top of the applet, delete the Query Assistant button.
d. Drag the NewRecord button control into the placeholder marked New.
e. Drag the CloseApplet button control that you created earlier into the placeholder marked OK
in the bottom right of the layout window.
f. Repeat the last two steps for Base mode (1: Base).
g. Close the Web Layout Editor, saving any changes.

11. Modify the multi-value link (MVL) that was created by the wizard.
a. Select the ABC Contact note multi-value link in the Contact business component.
b. Set the Primary ID Field property to Primary Note Id. Using a primary for the MVG you
have created will result in better performance when displaying a contact record because no
extra SQL queries will be needed to display the primary record in the MVG field in the
Contact Form Applet.
12. Change the form applet so it will show the new Multi-value Field.
a. Edit the Web layout of the Contact Form Applet.
b. Select 1: Edit from the Mode drop-down in the top left of the application.
c. Drag the Text control from the Palettes pane to the grid, placing the control adjacent to other
controls.

d. If necessary, right-click the new control and select View Properties Window.
e. Set these properties for the new text control:
Name Notes
Caption – String Override Notes
Field Contact Note MVF
HTML Type Field
MVG Applet ABC Contact Note MVG
Applet
Runtime TRUE
f. Create a Notes label control and drag it onto the Grid next to the new Text control.
g. Save your work and close the layout designer.
13. Compile all locked projects and start the client.
14. Test your work.

a. Select Contacts > Contacts List. Does the Note MVF control appear in the Contact form?
b. Create a contact record.

c. In the Notes field, click the Select button. Does the MVG applet appear?
d. Does the MVG applet display the Primary, Private, Note Type, and Note fields?
e. Verify that you can enter records in the Notes MVG applet.
i. Is the Primary check mark visible in the Notes MVG applet?

ii. Can more than one record be marked as the Primary note?
15. To prepare for the next lab, check out the Table Asset project. This process may take some time
to complete, so let it run during the next lecture.

Solutions 32-1 Configuring a Multi-Value Field

(Unguided)
Answers:
1.b.i. What is the bottom business component?
Contact Note.
1.b.ii. What is the bottom applet?

Contact Note Applet.

1.b.iii. What is the caption of the list column that stores the note text?
Description.
1.b. Click the Private Notes link. What is the bottom business component?
Contact Private Note.
2.a. In Siebel Tools, examine the list columns for the applet you found above. Find the column
that has Description in the Display Name property. What field does this list column map
to?
Note.
2.b. Query for the two business components you noted earlier using an OR operator. Other than
the names, what one property is different between these business components? What are
the values?
The Search Specification property differs. It is “Private = ‘N’ OR Private IS NULL” for
the first business component, and “Private = ‘Y’ AND Created By = Login Id()” for the
second business component.
2.c. What table and column is used to store the contact note information for these business
components?
The NOTE column in the S_NOTE_CON table.
4. What field in your new business component appears to be a foreign key to S_CONTACT?
Contact Id.
6.a. Which column in the S_CONTACT table acts as a foreign key to S_NOTE_CON?
PR_NOTE_ID.
6.b. Does the Contact business component have a primary foreign key field to S_ NOTE_CON;
that is, a field corresponding to the column you just found?
No.
14.a. Select Contacts > Contacts List. Does the Note MVF control appear in the Contact form?
Yes.

14.c. In the Notes field, click the Select button. Does the MVG applet appear?
Yes.
14.d. Does the MVG applet display the Primary, Private, Note Type, and Note fields?
Yes.
14.e.i. Is the Primary check mark visible in the Notes MVG applet?
Yes.
14.e.ii. Can more than one record be marked as the Primary note?
No.

Lab 32-1 Configuring a Multi-Value Field (Guided)
Goal To configure primary records, multi-value fields (MVFs), multi-value links (MVLs), and multi-
value group (MVG) applets.
Instructions:

ABC Company stores many notes about a contact. You determine that the best way to do this is with
a business component that will store public and private notes about contacts. You will display this
information as a multi-value field on the form applet.
1. First, you will examine the Call Center application and find how notes are already stored.
b. Click the Contacts screen tab, then the Contacts List link. Select Help > About View. What is
the name of the bottom applet?
c. Drill down on the first contact’s Last Name.

d. Click the Notes tab, and then the Public Notes hyperlink.
e. Select Help > About View.
i. What is the bottom business component?
ii. What is the bottom applet?
iii. Click OK.

f. What is the caption of the list column that stores the note text?
g. Click the Private Notes link. Select Help > About View. What is the bottom business
component?
h. Click OK to close the About View dialog.

i. Log out of Siebel Call Center and close the browser.

2. You will gather the information you need to create a multi-value group applet that shows all
public notes and your private notes about this contact.
Local database.
b. Expand the Object Explorer and go to Applet:: Contact Note Applet | List :: List | List
Column.
c. Find the column that has Description in the Display Name property. What field does this list
column map to?
d. In the Object Explorer, select Business Component.

e. Query for the two business components you noted earlier. The query should be in the Name
property, and use the syntax Contact Note OR Contact Private Note.

i. Other than the names, what one property is different between these business
components?
ii. What is the value of this property in the first business component?
iii. What is the value of this property in the second business component?
iv. What is the value of the Table property on these business components?
v. Select Business Component :: Contact Note | Single Value Field :: Note. What is the
value of the Column property?
3. You will create a business component that represents a combination of the two business
components you just explored: Contact Note and Contact Private Note.
a. Select Business Component :: Contact Note.
b. From the application-level Edit menu, select Copy Record.
c. Set the following Properties on the new copy of the record:
Name ABC Contact Note
Search Private = ‘N’ or Private IS NULL or (Private = ‘Y’ AND Created By = LoginId())
Specification
The search specification will return all notes that are either public (non-private), or private
and created by the current user.
It is important that the search specification match the above exactly. Notice that there are
spaces between the words, and that the expression uses single quotes.

d. Select Business Component :: Contact Note | Single Value Field. What field appears to be a
foreign key to S_CONTACT?
4. You will create a link from Contact to your new Business Component.
a. Create a new link with the following properties:
Parent Business Component Contact
Child Business Component ABC Contact Note
Source Field Id

Destination Field Contact Id
Cascade Delete Delete
5. Next, you will create a single-value field that points to the primary note. You will use the
primary to improve performance.
a. Determine whether the underlying column already exists.
i. Go to Table :: S_CONTACT | Column.
ii. In the Foreign Key Table property, query for S_NOTE_CON. Which column acts as
a foreign key to S_NOTE_CON?
b. Determine whether the Contact business component has a primary foreign key field to S_
NOTE_CON.
i. Go to Business Component :: Contact | Single Value Field.
ii. Query the single value fields for Column = PR_NOTE_ID. Notice that there is no
primary foreign key field.
c. Create a new single value field with the following properties:
Name Primary Note Id
Join S_CONTACT
Column PR_NOTE_ID
Type DTYPE_ID
6. You will create the multi-value link and multi-value field using the MVG Wizard.
a. Select File > New Object…
b. Under the General tab, select MVG and click OK.
c. In the General dialog box, fill in the following properties:
Project Contact
Master Business Component Contact
d. Click Next.

e. In the next dialog box, fill in the following properties:

Detail Business Component ABC Contact Note
Multi-Value Link ABC Contact Note
f. Click Next.
g. In the Direct Links dialog box, select a link:
Source Field Id
h. Click Next.
i. In the Primary Id Field dialog box, set these properties:
i. Leave the Primary Id field blank. You will manually set the primary ID field for the
multi-value link created by the wizard.

ii. Verify that Auto Primary is set to Default. This setting will cause the first record
entered in the MVG to become the primary by default.
iii. Check the Use Primary Join check box.
iv. Leave the Check No Match check box unchecked.
j. Click Next.
k. In the Multi-Value Link dialog box, confirm that all properties are blank (unchecked) and
click Next. You do not want to restrict these properties for this applet.
l. In the Multi-Value Fields dialog box, select Note for the field in the destination business
component of the multi-value link. Enter Contact Note MVF as the name of the multi-value
field. Click Add.
m. Click Next.
n. Review the settings and click Finish. The MVG Applet wizard should start immediately. If it
does not, select File > New Object > Applets > MVG Applet. (Note the General dialog box
should display automatically after File > New Object is selected.)
7. You will now create the MVG applet. This applet will appear when the user clicks the MVG icon
in the Notes field, which you will create later in this lab.
Name ABC Contact Note MVG
Applet
Display Title Notes
Business Component ABC Contact Note
Note: The Contact project contains generic Contact-related objects, while Contact (SSE),
Contact (SSV), and Contact (SCW) contain UI object definitions for different Siebel
applications. Contact (SSE) contains UI elements used by Siebel Call Center.
b. Click Next.
c. In the Web Layout - General dialog box, select the Popup List MVG template for both base
and edit modes.
d. Click Next.

e. In the Web Layout – Fields dialog box, add each of these fields to the MVG applet in the
order listed below. These are the fields you have chosen to appear in the MVG applet.
SSA Primary Field
Private
Note Type
Note
f. Click Next.
g. Click Next to add all the specified controls.
h. Review the settings and click Finish. This should cause the applet to appear in the Layout
editor.
8. You will inspect the MVG applet created by the wizard.

a. Select the SSA Primary Field list column in the Applet window. This list column was
generated by the wizard and uses a special field to display the primary check box.
b. Right-click SSA Primary Field and select View Properties Window.
c. Set the following properties for the SSA Primary Field:
Display Name - String Primary
Override
HTML Icon Map CHECK
d. Select the Private list column and set the HTML Icon Map property to CHECK. This will
cause this list column to be represented by a check box.
9. You will add a control to the applet. The MVG applet created by the MVG wizard does not have
a control that can be bound to the OK button, because the control is not included in the Popup
List MVG web template you specified in the wizard. You will add this control and, in the next
step, bind it to the button.
a. Select Applet :: ABC Contact Note MVG Applet | Control in the Object Explorer.
b. In the OBLE, right-click and select New Record.
c. Use the Properties pane to enter the following parameters for this new control:
Caption OK
HTML Display Mode DontEncodeData
HTML Type MiniButton
Method Invoked CloseApplet
Name CloseApplet
Sort FALSE
Visible - Language Override TRUE
Note: These parameters are appropriate for a button that will display the caption OK and will
execute the CloseApplet method when invoked.
d. Save the record.

10. You will modify the buttons displayed on the MVG applet.
a. From the Mode drop-down in the Controls/Columns window, select 2: Edit List.
b. At the top of the applet, scroll to the right, right-click the Query Assistant button and select
Delete.
c. From the Controls/Columns window, drag the NewRecord button control into the
placeholder marked New.
d. From the Controls/Columns window, drag the CloseApplet button control that you created
earlier into the placeholder marked OK in the bottom right of the layout window.
e. Repeat the last two steps for Base mode (1: Base).
f. Close the Web Layout Editor, saving any changes.
11. You will inspect the multi-value link (MVL) that was created by the wizard.
a. Select Business Component :: Contact | Multi Value Link :: ABC Contact Note

b. Set the Primary ID Field property to Primary Note Id. Using a primary for the MVG you
have created will result in better performance when displaying a contact record because no
extra SQL queries will be needed to display the primary record in the MVG field in the
Contact Form Applet.
Note: You will add this MVG field to the Contact Form Applet later in this lab.
12. You will inspect the MVFs that were created by the wizard.
a. Select Business Component :: Contact | Multi Value Field.
b. Which multi-value link does the Contact Note MVF use?
13. Next, you will change the form applet so it will show the new Multi-value Field.
a. Select Applet :: Contact Form Applet.
c. Select 1: Edit from the Mode drop-down in the top left of the application.
d. Drag the Text control from the Palettes pane to the grid, placing the control adjacent to other
controls.
e. If necessary, right-click the new control and select View Properties Window.
f. Set these properties for the new text control:
Name Notes
Caption - String Override Notes
Field Contact Note MVF
HTML Type Field
MVG Applet ABC Contact Note MVG
Applet
Runtime TRUE
g. Drag the Notes label control onto the Grid next to the new Text control.
h. Save your work and close the layout designer.

14. Compile all locked projects and auto-start the client.
15. Finally, you will test your work.

a. Select Contacts > Contacts List. Does the Note MVF control appear in the Contact form?
b. Create a contact record.

c. In the Notes field, click the Select button. Does the MVG applet appear?
d. Does the MVG applet display the Primary, Private, Note Type, and Note fields?

e. Verify that you can enter records in the Notes MVG applet.
i. Is the Primary check mark visible in the Notes MVG applet?
ii. Can more than one record be marked as the Primary note?
16. Log out and close the application.
17. To prepare for the next lab, check out the Table Asset project. This process may take some time
to complete, so let it run during the next lecture.

Solutions 32-1 Configuring a Multi-Value Field (Guided)
Answers:
1.b. Go to the Contacts screen tab, the Contacts List hyperlink. Select Help > About View.
What is the name of the bottom applet?
Contact Form Applet
1.e.i. What is the bottom business component?

Contact Note

1.e.ii. What is the bottom applet?
Contact Note Applet
1.f. What is the caption of the list column that stores the note text?
Description
1.g. Click the Private Notes hyperlink. Select Help > About View. What is the bottom business
component?
Contact Private Note
2.c. Find the column that has Description in the Display Name property. What field does this
list column map to?
Note
2.e.i. Other than the names, what one property is different between these business components?
The Search Specification
2.e.ii. What is the value of this property in the first business component?
Private = ‘N’ OR Private IS NULL
2.e.iii. What is the value of this property in the second business component?
Private = ‘Y’ AND Created By = Login Id()
2.e.iv. What is the value of the Table property on these business components?
S_NOTE_CON
2.e.v. Select Business Component :: Contact Note | Single Value Field :: Note. What is the value
NOTE
3.d. Select Business Component :: Contact Note | Single Value Field. What field appears to be a
foreign key to S_CONTACT?
Contact Id

5.a.ii. In the Foreign Key Table property, query for S_NOTE_CON. Which column acts as a
foreign key to S_NOTE_CON?
PR_NOTE_ID
12.b. Which multi-value link does the Contact Note MVF use?
ABC Contact Note
15.a. Select Contacts > Contacts List. Does the Note MVF control appear in the Contact form?
Yes
15.c. In the Notes field, click the Select button. Does the MVG applet appear?
Yes
15.d. Does the MVG applet display the Primary, Private, Note Type, and Note fields?

Yes
15.e.i. Is the Primary check mark visible in the Notes MVG applet?
Yes
15.e.ii. Can more than one record be marked as the Primary note?
No


Module 33: Data Layer Configuration
Lab 33-1 Adding Extension Columns (Unguided)
Goal To add custom extension columns to a table.
Instructions:

ABC field service reps often need detailed information regarding how to locate and gain access to
assets on a customer’s premises.
In this lab, you will provide for this by adding two new fields to the existing Asset Mgmt - Asset
business component, using custom extension columns in the base table. You will first verify that
there are no existing fields in the business component or columns in the base table that could satisfy
your requirements. You will then extend the base table by adding two extension columns.
1. If you have not already done so, check out the Table Asset project. You should have completed
this at the end of the previous lab.
2. For each asset record, you will need to store access instructions and a flag indicating whether the
service person must call first before attempting to access the asset. Before you proceed with
creating new columns, inspect the existing columns to determine whether there are any that will
meet the users’ requirements.
a. Select Table :: S_ASSET | Columns.
b. Query for Physical Type = VarChar. You may need to scroll to the right to see this column.
Do any of the columns look like they are designed to store access instructions?
c. Re-query for Physical Type = Character. Do any of the columns look like they store a Call
First flag?
3. Add custom columns to S_ASSET.

a. Add a column record with following properties:
Name ACCESS_INSTR
Physical Type Varchar
Length 100
Note: The column name is automatically prefixed with X_.

b. Add a second new column record with the following properties:

Name CALL_FLG
Physical Type Character
Length 1
4. Make the physical changes to the local database by clicking the Apply/DDL button in the
OBLE. Use the following parameters:
Tables Current Row
Database user SIEBEL
Database user Password PPENGUIN
ODBC data source

SSD Local Db default instance
5. Verify that the database changes were successfully implemented. You can use the dbisqlc.exe
tool supplied by the vendor of the SQL Anywhere database to query the local database.
a. Navigate to D:\OUsea\Tools\BIN directory and double-click dbisqlc.exe to start the
interactive SQL product for the SQL Anywhere database.
b. Click the Database tab in the Connect to Adaptive Server Anywhere dialog box. Using the
Browse button, change the File Type to All Files and select the database file:
D:\OUsea\Tools\LOCAL\sse_data.dbf.
c. Click the Login tab and fill in following fields:
User ID PPENGUIN
Password PPENGUIN
d. Click OK to launch the SQL tool.
e. Enter the following in the Command pane:
Select NAME, X_ACCESS_INSTR, X_CALL_FLG from SIEBEL.S_ASSET
f. Click Execute. You should see column names displayed in the Data window. (You may
have to scroll to the right to see all three column names.)
g. Exit the SQL tool.
6. Compile the S_ASSET table rather than compiling the entire Table Asset project. (The Table
Asset project is very large and would take several minutes to compile.)

Solutions 33-1 Adding Extension Columns (Unguided)
Answers:
2.b. Query for Physical Type = VarChar. You may need to scroll to the right to see this
column. Do any of the columns look like they are designed to store access instructions?
No
2.c. Re-query for Physical Type = Character. Do any of the columns look like they store a Call
First flag?

No


Lab 33-1 Adding Extension Columns (Guided)
Goal To add custom extension columns to a table.
Instructions:

ABC field service reps often need detailed information regarding how to locate and gain access to
assets on a customer’s premises.
In this lab, you will provide for this by adding two new fields to the existing Asset Mgmt – Asset
business component, using custom extension columns in the base table. You will first verify that
there are no existing fields in the business component or columns in the base table that could satisfy
your requirements. You will then extend the base table by adding two extension columns.
1. If necessary, open Siebel Tools and log in as PPENGUIN/PPENGUIN to the Local database.
2. If you have not already done so, check out the Table Asset project. You should have completed
this at the end of the previous lab.
3. For each asset record, you will need to store access instructions and a flag indicating whether the
service person must call first before attempting to access the asset. Before you proceed with
creating new columns, inspect the existing columns to determine whether there are any that will
meet the users’ requirements.
a. Select Table :: S_ASSET | Columns.
b. Query for Physical Type = VarChar. You may need to scroll to the right to see this column.
Do any of the columns look like they are designed to store access instructions?
c. Re-query for Physical Type = Character. Do any of the columns look like they store a Call
First flag?
4. You will add custom columns to S_ASSET.

a. Select Table :: S_ASSET | Column.
b. Add a new record with following properties:
Name ACCESS_INSTR
Physical Type Varchar
Length 100
Note: The column name is automatically prefixed with X_.

c. Add a second new column record with the following properties:

Name CALL_FLG
Physical Type Character
Length 1
5. You will make the physical changes to the local database. This is accomplished by using the
Apply/DDL button in the OBLE.
a. Select Table :: S_ASSET.
b. Click Apply/DDL.
c. In the Choose Option window, verify that Apply is selected and click OK.
d. In the Warning dialog, click OK.

e. Set or verify the following parameters in the Apply Schema dialog box:
Tables Current Row
Database user Password PPENGUIN
ODBC data source SSD Local Db default instance
f. Click Apply to accept these values.
g. After a few minutes you should see a message box that says, “Changes successfully applied.”
Click OK.
6. Now you will verify that the database changes were successfully implemented. You can use the
dbisqlc.exe tool supplied by the vendor of the SQL Anywhere database to query the local
database.
a. Navigate to D:\OUsea\Tools\BIN directory and double-click dbisqlc.exe to start the
interactive SQL product for the SQL Anywhere database.
b. Click the Database tab in the Connect to Adaptive Server Anywhere dialog box. Using the
Browse button, change the File Type to All Files and select the database file:
D:\OUsea\Tools\LOCAL\sse_data.dbf.
c. Click the Login tab and fill in following fields:
User ID PPENGUIN
Password PPENGUIN
d. Click OK to launch the SQL tool.
e. Enter the following in the Command pane:
Select NAME, X_ACCESS_INSTR, X_CALL_FLG from SIEBEL.S_ASSET
f. Click Execute. You should see column names displayed in the Data window. (You may
have to scroll to the right to see all three column names.)
g. If you receive the error “Column not found,” follow these steps to troubleshoot. Otherwise,
skip to the next step.
i. Verify the typing of your query.
ii. Try another query to make sure you are connected to the local database. Enter:
Select count(*) from SIEBEL.S_ASSET

iii. Exit the dbisqlc application and again verify your connection parameters.
iv. Go back to Siebel Tools and verify the column names.
v. Try to apply again.
vi. Consult your instructor for assistance if the preceding steps were unsuccessful.
h. Select File > Exit to exit the SQL tool.
7. Compile the S_ASSET table rather than compiling the entire Table Asset project. (The Table
Asset project is very large and would take several minutes to compile.)

Solutions 33-1 Adding Extension Columns (Guided)
Answers:
3.b. Query for Physical Type = VarChar. You may need to scroll to the right to see this
column. Do any of the columns look like they are designed to store access instructions?
No.
3.c. Re-query for Physical Type = Character. Do any of the columns look like they store a Call
First flag?

No.

Lab 33-2 Adding New Fields (Unguided)
Goal To reference the custom extension columns and display them on a list applet.
Instructions:

In this lab you will add new fields to an existing business component to reference the custom
extension columns you just created. You will then add two fields to the ABC Asset Location List
Applet to display the new data.
1. Add two new single value fields to the Asset Mgmt - Asset business component :
Name Column Type
Access Instructions X_ACCESS_INSTR DTYPE_TEXT
Call First X_CALL_FLG DTYPE_BOOL
3. Add new controls to the Asset Mgmt - Asset Detail Applet to display these fields. To make
room for the new fields, delete the Comments text and label controls. The access instructions
text control should have the following properties:
Name Access Instructions
Field Access Instructions
HTML Type Field
The call first checkbox control should have the following properties:
Name Call First
Field Call First
HTML Icon Map CHECK
HTML Type CheckBox
Runtime TRUE
Do not forget to add labels for each control.
4. Test your work by compiling the Asset Management project and verifying that the two new
fields appear in the form applet from the Assets List view.


Lab 33-2 Adding New Fields (Guided)
Goal To reference the custom extension columns and display them on a list applet.
Instructions:

In this lab you will add new fields to an existing business component to reference the custom
extension columns you just created. You will then add two fields to the ABC Asset Location List
Applet to display the new data. Since you performed similar configuration in the prior labs, the steps
in this lab indicate what you need to accomplish but do not give the detailed steps. If you need some
assistance with these steps, review the detailed steps in the previous labs.
1. Add two new single value fields to the Asset Mgmt - Asset business component :
Name Column Type
Access Instructions X_ACCESS_INSTR DTYPE_TEXT
Call First X_CALL_FLG DTYPE_BOOL
3. You will add new controls to the Asset Mgmt – Asset Detail Applet to display these fields.
a. Select Applet :: Asset Mgmt – Asset Detail Applet.
c. In the Mode drop-down at the top left, select 1: Edit.
d. To make room for the new fields, select the Comments text and label controls, right-click,
and select Delete.
e. From the Web Controls Palette, next to the Web Layout Editor, drag and drop a Text control
onto the applet. A text control entitled (HTML Text) should appear.
f. Right-click the new text control and select View Properties Window if necessary. Set the
following properties:
Name Access Instructions
Field Access Instructions
HTML Type Field
g. From the Web Controls Palette, drag and drop a Label control next to the Access
Instructions text control.
h. In the Properties window, set the Caption – String Override property of the new label to
Access Instructions:. Set the Text Alignment property to Right.
i. From the Web Controls Palette, drag and drop a CheckBox control onto the applet.

j. In the Properties window, set the following properties:

Name Call First
Field Call First
HTML Icon Map CHECK
HTML Type CheckBox
Runtime TRUE
k. From the Web Controls toolbar, drag and drop a Label control (it has a picture of the letter
A) next to the Access Instructions text control.
l. Set the Caption – String Override property of the new Label to Call First and set the Text
Alignment property to Right.
m. Save your changes and close the Web Layout Editor.

4. You will test your work.
a. Compile the Asset Management project.
b. Start Siebel Call Center from Tools, if necessary.
d. Verify that the two new fields appear in the form applet.

Lab 33-3 Configuration Wrap-Up (Unguided)
Goal To transfer the modified configuration to the server.
Instructions:

You have now completed your configuration of the ABC application. In this lab you will check in all
of your checked out projects. Since you made changes to the S_ASSET table, you will need to apply
these changes to the server database before you can test the ABC application using the Siebel Web
Client. You must also copy any template files that were modified to the corresponding server
directories. You will also need to administer any new views that you created, as well as add the new
LOV values you created for the ABC Stocking Frequency Picklist.
1. Check in all of the projects that you updated and created, and release the locks. Resize the Tools
window to less than full screen, to allow you to do other work while the check-in runs.
2. Apply your schema changes to the server database by starting Siebel Tools and logging in as
PPENGUIN/PPENGUIN to the Server database and applying the changes. Use the following
parameters:
Tables Current Row
Database user Password SIEBEL
ODBC data source SSD default instance
3. Verify your schema changes using a database vendor tool.

Express.
b. Click Connect.
c. Click New Query.
d. Select siebeldb from the database drop-down list.
e. Enter the following query in the window: The column and table names in the query are case-
sensitive.
Select X_ACCESS_INSTR, X_CALL_FLG from S_ASSET
The column and table names in this query are case-sensitive.
f. Execute the query. The results appear in the bottom part of the window. If you receive the
error “invalid column name,” refer to the troubleshooting steps in first lab for this module.
g. Exit SQL Server Management Studio Express without saving changes.

4. Synchronize your local database with the server database using Siebel Remote.
a. Open the Siebel Developer Web Client and log in to Siebel Call Center as
PPENGUIN/PPENGUIN connecting to the Local database.
b. Select File > Synchronize Database.
c. In the dialog that appears, click the Synchronize button. This will synchronize the
administrative data you have created in your local database to the server.
Note: This Siebel Remote function synchronizes user and administrative data between the
local database and the server.
For the remainder of the lab, you will verify that the data you synchronized appears in the
server database. Note that this administrative data was not copied during check-in, but as part
of the Siebel Remote synchronization process.

5. Start the Siebel Call Center Web client and log in as PPENGUIN/PPENGUIN.
6. Verify the ABC Developer responsibility has been updated in the server database to include the
following views:
ABC Account Asset View
ABC Asset Supply Plan List View
List of Values View
7. Copy the file siebel.srf from D:\OUsea\Client\OBJECTS\ENU to

D:\OUsea\siebsrvr\OBJECTS\ENU\new_siebel.srf. You will not be able to overwrite siebel.srf
in the destination directory, as the Siebel Server has it open. This is intentional to prevent
accidentally overwriting the original .srf file. You will rename new_siebel.srf after stopping the
Siebel Server service. Normally you would do a full compile of the server repository, but since
you are a single developer you know that you implemented all of the changes so a copy is faster.
8. Stop the Siebel Server service, rename siebel.srf to originalsiebel.srf, and rename
new_siebel.srf to siebel.srf.
9. Verify that the LOV data you created in the picklist lab appears on the server..
a. Start the Siebel Call Center Web client and log in as PPENGUIN/ PPENGUIN.
b. Select Administration - Data > List of Values.
c. Query for Type = ABC_STOCK_FREQ.
d. Verify that the values you created for the ABC Stocking Frequency picklist appear– Twice
Weekly, Weekly, Biweekly, and Monthly (4 weeks).
e. Ensure these values appear in the List of Values by clearing the cache. In the List of Values
list, click Clear Cache.
10. Verify the picklist values in Siebel Call Center application.

a. Navigate to Assets > List > Supply Plans.
b. Add a new Asset record in the form and select a product.
c. Add a new supply record in the list and verify the values in the Stocking Frequency picklist:
Twice Weekly, Weekly, Biweekly, and Monthly (4 weeks).

11. Log out of the Call Center application where you are logged in as PPENGUIN and close the
browser.


Lab 33-3 Configuration Wrap-Up (Guided)
Goal To transfer the modified configuration to the server.
Instructions:

You have now completed your configuration of the ABC application. In this lab you will check in all
of your checked out projects. Since you made changes to the S_ASSET table, you will need to apply
these changes to the server database before you can test the ABC application using the Siebel Web
Client. You must also copy any template files that were modified to the corresponding server
directories. You will also need to administer any new views that you created, as well as add the new
LOV values you created for the ABC Stocking Frequency Picklist.
1. If necessary, start Siebel Tools and log in as PPENGUIN/PPENGUIN to the Local database.
2. You will check in all of the projects that you updated and created, and release the locks. You
may resize the window to less than full screen, to allow you to do other work while the check-in
runs.
a. Select Tools > Check In.
b. Select Locked/New objects.
c. Be sure that Maintain lock is not checked.
d. Click Check In. This will take about two minutes.
3. You will apply your schema changes to the server database.

a. Close the instance of Siebel Tools where you are connected to the Local database.
b. Start Siebel Tools and log in as PPENGUIN/PPENGUIN to the Server database.
c. Select Table :: S_ASSET | Column.
i. Query for all changed columns or query for columns that begin with X. Verify that
the two new columns you created in the first part of this lab appear:
X_ACCESS_INSTR and X_CALL_FLG.
d. Select Table :: S_ASSET.
i. Click Apply/DDL to apply the database schema changes to the server.
ii. Verify that Apply is selected and click OK.
iii. Set or verify the following parameters in the Apply Schema dialog box:
Tables Current Row
Database user Password SIEBEL
ODBC data source SSD default instance

iv. Click Apply. The message “Changes successfully applied” will appear. If it does not,
review the work you did in the earlier lab where you added an extension column.
v. Click OK.
e. Close the instance of Siebel Tools where you are connected to the Server database.
4. Now you will verify your schema changes using a database vendor tool.
Express.
b. Click Connect.
c. Click New Query.
d. Select siebeldb from the database drop-down list.
e. Enter the following query in the window: The column and table names in the query are case-
sensitive.

Select X_ACCESS_INSTR, X_CALL_FLG from S_ASSET
The column and table names in this query are case-sensitive.
f. Execute the query. The results appear in the bottom part of the window. If you receive the
error “invalid column name,” refer to the troubleshooting steps in first lab for this module.
g. Exit SQL Server Management Studio Express without saving changes.
5. You will synchronize your local database with the server database using Siebel Remote.
a. Open the Siebel Developer Client and log in to Call Center as PPENGUIN connecting to the
Local database.
b. Select File > Synchronize Database.
c. In the dialog that appears, click the Synchronize button. This will synchronize the
administrative data you have created in your local database to the server.
Note: This Siebel Remote function synchronizes user and administrative data between the
local database and the server.
For the remainder of the lab, you will verify that the data you synchronized appears in the
server database. Note that this administrative data was not copied during check-in, but as part
of the Siebel Remote synchronization process.
6. Start the Siebel Call Center Web client and log in as PPENGUIN/PPENGUIN.
7. Verify the ABC Developer responsibility has been updated in the server database.
a. Navigate to Administration - Application > Responsibilities.
b. Select the ABC Developer responsibility.
c. Verify that the views you created (ABC Account Asset View and ABC Asset Supply Plan
List View) appear in the Views list.
d. Verify the following views also appear in the Views list for the ABC Developer
responsibility:
List of Values View
e. Log out of the Siebel Call Center application and close the browser.

8. You will copy the repository file to the server directory.

a. Copy the file siebel.srf from D:\OUsea\Client\OBJECTS\ENU to
D:\OUsea\siebsrvr\OBJECTS\ENU\new_siebel.srf. You will not be able to overwrite
siebel.srf in the destination directory, as the Siebel Server has it open. You will rename
new_siebel.srf after stopping the Siebel Server service. Normally you would do a full
compile of the server repository, but since you are a single developer you know that you
implemented all of the changes so a copy is faster.
9. You will stop and start the Siebel Server service to ensure that the Call Center Object Manager
references the newly copied version of the .srf file.
a. Switch to the Services window.
b. Locate the Siebel Server [Siebel_OUsrvr] service, right-click the record, and select Stop.
Monitor the progress until the service has stopped.

c. In Windows Explorer, navigate to D:\OUsea\siebsrvr\OBJECTS\ENU.
d. Right-click the siebel.srf file and rename it originalsiebel.srf.
e. Right-click the new_siebel.srf file and rename it siebel.srf.
f. Start the Siebel Services. Right-click the Siebel Server [Siebel_OUsrvr] service and select
Start. Monitor the progress until the service has started. Once the window disappears, the
service status will be Started.
Note: Open the Windows Task Manager. The CPU will work at roughly 100% for
approximately 1 to 3 minutes after the status Started appears in Services. When the CPU
stops working at 100%, the Siebel Server service is completely started. Wait until the CPU
stops working at 100% before continuing with the lab.
10. You will verify that the LOV data you created in the picklist lab appears on the server. Recall
that the LOV data you created during configuration was only in your local database.
a. Start the Siebel Call Center (now ABC Call Center) Web client and log in as PPENGUIN/
PPENGUIN.
b. Select Administration – Data > List of Values.
c. Query for Type = ABC_STOCK_FREQ.
d. Verify that the values you created for the ABC Stocking Frequency picklist appear– Twice
Weekly, Weekly, Biweekly, and Monthly (4 weeks).
e. Ensure these values appear in the List of Values by clearing the cache. In the List of Values
list, click Clear Cache.
11. Next, you will verify the picklist (LOV) values in Siebel Call Center application.
a. From the Site Map select Assets > List > Supply Plans.
b. Add a new Asset record in the form and select a product.
c. Add a new supply record in the list and verify the LOV display values in the Stocking
Frequency picklist: Twice Weekly, Weekly, Biweekly, and Monthly (4 weeks).
12. Log out of the Call Center application where you are logged in as PPENGUIN and close the
browser.


Module 34: Siebel Business Services
Lab 34-1 Examining a Business Service (Unguided)
Goals To examine the methods and arguments of a business service using Siebel Tools
Time 5 - 10 minutes
Instructions:
In this lab you will import the String Manipulation Business Service as described on the slides in the

module. After importing the Business Service, you will examine its methods and arguments using
Siebel Tools, and in a subsequent lab you will test it using the Business Service Simulator.
1. Start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample database.
2. Import the StringManipulation.sif archive file from D:\Labs\Essentials.
3. Examine the String Manipulation business service methods.

a. Select Business Service :: StringManipulation | Business Service Method.
b. Which business service methods are defined for the StringManipulation business service?
c. For the Length business service method:

i. What are the input arguments?
ii. What are the output arguments?

d. For the Truncate business service method:

i. What are the arguments? Indicate if any are optional.
ii. What is specified using the Length argument?
4. Compile the imported StringManipulation business service into the client repository (.srf) file.

Solutions 34-1 Examining a Business Service

(Unguided)
Answers
3.b. Which business service methods are defined for the StringManipulation business service?
Concatenate, Length, and Truncate.
3.c.i. What are the input arguments?

InputString.

3.c.ii. What are the output arguments?
Length.
3.d.i. What are the arguments? Indicate if any are optional.

Direction (optional), InputString, Length, and OutputString.
3.d.ii. What is specified using the Length argument?

This argument specifies the number of characters to be returned.


Lab 34-1 Examining a Business Service (Guided)
Goals To examine the methods and arguments of a business service using Siebel Tools
Time 5 - 10 minutes
Instructions:
In this lab you will import the String Manipulation Business Service as described on the slides in the

module. After importing the Business Service, you will examine its methods and arguments using
Siebel Tools, and in a subsequent lab you will test it using the Business Service Simulator.
1. First you will import an archive (.sif) file that contains the String Manipulation Business Service.
a. Start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample database.
b. Select Business Service in the Object Explorer.
c. Select Tools > Import from Archive.
d. Navigate to D:\Labs\Essentials and select StringManipulation.sif.
e. Click Open.
f. Accept the default setting for conflict resolution, as the object definitions in the archive are
new ones.
g. Click Next.
h. Click Next.
i. Click Yes.
j. Click Finish when the import has completed.
2. You will now examine the String Manipulation business service methods.
a. Select Business Service :: StringManipulation | Business Service Method.

b. Which business service methods are defined for the StringManipulation business service?
3. Next you will examine the String Manipulation business service method arguments.
a. Select Business Service :: StringManipulation | Business Service Method :: Length | Business
Service Method Arg.
i. What are the input arguments?
ii. What are the output arguments?

b. Select Business Service :: StringManipulation | Business Service Method :: Truncate |
Business Service Method Arg.
i. What are the arguments? Indicate if any are optional.
ii. What is specified using the Length argument?
4. Finally you will compile the imported object definitions into the Client repository (.srf) file.
a. Log out of and close Siebel Call Center, if not already closed.
b. Select Business Service :: StringManipulation.
c. Right-click the StringManipulation Business Service and select Compile Selected Objects.
d. Ensure that you are compiling to D:\OUsea\Client\OBJECTS\ENU\siebel.srf.
e. Click Compile.

Solutions 34-1 Examining a Business Service (Guided)
Answers
2.b. Which business service methods are used with the StringManipulation Business Service?
Concatenate, Length, and Truncate.
3.a.i. What are the input arguments?

InputString.
3.a.ii. What are the output arguments?

Length.
3.b.i. What are the arguments? Indicate if any are optional.

Direction (optional), InputString, Length, and OutputString.
3.b.ii. What is specified using the Length argument?

This argument specifies the number of characters to be returned.


Lab 34-2 Testing a Business Service (Unguided)
Goals To test a business service using the business service simulator
Time 5 - 10 minutes
Instructions:
1. Start the Siebel Call Center Developer Web Client and log in as SADMIN/SADMIN connecting

to the Sample database.
2. Test the StringManipulation Business Service that was imported in the previous lab.
a. Navigate to Administration - Business Service > Simulator.
b. Create a new record in the top applet using the following parameters. Make sure that you
pick the service and names from the respective picklists.
Service Name StringManipulation
Method Name Length
3. Create the input arguments.

a. Create a new record in the Input Arguments list applet with a Test Case # of 1, a Property
Name of InputString, and a Value of Siebel CRM.
4. Run the Business Service Simulator.

a. Select StringManipulation in the Simulator list applet.
b. Click Run on One Input in the top applet.
5. Observe the output in the lowermost applet, Output Arguments. What are the Output Arguments
of the Business Service?
6. Test another method of the business service.

a. Create a new record in the Simulator applet to test the Concatenate method of the
StringManipulation business service.

b. Create two Input Arguments for this method: String1 with a value of Larry, and String2
with a value of Ellison, including a space before the word Ellison.
c. Test the Concatenate method by incrementing the Test Case # value and using the Run on
One Input button.
d. What is the output of the business service?

Solutions 34-2 Testing a Business Service (Unguided)
Answers
5. Observe the output in the lowermost applet, Output Arguments. What are the Output
Arguments of the Business Service?
A property set containing an empty Type and Value and a property name of Length with the
property value 10.
6.d. What is the output of the business service?

Larry Ellison.

Lab 34-2 Testing a Business Service (Guided)
Goals To test a business service using the business service simulator
Time 5 - 10 minutes
Instructions:

2. You will test the StringManipulation Business Service that was imported in the previous lab.
a. Navigate to Site Map > Administration - Business Service > Simulator.
b. Create a new record in the top applet using the following parameters. Make sure that you
pick the service and names from the respective picklists.
Service Name StringManipulation
Method Name Length
3. Next you will create the input arguments.

a. Click New in the Input Arguments list applet to create a new record.
b. Enter 1 in the Test Case # field.
c. Click the Select button in the Property Name field.
d. In the Property Set Properties window, click New, then create new input arguments using the
following parameters. Note that this property set contains a single name value pair
Property Name Property Value
InputString Siebel CRM
e. Click Save.
f. Click OK.
4. You will next run the Business Service Simulator.

a. Select StringManipulation in the Simulator list applet.
b. Click Run on One Input in the top applet.

5. Observe the output in the lowermost applet, Output Arguments.

a. What are the Output Arguments of the Business Service?
6. You will test another method of the business service.

a. Create a new record in the Simulator applet to test the Concatenate method of the
StringManipulation business service.
b. Create a new record in the Input Arguments list applet.
c. Click the Select button in the Property Name field.
d. In the Property Set Properties window, click New and create two new name value pairs using
the following parameters. Make sure to add a space character in front of Ellison in String2.

Property Name Value
String1 Larry
String2 Ellison
e. Test the Concatenate method. You can increment the Test Case # value and use the Run on
One Input button, or alternately delete the existing Input and Output Arguments before
testing the next method.
f. What is the output of the business service?

Solutions 34-2 Testing a Business Service (Guided)
Answers
5.a. What are the Output Arguments of the Business Service?
A property set containing an empty Type and Value and a property name of Length with the
property value 10.
6.d. What is the output of the business service?

Larry Ellison

Module 35: Building Siebel Workflow Processes
Lab 35-1 Building a Siebel Workflow Process (Unguided)
Goals To create a Siebel workflow process
Instructions:
In this lab you will build a workflow process that retrieves the first and last name of a contact, and

then creates an identifier for the contact using the first initial followed the full last name. Typically
you would store this identifier in a new field but for the purposes of this lab you will use an existing
field.
The workflow consists of a Siebel operation step to retrieve the contact’s first and last name, a
business service step to truncate the first name to a single character, another business service step to
concatenate the initial and the last name, and finally a second Siebel operation step to update the
contact record with the concatenated string. You will use the StringManipulation business service
you examined in the previous lab to perform the string operations.
You will add additional process properties to store the data manipulated by the workflow. This lab is
intended to provide practice in using process properties in workflows.
1. If necessary, start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample
database.
2. If necessary, lock the ABC WF project as you will be assigning new object definitions to that
project.
3. Create a new workflow process object definition using the parameters below and invoke the
workflow designer on it.
Process Name ABC Create Contact Identifier
Project ABC WF
Business Object Contact
4. Add workflow steps and connect them to specify the workflow process.
a. Add the following steps in order: Start, Siebel Operation, Business Service, Business Service,
Siebel Operation, and End.

b. Add connectors between each step, making sure that each connector is anchored at both ends.
The workflow should look like the following:

5. Assign meaningful names to each step as follows:
Step Name
Siebel Operation 0 Get First and Last Name
Business Service 0 Truncate First Name
Business Service 1 Concatenate Names
Siebel Operation 1 Store Identifier
End 0 End
6. Before you configure each of the steps, create additional process properties to store the data that
is processed in this workflow. Process properties are edited in the Multi-Value Properties
Window (MVPW) at the bottom of the editor.
a. Click on the workspace grid to display the process properties in the MVPW.
b. Add the following new process properties accepting the default values for In/Out and Type.
Name
FirstName
LastName
Initial
ContactCode
7. Configure each of the steps. You will first configure the Get First and Last Name step to query
the contact business component for the record whose Id field equals the value in the Object Id
process property. The operation then returns the first and last name of the contact.
a. Select the Get First and Last Name step and assign the following properties:
Business Component Contact
Operation Query

b. Create Search Spec Input Arguments as follows:

Expression Business Component Contact
Filter Business Component Contact
Type Expression
Search Specification "[Id]='" + [&Object Id] + "'"
This expression indicates to retrieve the record whose Id is equal to the value in the Object Id
process property. The syntax used in this search expression is very important. After the equal
sign there is a single quote followed by a double quote. At the end of the expression there is a
double quote followed by a single quote followed by a double quote. And a space is needed
before and after each of the plus signs.
You may copy and paste the expression from D:\Labs\Essentials\WF SearchSpec.txt.

c. Create Output Arguments to specify the fields to be returned and the process property to
which each field is to be assigned as follows:
Property Name Type Business Component Name Business Component Field
FirstName Business Component Contact First Name
LastName Business Component Contact Last Name
8. Configure the Truncate First Name step to return the first letter of the contact's first name (that
is, the first initial).
a. Select the Truncate First Name step and assign the following properties:
Business Service Name StringManipulation
Business Service Method Truncate
b. Add the following Input Arguments for the call to the Truncate method.
Input Argument Type Value Property Name
InputString Process Property FirstName
Length Literal 1
A length of 1 converts the first name into an initial.
c. Assign the output argument to a process property as follows:
Property Name Type Output Argument
Initial Output Argument OutputString
9. Configure the Concatenate Names step to combine the contact's initial and last name to form the
desired contact identifier. The identifier will be stored in the ContactCode process property.
a. Select the Concatenate Names step and assign the following properties:
Business Service Method Concatenate
b. Add input arguments for the call to the Concatenate method.
String1 Process Property Initial
String2 Process Property LastName

c. Add output arguments to a process property.

ContactCode Output Argument OutputString
10. Configure the Store Identifier step. You will assign the identifier you created to the Mail Stop
field for the purposes of this lab.
a. Select the Store Identifier step and assign the following properties:
Operation Update
You use the Update operation to store a value in a business component field.
b. Add the following Field Arguments to specify the field in the contact business component to

be updated.
Field Name Type Property Name
Mail Stop Process Property ContactCode
11. Validate the workflow to check for syntactic errors.

Lab 35-1 Building a Siebel Workflow Process (Guided)
Goals To create a Siebel workflow process
Instructions:
In this lab you will build a workflow process that retrieves the first and last name of a contact, and

then creates an identifier for the contact using the first initial followed the full last name. Typically
you would store this identifier in a new field but for the purposes of this lab you will use an existing
field.
The workflow consists of a Siebel operation step to retrieve the contact’s first and last name, a
business service step to truncate the first name to a single character, another business service step to
concatenate the initial and the last name, and finally a second Siebel operation step to update the
contact record with the concatenated string. You will use the StringManipulation business service
you examined in the previous lab to perform the string operations.
You will add additional process properties to store the data manipulated by the workflow. This lab is
intended to provide practice in using process properties in workflows.
1. If necessary, start Siebel Tools and log in as SADMIN/SADMIN to the Sample database
2. If necessary, lock the ABC WF project as you will be assigning new object definitions to that
project.
3. You will first create a workflow process object definition and invoke the workflow designer.
a. Select Workflow Process in the Object Explorer.
b. Create a new record with the following:
Process Name ABC Create Contact Identifier
Project ABC WF
Business Object Contact
c. Right-click ABC Create Contact Identifier and select Edit Workflow Process. Observe
that the workflow designer appears in a separate tab in the editing window.
4. You will next add workflow steps and connect them to specify the workflow process.
a. Drag a Start step onto the designer workspace by clicking the step in the palette and keeping
the button depressed until the step is positioned as desired.
b. Add the following steps in order: Siebel Operation, Business Service, Business Service,
Siebel Operation, and End.
c. Drag a connector and position it so that the left end is in the Start step.

d. Position the mouse over the white box at the right end of the connector and stretch the
connector until it touches the Siebel operation step. A red dot appears when the connector is
anchored to the step.
e. Add connectors to sequence the remaining steps, making sure that each connector is
anchored at both ends. The workflow should look like the following:

5. You will now assign meaningful names to each step.
a. Select the first Siebel Operation step. A selection box appears around the step.
b. Right-click and select View Properties Window.
c. Change the Name property to Get First and Last Name.
d. Repeat the above step for the remaining steps in the workflow, assigning the following
names:
Step Name
Business Service 0 Truncate First Name
Business Service 1 Concatenate Names
Siebel Operation 1 Store Identifier
End 0 End
6. Before you configure each of the steps, you will create additional process properties to store the
data that is processed in this workflow. Process properties are edited in the Multi-Value
Properties Window (MVPW) at the bottom of the editor.
a. Click on the workspace grid to display the process properties in the MVPW
b. Add the following new process properties accepting the default values for In/Out and Type.
Name
FirstName
LastName
Initial
ContactCode

7. You will next configure each of the steps. Note that some of the values are entered in the
standard properties window while others are entered in the MVPW. You will first configure the
Get First and Last Name step to query the Contact business component for the record whose Id
field equals the value in the Object Id process property. The operation then returns the first and

last name of the contact.
a. Select the Get First and Last Name step, right-click, and select View Properties Window
to display the standard properties window.
b. Assign the following properties
Operation Query
c. Under the Search Spec Input Arguments tab in the MVPW , create a new record with:
Expression Business Component Contact
Filter Business Component Contact
Type Expression
Search Specification "[Id]='" + [&Object Id] + "'"
This expression indicates to retrieve the record whose Id is equal to the value in the Object Id
process property. The syntax used in this search expression is very important. After the equal
sign there is a single quote followed by a double quote. At the end of the expression there is a
double quote followed by a single quote followed by a double quote. And a space is needed
before and after each of the plus signs.
You may copy and paste the expression from D:\Labs\Essentials\WF SearchSpec.txt.
d. Under the Output Arguments tab add the following two records to specify the fields to be
returned and the process property to which each field is to be assigned. Make sure you
populate the properties in the order shown. For instance you will not be able to select the
contact business component until you set Type to Business Component.
Property Name Type Business Component Name Business Component Field
FirstName Business Component Contact First Name
LastName Business Component Contact Last Name

8. You will next configure the Truncate First Name step to return the first letter of the contact's first
name (that is the first initial).
a. Select the Truncate First Name step and make sure the properties window is open.
b. Assign the following properties in the standard properties window. Make sure you first pick
the Business Service Name from the picklist. Then pick the method name from its picklist.
Business Service Method Truncate

You may need to make the properties window wider to be able to easily identify the two
properties listed above.
c. Under the Input Arguments tab in the MVPW add the following two records to configure the
input arguments for the call to the Truncate method. If the Display Name value for a record
in the picklist is blank, scroll to the right and look for the Name value.
InputString Process Property FirstName
Length Literal 1
A length of 1 converts the first name into an initial.
d. Under the Output Arguments tab add the following record to assign the output argument to a
process property.
Initial Output Argument OutputString
9. You will next configure the Concatenate Names step to combine the contact's initial and last
name to form the desired contact identifier. The identifier will be stored in the ContactCode
process property.
a. Select the Concatenate Names step and make sure the properties window is open.
b. Assign the following properties in the standard properties window. Make sure to pick each
property from its picklist.
Business Service Method Concatenate
c. Under the Input Arguments tab add the following two records to configure the input
arguments for the call to the Concatenate method.
String1 Process Property Initial
String2 Process Property LastName

d. Under the Output Arguments tab add the following record to assign the output argument to a
process property.
ContactCode Output Argument OutputString
10. You will finally configure the Store Identifier step. You will assign the identifier you created to
the Mail Stop field for the purposes of this lab.
a. Select the Store Identifier step and make sure the properties window is displayed.
Operation Update
You use the Update operation to store a value in a business component field.

c. Under the Field Input Arguments tab add the following record to specify the field in the
contact business component to be updated.
Field Name Type Property Name
Mail Stop Process Property ContactCode
11. Finally you will validate the workflow for syntactic errors. On the lab for the next module you
will simulate the workflow to verify that it executes as designed.
a. Right-click on the designer background and select Validate.
b. Click Yes if asked to save changes.
c. Click Start.
d. Examine any messages that may appear and edit your configuration accordingly.
e. Click Cancel to close the validation window.


Lab 35-2 Branching in a Siebel Workflow Process

(Unguided)
Goals To create a Siebel workflow process that includes conditional logic
Instructions:

In this lab you will build a workflow process that sets the priority of a service request to ASAP
whenever the severity is set to Critical. You will configure a decision step to implement this logic.
In addition you will design the workflow process so that the decision logic is applied only to
workflows whose status is not Closed.
This lab is intended to provide practice in incorporating conditional logic in workflow processes.
1. Create a new workflow process object definition using the parameters below and invoke the
workflow designer on it.
Process Name ABC Update SR Priority
Project ABC WF
Business Object Service Request
2. Add workflow steps and connections to specify the workflow process as shown below.
3. Rename the following steps.

Decision Point step Assess Priority
Siebel Operation step Set Priority to ASAP

4. Configure the decision step by specifying conditions on one or more of the outgoing connectors.
In this case you will set a condition on Connector 1(in the above diagram) that checks if the
Severity of the service request is Critical. You will set Connector 3 to be the default connector
(that is if the severity is other than Critical).
a. Modify the properties of the connector between the decision step and the Siebel Operation
step as follows:
Name Critical
Type Condition
b. Edit the conditions of the Critical connector as follows:
Compare to Business Component
Operation One Must Match (Ignore Case)

Object Service Request
Field Severity
Values 1-Critical
c. Select the connector between the decision step and the end step and set the properties as
follows:
Name Not Critical
Type Default
5. Add logic that first checks if the status of the workflow is closed. If the service request is closed,
the workflow should proceed directly to the end step. Another decision step (between the start
and Assess Severity step) could be used. However, you will configure this logic using branches
on the Start step itself.
a. Set the properties of the connector between the Start step and End step as follows:
Name Closed
Type Condition
b. Edit the conditions of the connector as follows:
Field Status
Values Closed
c. Set the properties of the connector between the Start step and the Decision step as follows:
Name Not Closed
Type Default

6. Configure the Siebel Operation step to assign a priority of ASAP to the service request.
a. Select the Set Priority to ASAP step and assign the following properties:
Business Component Service Request
Operation Update
b. Add field input arguments to the step as follows:
Field Name Type Value
Priority Literal 1-ASAP
7. Save all of your configuration changes.
8. Validate the workflow for syntactic errors.


Lab 35-2 Branching in a Siebel Workflow Process

(Guided)
Goals To create a Siebel workflow process that includes conditional logic
Instructions:

In this lab you will build a workflow process that sets the priority of a service request to ASAP
whenever the severity is set to Critical. You will configure a decision step to implement this logic.
In addition you will design the workflow process so that the decision logic is applied only to
workflows whose status is not Closed.
This lab is intended to provide practice in incorporating conditional logic in workflow processes.
1. You will first create a workflow process object definition and invoke the workflow designer.
a. In Siebel Tools, select Workflow Process in the Object Explorer.
b. Create a new record with the following:
Process Name ABC Update SR Priority
Project ABC WF
Business Object Service Request
c. Invoke the workflow designer by right-clicking the record and selecting Edit Workflow
Process.
2. You will next add workflow steps and connect them to specify the workflow process.
a. Add the following steps in order: Start, Decision Point, Siebel Operation, and End.
b. Add connectors as follows. Make sure each connector is anchored at both ends.
From step To Step
Start Decision
Decision Siebel Operation
Siebel Operation End
Decision End
Start End

c. Arrange the steps in the designer as shown below. Observe that the connectors bend
automatically at right angles eliminating the need to manually edit the connector itself Also
observe that a label appears on some of the connectors; you will edit the label when you
create conditions for these connectors.

3. Rename the following steps.
Hint: to rename a step, select the step and right-click to display the properties window. Edit the
name property.
Decision Point step Assess Priority
Siebel Operation step Set Priority to ASAP
4. Next you will configure the decision step by specifying conditions on one or more of the
outgoing connectors. In this case you will set a condition on Connector 1(in the above diagram)
that checks if the Severity of the service request is Critical. You will set Connector 3 to be the
default connector (that is if the severity is other than Critical).
a. Select the connector between the decision step and the Siebel Operation step.
Name Critical
Type Condition
Note: The name property specifies the label that appears in the workflow designer.
d. Right-click the Critical connector and select Edit Conditions.
e. Enter the following information in the Compose a Condition dialog box:
Field Severity
Setting these values specifies that the severity field is to be checked at run time
f. Click the New button next to the Values field to create a new record.

g. In the Pick Value box, select 1-Critical, and click OK.

h. Click Add to add this condition, and then click OK.
i. Select the connector between the decision step and the end step.
j. Right-click and select View Properties Window.
k. Set the following properties:
Name Not Critical
Type Default

5. You will next add logic that first checks if the status of the workflow is closed. If the service
request is closed, the workflow should proceed directly to the end step. Another decision step (in
between the start and Assess Severity step) can be used. However you will configure this logic
using the branches on the start step itself.
a. Click the connector between the Start step and the End step.
Name Closed
Type Condition
d. Right-click this same connector and select Edit Conditions.
e. Enter the following information in the Edit Conditions dialog box: Be sure to select the
Service Request object from the picklist rather than typing it in

Field Status
f. Click the New button next to the Values field to create a new record.
g. In the Pick Value box, select Closed, and click OK.
h. Click Add to add this condition, and then click OK.
i. Click the connector between the Start step and the Decision step
j. Right-click and select View Properties Window.
k. Set the following properties::
Name Not Closed
Type Default
6. You will next configure the Siebel Operation step to assign a priority of ASAP to the service
request.
a. Select the Set Priority to ASAP step and make sure the properties window is displayed.
Operation Update
c. Under the Field Input Arguments tab add the following record to specify the field to be
updated.
Field Name Type Value
Priority Literal 1-ASAP
In this case a literal value (1-ASAP) is assigned to the business component field.
7. Save all of your configuration changes.
8. Validate the workflow for syntactic errors.

Module 36: Testing and Deploying Siebel Workflow Processes
Lab 36-1 Testing a Siebel Workflow Process (Unguided)
Goals To simulate a workflow process to determine that the workflow executes as designed
Instructions:

database.
2. Set or confirm the following debug options in Siebel Tools:

Executable E:\OUSea\Client\BIN\siebel.exe
CFG File E:\OUSea\Client\BIN\ENU\uagent.cfg
Browser E:\Program Files\Internet Explorer\IEXPLORER
Working Directory E:\OUSea\Client\BIN
Arguments /h
Login information:
User name SADMIN
Password SADMIN
Data source Sample
3. If necessary, expose the Simulation toolbar.
4. In order to simulate the ABC Create Contact Identifier workflow you created in the previous lab,
you need to first create a test contact record in the Siebel application.
a. Start the Siebel Call Center Developer Web client and log in as SADMIN/SADMIN to the
Sample database.
b. Create a new Contact record with
Last Name Pearson
First Name Lester
c. Verify that the contact’s Mail Stop field is blank. This is the field into which the workflow
process inserts the contact identifier.
d. Record the row number of the contact you created. ____________
e. Log out of the Siebel Call Center. There must be no running instances of the Siebel client for
the simulator to start.

5. Invoke the Workflow Simulator to test the workflow process. The simulator can be invoked from
within Siebel Tools from either the workflow process list in the object list editor or directly from
the workflow designer.
a. Display the workflow designer with the ABC Create Contact Identifier workflow process.
b. Add the Row Id of the test record you created to the Default String field of the Object Id
process property and explicitly save your change.
c. Right-click in the workflow designer and select Simulate. Observe that a new tabbed window
appears in the editor with the first step of the workflow outlined. Also note that the first
button in the Simulator toolbar is highlighted.
d. Click the (green) Start Simulation button in the Simulate toolbar. Observe that an instance
of the Siebel client starts, and that it takes several seconds for the client to display a view
titled Workflow Simulator.

e. Once that view appears return to Siebel Tools, and wait until the initiation of the simulation
has completed. You should see the second step in the workflow process highlighted.
f. Launch the Watch Window to monitor the changes to the data as the workflow moves
through each step.
g. Click the Simulate Next button to execute the steps of the workflow. Observe the FirstName
and LastName process properties in the Watch window display the fields from the contact
record you created.
h. Click OK and then close the Simulator window.
6. In Siebel Call Center, verify that the workflow stored the contact identifier for Lester Pearson in
the Mail Stop field.
7. In Siebel Tools, delete the row number for the context record you created and explicitly save this
change.
8. Deploy the workflow to the client for further testing by selecting it and clicking the Publish
button. Verify that the workflow process was deployed by checking that the status is updated to
Completed.
9. Activate the workflow process in the client.

a. In Siebel Call Center, navigate to the Workflow Deployment view.
b. Select ABC Create Contact Identifier in the Repository Workflow Processes list applet and
click Activate.
c. Verify that the workflow appears in the Active Workflow Processes tab in the lower applet.
The workflow is now ready to be tested in the client.

Lab 36-1 Testing a Siebel Workflow Process (Guided)
Goals To simulate a workflow process to determine that the workflow executes as designed
Instructions:

database.
2. You will first make sure that the Debug options are set to allow the Workflow Simulator to run
correctly.
a. In Siebel Tools, select View > Options.
b. Click the Debug tab.
c. Make sure the following run-time startup information is entered.
Executable D:\OUSea\Client\BIN\siebel.exe
CFG File D:\OUSea\Client\BIN\ENU\uagent.cfg
Working Directory D:\OUSea\Client\BIN
Arguments /h
d. Make sure the following login information is entered.
User name SADMIN
Password SADMIN
Data source Sample
e. Click OK.
3. If necessary, expose the Simulation toolbar by selecting View > Toolbars > Simulate.
4. In order to simulate the ABC Create Contact Identifier workflow you created in the previous lab,
you will need to first create a test contact record in the Siebel application.
a. If necessary, start the Siebel Call Center Developer Web client and log in as
b. Navigate to the My Contacts View.
c. Create a new record with
Last Name Pearson
First Name Lester
d. Drill down on the new record and click the More Info tab.

e. Verify that the Mail Stop field is blank. This is the field into which the workflow process
inserts the contact identifier.
f. Right-click the record and select About Record. Record the row number. ____________
g. Click OK.
h. Log out of the Siebel Call Center. There must be no running instances of the Siebel client for
the simulator to start.
5. You will now invoke the Workflow Simulator to test the workflow process. The simulator can be
invoked from either the workflow process list in the object list editor or directly from the
workflow designer.
a. Return to Siebel Tools and display the workflow designer with the ABC Create Contact
Identifier workflow process.
b. Click the Process Properties tab on the MVPW.

c. Select the Object Id process property.
d. Locate the Default String property and enter the row number for the contact record you just
created. You may have to scroll to the right to display the Default String property.
e. Save the new data by clicking the Save button in the toolbar. Configuration data in the
workflow designer must be saved explicitly.
f. Right-click in the workflow designer and select Simulate. Observe that a new tabbed
window appears in the editor with the first step of the workflow outlined. Also note that the
first button in the Simulator toolbar is highlighted.
g. Click the (green) Start Simulation button in the Simulate toolbar. Observe that an instance
of the Siebel client starts, and that it takes several seconds for the client to display a view
titled Workflow Simulator.
h. Once that view appears return to Siebel Tools, and wait until the initiation of the simulation
has completed. You should see the second step in the workflow process highlighted.

i. Right-click in the simulator window and select Watch Window to open the watch window.
If necessary expand PS:Property Set to display the properties in the watch window.

j. Click the Simulate Next button to execute the step that is highlighted.
Observe the FirstName and LastName process properties in the Watch window display the
fields from the contact record you created. If necessary expand Workflow Process Data to
display the properties in the watch window. If this step errors out, you should stop the
simulation and verify that the search specification was entered correctly.
k. Click the Simulate Next button until the End step is highlighted. After each step inspect the
process properties to verify that the process properties are populated as desired.
l. Click the Simulate Next button once more to complete the simulation.
m. Click OK and then close the Simulator window.

6. You will now verify that the workflow did store the contact identifier.
a. Return to the Siebel Call Center application.
b. Navigate to the Lester Pearson contact record you created. A direct way to do so is to
navigate to the Contacts Home screen and click the link under recent records.
c. Navigate to the More Info view.
d. Verify that the Mail Stop field now displays the contact identifier created by the workflow.
7. Once you have completed simulation of the workflow process, you should delete the row number
for the context record you created.
a. In Siebel Tools, return to the workflow designer.
b. In the Process Properties tab in the MVPW, clear the Default String property for the Object

Id process property.
c. Make sure to explicitly save these changes.
8. The work flow is now ready to be deployed to the client for further testing.
a. Click the Workflow Process List tab in the editor.
b. Select the ABC Create Contact Identifier record.
c. Click the Publish button in the WF/Task Editor Toolbar

d. Verify that the workflow process was deployed by checking that the status is updated to
Completed.
9. You will finally activate the workflow process in the client.

a. In Siebel Call Center, navigate to Administration - Business Process > Workflow
Deployment.
b. Select ABC Create Contact Identifier in the Repository Workflow Processes list applet and
click Activate.
c. Verify that the workflow appears in the Active Workflow Processes tab in the lower applet.
The workflow is now ready to be tested in the client.

Lab 36-2 Testing Branching in a Siebel Workflow

Process (Unguided)
Goals To simulate a workflow process that involves branching
Instructions:

In this lab you will simulate the ABC Update SR Priority workflow process you created in a
previous lab. The workflow includes conditional processing and you will run the simulator several
times to verify that the workflow executes the conditional processing correctly.
1. In Siebel Call Center, create a test service request record with the following properties:
Summary Test ABC Update SR Priority Workflow
Priority 3 - Medium
Severity 1 - Critical
Record the row number of the service request record. _______________
2. Add the row number as the default value for the Object Id process property for the ABC Update
SR Priority workflow process.
3. Simulate the workflow to verify that it executes the desired conditional logic; that is, it sets the
priority to 1 - ASAP.
4. Confirm that the priority has been properly set by checking in Siebel Call Center.
5. Modify the service request as follows, run the workflow simulation, and observe how the
workflow behaves with the data.
Priority 3 - Medium
Severity 4 - Low
6. Close the service request, run the workflow simulation, and observe how the workflow behaves.
7. Once you have completed your simulations, delete the row number from the workflow.
8. The workflow is now ready to be deployed to the client for further testing. Use the
Publish/Activate button that publishes the workflow to the client and activates it there as well.
a. Verify that the workflow process was deployed by checking that the status is updated to
Completed.
b. Verify that the workflow process is also activated in Siebel Call Center.


Lab 36-2 Testing Branching in a Siebel Workflow

Process (Guided)
Goals To simulate a workflow process that involves branching
Instructions:

In this lab you will simulate the ABC Update SR Priority workflow process you created in a
previous lab. The workflow includes conditional processing and you will run the simulator several
times to verify that the workflow executes the conditional processing correctly.
The instructions in this lab are not as detailed as in the previous lab. Feel free to refer to those
instructions when you might need additional details.
1. You will first create a test service request record.

a. In Siebel Call Center, navigate to Service Requests > Service Request List
b. Create a new record with:
Summary Test ABC Update SR Priority Workflow
c. Drill down on the new record.
d. Click the Show More button to display the Priority and Severity fields.
e. Verify that the Priority is 3 - Medium.
f. Set the Severity to 1 - Critical.
g. Save the new record.
h. Right-click the record, select About Record, and record the row number. _______________
i. Log out of Siebel Call Center. There must be no running instances of the Siebel client for the
simulator to start.
2. You will now add the row number as the default value for the Object Id process property.
a. Return to Siebel Tools and display the workflow designer with the ABC Update SR Priority
workflow process.
b. Click the Process Properties tab on the MVPW.
c. Select the Object Id process property.
d. Locate the Default String property and enter the row number for the contact record you just
created. You may have to scroll to the right to display the Default String property.
e. Save the new data.
3. You will next simulate the workflow to verify that it executes the desired conditional logic.
a. Start the simulation following the steps you used in the first part of this lab.
b. Use the Simulate Next button to manually advance the simulation one step at a time.

c. Verify that the workflow executes the Assign Priority step.

d. Complete the simulation, and leave the simulation window open.
e. Return to Siebel Call Center and navigate back to the service request record you created.
f. Verify that the priority was changed to 1-ASAP.
4. You will next modify the service request and observe how the workflow behaves with the data.
a. Modify the service request fields as follows:
Priority 3 - Medium
Severity 4 - Low
b. Save the record.
c. Log out of Siebel Call Center.
d. In Siebel Tools run the simulation until it completes. What occurred this time?

e. Verify in Siebel Call Center that the priority of the workflow was not changed.
5. You will close the service request and observe how the workflow behaves.
a. Modify the service request fields as follows:
Status Closed
b. Save the record.
c. Log out of and close Siebel Call Center.
d. In Siebel Tools run the simulation until it completes. What occurred this time?
e. Restart Siebel Call Center and verify that the priority of the workflow was not changed.
6. Once you have completed your simulations, you should delete the row number for the service
request record you created.
a. Close the Simulation Window.
b. Return to the workflow designer.
c. In the Process Properties tab in the MVPW, clear the Default String property for the Object
Id process property.
d. Make sure to save these changes.

7. The workflow is now ready to be deployed to the client for further testing. This time you will use
the Publish/Activate button that publishes the workflow to the client and activates it there as
well.
a. Click the Workflow Process List tab in the editor.
b. Select the ABC Update SR Priority record.
c. Click the Publish/Activate button in the WF/Task Editor Toolbar

d. Verify that the workflow process was deployed by checking that the status is updated to
Completed.
e. Verify that the workflow process is also activated
i. In Siebel Call Center, navigate to Administration - Business Process > Workflow
Deployment.

ii. Verify that the ABC Update SR Priority workflow appears in both the Repository
Workflow Processes upper applet and the Active Workflow Processes tab in the
lower applet.

Solutions 36-2 Testing Branching in a Siebel Workflow

Process (Guided)
Answers
4.d In Siebel Tools run the simulation until it completes. What occurred this time?
The simulation started by advancing to the Assess Priority step and then proceeded directly
to the End Step. This occurred because the priority was not equal to 1-Critical
5.d In Siebel Tools run the simulation until it completes. What occurred this time?

The simulation stated by advancing directly to the End step, and completing immediately.
This occurred because of the condition on the start step that first checks if the service
request is closed.

Module 37: Executing Workflow Processes
Lab 37-1 Executing a Workflow Process using a

Run-time Event (Unguided)
Goals To invoke a workflow process using a run-time event
Instructions:

In a previous lab you created the ABC Update SR Priority workflow process and published/activated
it to the client. You will incorporate this workflow process as-is into a workflow policy in a
subsequent lab. In this lab you will make a copy of this workflow process and modify it slightly to
enable it to be invoked by a run-time event.
database.
2. Make a copy of the ABC Update SR Priority workflow process and name it ABC Update SR
Priority RTE. RTE stands for run-time event.
Note: You may need to revise the original workflow before copying it to ensure the copy is
editable.
3. Modify the workflow process to allow it to be invoked by a runtime event.

a. Start the workflow designer for the ABC Update SR Priority RTE workflow process and
modify the Not Closed connector leading from the Start step with the following properties:
Type Condition
Event Object Type BusComp
Event Object Service Request
Event WriteRecord
These properties specify that the workflow will be invoked whenever a Service Request
record is written to the database.
b. Save your changes.
4. Deploy and activate the workflow and verify that the status changes to Completed.
5. In Siebel Call Center, navigate to the Workflow Deployment View and verify that your new
workflow was successfully deployed and activated.
6. Refresh the cache of run-time events by navigating to the Runtime Events view and selecting
Reload Runtime Events.

7. Test that the workflow is invoked by a run-time event.

a. Create and save a new service request with the following properties:
Summary ABC WF RTE test
Priority 3 - Medium
b. Verify that the Priority has been updated to 1 - ASAP.
c. Reset the priority to 3 - Medium, set the severity to something other than 1 - Critical, and
save the record. Confirm that the priority remains unchanged.
8. Once you are satisfied that the workflow behaves as desired, deactivate it so that the priority of a
service request will no longer be adjusted by this workflow. You do this to prevent this workflow

from potentially interfering with following labs.
a. Navigate to the Administration - Business Processes > Workflow Deployment View.
b. Select ABC Update SR Priority RTE in the Active Workflows Processes list and select
Menu > Deactivate Process in the lower list applet.
c. Verify that the Deployment State changes to Inactive.
d. Refresh the cache of run-time events.

Lab 37-1 Executing a Workflow Process using a

Run-time Event (Guided)
Goals To invoke a workflow process using a run-time event
Time 10 -15 minutes
Instructions:

In a previous lab you created the ABC Update SR Priority workflow process and published/activated
it to the client. You will incorporate this workflow process as-is into a workflow policy in a
subsequent lab. In this lab you will make a copy of this workflow process and modify it slightly to
enable it to be invoked by a run-time event.
database.
2. You will first make a copy of the ABC Update SR Priority workflow process.
a. Select Workflow Process :: ABC Update SR Priority.
b. Select Edit > Copy Record.
c. Name the process ABC Update SR Priority RTE. RTE stands for run-time event.
d. Save the modified record.
Note: You may need to revise the original workflow before copying it to ensure the copy is
editable.
3. You will next modify the workflow process to allow it to be invoked by a runtime event.
a. Start the workflow designer for the ABC Update SR Priority RTE workflow process.
b. Select the Not Closed connector leading from the Start step.
c. Right-click and select View Properties Window.

d. Change the following properties (in the order listed):

Type Condition
Event Object Type BusComp
Event Object Service Request
Event WriteRecord

These properties specify that the workflow will be invoked whenever a Service Request
record is written to the database.
e. Save your changes.
4. You are now ready to deploy and activate the workflow

a. Return to the Workflow Process list in the Editor.
b. Publish/Activate the ABC Update SR Priority RTE workflow process.
c. Verify that the status changes to Completed.
5. In Siebel Call Center, navigate to the Administration - Business Processes > Workflow
Deployment View and verify that your new workflow was successfully deployed and activated.
6. You will finally need to refresh the cache of run-time events.

a. Navigate to the Administration - Runtime Events > Events view.
b. Click the Applet menu button and select Reload Runtime Events.
7. You are now ready to test that the workflow is invoked by a run-time event.
a. Navigate to the My Service Requests view.
b. Create a new service request with
Summary ABC WF RTE test
Priority 3 – Medium
c. Right-click and select Save Record.
d. Verify that the Priority has been updated to 1 - ASAP. This indicates that the workflow was
invoked.
e. Reset the priority to 3 - Medium and set the severity to something other than 1-Critical
f. Save the record and verify that Priority remains unchanged.

8. Once you are satisfied that the workflow behaves as desired, you will deactivate it so that the
priority of a service request will no longer be adjusted by this workflow. You will do this to
prevent this workflow from potentially interfering with following labs.
a. Navigate to navigate to the Administration - Business Processes > Workflow Deployment
View.
b. Select ABC Update SR Priority RTE in the Active Workflows Processes list.
c. Select Menu > Deactivate Process (in the lower list applet).
d. Verify that the Deployment State changes to Inactive.
e. Navigate to the Administration - Runtime Events > Events view to update the run-time event
cache
f. Click the Applet menu button and select Reload Runtime Events to refresh the cache of
run-time events.


Lab 37-2 Executing a Workflow Process from a Control

(Unguided)
Goals To invoke a workflow process from a menu item in an applet
Instructions:

In this lab you will add a menu item to the applet menu in the Contact Form applet and then create
an Applet User property to invoke the ABC Create Contact Identifier workflow process you built
and tested in previous labs.
1. This lab involves configuring two object types (Command and Applet User Prop) that are not
normally exposed in the Object Explorer. Expose the Command and Applet User Prop object
types.
2. Lock the Contact (SSE) project. This is the project that contains the Contact Form applet you
will edit.
3. Create a new Command object using the properties below. This command references a named
method (ABCContact) that will invoke the workflow.
Name ABC Update Contact
Method ABCContact
Target Server
4. Compile the ABC Update Contact command object.
5. Create an Applet Method Menu Item on the Contact Form Applet using the properties below.
This menu item allows the user to invoke the command using the applet menu.
Command ABC Update Contact
Menu text – String Override Update Contact Identifier
Position 99

6. Create an Applet User Property on the Contact Form Applet using the properties below. This
user property associates the ABCContact named method with the ABC Update Contact Identifier
workflow process you created and tested.
Name Named Method: ABCContact
Value 'INVOKESVC'. "Workflow Process Manager','RunProcess','"ProcessName'",
'"ABC Create Contact Identifier"','"RowId"','[Id]'
Syntax is important here; all parameters have single quotes surrounding them. In addition
Process Name , RowId, and the name of the workflow have additional double quotes inside the
single quotes. The easiest way to create this expression is to copy the Named Method: New
Order User Prop and edit the value using the expression builder.
The parameters that follow INVOKSVC specify to invoke the Workflow Process Manager using
the RunProcess method (that is execute a workflow) and to pass in (Process Name) ABC Create

Contact Identifier workflow and (RowId) the Id field of the selected business component.
7. Compile the Contact Form Applet object.
8. Test the configuration you performed.

a. Start the Siebel Call Center Developer Web client and log in as SADMIN/SADMIN
b. Query for the Robert Abel contact record.
c. Verify that the Mail Stop field is blank.
d. Click the applet menu button in the upper applet and verify that a new menu item named
Update Contact Identifier appears at the bottom of the menu.
e. Select Update Contact Identifier in the applet menu, and verify that the contact identifier is
generated and displayed in the Mail Stop field.

Lab 37-2 Executing a Workflow Process from a Control

(Guided)
Goals To invoke a workflow process from a menu item in an applet
Instructions:

In this lab you will add a menu item to the applet menu in the Contact Form applet and then create
an Applet User Prop property to invoke the ABC Create Contact Identifier workflow process you
built and tested in previous labs.
1. This lab involves configuring several object types (Command and Applet User Prop) that are not
normally exposed in the Object Explorer. You will expose these object types.
a. In Siebel Tools, select View > Options and click the Object Explorer tab.
b. Select Command.
c. Expand Applet and select Applet User Prop.
d. Click OK.
2. Lock the Contact (SSE) project. This is the project that contains the Contact Form applet you
will edit.
3. You will first create a Command object that references a named method (ABCContact) that will
invoke the workflow.
a. Select Command in the Object Explorer.
b. Create a new record with
Name ABC Update Contact
Method ABCContact
Target Server
c. Compile the new command object into D:\OUsea\Client\OBJECTS\ENU\siebel.srf .
Remember to close any active instances of the Siebel client.
4. Next you will create an Applet Method Menu Item that allows the user to invoke the command.
a. Select Applet :: Contact Form Applet | Applet Method Menu Item
Command ABC Update Contact
Menu text – String Override Update Contact Identifier
Position 99

5. Finally you will create an Applet User Property that associates ABCContact named method with
the ABC Update Contact Identifier workflow process you created and tested.
a. Select Applet :: Contact Form Applet | Applet User Prop
Name Named Method: ABCContact
Value 'INVOKESVC', 'Workflow Process Manager','RunProcess','"ProcessName'",
'"ABC Create Contact Identifier"','"RowId"','[Id]'
Syntax is important here; all parameters have single quotes surrounding them. In addition
Process Name , RowId, and the name of the workflow have additional double quotes inside
the single quotes. The easiest way to create this expression is to copy the Named Method:
New Order User Prop and edit the value using the expression builder.

The parameters that follow INVOKSVC specify to invoke the Workflow Process Manager
using the RunProcess method (that is execute a workflow) and to pass in (Process Name)
ABC Create Contact Identifier workflow and (RowId) the Id field of the selected business
component.
c. Click OK to close the expression builder.

d. Click OK to dismiss the warning dialog.
6. Compile the Contact Form Applet object into D:\OUsea\Client\OBJECTS\ENU\siebel.srf .
7. You are now ready to test the configuration you performed.

a. Start the Siebel Call Center Developer client and log in as SADMIN/SADMIN connecting to
the Sample database.
b. Navigate to the My Contacts view.
c. Query for the Robert Abel record and drill down on it.
d. Click the More Info tab and verify that the Mail Stop field is blank. This is the field that will
display the contact identifier when it is created by the workflow.

e. Click the applet menu button in the upper applet and verify that a new menu item named
Update Contact Identifier appears at the bottom of the menu.

f. Select Update Contact Identifier in the applet menu, and verify that the contact identifier is
generated and displayed in the Mail Stop field.


Module 38: Using Workflow Policies
Lab 38-1 Creating a Workflow Policy (Unguided)
Goals To create a workflow policy that invokes the ABC Update SR Priority workflow process
when certain conditions are met
Time 5 - 10 minutes
Instructions:
In this lab you will be creating and running a workflow policy in the Workflow Process Manager

server component. Typically you would develop and test workflows using a local database and
check them in to the server repository. Since you developed the workflow using the sample database,
you cannot migrate the workflow by checking it in. Rather, you export the workflow from the
sample repository and import it into the server repository. Since the focus of this lab is creating a
workflow policy, the server database has already been populated with a copy of the ABC Update SR
Priority workflow you developed in the previous labs.
1. Activate the workflow on the server.

b. Navigate to the Workflow Deployment view.
c. Select the ABC Update SR Priority workflow process and activate it.
2. Create a workflow group under Administration - Business Process > Policy Groups with the
properties below. A workflow group is a collection of workflow policies that will monitored
together.
Name ABC Daily Workflows
Comments Policies that invoke workflow
processes that run once daily
3. Create a workflow policy action under Administration - Business Process > Actions with the
properties below. Workflow policy actions specify the processing to be performed when a policy
is satisfied.
Name Run ABC Update SR Priority
Program Run Workflow Process
Workflow Object Service Request
4. Create arguments for the Run ABC Update SR Priority action with the following values. Note
that the value you are entering is the name of the workflow to be executed when the policy is
satisfied.
Argument ProcessName
Value ABC Update SR Priority

5. Create a workflow policy to specify the conditions under which the policy will be executed.
a. Create a new policy under Administration - Business Process > Policies with the following
values:
Name SR Policy
Policy Group ABC Daily Workflows
Activation <yesterday’s date>
Duration 0
Units Minute(s)
You left Duration and Units at the default value of zero minutes for testing purposes. Once
you have verified that the policy works, you would then change these values so that the

duration specifies the actual length of time required by your business policies.
b. Create the following condition for the policy:
Condition Field Service Request Status
Operation =
Value Pending
c. Reference the action you created earlier.
Action Run ABC Update SR Priority
Sequence 1
d. Verify that the arguments you specified previously appear.

Lab 38-1 Creating a Workflow Policy (Guided)
Goals To create a workflow policy that invokes the ABC Update SR Priority workflow process
when certain conditions are met
Time 5 - 10 minutes
Instructions:
In this lab you will be creating and running a workflow policy in the Workflow Process manager

server component. Typically you would develop and test workflows using a local database and
check them into the server repository. Since you developed the workflow using the sample database,
you cannot migrate the workflow by checking it in. Rather you export the workflow from the sample
repository and import it into the server repository. Since the focus of this lab is creating a workflow
policy, the server database has already been populated with a copy of the ABC Update SR Priority
workflow you developed in the previous labs.
1. You will first activate the workflow on the server.

a. Start the Siebel Call Center Web client and login as SADMIN/SADMIN.
b. Navigate to the Administration - Business Process > Workflow Deployment view.
c. Select the ABC Update SR Priority workflow process and activate it.
2. You will now create a workflow group. A workflow group is a collection of workflow policies
that are monitored together.
a. Navigate to Administration - Business Process > Policy Groups, by clicking the Policy
Groups link in the link bar.
b. In the Policy Groups list, create a new record with the following values:
Name ABC Daily Workflows
Comments Policies that invoke workflow processes that run once daily
3. You will next create a workflow policy action to specify the processing to be performed when a
policy is satisfied.
a. Navigate to Administration - Business Process > Actions, by clicking the Actions link in the
link bar.
b. In the Actions list, create a new record with the following values:
Name Run ABC Update SR Priority
Program Run Workflow Process

c. In the Arguments list, create a new record with the following values. Note that the value you
are entering is the name of the workflow to be executed when the policy is satisfied.
Argument ProcessName
Value ABC Update SR Priority
4. You will finally create a workflow policy to specify the conditions under which the action will
be executed.
a. Navigate to Administration - Business Process > Policies by clicking the Policies link.
b. In the Policies List list, create a new record with the following values:
Name SR Policy
Policy Group

ABC Daily Workflows
Activation <yesterday’s date>
Duration 0
Units Minute(s)
You left Duration and Units at the default value of zero minutes for testing purposes. Once
you have verified that the policy works, you would then change these values so that the
duration specifies the actual length of time required by your business policies.
c. In the Conditions list, create a new record with the following values:
Condition Field Service Request Status
Operation =
Value Pending
d. In the Actions list, refer to the action you created earlier: You will need to scroll down to find
the Actions list applet
Action Run ABC Update SR Priority
Sequence 1
e. Scroll down to the bottom applet and verify that the arguments you specified previously
appear.

Lab 38-2 Administering Server Components (Unguided)
Goals To enable the use of a workflow policy by generating triggers and starting a workflow
monitor agent task
Instructions:
Now that workflow policies are defined, triggers need to be set in the Siebel database to support the

policies. You will then start the Workflow Monitor Agent server component so that the activated
policies are monitored and enforced.
Depending on the current state of the server components, you might need to do additional server
management.
1. Check to make sure that the Workflow Management component group (which includes the
Generate Triggers component) is enabled on the server. If it is not enabled on the server, enable
it and restart the server.
2. Check to make sure that the background components are properly synchronized by verifying that
the Generate Triggers component is listed as a synchronized component.
3. Create and submit a Generate Triggers job with the following parameters and confirm that the
job completes successfully:
Name Value
EXEC True
Privileged User SIEBEL
Privileged User Password SIEBEL
4. Customize a copy of the Workflow Monitor Agent component definition to monitor the ABC
Daily Workflows policy group.
a. Locate the Workflow Monitor Agent component definition in the Administration - Server
Configuration > Enterprises > Component Definitions view.
b. Copy the Workflow Monitor Agent component definition and set the following properties:
Component ABC Workflow Monitor – Daily Group
Alias ABCWorkMonDaily
Component Type Workflow Monitor Agent
Component Group Workflow Management
Run Mode Background

c. Set the following component parameters:

Group Name ABC Daily Workflows
Password SADMIN
User Name SADMIN
d. Set the following advanced component parameters.
Auto Restart TRUE
Default Tasks 1
Siebel File System D:\siebfile
Sleep Time 30
These parameters will cause the new copy of Workflow Monitor Agent to start automatically

when the Siebel Server is online, and check the ABC Daily Workflows Group every 30
seconds. In the future, you may change the Sleep Time to a period greater than 30 seconds,
but for the purposes of testing this lab, you will need it to run more frequently.
5. Activate the Component Definition and then synchronize the components.
6. Restart the Siebel Server service to make the ABC Workflow Monitor - Daily Group
component available on the Siebel Server.
7. Verify that the ABC Workflow Monitor component is now running on your Siebel server
b. Verify that ABC Workflow Monitor - Daily Group component appears as a task and is
running.

Lab 38-2 Administering Server Components (Guided)
Goals To enable the use of a workflow policy by generating triggers and starting a workflow
monitor agent task
Instructions:
Now that workflow policies are defined, triggers need to be set in the Siebel database to support the

policies. You will then start the Workflow Monitor Agent server component so that the activated
policies are monitored and enforced.
Depending on the current state of the server components, you might need to do additional server
management.
1. You will first check to make sure that the Workflow Management component group (which
includes the Generate Triggers component) is enabled. If it is not enabled on the server you will
then enable it.
a. If necessary, start the Siebel Call Center Web client and log in as SADMIN/SADMIN.
b. Navigate to Administration - Server Configuration > Enterprises > Component Groups.
c. Query for Workflow Management in the Component Groups list applet.
d. Examine the record in the Component Groups Assignments list applet.
i. If the Assigned? And Enable on Server? fields are both checked the Workflow
Management Component group is enabled and you will proceed to step 2.
ii. If they are not both checked, click Assign and /or Enable.
iii. Log out of the Siebel Call Center Web client.
iv. Stop the Siebel Server service using the Services window.
v. Start the Siebel Server service. Remember to wait until the Siebel Server service has
started up completely
vi. Start the Siebel Call Center Web client and log in as SADMIN/SADMIN.
2. You will next check to make sure that the batch components are properly synchronized.
a. Navigate to Administration - Server Configuration > Enterprises > Synchronize.
b. Query for the Generate Triggers component. Typically either no components are listed or
all of the enabled batch components are listed.
c. If the Generate Triggers component is not listed, then click Synchronize to update the batch
component parameters in the gateway server. This may take several minutes to complete.
3. You will create a Generate Triggers component request in the Siebel Call Center Web client
c. In the Component/Job field, select Generate Triggers from the picklist.

d. In the Job Parameters list at the bottom of the screen, add three new parameters.:
Name Value
EXEC True
4. You will run the Generate Triggers job.

a. In the Jobs list, click the Submit Job button.
b. Refresh the view by clicking Query then clicking Go to monitor the job status until the job
has completed successfully.
5. You now ready to customize a copy of the Workflow Monitor Agent component definition that

you will configure to monitor the ABC Daily Workflows policy group.
a. Navigate to Administration - Server Configuration > Enterprises > Component Definitions.
b. In the Component Definitions list, query for Component = Workflow Monitor Agent.
c. Right-click the Workflow Monitor Agent component definition and select Copy Record.
d. Enter or verify the following properties:
Component ABC Workflow Monitor – Daily Group
Alias ABCWorkMonDaily
Component Type Workflow Monitor Agent
Component Group Workflow Management
Run Mode Background
e. Save the record by clicking the Menu button and selecting Save Record.
f. Refresh the list by querying for Component = ABC* and verify that the new component
definition has the value Creating.
6. You will now customize the component definition by specifying parameters.

a. In the Component Parameters list, click the Parameter column heading to sort the parameters
alphabetically.
b. If necessary, click the Reset button.
c. Verify that the following parameters have the corresponding values. Update the parameter if
necessary.
Group Name ABC Daily Workflows
Password SADMIN
User Name SADMIN
d. Click the Advanced button and specify the following parameters in the list.
Auto Restart TRUE
Default Tasks 1
Siebel File System D:\siebfile
Sleep Time 30

These parameters will cause the new copy of Workflow Monitor Agent to start automatically
when the Siebel Server is online, and check the ABC Daily Workflows Group every 30 seconds.
In the future, you may change the Sleep Time to a period greater than 30 seconds, but for the
purposes of testing this lab, you will need it to run more frequently.
7. You will next activate the Component Definition.

a. In the Component Definitions list, click the Activate button.
b. Verify that the State has changed from Creating to Active.
c. Click the Synchronize button. This should run for several seconds as the component
definition is synchronized to the Gateway servers to make it available for use.
8. The ABC Workflow Monitor - Daily Group component is not yet available on your Siebel
Server. You will need to restart the Siebel Server service to make it available.

a. Log out of the Siebel Call Center Web client.
b. Stop the Siebel Server service using the Services window.
c. Start the Siebel Server service. Remember to wait until the Siebel Server service has started
up completely
d. Close the Services window
9. You will finally verify that the ABC Workflow Monitor component is now running on your
Siebel server
b. Navigate to Administration - Server Management > Components.
c. Verify that ABC Workflow Monitor - Daily Group component appears in the Components
list applet.
d. Verify that the state of the ABC Workflow Monitor - Daily Group task is running.


Lab 38-3 Invoking a Workflow Process via Workflow

Policy (Unguided)
Goals To invoke the workflow process via a workflow policy.
Time 10 minutes

Instructions:
You are now ready to test the workflow policy you created.
1. Create a service request with the properties below to meet the conditions of the workflow policy
created in the previous lab.
Summary Testing WF Policy
Status Pending
Severity 1-Critical
Priority 3-Medium
2. Verify that the workflow process was invoked by checking to see that the service request Priority
has been elevated to 1-ASAP.
Note: Since the Workflow Monitor Agent runs every 30 seconds, wait at least one minute to
view the results. Remember to refresh the view by executing an empty query.
3. Under Administration - Server Management > Tasks, verify that the ABC Workflow Monitor -
Daily Group task is still running. In addition, observe that there is a just-completed Workflow
Process Manager task.
4. Once you have verified that the workflow policy behaves as desired, shut down the ABC
Workflow Monitor - Daily Group component. You do this to reduce the load on the server.
5. Use the Administration - Server Configuration > Servers > Components view to set the ABC
Workflow Monitor - Daily Group component to Manual Start. Shutting it down only stopped
it for this instance of the server; setting it to Manual Start ensures it will not start up again if the
server is restarted. This will also avoid conflicts with later labs.


Lab 38-3 Invoking a Workflow Process via Workflow

Policy (Guided)
Goals To invoke the workflow process via a workflow policy.
Time 10 minutes

Instructions:
You are now ready to test the workflow policy you created.
1. You will create a service request to meet the conditions of the workflow policy created in the
previous lab.
a. Navigate to Service Requests > Service Request List > My Service Requests.
b. Create a new service request.
c. Drill down on the new record.
d. Click the Show More button in the form applet to display the severity and priority fields.
e. Enter the following values:
Summary Testing WF Policy
Status Pending
Severity 1-Critical
Priority 3-Medium
f. Save the record.
g. Verify that the workflow process was invoked by checking to see that the service request
Priority has been elevated to 1-ASAP.
Note: Since the Workflow Monitor Agent runs every 30 seconds, wait at least one minute to
view the results. Remember to refresh the view by executing a null query.

2. (Optional) Navigate to Administration - Server management > Tasks, and observe that the ABC
Workflow Monitor - Daily Group task is still running. In addition observe that there is a just-
completed Workflow Process Manager task.

3. Once you have verified that the workflow policy behaves as desired, you will shutdown the ABC
Workflow Monitor - Daily Group component. You will do this to reduce the load on the server.
a. Navigate to Administration - Server management > Components
b. Select ABC Workflow Monitor – Daily Group
c. Click Shutdown. This changes the state to Shutting Down and State Icon changes to yellow.
d. Wait several seconds and refresh the display by executing a blank query.
e. Verify that the state has changed to Shutdown.
4. You will next set the component to start manually so that it will no longer start every time you
have to restart the Siebel server.
a. Navigate to Administration - Server Configuration > Servers > Components
b. In the Components list, select ABC Workflow Monitor – Daily Group.
c. Click Manual Start.
5. Finally log out of the Siebel Web client and close the browser.

Module 39: Siebel Task UI
Lab 39-1 Executing a UI Task (Unguided)
Goals To execute a UI task
Time 5 - 10 minutes
Instructions:
In this lab you will invoke and execute a UI task that was created to demonstrate several key

concepts about a UI task. You will use this task to create a new contact and add several notes. The
task is designed to collect contact name information in the first view and phone details in the second
view. The task contains a view in which you choose to either add a note or review and submit the
information you entered. The task flow has been constructed to loop back after a note has been
added and to ask you to choose again.
1. The task you will examine in this lab is not part of the as-delivered Call Center application.
Rather the task was configured separately and compiled into a modified SRF file that was used in
the initial labs in this course. When you started the configuration section of the course you
performed a complete compile which produced a SRF file that does not contain the configured
task. Replace the SRF file that you created in the configuration section with a backup copy of the
original SRF file that includes the task customizations.
a. If necessary, log out of the Siebel Call Center Developer Web client.
b. If necessary, close Siebel Tools.
c. In Windows Explorer, navigate to D:\OUsea\client\OBJECTS\ENU.
d. Rename siebel.srf to siebel_config.srf
e. Copy siebel_back.srf and name the copy siebel.srf.
2. Start the Siebel Call Center Developer Web client and log in as SADMIN/SADMIN to the
Sample database.
3. Display the task pane and verify that it lists a UI task with the name Create a New Contact and
Add Notes.

4. Invoke the UI Task.

a. Click Create a New Contact and Add Notes and create a new record with the following
values:
Last Name Tiger
First Name Scott
Mr/Ms Mr
Work Phone # 925-694-1111
Work Fax # 925-694-1991
Mobile Phone # 510-325-1199
Home Phone # 510-564-9119

Email scott.tiger@oracle.com
Feel free to enter other values for these fields. Using the exact values above is not critical in
this lab.
b. Add two new notes.
c. Verify that the final view shows all the data you entered and then submit the data.
5. Verify that the new contact record is now accessible in the regular Siebel application, and that
the notes for that contact now appear in the standard public notes view.
6. Create a new contact, but practice pausing and resuming the task.
a. Start the task.
b. Enter the new contact name information and click Next.
c. Enter some phone details for the contact and click Pause to suspend execution of the task.
d. Click OK to dismiss the dialog box.
e. Navigate to Accounts > Accounts List and select the 3Com record. This simulates an
interruption that you might encounter while working on a task.
f. Navigate to the Inbox to resume the UI task by clicking the Go to Inbox link at the bottom of
the task pane.
g. Locate the paused UI task and drill down on it.
h. Verify that the task resumes where you paused it and that any data you entered into that view
is still there.
i. Complete the task and confirm that all the new data you entered is now displayed in a
standard Siebel view, just as if you had completed the task without pausing.

Lab 39-1 Executing a Task (Guided)
Goals To execute a task
Instructions:
In this lab you will invoke and execute a task that was created to demonstrate several key concepts
about the task UI framework. You will use this task to create a new contact and add several notes.

The task is designed to collect contact name information in the first view and phone details in the
second view. The task contains a view in which you choose to either add a note or review and submit
the information you entered. The task flow has been constructed to loop back after a note has been
added and to ask you to choose again.
1. The task you will examine in this lab is not part of the as-delivered Call Center application.
Rather the task was configured separately and compiled into a modified SRF file that was used in
the initial labs in this course. When you started the configuration section of the course you
performed a complete compile which produced a SRF file that does not contain the configured
task. You will now replace the SRF file that you created in the configuration section with a
backup copy of the original SRF file that includes the task customizations.
a. If necessary, log out of the Siebel Call Center Developer Web client.
b. If necessary, close Siebel Tools.
c. In Windows Explorer, navigate to D:\OUsea\client\OBJECTS\ENU.
d. Rename siebel.srf to siebel_config.srf
e. Copy siebel_back.srf and name it siebel.srf.

2. You will first display the task pane in order to invoke the task.
Sample database.
b. Click the Task button in the global toolbar to display the task pane.
c. Verify that the Task Pane is displayed and that it lists a task with the name Create a New
Contact and Add Notes.

3. You will now invoke the task.
a. In the task pane, click Create a New Contact and Add Notes.
b. Verify that a task view replaces the normal Siebel view.
c. Create a new record with the following:
Last Name Tiger
First Name Scott
Mr/Ms Mr.
Feel free to enter other values for these fields. Using the exact values above is not critical in
this lab.
d. Click Next.
e. Enter the following phone details:
Work Phone # 925-694-1111
Work Fax # 925-694-1991
Mobile Phone # 510-325-1199
Home Phone # 510-564-9119
Email scott.tiger@oracle.com
f. Click Next.
g. Select Add a new note, and click the Next button in the playbar applet in the lower right
corner of the task view.
h. Enter a short note in the Description field

i. Click Next.
j. Select Add a new note, and click Next.
k. Enter a second note in the Description field.
l. Click Next
m. Select Review and submit, and click Next.
n. Verify that the final view shows all the data you entered.
o. Click the Submit button in the playbar applet at the bottom of the view. Observe that the task
view disappears and the previous Siebel view reappears.
4. You will next verify that the new contact record is now accessible in the regular Siebel
application.
a. Navigate to Contacts > Contacts List > My Contacts.

b. Query for the contact you created above (Scott Tiger or whomever you created).
c. Drill down on the record to navigate to the contact detail view.
d. Navigate to the Contact Notes Public Notes view, and verify that all the data you entered is
now displayed in a standard Siebel view.
5. Finally you will create a new contact. However you will pause and resume the task.
a. In the task pane, click Create a New Contact and Add Notes.
b. Enter the new contact name information and click Next.
c. Enter some phone details for the contact and click Pause to suspend execution of the task.
d. Click OK to dismiss the dialog box. Observe that the task view disappears and is replaced by
the previous Siebel view.
e. Navigate to Accounts > Accounts List and select the 3Com record. This simulates an
interruption that you might encounter while working on a task.
6. You will now resume the task and verify that you did not lose any data you entered.
a. Click the Go to Inbox link at the bottom of the task pane to navigate to the Inbox to resume
the task
b. Locate the paused task (with the most recent timestamp) and drill down on it.
c. Verify that the task resumes where you paused it and that any data you entered into that view
is still there.
d. Complete the task, and click the Submit button in the playbar applet.
e. Navigate to the My Contacts view.
f. Query for the new contact you entered.
g. Navigate to the Contact Notes Public Notes View and verify that all the new data you entered
is now displayed in a standard Siebel view, just as if you had completed the task without
pausing.


Module 40: Task UI - Creating a Task
Lab 40-1 Creating a UI Task (Unguided)
Goals To create a simple UI task that includes two task views
Instructions:
In this lab you will create a new task that guides a user through creating a new account and

associating an opportunity with that account. In a real implementation, you would first design and
create several custom applets to enter the account fields of interest. Each applet would appear
sequentially in the task.
However since you have already learned how to configure applets, you will instead reuse existing
applets in this lab, and concentrate on configuring the task-related objects.
This basic task uses two sequential views in which the user first enters account information and then
enters opportunity information.
1. Before you start any configuration you will expose several object types that are not displayed by
default in the object explorer.
a. If necessary, start Siebel Tools and log in as SADMIN/SADMIN to the Sample database.
b. Expose the Task Group and View Task Group objects.
2. Create the task by configuring the Task object in Siebel Tools.

a. Create and lock a new project called ABC UI Tasks.
b. Create a new task using the Task wizard and using the following values:
Project ABC UI Tasks
Task Name ABC Create New Account
Display Name Create New Account and Opportunity
Leave the default transient business component blank as this UI task does not require one.
c. Click Finish. This creates a new Task object and invokes the Task Designer. Observe that a
Start and End step have been automatically created and displayed in the designer.

3. You will now use the Task Designer to build the task.
a. Add the following steps: Siebel Operation, Task View, Siebel Operation, and Task View.
b. Connect each step as depicted in the diagram.

4. Configure the first Siebel Operation step to create a new Account record, and the second Siebel
Operation step to create a new child Opportunity record. Configure the Siebel Operation steps as
follows:
a. Select the Siebel Operation 0 step and set the following properties:
Business Component Account
Defer Write Record True
Name Create Account
Operation Insert
Note: You need to set the Defer Write Record property to True since you will be supplying
required fields in the following task view. Otherwise an error indicating missing required
fields will be generated at the completion of the Siebel Operation step
b. Set the properties for the Siebel Operation 1 step as follows:
Name Add Opportunity
Operation Insert

5. Create the Task View object that will be used to display the applet in which account information
is entered.
a. Create a new Task View using the Task View wizard and enter the following:
View Name ABC Account Entry Task View
Display Name Enter Account Details
Upgrade Behavior Admin
Web Template View Basic
Selected Applets Account Entry Applet

Note: Upgrade behavior is used to determine upgrade behavior for Siebel-provided objects. It
is not used for custom objects.
b. Select No as you will not be adding a Task Applet, and click Next.
c. Select the Task Playbar Applet – Bottom and assign it as the bottom playbar applet.
d. Review the properties and click Finish. This invokes the View Web Template Layout editor.
e. Verify that the Account Entry applet appears on the template. If you can not see the applet in
the editor, right-click on the editor surface and select Preview.
6. Repeat the previous step to create a second Task View object for entering the details of the
associated opportunity.
a. Use the following properties for the task view.
View Name ABC Opportunity Entry Task View
Display Name Enter Opportunity Details
b. Use the same view Web layout template (View Basic) but assign the Opportunity Form
Applet to the template.
7. Bind the new task views you created to the Task View steps in the Task Flow.
a. Return to the task Designer and select the task View step that follows the Create Account
step.
b. Right-click and select Bind Task View.
c. Select ABC Account Entry Task View, and click OK.
d. Make sure the task view is still selected and right-click and select View Properties Window.

e. Enter the following properties:

Disable Previous True
Display Name –String Override Enter Account Details
Forward Button Type Next
Since this is the first view in the UI task, you must disable the Previous button since there is
no previous view.
f. Select the task View step that follows the Add Opportunity step in the task designer and bind
the ABC Opportunity Entry Task View to the View step.
g. Enter the following properties:
Disable Previous False
Display Name –String Override Enter Opportunity Details

Forward Button Type Submit
8. The designers have decided that this task should contain two chapters. Create the chapters and
then assign steps to each chapter.
a. Display the multi-valued properties window (MVPW) for the task.
b. Click the Chapters tab and create two new chapter records in the MVPW.
Name Display Name –String Override Sequence
Chapter 1 Enter New Account 10
Chapter 2 Add the Opportunity 20
c. Right-click on the designer background and select Show Chapters.
d. Assign the following three steps to Chapter 1:
Start
Create Account
ABC Account Entry Task View

e. Assign the remaining three steps to Chapter 2. Verify that each step has the color of its
chapter.

.
9. Still in Siebel Tools, create a Task Group to which you will add this task. A task group
represents one or more tasks that are displayed as a group in the task pane.
a. Create a new Task Group record with the following values:
Name ABC Account Tasks
Display Name –String Override Account Tasks
b. Create a new Task Group Item record with the following values:
Action Invoked ABC Create New Account
Type Task
Sequence 1
10. Associate the new task group with a view. This determines when the task group is visible in the
client. In this case you will assign it to the Task Pane View in order for it to be globally
accessible. Add a View Task Group record with:
Task Group ABC Account Tasks
Sequence 2
11. Compile the ABC UI Tasks and Task UI Framework (SWE) projects into the client .srf file.
12. Publish the task into the client (runtime) database.

a. Validate the Task ABC Create New Account. If any errors are displayed, make sure that
you fix them before you continue.
b. Publish the Task ABC Create New Account. Observe that the Status property changes to
Completed.

13. Administer the task in the client, with the first step being to activate the task.
Sample database.
b. In the Administration - Business Process > Task Deployment view, activate the ABC Create
New Account task.
14. Register the task and assign it to a responsibility so that users will be able to invoke it.
a. Under Administration - Application > Tasks, register the ABC Create New Account task
and add the Siebel Administrator responsibility.
b. Make sure the Allow Delete and Allow Transfer flags are checked to permit the user to either
delete or transfer a paused task in the user's inbox.
c. Click Clear Cache to update the cached responsibilities.
d. Log out of Siebel Call Center and then log back in as SADMIN/SADMIN.

15. Verify that the task was successfully deployed to the client and works as designed.
a. In Siebel Call Center, click the Tasks button to display the task pane. Verify that the task you
deployed is displayed.
b. Click the Create New Account and Opportunity link.
c. Verify that the first task view appears and that the task pane now displays both chapters. Also
observe that the Previous button is disabled.
d. Enter an account name and site.

e. Click the Next button.
f. Verify that the account name appears in the opportunity applet.

g. Enter an opportunity name and click Submit.
h. Locate the account you created, drill down on it and navigate to the account opportunity
view. Verify that the new account and opportunity now appear in the regular Siebel UI.

Lab 40-1 Creating a Task (Guided)
Goals To create a simple task that includes two task views
Instructions:
In this lab you will create a new task that guides a user through creating a new account and
associating an opportunity with the account. In a real implementation, you would first design and

create several custom applets to enter the account fields of interest. Each applet would appear
sequentially in the task.
However since you have already learned how to configure applets, you will instead reuse existing
applets in this lab, and concentrate on configuring the task related objects.
This basic task uses two sequential views in which the user first enters account information and then
enters opportunity information.
1. Before you start any configuration you will expose several object types that are not displayed by
default in the object explorer.
b. Select View > Options.
c. Click the Object Explorer tab.
d. Deselect Task and then select it to display all of its child object types.
e. Select Task Group.
f. Expand View and select View Task Group.
g. Click OK to close the window.
2. You will start creating the task by configuring the Task object in Siebel Tools.
a. Create and lock a new project called ABC UI Tasks.
b. Select File > New Object.
c. Click the Task tab and select Task.
d. Click OK to invoke the New Task Wizard.
e. Enter the following:
Task Name ABC Create New Account
Display Name Create New Account and Opportunity
Leave the default transient business component blank as this task does not require one.
f. Click Finish. This creates a new Task object and invokes the Task Designer. Observe that a
Start and End step have been automatically created and displayed in the designer.

3. You will now use the Task Designer to build the task.
a. Add the following steps in order to the designer: Siebel Operation, Task View, Siebel
Operation, Task View.
b. Move the end of the connector from the End step to the first Siebel Operation step.
c. Drag additional connectors to the designer workspace and sequence the remaining steps,
making sure that each connector is anchored at both ends. The task should look like the
following:

4. The first Siebel Operation step will be configured to create a new Account record while the
second Siebel Operation step will be configured to create a new child Opportunity record. You
will configure the first Siebel Operation step as follows:
a. Select the step that immediately follows the Start step.
c. Enter the following properties:
Business Component Account
Name Create Account
Operation Insert
You need to set the Defer Write Record property to True since you will be supplying
required fields in the following task view. Otherwise an error indicating missing required
fields will be generated at the completion of the Siebel Operation step.

d. Verify the properties look like:

e. Set the properties for the second Siebel Operation step as follows. Make sure that you select
the step before you right-click to view the Properties Window.
Name Add Opportunity
Operation Insert
f. Save the configuration you created by clicking the Save button in the toolbar.
5. You will next create the Task View object that will be used to display the applet in which
account information is entered.
b. Click the Task tab and select Task View.
c. Click OK to invoke the New View Wizard.
d. Enter the following:
View Name ABC Account Entry Task View
Title Enter Account Details
Note: Upgrade behavior is used to determine upgrade behavior for Siebel-provided objects. It
is not used for custom objects.
e. Click Next.
f. Select View Basic for the Web layout template and click Next.
g. Select the Account Entry applet and move it to the selected applets column. Normally you
would select an applet that you customized, but in this lab you will use an existing applet
from the repository.
h. Click Next.

i. Select No as you will not be adding a Task Applet, and click Next.
j. Select the Task Playbar Applet – Bottom and assign it as the bottom playbar applet.

k. Click Next.
l. Review the properties and click Finish. This invokes the View Web Template Layout editor.
m. Verify that the Account Entry applet appears on the template. If you can not see the applet in
the editor, right-click on the editor surface and select Preview.
6. Repeat the previous step to create a second Task View object for entering the details of the
associated opportunity.
a. Use the following properties for the task view.
View Name ABC Opportunity Entry Task View
Title Enter Opportunity Details
b. Use the same view Web layout template (View Basic) but assign the Opportunity Form
Applet to the template.
7. You will now bind the new task views you created to the Task View steps in the Task Flow.
a. Return to the Task Designer.
b. Select the Task View step that follows the Create Account step.

c. Right-click and select Bind Task View.

d. Select ABC Account Entry Task View, and click OK.
e. Enter the following properties. If necessary right-click the task view and select View
Properties Window.
Disable Previous True
Display Name –String Override Enter Account Details
Since this is the first view in the task, you must disable the Previous button as there is no
previous view.
f. Return to the task Designer and select the task View step that follows the Add Opportunity
step.

g. Right-click and select Bind Task View.
h. Select ABC Opportunity Entry Task View and click OK..
i. Enter the following properties. If necessary right-click the task view and select View
Properties Window.
Display Name –String Override Enter Opportunity Details
j. Save the configuration changes by clicking the Save button in the toolbar.
8. The designers have decided that this task should contain two chapters. You will create the
chapters and then assign steps to each chapter.
a. Click on the designer background to display the multi-valued properties window (MVPW)
for the task.
Chapter 1 Enter New Account 10
Chapter 2 Add the Opportunity 20
d. Select the following three steps by shift-clicking:
Start
Create Account
ABC Account Entry Task View
e. Right-click and select Assign Chapter.
f. Select Chapter 1 and click OK.

g. Select the three remaining steps and assign them to Chapter 2. Verify that each step has the
color of its chapter.

.
h. Save your configuration changes.
9. You will next create a Task Group to which you will add this task. A task group represents one
or more tasks that are displayed as a group in the task pane.
a. In the editor window click the View List tab to display the object list editor.
b. Select Task Group in the Object Explorer.
c. Create a new Task Group record with:
Name ABC Account Tasks
Display Name –String Override Account Tasks
d. Select Task Group :: ABC Account Tasks | Task Group Item.
e. Create a new record with:
Action Invoked ABC Create New Account
Type Task
Sequence 1
10. You will now associate the new task group with a view. This determines when the task group is
visible in the client. In this case you will assign it to the Task Pane View in order that it be
globally accessible.
a. Select View :: Task Pane View | View Task Group.
b. If necessary, lock the project by selecting Tools > Lock Project.
c. Add a new record with
Task Group ABC Account Tasks
Sequence 2

11. You are now ready to compile the new configured objects in to the client SRF file.
a. Make sure that Siebel Call Center is closed.
b. Select Tools > Compile Projects.
c. Make sure that only the ABC UI Tasks and Task UI Framework (SWE) projects are selected.
d. Compile these projects into D:\OUsea\Client\OBJECTS\ENU\siebel.srf
12. You are now ready to publish the task into the client (runtime) database.
a. Click the Task ABC Create New Account - 0 tab in the editor to return to the Task
Designer.
b. Right-click on the designer background and select Validate.
c. Click Start.
d. Verify that no errors occur and click Cancel. If any errors are displayed, make sure that you

fix them before you continue.
e. Select Task :: ABC Create New Account.
f. Click the Publish button in the WF/Task Editor toolbar to publish the task.
Since you just validated the task, click Yes to continue.
g. Observe that the Status property changes to Completed. You will not be able to edit this task
without first revising it.
13. You will now administer the task in the client, with the first step being to activate the task.
a. Start the Siebel Call Center Developer Web client and log in as SADMIN/SADMIN
b. Navigate to Administration - Business Process > Task Deployment.
c. Select ABC Create New Account in the Published tasks applet and click Activate. Observe
that the task is added to the Active tasks applet.
14. Next you will register the task and assign it to a responsibility so that users will be able to invoke
it.
a. Navigate to Administration - Application > Tasks.
b. In the Registered Tasks applet create a new record and select the ABC Create New Account
task from the picklist.
c. In the lower Responsibilities applet, click New and add the Siebel Administrator
responsibility.
d. Make sure the Allow Delete and Allow Transfer flags are checked to permit the user to either
delete or transfer a paused task in the user's inbox.
e. Click Clear Cache to update the cached responsibilities.
f. Log out of Siebel Call Center and then log back in as SADMIN/SADMIN.

15. You will finally verify that the task was successfully deployed to the client and works as
designed.
a. In Siebel Call Center, click the Tasks button to display the task pane. Verify that the task you
deployed is displayed.

b. Click the Create New Account and Opportunity link.
c. Verify that the first task view appears and that the task pane now displays both chapters. Also
observe that the Previous button is disabled.
d. Enter an account name and site.

e. Click the Next button.
f. Verify that the account name appears in the opportunity applet.

g. Enter an opportunity name and click Submit.
h. Navigate to the My Accounts view, select the account you created, drill down on it and
navigate to the account opportunity view. Verify that the new account and opportunity now
appear in the regular Siebel UI.

Lab 40-2 Adding a Summary View (Unguided)
Goals To add a summary view to allow users to review entries before submitting
Instructions:
In this lab you will extend the task you created in the previous lab by adding a summary view. This
task view allows users to review the data they have entered in earlier task views before they commit

the data to the database.
1. Since the task flow you developed has been published, you will need to first revise it
a. In Siebel Tools, locate the ABC Create New Account task.
b. Click Revise in the WF/Task Editor Toolbar. This creates a new version of the completed
task and increments the version number.
c. Edit the task flow and insert a Task View Step immediately before the End step.
d. Arrange the connectors as required.
2. Create the summary task view.

a. Use the Task View Wizard to create a Task View object using the following parameters:
View Name ABC Account Summary View
Display Name Review Details
Selected Applets Account Entry Applet
Opportunity Form Applet
b. Verify that both applets appear in the Web template in the Web layout editor.
3. Bind the ABC Account Summary View to the new task view step
a. Return to the Task Designer and bind the ABC Account Summary View to the Task View
step.
b. Set the following properties:
Display Name –String Override Review Details and Submit

4. You need to make a small change to the previous task view which is still configured as the final
view.
a. Return to the task Designer and select ABC Opportunity Entry Task View.
b. Set the following properties:
5. Assign the new step to Chapter 2.
6. Deploy the modified task. In this case you will both publish and activate the task flow directly
from Siebel Tools.
a. First validate the modified task flow, and resolve any defects discovered.
b. Click the Publish/Activate button in the WF/Task Editor Toolbar.

7. Compile the ABC Account Summary View you created earlier.
8. Restart Siebel Call Center, log in as SADMIN/SADMIN, and invoke the task. Enter test data
and verify that the task now includes a summary view.

Lab 40-2 Adding a Summary View (Guided)
Goals To add a summary view to allow users to review entries before submitting
Instructions:
In this lab you will extend the task you created in the previous lab by adding a summary view. This

task view allows users to review the data they have entered in earlier task views before they commit
the data to the database.
1. Since the task flow you developed has been published, you will need to first revise it
a. In Siebel Tools, select Task :: ABC Create New Account.
b. Click the Revise button in the WF/Task Editor Toolbar. This creates a new
version of the completed task and increments the version number.
c. Right-click and select Edit Task Flow.
d. Insert a Task View Step immediately before the End step.
e. Arrange the connectors as required
2. You will now create the summary task view.

a. Repeat the steps you used in the previous lab to create a Task View object.
i. Use the Task View Wizard and enter the following:
View Name ABC Account Summary View
Title Review Details

ii. Select the View Basic view Web layout template.

iii. Assign both the Account Entry Applet and Opportunity Form Applet to the template.
b. Verify that both applets appear in the Web template in the Web layout editor. If you cannot
see both applets in the editor window, right-click on the editor surface and select Preview.

c. Save your configuration and close the Web layout editor window.
3. You will now bind the ABC Account Summary View to the new task view step
a. Return to the Task Designer and select the Task View step you added in this lab.
b. Right-click and select Bind Task View.
c. Select ABC Account Summary View, and click OK.
d. Make sure the task view is still selected and right-click and select View Properties Window.
e. Enter the following properties:
Display Name –String Override Review Details and Submit
f. Save the configuration changes.
4. You will need to make small change to the previous task view which is still configured as the
final view.
a. Return to the task Designer and select ABC Opportunity Entry Task View..
b. Enter the following property. If necessary right-click the task view and select View
Properties Window.

c. Save the configuration changes.
5. Next you will assign the new step to a chapter.

a. Click on the designer background to display the multi-valued properties window for the task.
b. Right-click on the designer background and select Show Chapters.
c. Select the ABC Account Summary View step.
d. Right-click and select Assign Chapter.
e. Select Chapter 2 and click OK.
f. Right-click on the designer background and de-select Show Chapters.
g. Save the configuration changes.
6. You are now ready to deploy the modified task. In this case you will both publish and activate
the task flow directly from Siebel Tools.

a. First validate the modified task flow, and resolve any defects discovered.
b. Click the Publish/Activate button in the WF/Task Editor Toolbar.

c. Click Yes to bypass validation since you just completed it.
7. You will next compile the ABC Account Summary View you created earlier.
a. Make sure that Siebel Call Center is closed.
b. Select View :: ABC Account Summary View
c. Right-click and select Compile Selected Objects.
d. Compile the object into D:\OUsea\Client\OBJECTS\ENU\siebel.srf
8. Restart Siebel Call Center, and invoke the task. Enter test data and verify that the task now
includes a summary view.


Module 41: Transient Business Components and Branching
Lab 41-1 Adding Branching to a UI Task (Unguided)
Goals To create a task that allows branching based on user input
Instructions:
In this lab you will extend the task you created in the previous lab by adding an additional task view

to enter an activity. Furthermore, you will add the following view that asks users to indicate whether
they wish to add a new activity or to submit the data collected to that point.
The task flow will be designed so that users will be asked this after creating the account and
opportunity as well as after each activity they enter. In this way users will be able to enter as many
activities as they choose.
What the user enters in this view is data that will be used by the task flow to determine the next view
to display but is not data that needs to be stored persistently. Therefore a transient business
component (TBC) will be used to capture this data.
In addition, the choices will be presented to the user in the form of a radio button list. This list
requires an underlying static list of values (LOV) that you will create in this lab.
1. Modify the task flow for the task you built in the previous lab to include a decision step and a
step to create an activity.
a. If necessary start Siebel Tools and log in as SADMIN/SADMIN to the Sample database.
b. Revise the ABC Create New Account task and invoke the Task Designer.
c. Add the following steps between the ABC Opportunity Entry Task View and the ABC
Account Summary View: Task View step (2), Decision Point step, and Siebel Operation
step.

d. Add new connectors and arrange the steps as depicted in the diagram.

2. The radio button control in the Select Next Step view displays members of List of Values
(LOV). Create an LOV with two members (Review and submit, Add a new activity). LOVs can
be administered from either Siebel Tools or the Siebel client. You will use Siebel Tools to do so.
a. In Siebel Tools, select Screens > System Administration > List Of Values.
b. Create an LOV record type with the following values:
Type LOV_TYPE
Display Value ACCOUNT_UI_TASK
Translate True
Multilingual False
Language Independent Code ACCOUNT_UI_TASK
This record defines the LOV itself.
c. Add two LOV records with the following values:
Type Display Value Language Independent Order Translate Language Name
Code
ACCOUNT_UI_TASK Review and submit Review and submit 1 True English-American
ACCOUNT_UI_TASK Add a new activity Add a new activity 2 True English-American
These records define the members of the ACCOUNT_UI_TASK LOV, and are the values
that will be displayed in the Select Next Step view.

d. Create a new picklist record that references the LOV that you just created using the values
below. This picklist will be used to populate a field in the business component that captures
the user's input in this view.
Name ABC Account Prompt
Bounded True
Static True
Type Field Type
Type Value ACCOUNT_UI_TASK

3. The user's input is required for processing by the task but does it not need to be saved to the
database. Configure a transient business component (TBC) with a single field called Next Step to
capture this input.
a. Create a TBC using the Transient BusComp wizard using the following properties:
Project ABC UI Task
Transient Business Component name ABC Account Prompt
b. Add a single value field to the new TBC with the following properties:
Name Next Step
Picklist ABC Account Prompt
Predefault Value Review and submit
Required True
Text Length 40
c. Add a pickmap to the field with the following properties:
Field Next Step
Picklist Field Value
4. Configure a task applet that exposes the TBC you just configured.
a. Create a task applet using the Task Applet wizard using the following values:
Applet name ABC Account Prompt Applet
Display Title Select Next Step
Task ABC Create New Account
Transient Business Component ABC Account Prompt
b. Add Next Step to the Selected Fields column.

c. In the Web layout editor, expand the size of the control as appropriate. Use preview mode to
make sure the entire control is visible.

5. Create the Task View object that will display the task applet. This configuration is similar to
those you performed previously except that you will add a Task Applet rather than a regular
Siebel applet.
a. Create a task view using the Task View wizard and using the following values:
View Name ABC Account Prompt View
Display Name Select Next Step
b. Click Next since you will need to add a regular Siebel applet to this view.

c. In the Select Task panel, select ABC Create New Account.
d. Add ABC Account Prompt Applet to the Selected column.
e. Select Task Playbar Applet - Bottom, and assign it as the bottom playbar applet.
f. Review the final configuration and click Finish.
g. Verify that the task applet appears in the template.
6. Bind this new task view to the Task View step in the Task Flow.
a. In the Task Designer select the Task View step that immediately precedes the decision step.
b. Bind the task view to the ABC Account Prompt View and enter the following properties:
Display Name –String Override Select Next Step
7. Configure the new Siebel Operation step that follows the decision step to insert a new child
activity record. Set the properties of the Siebel Operation step as follows:
Business Component Action
Name Add New Activity
Operation Insert
8. Create a new Task View that allows the user to enter a new child activity. This configuration is
similar that you performed in the previous module, as you will add only a regular Siebel applet to
the task view.
a. Invoke the Task View Wizard and enter the following properties:
View Name ABC Activity Entry Task View
Display Name Enter Activity Details

b. Complete the configuration.

i. Assign the Activity Form Applet to the template.
ii. Do not add a task applet.
iii. Select the Task Playbar Applet - Bottom and assign it as the bottom playbar applet.
9. Bind this task view to the new task step that follows the Add New Activity Siebel Operation
step.
a. Bind the ABC Activity Entry Task View to the new task step that follows the Add New
Activity Siebel Operation step.
b. Enter the following properties:
Display Name - String Override Enter an Activity

10. Configure the decision step to branch to either add a new activity or to review and submit the
records based on the user input.
a. Change the Name of the decision step to Next Step?.
b. Modify the connector of the ABC Account Summary View step in the Compose Condition
Criteria dialog box as follows:
Operation All Must Match
Object ABC Account Prompt
Field Next Step
Values Review and submit
c. With the connector still selected, set its Label property to Review.
d. Configure the other connector to branch on the value Add a new activity, and set its Label
property to Activity.
11. The final bit of configuration involves modifying the summary view to display any activities the
user might have added.
a. Return to the Task Editor and drill down into the ABC Account Summary View step. This
invokes the Web layout editor for the view.
b. Drag a List Applet icon from the Applets window and position in the layout editor in applet
placeholder below the playbar applet.
c. Select the Account Activity List Applet from the list of available applets and click Pick.
d. Move the playbar applet below the applet you just added, by clicking one of the buttons in
the playbar applet and dragging the playbar.
e. Preview the view to verify the applets are positioned as desired.
12. Create new chapters and assign the new task steps to the chapters.
a. Add two new chapters as follows:
Chapter 3 Optionally Add new Activities 30
Chapter 4 Review and Submit 40

b. Add the four new steps to Chapter 3.

c. Select the final two task steps and assign them to Chapter 4.
13. Compile the ABC UI Tasks project to make sure that you compile all the objects that you
created or modified.
14. Validate the task.
15. Publish and activate the task in Siebel Tools.
16. Once the task is activated, test the task in the Siebel client.
a. Start the Siebel Developer Web client and log in as SADMIN/SADMIN, connecting to the
Sample database.
b. Invoke the ABC Create New Account task from the task pane.

c. Create a new account and add an opportunity.
d. Verify that the Select Next Step task view appears and add several activities.
e. Complete the task by selecting Review and submit.

Lab 41-1 Adding Branching to a Task (Guided)
Goals To create a task that allows branching based on user input
Instructions:
In this lab you will extend the task you created in the previous lab by adding an additional task view
to enter an activity. Furthermore you will also add the following view that asks users to indicate

whether they wish to add a new activity or to submit the data collected to that point.
The task flow will be designed so that users will be asked this after creating the account and
opportunity as well as after each activity they enter. In this way users will be able to enter as many
activities as they choose.
What the user enters in this view is data that will be used by the task flow to determine the next view
to display but is not data that needs to be stored persistently. Therefore a transient business
component (TBC) will be used to capture this data.
In addition the choices will be presented to the user in the form of a radio button list. This list
requires an underlying static list of values (LOV) that you will create in this lab.
1. You will start by modifying the task flow for the task you built in the previous lab to include a
decision step and a step to create an activity.
a. If necessary start Siebel Tools and log in as SADMIN/SADMIN to the Sample database.
b. Select Task :: ABC Create New Account. Make sure to pick the most recent version of this
task.
c. Click the Revise button in the WF/Task Editor tool bar to revise the task.
d. Right-click ABC Create New Account and select Edit Task Flow to invoke the Task
Designer.

e. Insert a task view step and a decision step between the ABC Opportunity Entry Task View
and the ABC Account Summary View.
f. Add new connectors and make sure the old and new connectors are anchored on the steps.

g. Drag a Siebel Operation step below the decision step.
h. Drag a Task View step to the right of the Siebel Operation step.
i. Drag connectors to create a loop from the decision step to the Siebel Operation step to the
second new task view step back to the first new task view step.
j. Save your configuration changes by clicking the Save button in the Edit toolbar.
2. The radio button control in the Select Next Step view displays members of List of Values
(LOV). You will now create a LOV with two members (Review and submit, Add a new activity)
LOVs can be administered from either Siebel Tools or the Siebel client. You will use Siebel
Tools to do so.
a. In the application menu bar in Siebel Tools, select Screens > System Administration > List
Of Values.

b. Create a LOV type record with:

Type LOV_TYPE
Display Value ACCOUNT_UI_TASK
Translate True
Multilingual False
Language Independent Code ACCOUNT_UI_TASK
This record defines the LOV itself
c. Add two LOV records with
Type Display Value Language Independent Order Translate Language Name
Code
ACCOUNT_UI_TASK Review and submit Review and submit 1 True English-American

ACCOUNT_UI_TASK Add a new activity Add a new activity 2 True English-American
These records define the members of the ACCOUNT_UI_TASK LOV, and are the values
that will be displayed in the Select Next Step view.
d. Verify that the records look like:
3. Next you will build a pick list that references the LOV that you just created. This picklist will be
used to populate a field in the business component that captures the user's input in this view.
a. Select Pick List in the Object Explorer.
b. Create a new record with:
Name ABC Account Prompt
Bounded True
Static True
Type Field Type
Type Value ACCOUNT_UI_TASK

4. The user's input is required for processing by the task but does it not need to be saved to the
database. You will configure a transient business component (TBC) with a single field called
Next Step to capture this input. In this step you will use the TBC wizard to create a new TBC.
b. Click the Task tab and select Transient BusComp
c. Click OK to invoke the New Business Component Wizard. Using the wizard is highly
recommended since it provides default values for several additional properties that are
required for a TBC
Project ABC UI Task
Transient Business Component name ABC Account Prompt

e. Click Finish. This invokes the list editor which displays the newly-created business
component.
f. Add a single value field to the new TBC with
Name Next Step
Picklist ABC Account Prompt
Predefault Value Review and submit
Required True
Text Length 40
g. Add a pickmap to the field with the following properties. Expand Single Value Field in the
Object Explorer to access the SVF Pick Map.
Field Next Step
Picklist Field Value
5. Next you will configure a task applet that exposes the TBC you just configured. You will use the
Task Applet wizard to do so.
b. Click the Task tab and select Task Applet
c. Click OK.
Applet name ABC Account Prompt Applet
Display Title Select Next Step
Task ABC Create New Account
Transient Business Component ABC Account Prompt
e. Click Next.
f. Select Next Step from the Available Fields, and move it to the Selected Fields column.
g. Click Next.

h. Click Finish. The applet is configured for you and after a short while, the applet Web layout
editor opens with the picklist field displayed as a radio button.
i. Use the preview mode to inspect how the applet will display at runtime to ensure both radio
buttons appear. If not, expand the size of the control.
j. Save the configuration.
k. Close the Web layout editor.
6. You will next invoke the Task View wizard to create the Task View object that will display the
task applet. This configuration is similar to those you performed previously except that you will
add a Task Applet rather than a regular Siebel applet.
b. Click the Task tab and select Task View.
c. Click OK to invoke the New View Wizard.

View Name ABC Account Prompt View
Title Select Next Step
e. Click Next.
f. Select View Basic for the Web layout template.
g. Click Next since you will not need to add a regular Siebel applet to this view.
h. In the Select Task panel, select ABC Create New Account. This displays the task applets
that have been assigned to this task.
i. Click Next.
j. Select ABC Account Prompt Applet and move it to the Selected column, and click Next.
k. Select Task Playbar Applet – Bottom, assign it as the bottom playbar applet, and click
Next.
l. Review the final configuration and click Finish.
m. Verify that the task applet appears in the template. You may choose to preview the view in
the layout editor to verify how it will look when displayed in the application.
n. Close the Web layout editor.
7. You will now bind this new task view to the Task View step in the Task Flow.
a. Return to the Task Designer.
b. Select the Task View step that immediately precedes the decision step.
c. Right-click and select Bind Task View.
d. Select ABC Account Prompt View, and click OK.
e. Make sure the task view is still selected and right-click and select View Properties Window.

f. Enter the following properties:

Display Name –String Override Select Next Step
g. Save the configuration changes.
8. You will next configure the new Siebel Operation step that follows the decision step to insert a
new child activity record.
a. Right-click the Siebel Operation step and select View Properties Window.
b. Set the properties as follows.
Business Component Action

Name Add New Activity
Operation Insert
c. Save the configuration you created.
9. You are now ready to create a new Task View that allows the user to enter a new child activity.
This configuration is similar that you performed in the previous module, as you will add only a
regular Siebel applet to the task view.
a. Invoke the Task View Wizard and use the following properties:
View Name ABC Activity Entry Task View
Title Enter Activity Details
b. Complete the configuration:
i. Use the View Basic view Web layout template
ii. Assign the Activity Form Applet to the template. Normally you would assign a
customized activity form applet that contains a smaller number of fields.
iii. Do not add a task applet.
iv. Select the Task Playbar Applet – Bottom and assign it as the bottom playbar applet.
10. You will next bind this task view to the new task step that follows the Add New Activity Siebel
Operation step.
a. Select the Task View step and right-click and select Bind Task View.
b. Select ABC Activity Entry Task View, and click OK.
c. Make sure the task view is still selected and right-click and select View Properties Window.
d. Enter the following properties:
Display Name –String Override Enter an Activity
e. Save the configuration changes.

11. Now you will configure the decision step to branch to either add a new activity or to review and
submit the records based on the user input
a. Select and right-click the decision step, and select View Properties Window.
b. Set the Name property to Next Step?
c. Select and right-click the connector to the ABC Account Summary View step, and select
Edit Conditions.
d. In the Compose Condition Criteria dialog box, fill in the following in the Compose a
Condition section:
Operation All Must Match
Object ABC Account Prompt

Field Next Step
e. Click New.
f. Select Review and submit from the dropdown.
g. Click Add to complete the creation of the condition.
h. Click OK.
i. With the connector still selected, set its Label property to Review.
j. Configure the other connector to branch on the value Add a new activity, and set its Label
property to Activity.
k. Save the configuration changes.

12. The final bit of configuration involves modifying the summary view to display any activities the
user might have added.
a. Return to the Task Editor and double-click the ABC Account Summary View step. This
invokes the Web layout editor for the view.
Hint: Consider hiding some of the surrounding windows to increase the space available to
display the layout editor.
b. Drag a List Applet icon from the Applets window and position in the layout editor in applet
placeholder below the playbar applet.
c. Select the Account Activity List Applet from the list of available applets and click Pick.
You might need to sort the list of available applets first by clicking on the column heading.
d. Move the playbar applet below the applet you just added, by clicking one of the buttons in
the playbar applet and dragging the playbar.

e. Preview the view to verify the applets are positioned as desired.
f. Save the configuration changes.
g. Close the Web layout editor.
13. You will create new chapters and assign the new task steps to the chapters.
a. Click on the designer background to display the multi-valued properties window (MVPW)
for the task.
Chapter 3 Optionally Add new Activities 30
Chapter 4 Review and Submit 40
d. Select the four new steps by shift-clicking or dragging a selection box around them.
e. Right-click and select Assign Chapter.
f. Select Chapter 3 and click OK.
g. Select the final two task steps and assign them to Chapter 4.

h. Verify that the final flow looks similar to the following.

i. Save your configuration changes.
14. Compile the ABC UI Tasks project to make sure that you compile all the UI objects that you
created or modified.
15. Validate the task. Remember validation can discover many common errors in the task flow.
16. Publish and activate the task in Siebel Tools.
17. Once the task is activated, you will test the task in the Siebel client.
a. Restart Siebel Call Center Developer Web client, logging in as SADMIN/SADMIN and
b. Invoke the ABC Create New Account task from the task pane.
c. Create a new account and add an opportunity.

d. Then verify that the Select Next Step task view appears and add several activities.
e. Select Review and submit and click Next to view the records you entered.
f. Click Submit to complete the task.
18. Close Siebel Tools.

Module 42: Siebel Business Rules
Lab 42-1 Examining Siebel Business Rules (Unguided)
Goals To examine a rule module and identify the business logic
Instructions:
Due to the nature of this lab, there is no Unguided version of it. Please turn the page and do the

Guided version.


Lab 42-1 Examining Siebel Business Rules (Guided)
Goals To examine a rule module and identify the business logic
Instructions:
In this lab you will examine a small set of business rules and policies that apply to expense reports.

You will then create some test expense reports and verify that the business logic expressed in the
rules are applied.
The rules were authored in HaleyAuthority and are written in natural English using the names of
business components and fields as they appear in the Siebel repository. In particular the rules you
will examine refer to the following business components and fields.
Business Component Field
Expense Description
Expense Item Comments
Description
Reimbursable flag
Amount
Expense item type
1. You will first start HaleyAuthority.

a. Select Start > Programs > Siebel Tools 8.0 > Siebel Business Rules Developer.
b. Select More data sources and click OK.
c. Uncheck Only Display Sources that.
d. Select Haley and click OK.
e. Enter the following credentials:
Login ID HaleyAuth
Password BusRules
f. Click OK.

g. Observe that HaleyAuthority starts and that the Modules & Statements tab (at the bottom of
the window) is selected.

2. You will now examine the rule module itself.
a. Select Expense Validation in the Modules & Statements folder.
b. Right-click and select Expand All.
c. Observe that there are two submodules (Expense and Expense Item) with multiple
statements.
d. Inspect the statements in the Expense submodule.
i. Which field of the Expense business component is required?
____________________________________________
ii. Can an expense report be submitted without any expense items?
____________________________________________
e. Inspect the statements in the Expense Item submodule. Which fields of the Expense Item
business component are referenced in these rules?
________________________________________________________________________
f. A statement in the Expense Item submodule addresses expense items of type Personal. What
policy is implemented in this statement?
________________________________________________________________________
g. A statement in the Expense Item submodule addresses a requirement for receipts. What
processing is specified in this statement?
________________________________________________________________________

3. You will next create a sample expense report to verify that the above business rules and policies
are implemented.
b. Navigate to Expense Reports > Expense List.
c. Create a new expense report with just the following fields, and accept all other default values
provided:
Name Report 1
Period <select the most recent period>
Submit To CCHENG
d. Right-click and select Save Record. A runtime event has been configured to execute the rule
module you just examined whenever an expense record is written to the database.

e. Examine the message that is displayed. Observe that the message refers to the absence of a
description for the expense report and that there are no expense items.
f. Click OK.
g. Add the following description to the expense record:
Description For business rules test
h. Drill down on the Expense Report Name. You may need to click OK in the message box
and then drill down on the name again.
i. In the Line Items list applet, create the following record:
Type Dinner
Amount 25
j. Right-click in the upper (Expense form) applet and select Save Record.
k. Examine the message that is displayed. Observe that the message refers to the absence of a
description for the expense item itself.
l. Add the following description to the expense item record:
Description Don't eat here again
m. Right-click in the upper (Expense form) applet and select Save Record. Observe that the
expense report is saved without displaying any messages as the expense report no longer
violates any of the policies in the rules module.
4. You will expose the Public Comments column on the expense item list applet in order to display
comments that might be generated by the rule module.
a. Right-click on the list applet and select Columns Displayed.
b. Select Public Comments from the Available Columns and move it to the Selected Columns.
c. Click Save.
d. Resize and reorder the columns as necessary to make sure the Public Comments column
appears in the list applet.

5. You will now add two more expense items and verify that the processing specified in the
statements in the rules modules occurs.
a. Add the following two expense items to the expense report.
Type Amount Description
Lunch 15 yummy
Personal 75 Speeding ticket
b. Right-click in the upper (Expense form) applet and select Save Record.
c. Verify that a comment was added to Lunch item stating that a receipt is not required.
d. Verify that the reimbursable flag was cleared (turned off) for the Personal item and a
comment explaining that personal items are not reimbursed was added.

6. Close HaleyAuthority.
7. Log out of the Siebel Call Center application.

Solutions 42-1 Examining Siebel Business Rules

(Guided)
Answers
2.d.i. Which field of the Expense business component is required?
Description.
2.d.ii. Can an expense report be submitted without any expense items?

No an expense report must have one or more expense items.

2.e. Inspect the statements in the Expense Item submodule. Which fields of the Expense Item
business component are referenced in these rules?
Reimbursable flag, expense item type, description, amount, comments.
2.f. A statement in the Expense Item submodule addresses expense items of type Personal.
What policy is implemented in this statement?
An expense item of type personal is not reimbursable unless the description field equals
"Pre-approved". In addition the rule sets (updates) the comment field and clears the
reimbursable flag.
2.g. A statement in the Expense Item submodule addresses a requirement for receipts. What
processing is specified in this statement?
If an expense item's amount is less than $20, the rule module sets the comments field with a
message that a receipt is not required.


Module 43: Creating Business Rules
Lab 43-1 Creating Siebel Business Rules (Unguided)
Goals To create and deploy a rule module using HaleyAuthority

To administer the rule module and to invoke the rule module using a runtime event
Instructions:

In this lab you will create a rule module that sets the priority of a service request to 1-ASAP if the
severity of the request is 1-Critical. In addition the rule module will set the priority of any scheduled
activities associated with the service request to 1-ASAP as well.
You will develop the rule module using HaleyAuthority and a new knowledge base. An empty
database called ServiceReqKB and an ODBC data source called Service Request KB have already
been created for this lab.
1. Make sure the Siebel Call Center Developer Web client is closed.
2. Start HaleyAuthority, and create the new knowledge base.

a. Start the Siebel Business Rules Developer and click Cancel to close the initial dialog box.
b. Select File > New.
c. Click the ODBC data sources and drivers tab.
d. Select Service Request KB and click OK.
e. Enter the following credentials:
Login ID HaleyAuth
Password BusRules
HaleyAuthority creates a new knowledge base and displays the Modules & Statements tab.
f. Click the Concepts tab (at the bottom of the window) and verify that no entities yet exist in
the knowledge base
3. Import a set of objects and fields from the Siebel repository to create the entities and values you
will use to create the rules. The initial import into a new knowledge base also creates a set of
base concepts used in all rule modules.
a. Select File > Import > Siebel Object.
b. Click Next.
SIebel 8.0 Essentials 181

c. Enter the following connection parameters for the master repository (source of object
definitions).
CFG File D:\Ousea\client\BIN\ENU\uagent.cfg
Language ENU
Login SADMIN
Password SADMIN
DataSource Sample
d. Select Local as the runtime database connection. Local specifies that the runtime system
(into which the rules will be deployed) is a client database of type .dbf rather than server
database.
e. The runtime database is the same as the master repository. Enter the same connection

parameters as you entered for the master repository.
f. Click Yes when notified that the runtime database already has imported data. This occurs
because the runtime database already contains previously-deployed rules.
g. Since this is the initial import into a new knowledgebase, multiple currency-related concepts
and relations as well as other items, such as functions and predicates, are created. Wait a few
minutes while this process completes.
4. After the initial sets of items have been created, you are ready to import the business components
and fields needed to support the business logic described at the beginning of the lab.
a. In the Siebel Object Import Wizard - Pick Task dialog, verify that Import Siebel Objects is
selected.
b. Select Service Request as the business object from the drop-down.
c. Select the Service Request business component from the list by clicking the box to its
immediate left, then expand it, and finally select the Action child business component as
well.
d. Select the Priority and Severity fields from the Service Request business component.
e. Select the Priority and Status fields from the Action business component.
182 SIebel 8.0 Essentials

f. Verify that the hierarchy displayed reflects the objects and fields to be imported, and click
Next.

g. HaleyAuthority then imports the desired objects. Verify that the import did not generate any
warnings, and click Finish.
h. Click No when asked if you would like to perform another task.
i. Close or minimize the Output window.
5. Examine the concepts that were created.

a. In the concepts tab, expand the entity concept, and verify that three entity concepts now
appear.
b. Expand Service Request and then expand Phrasings. Observe that the phrasings correspond
to the object and fields imported.
c. Repeat the previous step for the Action concept.

d. Expand the Value concept and then expand string and Phrasings. Observe that the imported
fields of type text are listed here.
e. (Optional) Expand the currency value entity and observe the large number of phrasings that
were created during the initial process prior to importing the objects you selected. These
entities and values are used to support processing of currencies in the business rules engine.
Now that the concepts have been created, you are ready to create statements for a rule module that
enforces the desired business logic. These statements will be developed using the concepts generated
during the import. Note that you must not modify or delete these concepts.
As you create the statements, HaleyAuthority parses the text you enter, that is, it compares the text to
nouns, verbs, and phrases it generated during the import and bolds all text that it recognizes.
HaleyAuthority also displays a list of valid next words whenever text is successfully parsed.

6. Create a set of statements that update a service request’s priority to 1-ASAP if the severity is 1-
Critical.
a. Select the Modules & Statements tab.
b. Right-click the Modules & Statements folder and select Add a module. A module is a
container for a set of rule statements and is the unit that is deployed to a run-time system.
c. Name the module Service Request - Write Record. The name is arbitrary but it is
recommended that the module name correspond to the mechanism by which it will be
invoked.
d. Right-click the new module you created and select Add a submodule. A submodule is an
arbitrary subgrouping of statements.
e. Name the submodule Update Priority.
f. Right-click the submodule you created and select Add a statement.
g. In the Edit Statement window, enter set "Priority" of a service request to "1-ASAP" and
click OK.
h. Right-click the statement you created and select Is Applicable > if.
i. Enter the condition: the service request’s severity is “1-Critical” and click OK.
j. Right-click the first statement you created and select Is Applicable > unless. Make sure you
select the top level statement.
k. Enter the sentence: the service request’s priority is "1-ASAP" and click OK.

7. Create statements that update the priority of associated scheduled actions to 1-ASAP as follows:

8. You are now ready to deploy the module to the Siebel runtime client.
a. Select Tools > Siebel Deployment.
b. Select Service Request - Write Record in the List of Modules, and click OK.
c. Observe that HaleyAuthority logs in to the runtime client and deploys the rule module.
9. The rule module has been written to the Siebel runtime database and you will now administer the
rule module to make it available for use at runtime.
SADMIN/SADMIN the Sample database.
b. Navigate to Administration - Business Rules > Rule Modules List, and verify that the Service
Request - Write Record rule module appears in the Rule Modules list applet.
c. Select the record and set the business object to Service Request. This identifies the business
object that the Siebel application will use to provide data to the rules engine at runtime.
d. In the Rules Module Relations list applet, create two new records: One for Service Request
and the other for Action. These specify the business components that will provide data for
evaluation by the business rules.
e. Click the Activate button in the Rule Module list applet to make the rule module available.
Observe that the status changes to Active.

10. The rule module has been made available for use. Create a runtime event with an action set that
invokes this rule module.
a. Create a new action set called ABC Service Request with:
Name ABC SR
Action Type BusService
Sequence 1
Active True
b. Enter the following fields in the More Info applet:
Business Service Name Business Rule Service
Business Service Method RunRules

Business Service Context Service Request - Write Record
Note that the context is the name of the rule module to be evaluated. Make sure that you
enter it exactly as it appears in the Rules Module List.
c. Explicitly save the ABC Service Request action set.
d. Create a new runtime event with
Name ABC Runtime Event
Sequence 1
Object Type BusComp
Object Name Service Request
Event WriteRecord
Action Set name ABC Service Request
e. Save the record.
f. Select Menu > Reload Runtime Events to deploy the new runtime event.
11. You are now ready to test the deployed rule module by creating a test service request.
a. Create a test Service Request record and accept all default values provided.
b. Observe that the priority defaults to 3-Medium.
c. Use the Show More button to expose the Severity field and set it to 1-Critical.
d. Right-click on the form applet and select Save Record. Verify that the Priority is updated to
1-ASAP.
12. Create several activity records to test the set of statements in the rule module that refer to action.
Make sure that the Priority of the Service request is still 1-ASAP.
a. Create the following activity records:
Type Status Priority
Appointment Unscheduled <blank>
Appointment Scheduled <blank>
Appointment Scheduled 4-Low
b. Return to the Service Request form applet and save the record. Verify that the priority of the
two scheduled activity records is updated to 1-ASAP.

13. Verify that the rules do not change the priority if the severity is something other than 1-Critical
by creating a new service request record with a Severity of 2-High.
14. Delete the runtime event to keep the rules engine from being invoked in future labs.
a. Navigate to Administration - Runtime Events > Events.
b. Query for the event with Action Set Name = ABC Service Request.
c. Delete the runtime event.
d. Select Menu > Reload Runtime Events


Lab 43-1 Creating Siebel Business Rules (Guided)
Goals To create and deploy a rule module using HaleyAuthority

To administer the rule module and to invoke the rule module using a runtime event
Instructions:

In this lab you will create a rule module that sets the priority of a service request to 1-ASAP if the
severity of the request is 1-Critical. In addition the rule module will set the priority of any scheduled
activities associated with the service request to 1-ASAP as well.
You will develop the rule module using HaleyAuthority and a new knowledge base. An empty
database called ServiceReqKB and an ODBC data source called Service Request KB have already
been created for this lab.
1. Make sure the Siebel Call Center Developer Web client is closed.
2. You will first start HaleyAuthority, and create the new knowledge base
a. Select Start > Programs > Siebel Tools 8.0 > Siebel Business Rules Developer.
b. Click Cancel.
c. Select File > New.
d. Click the ODBC data sources and drivers tab.
e. Select Service Request KB and click OK.
f. Enter the following credentials:
Login ID HaleyAuth
Password BusRules
g. Click OK. HaleyAuthority creates a new knowledge base and displays the Modules &
Statements tab.
h. Click the Concepts tab (at the bottom of the window) and verify that no entities yet exist in
the knowledge base

3. You will import a set of objects and fields from the Siebel repository to create the entities and
values you will use to create the rules. The initial import into a new knowledge base also creates
a set of base concepts used in all rule modules.
a. Select File > Import > Siebel Object.
b. Click Next.
c. Enter the following connection parameters for the master repository (source of object
definitions).
CFG File D:\Ousea\client\BIN\ENU\uagent.cfg
Language ENU
Login SADMIN
Password SADMIN

DataSource Sample
d. Click Next.
e. Select Local as the runtime database connection. Local specifies that the runtime system
(into which the rules will be deployed) is a client database of type .dbf rather than server
database.
f. Click Next.
g. The runtime database is the same as the master repository. Enter the same connection
parameters as you entered for the master repository.
h. Click Next.
i. Click Yes when notified that the runtime database already has imported data. This occurs
because the runtime database already contains previously-deployed rules.
j. Since this is the initial import into a new knowledgebase, multiple currency-related concepts
and relations as well as other items, such as functions and predicates, are created. Wait a few
minutes while this process completes.
4. After the initial sets of items have been created, you are ready to import the following business
components and fields to support the business logic described at the beginning of the lab.
Business Component Field
Service Request Priority
Severity
Action Status
Priority
a. In the Siebel Object Import Wizard – Pick Task dialog, verify that Import Siebel Objects is
selected and click Next.
b. Select Service Request as the business object from the drop-down and click Next.
c. Scroll down the list of business components and locate Service Request.
i. Select Service Request by clicking the box to its immediate left.
ii. Click the + sign to the immediate left to expand Service Request. This shows a list of
all its child business components.
iii. Select Action by clicking the box to its immediate left.
iv. Click Next.

d. A list of available fields for Service Request is displayed. Select Priority and Severity from
the available fields, move them to Selected Fields, and click Next.
e. A list of available fields for Action is displayed. Select Priority and Status from the
available fields, move them to Selected Fields, and click Next.
f. Verify that the hierarchy displayed reflects the objects and fields to be imported, and click
Next.

g. HaleyAuthority then imports the desired objects. Verify that the import did not generate any
warnings, and click Finish.
h. Click No when asked if you would like to perform another task.
i. Close or minimize the Output window.
5. You will now examine the concepts that were created.

a. In the concepts tab, expand the entity concept, and verify that three entity concepts now
appear.

b. Expand Service Request and then expand Phrasings. Observe that the phrasings correspond
to the object and fields imported.
c. Repeat the previous step for the Action concept.
d. Expand the Value concept and then expand string and Phrasings. Observe that the imported
fields of type text are listed here.
e. (Optional) Expand the currency value entity and observe the large number of phrasings that
were created during the initial process prior to importing the objects you selected. These
entities and values are used to support processing of currencies in the business rules engine.
Now that the concepts have been created, you are ready to create statements for a rule module that
enforces the desired business logic. These statements will be developed using the concepts generated
during the import. Note that you must not modify or delete these concepts.
As you create the statements, HaleyAuthority parses the text you enter, that is, it compares the text to

nouns, verbs, and phrases it generated during the import and bolds all text that it recognizes.
HaleyAuthority also displays a list of valid next words whenever text is successfully parsed.
6. You will create a set of statements that update a service request’s priority to 1-ASAP if the
severity is 1-Critical.
a. Select the Modules & Statements tab.
b. Right-click the Modules & Statements folder and select Add a module. A module is a
container for a set of rule statements and is the unit that is deployed to a run-time system.
c. Name the module Service Request - Write Record. The name is arbitrary but it is
recommended that the module name correspond to the mechanism by which it will be
invoked.
d. Right-click the new module you created and select Add a submodule. A submodule is an
arbitrary subgrouping of statements.
e. Name the submodule Update Priority.
f. Right-click the sub module you created and select Add a statement.
g. In the Edit Statement window, enter set "Priority" of a service request to "1-ASAP".
h. Click OK.
i. Right-click the statement you created and select Is Applicable > if.
j. Enter the condition: the service request’s severity is “1-Critical” and click OK.
k. Right-click the first statement you created and select Is Applicable > unless. Make sure you
select the top level statement.
l. Enter the sentence: the service request’s priority is "1-ASAP" and click OK.

7. In this step you will create statements that update the priority of any scheduled activities
associated with the service request to 1-ASAP.
a. Right-click the statement folder and select Add a statement.
b. Using the steps you just completed above, enter the following statement:
If a service request has an action then set "Priority" of the action to "1-ASAP"
c. Enter the following two applicability statements to qualify the statement you just entered.
Only if: the status of the action is “Scheduled”
Only if: the priority of the service request is “1-ASAP”
d. Verify that the rule module looks like the following:

8. You are now ready to deploy the module to the Siebel runtime client.
a. Select Tools > Siebel Deployment.
b. Select Service Request - Write Record in the List of Modules, and click OK.
c. Observe that HaleyAuthority logs in to the runtime client and deploys the rule module.
9. The rule module has been written to the Siebel runtime database and you will now administer the
rule module to make it available for use at runtime.
SADMIN/SADMIN the Sample database.
b. Navigate to Administration - Business Rules > Rule Modules List, and verify that the Service
Request - Write Record rule module appears in the Rule Modules list applet.
c. Select the record and set the business object to Service Request. This identifies the business
object that the Siebel application will use to provide data to the rules engine at runtime.
d. In the Rules Module Relations list applet, click New to specify the business components that
will provide data for evaluation by the business rules.

e. In the blank record created, click the select button in the Business Component field and
Service Request.
f. Create a second new record and select the Action business component.
g. Click the Activate button in the Rule Module list applet to make the rule module available.
Observe that the status changes to Active.
10. The rule module has been made available for use. You will create a runtime event with an action
set that invokes this rule module.
a. Navigate to Administration - Runtime Events > Action Sets.
b. In the top applet, create a new Action Set called ABC Service Request.
c. In the lower list applet create a new action record with:
Name ABC SR

Action Type BusService
Sequence 1
Active True
d. Scroll down to the bottom of the view and enter the following fields in the More Info applet:
Business Service Name Business Rule Service
Business Service Method RunRules
Business Service Context Service Request - Write Record
Note that the context is the name of the rule module to be evaluated. Make sure that you
enter it exactly as it appears in the Rules Module List.
e. Explicitly save the ABC Service Request action set.
f. Navigate to Administration - Runtime Events > Events.
g. Create a new runtime event with
Name ABC Runtime Event
Sequence 1
Object Type BusComp
Object Name Service Request
Event WriteRecord
Action Set name ABC Service Request
h. Save the record.
i. Select Menu > Reload Runtime Events to deploy the new runtime event.
11. You are now ready to test the deployed rule module by creating a test service request.
a. Navigate to Service > Service Requests List.
b. Create a test record and accept all default values provided.
c. Drill down on the new service request record and if necessary click the Show More button at
the top right of the form applet. This exposes the severity and priority fields. Observe that the
priority defaults to 3-Medium.
d. Set the Severity to 1-Critical.

e. Right-click on the form applet and select Save Record. Verify that the Priority is updated to
1-ASAP.
12. You will now create several activity records to test the set of statements in the rule module that
refer to action. Make sure that the Priority of the Service request is still 1-ASAP.
a. Create the following activity records:
Type Status Priority
Appointment Unscheduled <blank>
Appointment Scheduled <blank>
Appointment Scheduled 4-Low
b. Return to the Service Request form applet and save the record. Verify that the priority of the
two scheduled activity records is updated to 1-ASAP.

13. You will now verify that the rules do not change the priority if the severity is something other
than 1-Critical.
a. Create a new Service Request record.
b. Set the Severity to 2-High
c. Save the record and verify that the Priority is not modified in this case.
14. You will finally delete the runtime event to keep the rules engine from being invoked in future
labs.
a. Navigate to Administration - Runtime Events > Events.
b. Query for the Event with Action Set Name = ABC Service Request
c. Delete the runtime event.
d. Select Menu > Reload Runtime Events


Module 45: Creating Assignment Rules
Lab 45-1 Creating Assignment Rules for Sales Data

(Unguided)
Goals To create an assignment rule that assigns sales data to positions
Instructions:

It is common in many sales organizations to assign sales data such as accounts and opportunities to
sales teams based on geography. In this lab you will create a rule that assigns eastern accounts to the
East Sales Rep 1 and East Sales Rep 2 positions. For the purposes of this lab eastern accounts means
accounts in the states of New York (NY), New Jersey (NJ), and Pennsylvania (PA).
1. Start the Siebel Call Center Web client and log in as MPLANCK/MPLANCK. MPLANCK has
the Siebel Administrator responsibility and can administer assignment rules as well as perform
server management. You use MPLANCK to better see default assignment manager behavior.
2. Use the Administration - Assignment > Rule Groups List view to create an assignment rule
group named Sales Rules Group for a small set of sales assignment rules you will create in this
and subsequent labs.
3. Create an assignment rule that assigns eastern accounts.

a. Drill down on the Sales Rules Group to navigate to the Assignment Rules list for this group.
b. Create a new assignment rule with the following values:
Name Assign East Accounts
Object to be Assigned Account
c. Drill down on Assign East Accounts to navigate to the Assignment Rule form applet.
d. If necessary, set the Person Candidates Source to From Rule. This specifies that Assignment
Manager consider only candidates explicitly listed in the rule.
4. Create the criterion that assigns accounts in the eastern states.

a. Under the Criteria tab, in the Criteria list applet, create a record with the following values:
Rule Criterion Account State
Comparison Method Compare to Object
Inclusion Include
Required Always

b. Observe that the list applet below the criteria list applet displays two columns Score and
State. Enter three state records as follows, leaving the score field blank.
Score State
NY
NJ
PA
5. Click the Positions Candidates tab and add the following positions to specify the candidates to
be considered for assignment in this rule.
Position
East Sales 1

East Sales 2
6. Activate the rule to make it available for use by navigating to the Assignment Rules List view
and clicking Release. This updates the rules cache with all the currently active rules.
7. Create two accounts with the following values to use in testing the rules:
Account name Broadway Lights Great Lakes Beef
Address 1 Times Square 300 State Street
City New York Chicago
State NY IL
8. In the remainder of this lab, you will use Batch Assignment to test the rule you created. Verify
that the Assignment Manger server component is online. If it is not, enable and assign the
Assignment Management component group and restart the Siebel server.
9. Enable event logging on the Batch Assignment component as an aid for debugging your
assignment rules.
a. Navigate to the Events list applet for the Batch Assignment component.
b. Change the log level for Object Assignment and Rules Evaluation to 4. This level provides
detailed logging at the criterion-level during rule evaluation and at the candidate level during
object assignment.
10. Start a Batch Assignment job with the following job parameter:
Name Value
Assignment Object Name Account
Setting this parameter causes assignment manager to consider only Account Assignment Rules.
11. Once the job has completed, locate the task that just completed and examine its logs to verify
that it processed both accounts you created earlier in this lab.
Note that you can examine the log file directly by navigating to D:\OUsea\siebsrvr\log and
opening the most recent log file whose name starts with AsgnBatch_.

12. Examine the account teams on the two accounts and verify that the desired assignments were
made.
a. Navigate to the Broadway Lights account and bring up the Account team multi-value group
applet. Scroll to the far right in the Selected list and observe that the team members are
checked as either Manual or System. System indicates that the position was assigned as a
result of Assignment Manager while Manual indicates that the assignment occurred
otherwise. For instance the creator of the account is assigned to the team by default and the
creator's position is therefore checked as manual.
b. For each account list the positions assigned in the following table. Verify that MPLANCK's
position (CEO) appears as the manually assigned position in both accounts.
Account System Assigned Manual Assigned

Broadway Lights
Great Lakes Beef
c. Explain why the East Sales 1 and East Sales 2 positions were assigned as they were.
_
d. Observe that the SADMIN's position was assigned by Assignment Manager to the Great
Lakes Beef Account. This occurred because Assignment Manager was unable to find a rule
to use to assign positions to the Great Lakes Beef account. In that situation Assignment
Manager assigns a default position (in this case SADMIN's position). You will learn more
about the default positions (and how to specify them) in an upcoming module.
Note that while you created only a single rule in this lab, you would need to create a separate rule for
each sales/geographic region in your sales organization to assign all accounts.

Solutions 45-1 Creating Assignment Rules for Sales

Data (Unguided)
Answers
12.b. For each account list the positions assigned in the following table. Verify that MPLANCK's
Broadway Lights East Sales 1, East Sales 2 CEO (MPLANCK)

Great Lakes Beef Siebel Administrator (SADMIN) CEO (MPLANCK)
12.c. Explain why the East Sales 1 and East Sales 2 positions were assigned as they were.
The East Sales positions were assigned to the Broadway Lights account since that account
satisfied the conditions specified in the Assign East Accounts rule (the account state was in
the set(NY, NJ, PA).
These positions were not assigned to the Great Lakes Beef account since that account did
not satisfy the Assign East Accounts rule as (the account state was not in the set(NY, NJ,
PA).

Lab 45-1 Creating Assignment Rules for Sales Data

(Guided)
Goals To create an assignment rule that assigns sales data to positions
Instructions:

It is common in many sales organizations to assign sales data such as accounts and opportunities to
sales teams based on geography. In this lab you will create a rule that assigns eastern accounts to the
East Sales Rep 1 and East Sales Rep 2 positions. For the purposes of this lab eastern accounts means
accounts in the states of New York (NY), New Jersey (NJ), and Pennsylvania (PA).
1. Start the Siebel Call Center Web client and log in as MPLANCK/MPLANCK. MPLANCK has
the Siebel Administrator responsibility and can administer assignment rules as well as perform
server management. You use MPLANCK to better see default assignment manager behavior.
2. You will create an assignment rule group for a small set of sales assignment rules you will create
in this and subsequent labs.
a. Navigate to Administration - Assignment > Rule Groups List
b. Create a new rule group with
Name Sales Rules Group
3. You will create an assignment rule that assigns eastern accounts.

a. Drill down on the Sales Rules Group to navigate to the Assignment Rules list for this group.
Name Assign East Accounts
The Account value is entered as follows:
i. Click the select button in the Object to be Assigned field.
ii. Click New in the Assignment Object window.
iii. Select Account from the drop-down.
iv. Click Save.
v. Click OK.
c. Drill down on Assign East Accounts to navigate to the Assignment Rule form applet.
d. If necessary, set the Person Candidates Source to From Rule. This specifies that Assignment
Manager consider only candidates explicitly listed in the rule.

4. You will now create the criteria that assigns accounts in the eastern states.
a. If necessary, click the Criteria tab.
b. In the Criteria list applet, create a record with:
Rule Criterion Account State
Inclusion Include
Required Always
c. Observe that the list applet below the criteria list applet displays two columns Score and
State. Enter three state records as follows, leaving the score field blank.
Score State

NY
NJ
PA
5. Click the Positions Candidates tab and add the following positions to specify the candidates to
be considered for assignment in this rule.
Position
East Sales 1
East Sales 2
6. You will next activate the rule to make it available for use.
a. Navigate to the Assignment Rules List view.
b. Click Release, and click OK to dismiss the confirmation dialog. This updates the rules cache
with all the currently active rules.
7. You will next create two accounts to use in testing the rules.
a. Navigate to the My Accounts view.
b. Create and save two accounts with the following:
Account name Broadway Lights Great Lakes Beef
Address 1 Times Square 300 State Street
City New York Chicago
State NY IL
To enter an address:
i. Click the select button in the address field.
ii. Click New in the Account Addresses window.
iii. Enter the values listed above in the corresponding fields.
iv. Click Save.

8. In the remainder of this lab, you will use Batch Assignment to test the rule you created. First,
verify the Assignment Manger server component is online.
a. Navigate to Administration - Server Configuration > Enterprises > Component Groups.
b. Query for Assignment Management in the Component Groups list applet.
c. Examine the record in the Component Groups Assignments list applet.
i. If the Assigned and Enable on Server fields are both checked the Workflow
Management Component group is enabled; proceed to step 9.
ii. If they are not both checked, click Assign or Enable as required.
iii. Click the Synchronize view tab.
iv. Query for the Assignment Manager component. This is one of the components from
the Assignment Management component group.
v. If this component group is not found, click the Synchronize button. Synchronization

will take 1-2 minutes.
vi. Log out of the Siebel Call Center Web client.
vii. Stop the Siebel Server service using the Services window.
viii. Start the Siebel Server service. Remember to wait until the Siebel Server service has
started up completely.
ix. Start the Siebel Call Center Web client and log in as MPLANCK/MPLANCK.
9. You will also enable event logging as an aid for debugging your assignment rules.
a. Navigate to Administration - Server Configuration > Servers
b. In the Components list applet, select the Batch Assignment component.
c. In the Events list applet, change the log level for Object Assignment and Rules Evaluation to
4. This level provides detailed logging at the criterion-level during rule evaluation and at the
candidate level during object assignment.
10. You are now ready to start a Batch Assignment server task.
c. In the Component/Job field, select Batch Assignment.
d. In the Job Parameters list, create the following record:
Name Value
Assignment Object Name Account
Setting this parameter causes assignment manager to consider only Account Assignment
Rules.
e. Click Submit Job to start the job.
f. Click the Query and Go buttons successively until the task completes. Status should indicate
success.
g. Navigate to Administration - Server Management > Tasks by clicking the link next to the
Jobs link.
h. Select the tasks record with Component = Batch Assignment.
i. Scan through the log entries displayed in the lower applet and verify that Batch Assignment
processed both accounts you created earlier in the lab.

Note that you can examine the log file directly by navigating to D:\OUsea\siebsrvr\log and
opening the most recent log file whose name starts with AsgnBatch_.
11. Finally you will examine the account teams on the two accounts and verify that the desired
assignments were made.
a. Navigate to the My Accounts view.
b. Select the Broadway Lights account.
c. Click the select button on the Account team multi-value field to display the team members.
d. Scroll to the far right in the Selected list and observe that the team members are checked as
either Manual or System. System indicates that the position was assigned as a result of
Assignment Manager while Manual indicates that the assignment occurred otherwise. For
instance the creator of the account is assigned to the team by default and the creator's
position is therefore checked as manual.

e. For each account list the positions assigned in the following table. Verify that MPLANCK's
Broadway Lights
Great Lakes Beef
f. Explain why the East Sales 1 and East Sales 2 positions were assigned as they were.
_
g. Observe that the SADMIN's position was assigned by Assignment Manager to the Great
Lakes Beef Account. This occurred because Assignment Manager was unable to find a rule
to use to assign positions to the Great Lakes Beef account. In that situation Assignment
Manager assigns a default position (in this case SADMIN's position). You will learn more
about the default positions (and how to specify them) in an upcoming module.
Note that while you created only a single rule in this lab, you would need to create a separate rule for
each sales/geographic region in your sales organization to assign all accounts.

Solutions 45-1 Creating Assignment Rules for Sales

Data (Guided)
Answers
11.d. For each account list the positions assigned in the following table. Verify that MPLANCK's

11.e. Explain why the East Sales 1 and East Sales 2 positions were assigned as they were.
The East Sales positions were assigned to the Broadway Lights account since that account
satisfied the conditions specified in the Assign East Accounts rule (the account state was in
the set(NY, NJ, PA).
These positions were not assigned to the Great Lakes Beef account since that account did
not satisfy the Assign East Accounts rule as (the account state was not in the set(NY, NJ,
PA).


Lab 45-2 Creating Assignment Rules for Service Data

(Unguided)
Goals To create an assignment rule that assigns service data to qualified employees
Time 15 - 20
Instructions:

Organizations have many ways to assign service requests to service representatives. In this lab you
will create an assignment rule that assigns a request for service (for a product) to a representative
that is skilled in the associated product line.
1. A set of products and product lines have already been created by the product administrator. You
will examine them to become familiar with them as you will use them in creating assignment
rules and service requests.
a. Navigate to the Product Lines view and verify that three product lines exist. You will use
these product lines in creating assignment rules. What are the three Product Lines?
b. Navigate to the Products view and query for products that belong to any of the above product
lines. You will use these products in creating Service Requests.
2. A set of six employees have also been created for the purposes of this lab. They have been
assigned positions of Service Rep or Service Manager. Navigate to the Employees view and
query for employees with one of these two positions. Your results should look like this:

3. Create assignment rules based on employee skills. First add a skill attribute to an employee.
a. Select and drill down on the Colleen Commons employee record.
b. In the Assignment Skills list applet, create a new record with:
Skill Product Line
c. Observe that the Assignment Skill Items applet below displays two columns named Product
Line and Expertise. Create a new record in this applet with:
Product Line Cameras
Expertise Intermediate
d. Skill attributes have been already created for the remaining employees. Record the skills and
skill items for the employees in the table below.
Employee Skill Product Line Expertise

Colleen Commons Product Line Cameras Intermediate
Cameron Carlson
Corey Choi
Terrie Tolbert
Victor Vega
Marion May
Note that Marion May is the Service Manager, and will not be automatically assigned to a
service request. Therefore no skills have been defined for Marion.
4. Create a new assignment rule group named Service Rules Group to assign service requests to
the employee with the appropriate product line skill set.
5. Create a new assignment rule using the values below that will assign service requests based on
product line. Be sure to set the Person Candidates Source to From Rule, and the Assignee Filter
to One, Random. This selects only one qualified employee at random to be assigned to the
request.
Name Assign Service Request by Product Line
Object to be Assigned Service Request
6. In the Criteria list applet, add product criteria to the Service Request by Product Line rule
using the following values:
Rule Criterion Product Line
Comparison Method Compare Object to Person
Inclusion Include
Required Always

Note: Compare Object to Person is used here to compare the object, Service Request, to
attributes of person candidates, in this case, skill sets.

7. To prevent Assignment Manager from considering all employees in the database, explicitly
specify in the rule the six employees to be evaluated by adding them as employee candidates.
8. Activate the rule to make it available for use.
9. You will now create two service requests with the following values to test the rule:
Summary Telephone request Video request
Product T1000 Home phone center V52 large screen display
Owner <blank> <blank>
Make sure that you delete the default owner assigned to the Service Request. This allows
Assignment Manager to assign a new owner.
10. Start a batch assignment job to assign the test records by copying the previous job and changing
the parameter value to Service Request.
a. Verify the assignments.

b. To which candidate was each service request assigned? Why?
11. Create two requests for camera service and assign these new requests. First you will manually
change the status of the two requests you just assigned to prevent them from being considered for
assignment this time around.
a. Close the two service requests that were just assigned, by setting the status to Closed.
b. Create two additional service requests and assign the C5000 MagnaShot. Make sure to
delete the default owner.
c. Create and submit another Batch Assignment job. Make sure the Assignment Object is
Service Request.
d. Navigate to the All Service Requests view.

e. To which candidate was each service request assigned? Why?
f. (Optional). Repeat several times the assignments by deleting the owner and running a new
batch assignment job. Verify that the people assigned the service requests are not the same
every time, but are chosen randomly, as you specified.

Solutions 45-2 Creating Assignment Rules for Service

Data (Guided)
Answers
1.a. Navigate to the Product Lines view and verify that three product lines exist. You will use
these product lines in creating assignment rules. What are the three Product Lines?
Video, telephones, and cameras
3.d.. Skill attributes have been already created for the remaining employees. Record the skills

and skill items for the employees in the table below.
Cameron Carlson Product Line Cameras Expert
Corey Choi Product Line Cameras Expert
Terrie Tolbert Product Line Telephones Expert
Victor Vega Product Line Video Expert
Marion May
10.b. To which candidate was each service request assigned? Why?

The telephone request was assigned to TTOLBERT since her expertise in telephones. The
video request was assigned to VVEGA since his expertise in video.
11.e. To which candidate was each service request assigned? Why?

The requests are assigned to one or more of CCARLSON, CCHOI, and CCOMMONS
(since they are the employees with the camera skills). Because the rule specified an
assignee filter of One, Random, the actual assignees will vary from run to run. In addition
you may observe that both requests are assigned to the same person.


Lab 45-2 Creating Assignment Rules for Service Data

(Guided)
Goals To create an assignment rule that assigns service data to qualified employees
Instructions:

Organizations have many ways to assign service requests to service representatives. In this lab you
will create an assignment rule that assigns a request for service (for a product) to a representative
that is skilled in the associated product line.
1. A set of products and product lines have already been created by the product administrator. You
will examine them to become familiar with them as you will use them in creating assignment
rules and service requests.
a. Navigate to Administration - Product > Product Lines.
b. Verify that three product lines exist. You will use these product lines in creating assignment
rules.
c. Navigate to Administration - Product > Products.
d. Query for products that belong to any of the above product lines (Cameras, Telephones, or
Video). You will use these products in creating Service Requests.
2. A set of six employees have also been created for the purposes of this lab. They have been
assigned positions of Service Rep or Service Manager.
a. Navigate to Administration - User > Employees.

b. Query for employees with a position of Service Rep or Service Manager.
3. You will create assignment rules based on employee skills. You will add a skill attribute to an

employee.
a. Select and drill down on the Colleen Commons employee record.
b. In the Assignment Skills list applet, create a new record with:
Skill Product Line
c. Observe that the Assignment Skill Items applet below displays two columns named Product
Line and Expertise. Create a new record in this applet with:
Product Line Cameras
Expertise Intermediate
d. Skill attributes have been already created for the remaining employees. Record the skills and
skill items for the employees in the table below.
Cameron Carlson
Corey Choi
Terrie Tolbert
Victor Vega
Marion May
Note that Marion May is the Service Manager, and will not be automatically assigned to a
service request. Therefore no skills have been defined for Marion.
4. You are now ready to create a rule to assign service requests to the employee with the
appropriate product line skill set.
a. Navigate to Administration - Assignment > Rule Groups List
b. Create a new rule group with
Name Service Rules Group
5. You will create an assignment rule that assigns service requests based on product line.
a. Drill down on the Service Rules Group to navigate to the Assignment Rules list applet for
this group.


Name Assign Service Request by Product Line
Object to be Assigned Service Request
c. Drill down on Assign Service Request by Product Line to navigate to the Assignment Rule
form applet.
d. If necessary, set the Person Candidates Source to From Rule.
e. Set the Assignee Filter to One, Random. This selects only one qualified employee at random
to be assigned to the request.
6. In the Criteria list applet, add product criteria to the Service Request by Product Line rule using
the following values:
Rule Criterion Product Line

Comparison Method Compare Object to Person
Inclusion Include
Required Always
Note: Compare Object to Person is used here to compare the object, Service Request, to
attributes of person candidates, in this case, skill sets.
7. To prevent Assignment Manager from considering all employees in the database, you will
explicitly specify in the rule the employees to be evaluated.
a. Click the Employee Candidates tab.

b. Add the six employees you identified at the beginning of this lab. An easy way to enter these
employees is click New, and query for employees with a position beginning with Service.
Perform a group select on the six employees returned by the query.

8. You will next activate the rule to make it available for use.
a. Navigate to the Assignment Rules List view.
b. Click Release, and click OK to dismiss the confirmation dialog.
9. You will now create two records to test the rule.

a. Navigate to the All Service Requests view.
b. Create two service requests with:
Summary Telephone request Video request
Make sure that you delete the default owner assigned to the Service Request. This allows
Assignment Manager to assign a new owner.
10. You will now start a batch assignment job to assign the test records. An easy way to start a new
batch assignment job is to copy the previous one.
b. In the Jobs list, select the previous Batch Assignment record and right-click and select Copy
Record
c. In the Job Parameters list, change the value to Service Request.
d. Submit the job and monitor the progress by querying.
e. (Optional) Once the job has completed, read through the information in the Tasks Log view.
Remember this information also appears in the most recent batch assignment log file in the
server log directory.
f. Navigate to the All Service Requests view to verify the assignments.
g. To which candidate was each service request assigned? Why?

11. You will finally create two requests for camera service and assign these new requests. First you
will manually change the status of the two requests you just assigned to prevent them from being
considered for assignment this time around.
a. Close the two service requests that were just assigned, by setting the status to Closed.
b. Create two additional service requests and assign the C5000 MagnaShot. Make sure to
delete the default owner.
c. Create and submit another Batch Assignment job. Make sure the Assignment Object is
Service Request.
d. Navigate to the All Service Requests view.
e. To which candidate was each service request assigned? Why?
f. (Optional). Repeat several times the assignments by deleting the owner and running a new

batch assignment job. Verify that the previous owners are not always reassigned.

Solutions 45-2 Creating Assignment Rules for Service

Data (Guided)
Answers
3.d.. Skill attributes have been already created for the remaining employees. Record the skills
and skill items for the employees in the table below.

Cameron Carlson Product Line Cameras Expert
Corey Choi Product Line Cameras Expert
Terrie Tolbert Product Line Telephones Expert
Victor Vega Product Line Video Expert
Marion May
10.g. To which candidate was each service request assigned? Why?

The telephone request was assigned to TTOLBERT since her expertise in telephones. The
video request was assigned to VVEGA since his expertise in video.
11.e. To which candidate was each service request assigned? Why?

The requests are assigned to one or more of CCARLSON, CCHOI, and CCOMMONS
(since they are the employees with the camera skills). Because the rule specified an
assignee filter of One, Random, the actual assignees will vary from run to run. In addition
you may observe that both requests are assigned to the same person.

Module 46: Tailoring Assignment Rules
Lab 46-1 Prioritizing Assignment Rules (Unguided)
Goals To use rule sequencing to prioritize assignment rules
Instructions:
In addition to assigning accounts by geographic region, your company wishes to assign financial

accounts to a special account team (position is Finance Sales). In this lab you will create a rule that
uses rule sequencing to assign only the Finance Sales position to the finance accounts, regardless of
the state in which the account is located.
1. If necessary, start the Siebel Call Center Web client and log in as MPLANCK/MPLANCK.
2. Examine some seed data that was created to support assigning accounts by industry. Account
assignments can be based on a criterion called the Industry SIC Code, which will be used in this
lab.
a. Navigate to Administration - Data > Industries.
b. Inspect the seed Finance industry record.
3. Create a new assignment rule that assigns accounts based on the account's industry.
a. Create a new assignment rule with the following values:
Name Assign Finance Accounts
Rule Group Sales Rule group
b. If necessary, set the Person Candidates Source to From Rule.
c. Set the criterion as follows:
Rule Criterion Industry SIC Code
Inclusion Include
Required Always

d. Observe that the lower applet now displays columns corresponding to the Industry SIC Code
criteria. Enter the following record
SIC Low 1111
SIC High 1111
e. Click the Position Candidates tab and add the following position.
Position Finance Sales
4. Return to the Assignment Rules List and release the new rule.
5. Create two accounts to use in testing the rules using the following values:
Account name NY Express Bank of Pleasanton
Address 155 Wall Street 234 Main St

City New York Pleasanton
State NY CA
Industries Finance Finance
Make sure to assign the Industries field.
6. Test the two account assignment rules by creating and submitting a batch assignment job request.
To create the record, copy the previous batch assignment record and change the job parameter to
Account.
7. Examine the Account team for each of the four accounts.

a. List the positions assigned to each account team.
Bank of Pleasanton
Broadway Lights
Great Lakes Beef
NY Express
b. Why did NY Express have all those positions assigned to it? You might want to examine the
log files to see exactly how the assignments were made.
8. Your company's requirement is to assign finance accounts exclusively to the Finance Sales
position. You observed above that finance accounts in the east also have the regular east sales
positions also assigned. Use rule sequencing to prioritize the rules to make sure that finance
accounts are assigned only the Finance Sales position.
a. Return to the Assignment Rules List and drill down on the Sales Rule Group.

b. In the Assignment Rules list, specify the following sequence numbers:

Name Sequence
Assign East Accounts 2
Assign Finance Accounts 1
A sequence number of 1 indicates that the Assign Finance Account rule will be evaluated
first, and if any assignments can be made rule evaluation stops before consideration of other
rules with higher sequence numbers.
c. Return to the Assignment Rules List and release rules again.
9. Test the sequenced account assignment rules by copying and submitting a batch assignment job
request. Make sure the Assignment Object Name is set to Account.

10. Inspect the account teams on the accounts and verify that this time Assignment Manager assigns
only the Finance sales position to the NY Express account.
Bank of Pleasanton
Broadway Lights
Great Lakes Beef
NY Express

Solutions 46-1 Prioritizing Assignment Rules (Unguided)
Answers
7.a. List the positions assigned to each account team.
Bank of Pleasanton Finance Sales CEO (MPLANCK)

NY Express East Sales 1, East Sales 2, Finance Sales CEO (MPLANCK)
7.b. Why did NY Express have all those positions assigned to it? You might want to examine
the log files to see exactly how the assignments were made.
The NY Express account satisfied both the Assign East Accounts and Assign Finance
Accounts rules and thus had positions from both rules assigned to it.
10. Inspect the account teams on the accounts and verify that this time Assignment Manager
assigns only the Finance sales position to the NY Express account.
NY Express Finance Sales CEO (MPLANCK)

Lab 46-1 Prioritizing Assignment Rules (Guided)
Goals To use rule sequencing to prioritize assignment rules
Instructions:
In addition to assigning accounts by geographic region, your company wishes to assign financial

accounts to a special account team (position is Finance Sales). In this lab you will create a rule that
uses rule sequencing to assign only the Finance Sales position to the finance accounts, regardless of
the state in which the account is located.
2. You will first examine some seed data that was created to support assigning accounts by
industry. Account assignments can be based on a criterion called the Industry SIC Code.
a. Navigate to Administration - Data > Industries.
b. Inspect the seed Finance industry record.
3. You will now create a new assignment rule that assigns accounts based on the account's industry.
a. Navigate to Administration - Assignment > Assignment Rules List.
Name Assign Finance Accounts
Rule Group Sales Rule group
c. Drill down on Assign Finance Accounts to navigate to the Assignment Rule form applet.
d. If necessary, set the Person Candidates Source to From Rule.

4. You will now create the criterion that assigns finance accounts.
a. In the Criteria list applet, create a record with:
Rule Criterion Industry SIC Code
Inclusion Include
Required Always
b. Observe that the lower applet now displays columns corresponding to the Industry SIC Code
criteria. Enter the following record
SIC Low 1111
SIC High 1111

c. Click the Position Candidates tab and add the following position.
Position Finance Sales
5. Return to the Assignment Rules List and release the new rule.
6. You will next create two accounts to use in testing the rules.
a. Navigate the My Accounts view.
b. Create and save two accounts with the following:
Account name NY Express Bank of Pleasanton
Address 155 Wall Street 234 Main St
City New York Pleasanton
State NY CA
Industries Finance Finance
Make sure to assign the Industries field.
7. You will test the two account assignment rules by creating and submitting a batch assignment
job request.
b. In the Jobs list, select the previous Batch Assignment record and right-click and select Copy
Record
c. In the Job Parameters list, change the value to Account.
d. Submit the job and monitor the progress by querying. Wait until the job completes.
8. In the My Accounts view, examine the Account team for each of the four accounts.
a. List the positions assigned to each account team.
Bank of Pleasanton
Broadway Lights
Great Lakes Beef
NY Express

b. Why did NY Express have all those positions assigned to it? You might want to examine the
log files to see exactly how the assignments were made.
9. Your company's requirement is to assign finance accounts exclusively to the Finance Sales
position. You observed above that finance accounts in the east also have the regular east sales
positions also assigned. You will now use rule sequencing to prioritize the rules to make sure
that finance accounts are assigned only the Finance Sales position.
a. Return to the Assignment Rules List.
b. Drill down on the Sales Rule Group.

c. In the Assignment Rules list, specify the following sequence numbers:
Name Sequence
Assign East Accounts 2
Assign Finance Accounts 1
A sequence number of 1 indicates that the Assign Finance Account rule will be evaluated
first, and if any assignments can be made rule evaluation stops before consideration of other
rules with higher sequence numbers.
d. Return to the Assignment Rules List and release rules again.
10. Test the sequenced account assignment rules by copying and submitting a batch assignment job
request. Make sure the Assignment Object Name is set to Account.
11. Inspect the account teams on the accounts and verify that this time Assignment Manager assigns
only the Finance sales position to the NY Express account.
Bank of Pleasanton
Broadway Lights
Great Lakes Beef
NY Express

Solutions 46-1 Prioritizing Assignment Rules (Guided)
Answers
8.a. List the positions assigned to each account team.

NY Express East Sales 1, East Sales 2, Finance Sales CEO (MPLANCK)
8.b Why did NY Express have all those positions assigned to it? You might want to examine
the log files to see exactly how the assignments were made.
The NY Express account satisfied both the Assign East Accounts and Assign Finance
Accounts rules and thus had positions from both rules assigned to it.
11. Inspect the account teams on the accounts and verify that this time Assignment Manager
assigns only the Finance sales position to the NY Express account.
NY Express Finance Sales CEO (MPLANCK)

Lab 46-2 Using Workload Distribution (Unguided)
Goals To create a workload distribution rule that distributes service requests evenly
Instructions:
In the previous lab on assigning service requests, you created a rule that assigned a service request to

a qualified service representative. However if there were multiple qualified representatives (such as
in the case of cameras) the request was assigned randomly to a representative. This occurred because
the rule you created specified an assignee filter of One, Random.
Your company wishes to distribute the requests so as not to overload a given representative at the
expense of another. In this lab you will modify the assignment rule to include workload distribution
to ensure that the requests are assigned evenly.
1. Update the Assign Service Request by Product Line assignment rule you created in the
previous lab to use scoring to ensure that work is distributed evenly by changing the Assignee
Filter field to One, Best Fit. This causes the rule to select the best candidate based on scoring.
You will configure the candidates’ scores to depend upon their current workloads.
2. Create a workload rule that will distribute work once the conditions are met.
a. Navigate to the Workload Distribution Rules view.
b. Create a new workload distribution rule with the following values:
Name SR Workload
Assignment Object Service Request
c. In the Workload Conditions list, create the following two workload conditions:
Conditional Field Comparison Comparison
Service Request Status = Open
Service Request Sub-Status <> Waiting on Customer
3. Assign this workload distribution rule to the assignment rule.

a. Navigate back to the Assignment Rules List view.
b. Drill down on the Assign Service Request by Product Line rule.

c. Click the Workload Distribution tab and add the following workload rule to limit the
number of service requests in a service rep’s queue:
Workload Distribution Rule SR Workload
Score 5
Required Always
Maximum Workload 5
The score and maximum workload values are used to compute a workload score that favors
service reps with fewer assigned requests.
4. Return to the Assignment Rules list and click the Release button. The assignment rules are now
ready to be used.

5. Create the following three service requests to test the modified rule.
Summary WL 1 Camera WL 2 Camera WL 3 Camera
Product C5000 MagnaShot C5000 MagnaShot C5000 MagnaShot
Owner <blank> <blank> <blank>
Remember to explicitly delete the default owner assigned to the service requests.
6. Test the modified assignment rule by creating and submitting a batch assignment job request.
Make sure the Assignment Object Name is set to Service Request.
7. Navigate to the All Service Request view and verify that the three requests were assigned evenly
to the three camera-qualified service representatives.
8. Inspect the corresponding log file in the server directory to review how the requests were
assigned in an even fashion. Note how the score of each representative is decreased every time
an assignment is made to that representative. Representatives with higher scores are then
assigned requests until their scores are decreased.

Lab 46-2 Using Workload Distribution (Guided)
Goals To create a workload distribution rule that distributes service requests evenly
Instructions:
In the previous lab on assigning service requests, you created a rule that assigned a service request to

a qualified service representative. However if there were multiple qualified representatives (such as
in the case of cameras) the request was assigned randomly to a representative. This occurred because
the rule you created specified an Assignee Filter of One, Random.
Your company wishes to distribute the requests so as not to overload a given representative at the
expense of another. In this lab you will modify the assignment rule to include workload distribution
to ensure that the requests are assigned evenly.
1. You will first update the assignment rule to use scoring to ensure that work is distributed evenly.
a. Navigate to Administration - Assignment > Assignment Rules List.
b. Query for the Assign Service Request by Product Line rule you created in the previous lab.
c. In the Assignees Filter field, change the value to One, Best Fit. This causes the rule to select
the best candidate based on scoring, where the candidate score will depend upon the current
workload
2. You will next create a workload rule that will distribute work once the conditions are met.
a. Navigate to the Workload Distribution Rules view.
b. Create a new workload distribution rule with the following values:
Name SR Workload
c. In the Workload Conditions list, create the following two workload conditions:
Conditional Field Comparison Comparison
Service Request Status = Open
Service Request Sub-Status <> Waiting on Customer

3. You will now assign this workload distribution rule to the assignment rule.
a. Navigate back to the Assignment Rules List view.
b. Drilldown on the Assign Service Request by Product Line rule.
c. Click the Workload Distribution tab and add the following workload rule to limit the
number of service requests in a service rep’s queue:
Workload Distribution Rule SR Workload
Score 5
Required Always
Maximum Workload 5

The score and maximum workload values are used to compute a workload score that favors
service reps with fewer assigned requests.
4. Return to the Assignment Rules list and click the Release button. The assignment rules are now
ready to be used.
5. Create the following three service requests to test the modified rule.
Summary WL 1 Camera WL 2 Camera WL 3 Camera
Product C5000 MagnaShot C5000 MagnaShot C5000 MagnaShot
Owner <blank> <blank> <blank>
Remember to explicitly delete the default owner assigned to the service requests.
6. Test the modified assignment rule by creating and submitting a batch assignment job request.
Make sure the Assignment Object Name is set to Service Request.
7. Navigate to the All Service Request view and verify that the three requests were assigned evenly
to the three camera-qualified service representatives.
8. You will inspect the corresponding log file in the server directory to review how the requests
were assigned in an even fashion.
a. Navigate to D:\OUsea\siebsrvr\log and open the most recent log file whose name starts with
AsgnBatch_.
a. Note how the score of each representative is decreased every time an assignment is made to
that representative. Representatives with higher scores are then assigned requests until their
scores are decreased.

Module 47: Invoking Assignment Manager
Lab 47-1 Invoking Assignment Manager in Dynamic

Mode (Unguided)
Goals To use assignment manager to assign service requests dynamically as they are
created.
Instructions:

In this lab you will enable the requisite components to allow the service request assignment rule you
created in the previous labs to run dynamically, that is to assign requests in real time as they are
created
2. Examine the assignment policy for the Service Request assignment object. An assignment policy
specifies that Assignment Manager be invoked when the assignment conditions are satisfied.
a. Navigate to Administration - Assignment > Assignment Policies.
b. In the Assignment Policies list, look for an existing record with the following values:
Policy Group Assignment Group
c. Note that the policy has expired. Remove the expiration date to activate it.
3. Run a Generate Triggers job using the parameters below to create the triggers required to support
Assignment Manager.
Name Value
EXEC True
4. Start the Workflow Monitor Agent from the command line. In a previous lab, you started the
Workflow Monitor Agent from a server management view in the Siebel client. In this lab you
will use an alternative method (the command line interface) to start the Workflow Monitor
Agent. The Workflow Monitor Agent monitors tables for changes and invokes Assignment
Manager when changes are detected.
a. Open a command prompt and navigate to the D:\OUsea\siebsrvr\BIN directory.
b. Determine the name of your machine using the hostname command.

c. Enter the following command to log in to the Server Manager by entering the following
command. The parameter following the /g is the name of your machine. Replace
<MachName> with the actual name of your machine.
srvrmgr /g <MachName> /e Siebel /s OUsrvr /u SADMIN /p SADMIN
Note: Only the user name and password are case-sensitive for this command.
When you are successfully connected to server manager, you will see the prompt:
srvrmgr:OUsrvr>
d. Start the Workflow Monitor Agent task by entering the following command:
start task for component WorkMon with SleepTime=30,
GroupName=’Assignment Group’
Case is important, so be sure to enter the command as specified.
e. Verify that the task started by examining the response in the Command Prompt window:

f. Use the Exit command to exit the Server Manager.
5. In Siebel Call Center, verify that Assignment Manager is online, Server Request Broker is
running, and Workflow Monitor Agent is running.
6. Create two service requests using the values below to test the workflow:
Summary Dynamic AM 1 Dynamic AM 2
7. Verify that TTOLBERT is assigned to the first request and that VVEGA is assigned to the
second.
8. Create a service request without a product. Who is assigned?
9. Stop the Workflow Monitor Agent task to reduce the load on your Siebel server and to avoid
conflicts with subsequent labs.
10. Log out of Call Center.

Solutions 47-1 Invoking Assignment Manager in

Dynamic Mode (Unguided)
Answers
SADMIN is assigned because Assignment Manager could not find a qualified employee to
whom to assign the request. Assignment Manager then assigns the request to the default
employee (SADMIN).


Lab 47-1 Invoking Assignment Manager in Dynamic

Mode (Guided)
Goals To use assignment manager to assign service requests dynamically as they are
created.
Instructions:

In this lab you will enable the requisite components to allow the service request assignment rule you
created in the previous labs to run dynamically, that is to assign requests in real time as they are
created
2. You will examine the assignment policy for the Service Request assignment object. An
assignment policy specifies that Assignment Manager be invoked when the assignment
conditions are satisfied.
a. Navigate to Administration - Assignment > Assignment Policies.
b. In the Assignment Policies list, look for an existing record with the following values:
Policy Group Assignment Group
c. Note that the policy has expired. Remove the expiration date to activate it.
3. You will create a Generate Triggers component request in the Siebel Call Center Web client to
create the triggers required to support Assignment Manager.
c. In the Component/Job field, select Generate Triggers from the pick list. In the Job
Parameters list at the bottom of the screen, add three new parameters.
Name Value
EXEC True
4. You will run the Generate Triggers job.

a. In the Jobs list, click the Submit Job button.
b. Refresh the view by clicking Query then clicking Go to monitor the job status until the job
has completed successfully.

5. You will next start the Workflow Monitor Agent from the command line. In a previous lab, you
started the Workflow Monitor Agent from a server management view in the Siebel client. In this
lab you will use an alternative method (the command line interface) to start the Workflow
Monitor Agent. The Workflow Monitor Agent monitors tables for changes and invokes
Assignment Manager when changes are detected.
a. Select Start > Programs > Accessories > Command Prompt.
b. The Server Manager command line program resides in the D:\OUsea\siebsrvr\BIN directory.
Navigate to this directory via the command line. At the command prompt, enter
cd D:\OUsea\siebsrvr\BIN
c. Determine the name of your machine by entering the following command at the prompt
hostname
d. Log in to Server Manager by entering the following command. The parameter following the
/g is the name of your machine. Replace <MachName> with the actual name of your

machine.
srvrmgr /g <MachName> /e Siebel /s OUsrvr /u SADMIN /p SADMIN
Note: Only the user name and password are case-sensitive for this command.
When you are successfully connected to server manager, you will see the prompt:
srvrmgr:OUsrvr>
e. Start the Workflow Monitor Agent task by entering the following command at the
srvrmgr:OUsrvr> prompt:
start task for component WorkMon with SleepTime=30,
GroupName=’Assignment Group’
Case is important, so be sure to enter the command as specified.
f. Verify that the task started by examining the response in the Command Prompt window:
g. At the srvrmgr:OUsrvr> prompt enter

Exit
h. Close the Command Prompt window.
6. You will make sure that the required components are running.
a. In Siebel Call Center, navigate to Administration - Server Management > Components.
b. Verify that Assignment Manager is online, Server Request Broker is running, and Workflow
Monitor Agent is running.

7. You will now create several service requests to test the workflow.
a. Navigate to the All Service Request view.
b. Create two service requests with the following. Make sure to delete the default owner before
you save the record.
Summary Dynamic AM 1 Dynamic AM 2
c. Since the Workflow Monitor Agent runs every 30 seconds, once you have created your
service request, wait about one minute to view the results. Remember to refresh the view by
executing a series of blank queries. Moving between records in the view will not re-query.
d. Verify that TTOLBERT is assigned to the phone center request and that VVEGA is assigned

to the video request..
9. You will now stop the Workflow Monitor Agent task to reduce the load on your Siebel server
and to avoid conflicts with subsequent labs.
a. Navigate to Administration - Server Management > Tasks.
b. Select the Workflow Monitor Agent task with a state of running.
c. Click Stop.
10. Log out of Call Center.

Solutions 47-1 Invoking Assignment Manager in

Dynamic Mode (Guided)
Answers
SADMIN is assigned because Assignment Manager could not find a qualified employee to
whom to assign the request. Assignment Manager then assigns the request to the default
employee (SADMIN).

Module 48: Siebel State Model
Lab 48-1 Creating a Siebel State Model (Unguided)
Goals Create a state model to restrict the changes in the status of a service request
Instructions:
In this lab you will create a state model to manage the transitions between states in a simple four

state service request model. The states are the same as those in the example in the slides for this
module but the rules and policies are slightly different. The state model you will create is
diagrammed below.
Sub-status must
be resolved
Open Pending Closed
Must have a non- Sub-status must

Permitted only by null Area not be resolved
call center manager
Cancelled
1. Start the Siebel Call Center Developer Web client and log in as SADMIN/SADMIN connecting
2. Create a state model and identify the field upon which to base the state model.
a. Navigate to Administration - Application > State Models.
Name ABC Service Request
Field Status

3. Click the States tab and create the four states for this state model as shown below:
4. Specify the first of the six transitions for this state model. According to the specification, this
transition has a condition that the area must be set to some value; that is, it cannot be null.

a. Click the Transitions tab
From State Open
To State Pending
Public True
Rule Field Area
Rule Operator IS NOT NULL
5. Specify next transition for this state model. This transition is from Pending to Cancelled and has
a condition that the sub-status must not be resolved. Note that the sub-status value entered into
the Rule Value field must be embedded in quotes.
6. Create records for the four remaining transitions that incorporate the restrictions if any.
Remember to clear the Public flag on a transition when there are restrictions on who is allowed
to make the transition. Consult the solution to verify your configuration.
7. Create a record to specify who is authorized to make the transition from Open to Cancelled. For
the purposes of testing in this lab you will make the Siebel Administrator position the authorized
position.
a. In the Transitions list, select the Open to Cancelled transition.
b. Add the Siebel Administrator as an authorized position in the Authorized Positions applet
8. Test the state model.

b. Start the Siebel Call Center Developer Web client and log in as CCHENG/CCHENG
connecting to the Sample database in order to test the behavior using a position other than
Siebel Administrator.
c. Create a new service request. What is the state; that is, the value of the Status field in which
the service request is created?

d. Click the Status drop-down. To which states can you transition from this state?
e. Change the Status from Open to Pending. Why does the transition fail?
f. Set the Area to Printer, and then change the status to Pending. To which states can you now
transition from Pending?
9. Verify that you can progress from Pending to Closed only if the Sub-Status is set to Resolved.

10. Once you do reach Closed, transition back to Open as this transition is always allowed.
11. Similarly verify that you cannot progress from Pending to Cancelled if the Sub-Status is
Resolved.
12. Reconnect in the Siebel Administrator position and verify that you can cancel an open Service
request.
a. Select File > Connect.
b. Log in as SADMIN/SADMIN to the Sample database.
c. Create a new service request.
d. Verify that you can now proceed from Open to either Pending or Cancelled

Solutions 48-1 Creating a Siebel State Model (Unguided)
Answers
Remember to clear the Public flag on a transition when there are restrictions on who is
allowed to make the transition. Consult the solution to verify your configuration.

8.c. Create a new service request. What is the state; that is, the value of the Status field in which
Open.
8.d. Click the Status drop-down. To which states can you transition from this state?
Only the Pending state.
8.e. Change the Status from Open to Pending. Why does the transition fail?
The transition fails because the Area is Null.
8.f. Set the Area to Printer, and then change the status to Pending. To which states can you
now transition from Pending?
Open, Closed, Cancelled

Lab 48-1 Creating a Siebel State Model (Guided)
Goals Create a state model to restrict the changes in the status of a service request
Instructions:
In this lab you will create a state model to manage the transitions between states in a simple four

state service request model. The states are the same as those in the example in the slides for this
module but the rules and policies are slightly different. The state model you will create is
diagrammed below.
Sub-status must
be resolved
Open Pending Closed
Must have a non- Sub-status must

Permitted only by null Area not be resolved
call center manager
Cancelled
1. Start the Siebel Call Center Developer Web client and login into the sample database as
SADMIN/SADMIN
2. You will start by creating a state model and identifying the field upon which to base the state
model.
a. Navigate to Administration – Application > State Models.
Name ABC Service Request
Field Status

3. You will now specify the states to be included in the state model.
a. Click the States tab.
b. Create four state records as follows
State Name Description
Open Open
Pending Pending
Closed Closed
Cancelled Cancelled
c. Set the Default Flag to True for the Open state.
d. Verify that the Restrict Transition flag is set by default for all states.

4. You will specify the first of the six transitions for this state model. According to the
specification, this transition has a condition that the area must be set to some value, that is it
cannot be null.
a. Click the Transitions tab
From State Open
To State Pending
Public True
Rule Field Area
Rule Operator IS NOT NULL
5. You will specify next transition for this state model. This transition is from Pending to Cancelled
and has a condition that the sub-status must not be resolved.
a. Create a new transitions record with
From State Pending
To State Cancelled
Public True
Rule Field Sub-Status
Rule Operator <>
Rule Value "Resolved"
Note that the sub-status value entered into the Rule Value field must be embedded in quotes.

Remember to clear the Public flag on a transition when there are restrictions on who is allowed
to make the transition. Consult the solution to verify your configuration.
7. You will next create a record to specify who is authorized to make the transition from Open to
Cancelled. For the purposes of testing in this lab you will make the Siebel Administrator position
the authorized position.
a. In the Transitions list, select the Open to Cancelled transition.
b. Scroll down to the Authorized Positions applet.
c. Create a new record with Position = Siebel Administrator.
i. Click New.
ii. Select the position record with Position = Siebel Administrator and Division = Siebel
Administrator.

iii. Click OK.
8. You are now ready to test the state model.

b. Start the Siebel Call Center Developer Web client and login into the sample database as
CCHENG/CCHENG in order to test the behavior using a position other than Siebel
Administrator.
c. Navigate to Service > My Service Requests.
d. Create a new service request. What is the state, that is the value of the Status field, in which
e. Click the Status drop-down. To which states can you transition from this state?
f. Change the Status from Open to Pending. Why does the transition fail?
g. Set the Area to Printer, and then change the status to Pending. To which states can you now
transition from Pending?
9. Verify that you can progress from Pending to Closed only if the Sub-Status is set to Resolved.
10. Once you do reach Closed, transition back to Open as this transition is always allowed.
11. Similarly verify that you cannot progress from Pending to Cancelled if the Sub-Status is
Resolved.
12. You will reconnect in the Siebel Administrator position and verify that you can cancel an open
Service request.
a. Select File > Connect.
b. Log in as SADMIN/SADMIN to the Sample.

c. Navigate to Service > My Service Requests.

d. Create a new service request.
e. Verify that you can now proceed from Open to either Pending or Canceled

Solutions 48-1 Creating a Siebel State Model (Guided)
Answers
5. Create records for the five remaining transitions that incorporate the restrictions if any.
Remember to clear the Public flag on a transition when there are restrictions on who is
allowed to make the transition. Consult the solution to verify your configuration.

8.d. Create a new service request. What is the state, that is the value of the Status field, in which
Open.
8.e. Click the Status drop-down. To which states can you transition from this state?
Only the Pending state.
8.f. Change the Status from Open to Pending. Why does the transition fail?
The transition fails because the Area is Null.
8.g. Set the Area to Printer, and then change the status to Pending. To which states can you
now transition from Pending?
Open, Closed, Cancelled


Module 50: Creating Data Maps
Lab 50-1 Data Mapping: Solutions (Unguided)
Goals To map external data to Siebel EIM tables for import into Siebel base tables.
Instructions:
You have been given a file of legacy solutions data that you have to import into the Siebel database.

Solutions are answers to common customer issues, typically in the form of frequently asked
questions (FAQs). You need to construct a data mapping table that identifies how the external source
data maps to the EIM table, and how the EIM table maps to the base table.
1. Examine the legacy solutions data.

a. Navigate to D:\Labs\Essentials and open solution.txt.
b. Examine the records in this file. A vertical line (|) is used as a delimiter between attributes.
solution.txt contains seven records with the following five attributes:
Name | FAQ | Answer | Solution Type | Status
Two additional attributes will be added later: flags that specify whether the solution will be
published internally and/or externally.
2. You will be mapping this solution data to the Siebel database, with interface tables acting as an
intermediate staging area. First, you will start with the Siebel user interface (UI), where you will
map the solution attributes you inspected earlier to list columns and controls in the Siebel
application. You will trace these to database columns. As the final step in your mapping, you
will determine the appropriate EIM (interface) table and columns to use for the data transfer.
You have already explored the Siebel application and have an idea which view might hold the
solutions data. Determine which list columns and controls will hold each attribute.
b. Navigate to Administration - Solution > Solutions. Which business component is used in the
applets?
c. What is the name of the form applet?

d. Which controls in the form applet look like candidates to hold the source data for the
following?
Attribute Control
Name
FAQ
Answer
Solution Type
Status
Publish flag internal
Publish flag external

3. Use Siebel Tools to map the controls you selected to the underlying business component fields
and database columns.
a. If necessary, start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample
database.
b. Navigate to the applet you found above and view the applet Web template in 1: Edit mode
using the Web Layout editor. Note that you will be examining this applet in read-only mode.
c. In the Layout window, select the Name text box. Which field does Name map to?
d. Repeat this process to identify the fields for the other six source attributes and complete this
table:
Attribute Control Field
Name Name Name
FAQ FAQ
Answer Description
Solution Type Type
Status Status
Publish flag internal Publish Internal
Publish flag external Publish External
e. Navigate to the business component you found above. What is this business component’s
base table?

f. Use the View Details tool, locate each field you identified, and determine the base table
column it maps to. Fill in the target columns in this table:
Attribute Control Field Column
Name Name Name
FAQ FAQ FAQ
Answer Description Solution
Solution Type Type Solution Type
Status Status Status
Publish flag internal Publish Internal Publish Internal
Publish flag external Publish External Publish External

4. Use the table below (and/or the copy at the end of this exercise) to document legacy data to EIM
table/column to base table/column mappings. At the completion of this lab, you will have filled
in all the missing values in this table.
Attribute EIM Table EIM Column Base Table Base Column Default
Name NAME S_RESITEM NAME
FAQ S_RESITEM FAQ_QUES_TEXT
Answer S_RESITEM RESOLUTION_

TEXT
Solution Type S_RESITEM TYPE_CD
Status S_RESITEM STATUS_CD
Publish flag
S_RESITEM INTR_PUBLISH_
internal FLG
Publish flag
S_RESITEM PUBLISH_FLG
external
None S_RESITEM SOLUTION_ITEM_

FLG
Row ID for
BU_ID
None ORG_BU S_RESITEM Default
Organization

5. Use Siebel Tools to determine if there are additional required non-system columns for the base
table. Record these required columns in the previous table. These user data columns in the base
table must contain values, which you must provide in your mapping.
6. Examine the Default property for each of these columns and add these values to the mapping
table in the far right column.
7. Find candidate EIM tables.

a. In Siebel Tools, confirm that the EIM Interface Table object appears in the Object Explorer,
along with its child object types. If necessary, display these object types.
b. In the OE, select the Flat tab, then select the EIM Table Mapping object.
c. Execute a query where:

Parent EIM Interface Table = EIM*
Destination Table = S_RESITEM
d. Which parent EIM table is a candidate for your mapping?
e. Why did you search for Destination Table = S_RESITEM?
8. Generate the EIM Interface Tables report. You will use this report to determine which EIM
columns you need to populate the target base table columns.
a. Return to the Types tab in the OE and select EIM Interface Table :: EIM_SOLUTION.
b. Select Reports > EIM Interfaces Tables.
Note: You may get an error dialog titled axdesk. This is a known issue with Tools. To
proceed:
i. Click No.
ii. Click OK in the siebdev dialog box.
iii. Again, click OK in the siebdev dialog box.
iv. Close the Siebel Report Viewer Window.
v. Select Reports > EIM Interface Tables again. This time you should see the report for
EIM_SOLUTION.
c. Locate S_RESITEM in the Destination Table column of the report.
d. Fill in the EIM table and source column values in your mapping, using the values in the
report.
9. Verify your mappings against the solution, either at the end of this lab or in
D:\Labs\Essentials\solution_mapping_end.html.

Solutions 50-1 Data Mapping: Solutions (Unguided)
Answers
2.b. Navigate to Administration - Solution > Solutions. Which business component is used in
the applets?
Solution Admin
2.c. What is the name of the form applet?

Solution Form Applet w/Publish Internal w/NB

2.d. Which controls in the form applet look like candidates to hold the source data for the
following?
Attribute Control
Name Name
FAQ FAQ
Answer Description
Solution Type Type
Status Status
3.c. In the Layout window, select the Name text box. Which field does Name map to?
Name
3.d. Repeat this process to identify the fields for the other six source attributes and complete
this table:
Name Name Name
FAQ FAQ FAQ
3.e. Navigate to the business component you found above. What is this business component’s
base table?
S_RESITEM

3.f. Use the View Details tool, locate each field you identified, and determine the base table
column it maps to. Fill in the target columns in this table:
Name Name Name NAME
FAQ FAQ FAQ FAQ_QUES_TEXT
Answer Description Solution RESOLUTION_TEXT
Solution Type Type Solution Type TYPE_CD
Status Status Status STATUS_CD
Publish flag internal Publish Internal Publish Internal INTR_PUBLISH_FLG
Publish flag external Publish External Publish External PUBLISH_FLG

7.d. Which parent EIM table is a candidate for your mapping?
EIM_SOLUTION
7.e. Why did you search for Destination Table = S_RESITEM?

S_RESITEM is the target base table you wish to populate.
Completed Solutions Mapping
Source EIM Table EIM Column Base Table Base Column Default
Attribute
Name EIM_SOLUTION NAME S_RESITEM NAME
FAQ EIM_SOLUTION FAQ_QUES_TEXT S_RESITEM FAQ_QUES_TEXT
Answer EIM_SOLUTION RESOLUTION_TEXT S_RESITEM RESOLUTION_TEXT
Solution EIM_SOLUTION SOLN_TYPE_CD S_RESITEM TYPE_CD

Type
Status EIM_SOLUTION STATUS_CD S_RESITEM STATUS_CD
Publish EIM_SOLUTION INTR_PUBLISH_FLG S_RESITEM INTR_PUBLISH_FLG

Internal
Flag
Publish EIM_SOLUTION PUBLISH_FLG S_RESITEM PUBLISH_FLG

External
Flag
none EIM_SOLUTION SOLUTION_ITEM_FLG S_RESITEM SOLUTION_ITEM_FLG N
none EIM_SOLUTION ORG_BU S_RESITEM BU_ID Row ID for

Default
Organization

Lab 50-1 Data Mapping: Solutions (Guided)
Instructions:
You have been given a file of legacy solutions data that you have to import into the Siebel database.

Solutions are answers to common customer issues, typically in the form of frequently asked
questions (FAQs). You need to construct a data mapping table that identifies how the external source
data maps to the EIM table, and how the EIM table maps to the base table.
1. You will start by examining the legacy solutions data.

a. Navigate to D:\Labs\Essentials and open solution.txt.
b. Examine the records in this file. A vertical line (|) is used as a delimiter between attributes.
solution.txt contains seven records with the following five attributes:
Name | FAQ | Answer | Solution Type | Status
Two additional attributes will be added later: flags that specify whether the solution will be
published internally and/or externally.
c. Close solution.txt.
2. You will be mapping this solution data to the Siebel database, with interface tables acting as an
intermediate staging area. First, you will start with the Siebel user interface (UI), where you will
map the solution attributes you inspected earlier to list columns and controls in the Siebel
application. You will trace these to database columns. As the final step in your mapping, you
will determine the appropriate EIM (interface) table and columns to use for the data transfer.
You have already explored the Siebel application and have an idea which view might hold the
solutions data. You will determine which list columns and controls will hold each attribute.
b. Navigate to Administration – Solution > Solutions.
c. Select Help > About View. Which business component is used in the applets?
d. What is the name of the form applet?

e. Which controls in the form applet look like candidates to hold the source data for the
following?
Attribute Control
Name
FAQ
Answer
Solution Type
Status
Publish flag internal
Publish flag external

3. You will use Siebel Tools to map the controls you selected to the underlying business component
fields and database columns.
Hint: Use the bookmark function to speed your navigation in this lab.
b. Select Applet :: Solution Form Applet w/Publish Internal w/NB.
c. What is the business component for this applet?
d. View the applet Web template using the Web Layout editor.
i. Right-click the applet and select Edit Web Layout.
ii. Click OK in the Read-only Object dialog
iii. Close the Palettes window.
iv. Use the Controls/Columns window to verify that the 1: Edit mode is selected. You
may have to use View > Windows > Controls to open this window. You may close
this window after verifying the mode.
e. In the Layout window, select the Name text box.
f. Which field does Name map to?
Hint: Use the Properties window.
g. Repeat this process to identify the fields for the other six source attributes and complete this
table:
Name Name Name
FAQ FAQ
Answer Description
Solution Type Type
Status Status

h. Close the Applet Web Template.

i. Select Business Component :: Solution Admin.
j. What is this business component’s base table?
k. With Solution Admin selected, right-click and select View Details.

l. In BusComp Solution Admin, select each field you identified and determine the
S_RESITEM column it maps to. Fill in the target columns in this table:
Name Name Name
FAQ FAQ FAQ

4. You will use the table below (and/or the copy at the end of this exercise) to document legacy
data to EIM table/column to base table/column mappings. At the completion of this lab, you will
have filled in all the missing values in this table.
Name NAME S_RESITEM NAME
FAQ S_RESITEM FAQ_QUES_TEXT
Answer S_RESITEM RESOLUTION_

TEXT
Solution Type S_RESITEM TYPE_CD
Status S_RESITEM STATUS_CD
Publish flag
S_RESITEM INTR_PUBLISH_
internal FLG
Publish flag
S_RESITEM PUBLISH_FLG
external
None S_RESITEM SOLUTION_ITEM_

FLG
Row ID for
BU_ID
None ORG_BU S_RESITEM Default
Organization

5. You will use Siebel Tools to determine if there are additional required columns for the base
table. Record these required columns in the previous table.
a. In Siebel Tools, select Table :: S_RESITEM | Column.
b. Query for additional required, non-system columns:
Required: TRUE (checked)
Type: <>System
These user data columns in the base table must contain values, which you will provide in
your mapping.
c. Verify that these columns are in your mapping table. In addition, examine the Default
property for each of these columns and add these values to the mapping table in the far right
column.

6. You will find candidate EIM tables.
a. In Siebel Tools, confirm that the EIM Interface Table object appears in the Object Explorer,
along with its child object types.
i. Select View > Options to display the Development Tools Options dialog box.
ii. Click the Object Explorer tab.
iii. Expand the EIM Interface Table node and check the three child check boxes.
iv. Click OK.
b. In the OE, select the Flat tab, then select the EIM Table Mapping object.
c. Execute a query where:
Parent EIM Interface Table = EIM*
Destination Table = S_RESITEM
d. Which parent EIM table is a candidate for your mapping?
e. Why did you search for Destination Table = S_RESITEM?
7. You will generate the EIM Interface Tables report. You will use this report to determine which
EIM columns you need to populate the target base table columns.
a. Click the Types tab in the OE
b. Select EIM Interface Table in the OE.
c. Query for the EIM_SOLUTION table.
d. Select Reports > EIM Interfaces Tables.
Note: You may get an error dialog titled axdesk. This is a known issue with Tools. To
proceed:
i. Click No.
ii. Click OK in the siebdev dialog box.
iii. Again, click OK in the siebdev dialog box.
iv. Close the Siebel Report Viewer Window.

v. Select Reports > EIM Interface Tables again. This time you should see the report for
EIM_SOLUTION.
e. Locate S_RESITEM in the Destination Table column of the report.
f. Fill in the EIM table and source column values in your mapping, using the values in the
report.
Hint: Click the right arrow icon to advance to the next page of the report.
g. At this point, you would typically identify any required columns in the EIM interface table
by looking at the Required property for EIM Interface Table :: EIM_SOLUTION | EIM
Interface Table Column, but the EIM_SOLUTION table does not have any such columns.
h. Close the report.
8. Verify your mappings against the solution.

a. Navigate to D:\Labs\Essentials and open solution_mapping_end.html.

b. Compare your mappings and make sure they match. (The same completed mapping can be
found at the end of the Solutions following this lab.)
c. Close solution_mapping_end.html.

Solutions 50-1 Data Mapping: Solutions (Guided)
Answers
2.c. Select Help > About View. Which business component is used in the applets?
Solution Admin
2.d. What is the name of the form applet?

Solution Form Applet w/Publish Internal w/NB
2.e. Which controls in the form applet look like candidates to hold the source data for the

following?
Attribute Control
Name Name
FAQ FAQ
Answer Description
Solution Type Type
Status Status
3.c. What is the business component for this applet?

Solution Admin
3.f. Which field does Name map to?

Name
3.g. Repeat this process to identify the fields for the other six source attributes and complete
this table:
Name Name Name
FAQ FAQ FAQ
3.j. What is this business component’s base table?

S_RESITEM

3.l. In BusComp Solution Admin, select each field you identified and determine the
S_RESITEM column it maps to. Fill in the target columns in this table:
Name Name Name NAME
FAQ FAQ FAQ FAQ_QUES_TEXT
Answer Description Solution RESOLUTION_TEXT
Solution Type Type Solution Type TYPE_CD
Status Status Status STATUS_CD
Publish flag internal Publish Internal Publish Internal INTR_PUBLISH_FLG
Publish flag external Publish External Publish External PUBLISH_FLG

6.d. Which parent EIM table is a candidate for your mapping?
EIM_SOLUTION
6.e. Why did you search for Destination Table = S_RESITEM?

S_RESITEM is the target base table you wish to populate.

Completed Solutions Mapping
Source EIM Table EIM Column Base Table Base Column Default
Attribute
Name EIM_SOLUTION NAME S_RESITEM NAME
FAQ EIM_SOLUTION FAQ_QUES_TEXT S_RESITEM FAQ_QUES_TEXT
Answer EIM_SOLUTION RESOLUTION_TEXT S_RESITEM RESOLUTION_TEXT
Solution EIM_SOLUTION SOLN_TYPE_CD S_RESITEM TYPE_CD

Type

Status EIM_SOLUTION STATUS_CD S_RESITEM STATUS_CD
Publish EIM_SOLUTION INTR_PUBLISH_FLG S_RESITEM INTR_PUBLISH_FLG

Internal
Flag
Publish EIM_SOLUTION PUBLISH_FLG S_RESITEM PUBLISH_FLG

External
Flag
none EIM_SOLUTION SOLUTION_ITEM_FLG S_RESITEM SOLUTION_ITEM_FLG N
none EIM_SOLUTION ORG_BU S_RESITEM BU_ID Row ID for

Default
Organization

Lab 50-2 Data Mapping: Products (Optional)
Instructions:

You have been given a file of legacy product data that you need to import into the Siebel database.
You need to construct a data mapping worksheet that identifies how the external source data maps to
the EIM table and to the base table.
In this lab you will do more work on your own. The instructions are less explicit, and the mapping is
slightly more complex than the solutions mapping.
1. You will examine the legacy data.

a. Navigate to D:\Labs\Essentials and open product.txt. This file contains legacy product data.
b. A vertical line (|) is used as a delimiter between attributes. It contains eight records with the
following three attributes per record:
Attribute
Product Number
Product Name
Unit
c. When you are done examining the product data, close product.txt.
2. You will map the data to Siebel base tables by working backwards from the UI and using Siebel
Tools to determine which fields and database columns are behind the applet.
a. In Siebel Call Center, find an applet that contains the data you need to import.
Hint: Navigate to the Products > Internal Product List.
b. What business component is used for the applets?
c. What is the name of the form applet?
d. In Siebel Tools, find the base table for the business component you identified. What is the
base table?

e. Which three fields look like target fields for the source data?
Hint: Inspect the applet using the Edit Web Layout view.
Attribute Field
Product Number
Product Name
Unit
f. Which three columns in the base table map to the fields you identified in the previous step?
Hint: Inspect the business component using the details view.
Attribute Field Column

Product Number Part #
Product Name Name
Unit Unit of Measure
3. The table on the next page has been started to document your mappings. You need to complete
the table by filling in empty cells. Enter the information you have discovered so far into columns
labeled Base Table and Base Column. As you complete the next steps in this lab, fill in the
remaining empty cells.

Source
EIM Table EIM Column Base Table Base Column Default
Attribute
Product
EIM_PROD_INT PART_NUM S_PROD_INT PART_NUM
number
EIM_PROD_INT
Unit of
EIM_PROD_INT
Measure
none EIM_PROD_INT ACTIVE_FLG S_PROD_INT ACTIVE_FLG Y
PRODAPPLYEC APPLY_EC_
none EIM_PROD_INT S_PROD_INT N
RULEFLG RULE_FLG

AUTO_ AUTO_
UNGROUP_FLG UNGROUP_FLG
none EIM_PROD_INT PROD_BU S_PROD_INT BU_ID
none EIM_PROD_INT CMPND_FLG S_PROD_INT CMPND_FLG N

COMPENSATABLE_ COMPENSATABLE_
none EIM_PROD_INT S_PROD_INT Y
FLG FLG
CRT_AGREEMENT_ CRT_AGREEMENT_
FLG FLG
none EIM_PROD_INT CRT_AST_REC_FLG S_PROD_INT CRT_AST_REC_FLG Y
none EIM_PROD_INT CRT_INST_FLG S_PROD_INT CRT_INST_FLG Y
none EIM_PROD_INT ENTERPRISE_FLG S_PROD_INT
none EIM_PROD_INT FEATURED_FLG S_PROD_INT
INCLSV_ELIG_
none EIM_PROD_INT S_PROD_INT
RL_FLG
PROD_
none EIM_PROD_INT S_PROD_INT
INCLALLCRSEFLG
none EIM_PROD_INT ORDERABLE_FLG S_PROD_INT
POSTN_BL_ POSTN_BL_
PROD_FLG PROD_FLG
none EIM_PROD_INT S_PROD_INT SALES_PROD_FLG Y
none EIM_PROD_INT S_PROD_INT SALES_SRVC_FLG N
TARGET_ TARGET_
VRSN_FLG VRSN_FLG
TAX_SUBCOMP_ TAX_SUBCOMP_
FLG FLG
none EIM_PROD_INT VIS_ACTIVE_FLG ACTIVE_FLG Y
Default
none EIM_PROD_INT VIS_BU S_PROD_INT_BU BU_ID
Organization
VIS_ORDERABLE_
none EIM_PROD_INT S_PROD_INT_BU ORDERABLE_ FLG Y
FLG
none EIM_PROD_INT Y

4. You will use Siebel Tools to determine the required columns for the S_PROD_INT table, and the
default value for each.
a. In Tools, Table :: S_PROD_INT | Column.
b. Execute a query where:
Required: TRUE
Type: <> System
Note: You may want to reorder the columns to see both columns easily.
c. Add the Base Table and Base Column values to your table.
d. For the required columns for which you have values, record the default value listed in Siebel
Tools on your spreadsheet in the Default column.
Hint: Remember that the BU_ID columns on the base tables must be populated with the

organization name, not the row ID.
e. Now that you have identified the base (target) table and columns, you need to find candidate
EIM tables. What are the candidate parent interface tables?
Hint: Refer to the previous lab for detailed instructions.
f. What is the best candidate EIM table and why?
5. You will generate the EIM Interface Tables report. Use this report to determine the column
mappings, that is, which EIM columns you need to load to populate your target base table
columns.
a. Fill in the EIM Table and EIM Column columns of the mapping table using information
from the EIM Interface Tables report.
b. At this point, you would identify any additional required columns for the EIM interface table
by checking the required property for columns in this table. However, the EIM_PROD_INT
table does not have any such required columns.
c. The interface table, EIM_PROD_INT, maps to two tables; S_PROD_INT and the
intersection table, S_PROD_INT_BU. The intersection table stores the organization
associated with a product and its required fields must be populated as well. Inspect the
Required columns of the intersection table, S_PROD_INT_BU. Add the required values to
the mapping spreadsheet.
Hint: Query for Required = TRUE and Type = <>System AND <> Denormalized. You do
not need to include the PROD_INT_ID column as it will be resolved by EIM.
d. Close the report.

6. Finally, you will verify your mappings against the solution.

a. Navigate to D:\Labs\Essentials and open product_mapping_end.html.
b. Verify that your mappings match the solutions.
c. If they do not, double-check your work or ask your instructor for assistance.
Note: You will use the mappings in a later lab.
7. Close product_mapping_end.html.

Solutions 50-2 Data Mapping: Products (Optional)
Answers:
2.b. What business component is used for the applets?
Internal Product
2.c. What is the name of the form applet?

CX Product Form Applet
2.d. In Siebel Tools, find the base table for the business component you identified. What is the

base table?
S_PROD_INT
2.e. Which three fields look like target fields for the source data?
Hint: Inspect the applet using the Edit Web Layout view.
Attribute Field
Product Number Part #
Product Name Name
Unit Unit of Measure
2.f. Which three columns in the base table map to the fields you identified in the previous step?
Hint: Inspect the business component using the details view.
Attribute Field Column
Product Number Part # PART_NUM
Product Name Name NAME
Unit Unit of Measure UOM_CD
4.e. Now that you have identified the base (target) table and columns, you need to find
candidate EIM tables. What are the candidate parent interface tables?
Hint: Refer to the previous lab for detailed instructions.
EIM_PROD_INT
EIM_PROD_INT_UK
EIM_PROD_INT1
EIM_PRDINT_DTL
EIM_PROD_INT2
EIM_COURSE
EIM_PROD_INT3
4.f. What is the best candidate EIM table and why?

EIM_PROD_INT has the most column mappings to S_PROD_INT and contains mappings
for the columns you need to import, which is verified by looking at the EIM table report.

Completed Product Mapping

Product
EIM_PROD_INT PART_NUM S_PROD_INT PART_NUM
number
Product
EIM_PROD_INT NAME S_PROD_INT NAME
Name
Unit of
EIM_PROD_INT UOM_CD S_PROD_INT UOM_CD
Measure
none EIM_PROD_INT ACTIVE_FLG S_PROD_INT ACTIVE_FLG Y
PRODAPPLYEC APPLY_EC_
RULEFLG RULE_FLG
AUTO_ AUTO_

UNGROUP_FLG UNGROUP_FLG
Default
none EIM_PROD_INT PROD_BU S_PROD_INT BU_ID
Organization
none EIM_PROD_INT CMPND_FLG S_PROD_INT CMPND_FLG N
COMPENSATABLE_ COMPENSATABLE_
none EIM_PROD_INT S_PROD_INT Y
FLG FLG
CRT_AGREEMENT_ CRT_AGREEMENT_
FLG FLG
none EIM_PROD_INT CRT_AST_REC_FLG S_PROD_INT CRT_AST_REC_FLG Y
none EIM_PROD_INT CRT_INST_FLG S_PROD_INT CRT_INST_FLG Y
none EIM_PROD_INT ENTERPRISE_FLG S_PROD_INT ENTERPRISE_FLG N
none EIM_PROD_INT FEATURED_FLG S_PROD_INT FEATURED_FLG N
INCLSV_ELIG_ INCLSV_ELIG_
RL_FLG RL_FLG
PROD_ INCL_ALL_
INCLALLCRSEFLG CRSE_FLG
none EIM_PROD_INT ORDERABLE_FLG S_PROD_INT ORDERABLE_ FLG Y
POSTN_BL_ POSTN_BL_
PROD_FLG PROD_FLG
none EIM_PROD_INT SALES_PROD_FLG S_PROD_INT SALES_PROD_FLG Y
none EIM_PROD_INT SALES_SRVC_FLG S_PROD_INT SALES_SRVC_FLG N
TARGET_ TARGET_
VRSN_FLG VRSN_FLG
TAX_SUBCOMP_ TAX_SUBCOMP_
FLG FLG
none EIM_PROD_INT VIS_ACTIVE_FLG S_PROD_INT_BU ACTIVE_FLG Y
Default
none EIM_PROD_INT VIS_BU S_PROD_INT_BU BU_ID
Organization
VIS_ORDERABLE_
none EIM_PROD_INT S_PROD_INT_BU ORDERABLE_ FLG Y
FLG
VIS_SALES_
none EIM_PROD_INT S_PROD_INT_BU SALES_ PROD_FLG Y
PROD_FLG


Module 51: Running Enterprise Integration Manager
Lab 51-1 Loading EIM Tables with Legacy Data

(Unguided)
Goals To use SQL scripts written by a database administrator to load legacy solution and
product data from files into the appropriate EIM interface tables.
Instructions:

Due to the fact that this lab uses non-Oracle software to update the Siebel database, there is no
Unguided version of it. Please turn the page and do the Guided version.


Lab 51-1 Loading EIM Tables with Legacy Data (Guided)
Goals To use SQL scripts written by a database administrator to load legacy solution and
product data from files into the appropriate EIM interface tables.
Instructions:

In a prior lab, you mapped legacy solution data to the Siebel EIM and destination tables. You are
ready to populate the EIM table in preparation for running an EIM task to import the data. In
practice, this step typically involves a dedicated tool to load the legacy data to the Siebel EIM tables.
You will use SQL scripts to load the relatively simple legacy data in this and the next lab. The SQL
scripts are simple and clearly illustrate how data is loaded into the EIM interface tables.
1. You will examine the legacy data and compare the values with the mapping you did in a
previous lab.
a. Navigate to D:\Data\Essentials and open solution_import.txt.
b. Inspect the file. A vertical line (|) is used as a delimiter between attributes. Notice that the file
contains values for the three required EIM columns.
c. Refer to your solution mapping table, or open solution_mapping_end.html. Compare the
rows in this table with the columns in solution_import.txt. Which columns in
EIM_SOLUTION that you mapped are not shown in the legacy data file?
2. You will execute a SQL script to import data from solution_import.txt to the EIM_SOLUTION
table.
Express.
b. Click Connect.
c. Select File > Open > File. Navigate to D:\Labs\Essentials and open solution.sql.
d. Click Connect.
e. Examine the SQL script.
i. Scroll down to the update statement following the comment labeled 3.b.
ii. Which EIM_SOLUTION columns are updated in this step?
iii. How were the values for these columns chosen?

f. Click Execute from the toolbar (or type F5) to run the script. Ignore any warning messages
in the Messages tab.
g. Click the Results tab in the lower pane. Scroll down and examine the script output. You
should see the output from two select statements. The first select displays the contents of the
tempdb..mytemp table, where data is staged in preparation for movement to
siebeldb..EIM_SOLUTION. The second select outputs the columns in EIM_SOLUTION
populated by the script, including the two required non-system columns.
Contents of
mytemp table

Contents of
EIM_SOLUTION
table
Screenshot from Microsoft SQL Server Management Studio Express copyright © Microsoft Inc.
h. Compare the second select output against the legacy file solution_import.txt. Verify that the
legacy data was mapped correctly.
i. Leave Microsoft SQL Server Management Studio Express open.
j. Close solution_import.txt.
3. Next, you will load legacy product information into the EIM_INT_PROD table using another
script.
a. Navigate to D:\Labs\Essentials and open product_import.txt.
b. As with the solutions data, attributes are separated by a vertical line. Each row contains the
three mandatory EIM columns (ROW_ID, IF_ROW_BATCH_NUM, and IF_ROW_STAT)
and product attributes (Product Number, Product Name, and Unit of Measure).
c. Open product_mapping_end.html or refer to your completed mapping table. How many
additional columns must be mapped in EIM_PROD_INT?
d. Why do these columns in EIM_PROD_INT need to be populated?

e. Which base tables will ultimately be populated from EIM_PROD_INT?
f. Close product_mapping_end.html.
4. You will execute a script to load the legacy product data into EIM_PROD_INT.
a. Return to SQL Server 2005 Management Studio.
b. Select File > Open > File and open product.sql.
c. Click Connect.
d. Examine the SQL script. It is similar to the script for loading solutions, although there are
significantly more non-system required columns. (See step 3b. in the SQL script.)
e. Execute the script.
f. Click the Results tab and examine the output. As for the solutions script, the first select

output shows the values stored in a temporary table, while the second shows all the columns
populated in EIM_PROD_INT.
g. Close product_import.txt and SQL Server 2005 Management Studio Express.
5. Log out of Siebel Tools.

Solutions 51-1 Loading EIM Tables with Legacy Data

(Guided)
Answers
1.c. Refer to your solution mapping table, or open solution_mapping_end.html. Compare the
rows in this table with the columns in solution_import.txt. Which columns in
EIM_SOLUTION that you mapped are not shown in the legacy data file?
SOLUTION_ITEM_FLG and ORG_BU

2.e.ii. Which EIM_SOLUTION columns are updated in this step?
SOLUTION_ITEM_FLG and ORG_BU
2.e.iii. How were the values for these columns chosen?

These columns are populated with default values.
3.c. Open product_mapping_end.html or refer to your completed mapping table. How many
additional columns must be mapped in EIM_PROD_INT?
23
3.d. Why do these columns in EIM_PROD_INT need to be populated?

They are required non-system columns, which the script populates with their default
values.
3.e. What base tables will ultimately be populated from EIM_PROD_INT?

S_PROD_INT and S_PROD_INT_BU

Lab 51-2 Running EIM to Import Solution Data

(Unguided)
Goals To run EIM jobs to load legacy solution from the EIM_SOLUTION interface table to
destination tables.
Instructions:

You have loaded legacy solution data into EIM_SOLUTION. In this lab, you will run an EIM job to
import this data into the Siebel destination table, S_RESITEM. The steps you will take include:
• Configure system preferences for running an EIM import job
• Examine an EIM configuration file (.ifb) provided to you
• Enable the EAI component group, which includes the EIM server component
• Create and submit an EIM job
• Examine the results of this job and clean up
1. The default value for the EIM configuration file is default.ifb, located in
D:\OUsea\siebsrvr\ADMIN in your lab installation. If you do not change this parameter and run
EIM by mistake, this might produce unintended results. To prevent errors, rename default.ifb to
default_original.ifb.
2. Before your initial data loads, it is a good idea to turn off Siebel Remote’s transaction logging.
This function normally tracks database changes and allows data to be synchronized in the future
with remote clients. However, this capability comes with a performance cost, which will slow
down data loads. Best practice is to disable transaction logging for sizeable initial data loads, re-
enable transaction logging, and then perform a new database extract for clients.
b. Navigate to the Remote System Preferences view and turn off transaction logging.
3. Examine the EIM configuration file and move it to the proper location. Another team member
built a configuration (.ifb) file to be used to run the EIM task to import solution data. She copied
the default_original.ifb file, renamed it, and edited it.
a. Use Notepad to open D:\Labs\Essentials\solution.ifb.
b. Why is the BATCH = 100?

c. Why is the TABLE = EIM_SOLUTION?
d. Copy solution.ifb to D:\OUsea\siebsrvr\ADMIN.
4. Verify that the Enterprise Application Integration component group is enabled on the Siebel
server. If it is not, enable it and restart the server.
5. Inspect what data is already in the tables before you invoke EIM.
a. If necessary, start SQL Server Management Studio Express by selecting Start > Programs >
Microsoft SQL Server 2005 > SQL Server Management Studio Express.

b. Click Connect.
c. Click New Query on the toolbar.
d. In the main pane, enter:
select NAME from siebeldb..S_RESITEM
In this statement, the column, database, and table names are case-sensitive.
e. Click Execute to run the query.
f. Were any names returned?
g. Leave Management Studio open.
6. Create and submit an EIM job based on the Enterprise Integration Mgr component to populate
the base table from the interface table using the .ifb file. Use the following job parameters:
Name Configuration file
Value solution.ifb
7. Check to see if the import was successful.

a. Return to SQL Server Management Studio Express.
b. Query the IF_ROW_STAT column in the interface table EIM_SOLUTION.
i. Click New Query.
ii. In the new query pane, enter the following:
select NAME, IF_ROW_STAT from siebeldb..EIM_SOLUTION
iv. The IF_ROW_STAT value for each row should be set to ‘IMPORTED’.
c. Return to the pane containing your previous query on S_RESITEM and execute your query
again.
d. Modify the query to include other imported legacy data: FAQ_QUES_TEXT,
RESOLUTION_TEXT, TYPE_CD, and STATUS_CD. Ensure that the rows from the

solution.txt input file are reflected in the base table.
e. Use Siebel Call Center to verify the data. Navigate to Solutions > Solution List and compare

the solution records with the legacy data.
8. If the EIM import was successful, delete the rows from the interface table.
a. Create a new query and run the following SQL statement to clear out the interface table:
truncate table siebeldb..EIM_SOLUTION
b. Why should you clear the interface table?
c. Why is it not recommended to run a drop table?

Solutions 51-2 Running EIM to Import Solution Data

(Unguided)
Answers
3.b. Why is the BATCH = 100?
To match the batch number set for the solution data loaded into EIM_SOLUTION
3.c. Why is the TABLE = EIM_SOLUTION?

This table contains the solution data you loaded earlier and is mapped to the base table for

Solution, S_RESITEM.
5.f. Were any names returned?

Yes. Several records were already in the server database: ABC Copier (twice), ABC Fax,
and How to Contact Us.
8.b. Why should you clear the interface table?

Once you have imported the data there is no need to keep it in the interface table, as the
application does not refer to these tables.
8.c. Why is it not recommended to run a drop table?

Dropping tables is not a supported practice, because this alters the database schema and
can cause trouble in a future upgrade.

Lab 51-2 Running EIM to Import Solution Data (Guided)
Goals To run EIM jobs to load legacy solution from the EIM_SOLUTION interface table to
destination tables.
Instructions:

You have loaded legacy solution data into EIM_SOLUTION. In this lab, you will run an EIM job to
import this data into the Siebel destination table, S_RESITEM. The steps you will take include:
• Configure system preferences for running an EIM import job
• Examine an EIM configuration file (.ifb) provided to you
• Enable the EAI component group, which includes the EIM server component
• Create and submit an EIM job
• Examine the results of this job and clean up
1. The default value for the EIM configuration file is default.ifb. If you do not change this
parameter and run EIM by mistake, this might produce unintended results. To prevent errors, you
will rename default.ifb to default_original.ifb.
a. Navigate to D:\OUsea\siebsrvr\ADMIN. Right-click default.ifb and select Rename.
b. Rename the file to default_original.ifb.
2. Before your initial data loads, it is a good idea to turn off Siebel Remote’s transaction logging.
This function normally tracks database changes and allows data to be synchronized in the future
with remote clients. However, this capability comes with a performance cost, which will slow
down data loads. Best practice is to disable transaction logging for sizeable initial data loads, re-
enable transaction logging, and then perform a new database extract for clients.
b. Navigate to Administration – Siebel Remote > Remote System Preferences.
c. Verify or set the following value:
Enable Transaction Logging Unchecked
d. Click Save.
3. You will examine the EIM configuration file and move it to the proper location. Another team
member built a configuration (.ifb) file to be used to run the EIM task to import solution data.
She copied the default_original.ifb file, renamed it, and edited it.
a. Open D:\Labs\Essentials\solution.ifb with Notepad.

b. Why is the BATCH = 100?
c. Why is the TABLE = EIM_SOLUTION?
d. Close solution.ifb.
e. Copy solution.ifb to D:\OUsea\siebsrvr\ADMIN.

4. You will verify that the Enterprise Application Integration component group is enabled on the
Siebel server.
a. Navigate to Administration – Server Configuration > Enterprises > Component Groups.
b. In the Component Group applet, query for Alias EAI. This query will return the Enterprise
Application Integration component group, to which the EIM component belongs.
c. Verify that the EAI component group is assigned to and enabled on the Siebel server OUsrvr.
i. Examine the Component Group Assignments grandchild applet and verify that the
Assigned checkbox is checked.
ii. If necessary, click the Enable button to enable the component group for server
OUsrvr.
iii. Click the Synchronize view tab.
iv. Query for the Enterprise Integration Mgr component. This is one of the
components from the Siebel Remote component group.
v. If this component is not found, click the Synchronize button. Synchronization will
take 1-2 minutes
d. If you changed the Siebel server configuration at all, you will need to restart the server.
i. Log out of the Siebel client.
ii. Shut down and restart the Siebel Server service.
iii. After the Siebel server starts up, which may take a few minutes, start the Siebel Call
Center Web client and log in as SADMIN/SADMIN.
5. You will inspect what data is already in the tables before you invoke EIM.
a. If necessary, start SQL Server Management Studio Express by selecting Start > Programs >
Microsoft SQL Server 2005 > SQL Server Management Studio Express.
b. Click Connect.
c. Click New Query on the toolbar.
d. In the main pane, type:
select NAME from siebeldb..S_RESITEM
In this statement, the column, database, and table names are case-sensitive.
e. Select Execute (F5) to run the query.

f. Were any names returned?
g. Leave Management Studio open.
6. You will create an EIM job to populate the base table from the interface table using the .ifb file.
a. In Call Center, select Administration - Server Management > Jobs.
b. In the Jobs list applet, click New and create a new request with the following value:
Component/Job Enterprise Integration Mgr
c. In the Job Parameters list applet (bottom), click New and set the following parameter:
Name Configuration file

Value solution.ifb
Note: The default location for the configuration file is the Siebel Server ADMIN directory, or
D:\OUsea\siebsrvr\ADMIN for the classroom environment.
d. In the Jobs list applet (top), click Submit Job.
e. Monitor the task by refreshing the Jobs applet by periodically executing an empty query.
Monitor the EIM job until it completes.
7. Next you will check to see if the import was successful.

a. Return to SQL Server Management Studio Express.
b. Query the IF_ROW_STAT column in the interface table EIM_SOLUTION.
i. Click New Query.
ii. In the new query pane, enter the following:
select NAME, IF_ROW_STAT from siebeldb..EIM_SOLUTION
iv. The IF_ROW_STAT value for each row should be set to ‘IMPORTED’.
c. Return to the pane containing your previous query on S_RESITEM and execute your query
again.
d. Modify the query to include other imported legacy data: FAQ_QUES_TEXT,
RESOLUTION_TEXT, TYPE_CD, and STATUS_CD. Ensure that the rows from the
solution.txt input file are reflected in the base table.
e. Use Siebel Call Center to verify the data. Navigate to Solutions > Solution List and compare
the solution records with the legacy data.

8. If the EIM import was successful, you will delete the rows from the interface table.
a. Create a new query and run the following SQL statement to clear out the interface table:
truncate table siebeldb..EIM_SOLUTION
b. Why should you clear the interface table?
c. Why is it not recommended to run a drop table?

Solutions 51-2 Running EIM to Import Solution Data

(Guided)
Answers
3.b. Why is the BATCH = 100?
To match the batch number set for the solution data loaded into EIM_SOLUTION
3.c. Why is the TABLE = EIM_SOLUTION?

This table contains the solution data you loaded earlier and is mapped to the base table for

Solution, S_RESITEM.
5.f. Were any names returned?

Yes. Several records were already in the server database: ABC Copier (twice), ABC Fax,
and How to Contact Us.
8.b. Why should you clear the interface table?

Once you have imported the data there is no need to keep it in the interface table, as the
application does not refer to these tables.
8.c. Why is it not recommended to run a drop table?

Dropping tables is not a supported practice, because this alters the database schema and
can cause trouble in a future upgrade.


Lab 51-3 Running EIM to Load Product Data (Optional)
Goals To inspect the use of various .ifb parameters.
Instructions:

You have already populated the EIM_PROD_INT table with legacy product data, and now are ready
to import the data into the Siebel base tables, as you did with solutions data. In the course of this
import, you will spend more time examining the EIM configuration file (.ifb) and EIM logging
options.
1. Another team member built a configuration (.ifb) file to be used to run the EIM task.
a. Navigate to D:\Labs\Essentials and open product.ifb to inspect it.
b. Notice that the password is not in the file. How will you specify the password for the
SADMIN user?
c. When would you use the SHELL parameter?
d. What purpose does the FILTER QUERY serve?
e. Notice this entry: FIXED COLUMN = UOM_CD, “Each”. If a row has a value in the
UOM_CD column of EIM_PROD_INT, will the value be used?

2. Inspect the data mapping table that you created earlier and the data file (product_import.txt).
3. Create and submit an EIM job to populate the base tables from the interface table using
product.ifb. Set the following parameters in the grandchild Job Parameters applet:
Name Value
Password SADMIN
Configuration file D:\Labs\Essentials\product.ifb
Trace Flags 1
Error Flags 1
SQL Trace Flags 8
Note: When a full directory path to the configuration file is provided, then the job will use this

path, rather than the default directory, which is the Siebel Server ADMIN directory. Also, setting
the error and trace flags will provide detailed logs that can assist debugging the EIM job.
4. Next, you will inspect the results.

a. Select Tasks and execute a query where Component = Enterprise Integration Mgr.
b. Select the most recent task, and click the Log tab to view the log. Notice the output that was
produced by setting additional flags. EIM imports data on a best-effort basis, loading any
records it can and ignoring records that have failed. Even though errors occurred due to
foreign key values missing in the interface table, the required product data was still imported.
5. You will query the interface table and base table.

a. Query the IF_ROW_STAT column in the interface table EIM_PROD_INT in SQL Server
2005 Management Studio Express:
select NAME, IF_ROW_STAT from siebeldb..EIM_PROD_INT
If the import was successful, the IF_ROW_STAT value for each row will be set to
‘IMPORTED’.
b. Query the NAME column in the base table S_PROD_INT:
select NAME from siebeldb..S_PROD_INT
c. Make sure the products from the product_import.txt file are reflected in the base table. You
will see several products listed that were present in the server database prior to the EIM
import.
6. You will inspect the records in the application.

a. Navigate to Administration - Product > Products.
b. Execute a query for this value to separate the newly imported products from the pre-existing
ones. The recently imported products all have the Unit of Measure field set to Each.
7. If the import was successful, delete the rows from the interface table by running the following
statement in SQL Server Management Studio Express:
truncate table siebeldb..EIM_PROD_INT
8. Close SQL Server Management Studio Express, not saving any files. Close product.ifb. Log out
of Siebel Call Center and close the browser.

Solutions 51-3 Running EIM to Load Product Data

(Optional)
Answers:
1.b. Notice that the password is not in the file. How will you specify the password for the
SADMIN user?
You will set it as a job parameter when invoking the EIM job.
1.c. When would you use the SHELL parameter?

When you want to run multiple sections via a single .ifb file -- this saves time by loading the
dictionary information once for all the sections/tables.
1.d. What purpose does the FILTER QUERY serve?

Only rows on the EIM_PROD_INT table meeting the criteria specified will be processed in
the EIM run. In this case, it is all rows, because all rows meet the criteria.
1.e. If a row has a value in the UOM_CD column of EIM_PROD_INT, will the value be used?
No. Fixed column overrides any data specified in the column. In this case, the unit of
measure will be changed for all products that are either null or have a different value.


Module 53: Using Application Deployment Manager
Lab 53-1 Exporting and Packaging Application Changes

(Unguided)
Goals To export different application changes using Siebel Tools and the Siebel Web client
To build an ADM package for subsequent deployment

Instructions:
Guided version.


Lab 53-1 Exporting and Packaging Application Changes

(Guided)
Goals To export different application changes using Siebel Tools and the Siebel Web client
To build an ADM package for subsequent deployment

Instructions:
You have been given two application customizations from a development Siebel enterprise, an
image file and an exported workflow. Your task is to create an ADM package containing these
modifications, together with predefined queries (PDQs) from the development system. In the next
lab you will deploy this package to a target enterprise.
In the classroom lab environment, you will simulate the development enterprise using the sample
database, and the target system that you deploy to will be your server database. The following
diagram illustrates your tasks for this and the next lab:
Image File +
Exported ADM Package
Workflow Server DB
Sample DB
(provided)
All ABC
Predefined
Queries Package Deploy
Export
The last task shown, deployment, will be done in the next lab.
2. You will export predefined queries (PDQs) in the Sample database using the Siebel client ADM
screen.
a. Navigate to Administration - Application > Predefined Queries.
b. To keep the deployment time shorter, you will only export a subset of the PDQs. To do this,
you will create a filter, which is a predefined query that will extract the records you wish to
export.
i. Query for predefined queries with Name ABC*.

ii. How many records are returned by this query? _________________________

iii. From the application menu, select Query > Save Query As.
iv. Enter Query Name ABC Queries.
v. Click OK. You have now created a PDQ that acts on PDQs. This will be your filter
when you create an ADM project.
c. Before you can deploy an ADM session, you need to create a deployment project specifying
the data you wish to export. You will now create such a project.
i. Navigate to Application Deployment Manager > Deployment Projects.
ii. Create a new deployment project with the following parameters:
Name ABC PDQs
Description All ABC PDQs

Active Flag checked
Export to File checked
iii. In the child applet, specify the data type for this project. You will also specify a
deployment filter that only selects PDQs named ABC*. You will do this by specifying
the query you defined earlier as the deployment filter. Set the following parameters:
Data Type Name PDQ
Active Flag checked
Deployment Mode Synchronize
Deployment Filter ABC Queries
d. Select ABC PDQs in the top applet.
e. Click Enable. The status of the project should change to Enabled, which indicates the project
can be deployed as part of a deployment session.
f. Next you will create an ADM deployment session for this project, and deploy the predefined
queries to a file.
i. Use Windows Explorer to create the D:\export directory. This directory will contain
your exported data.
ii. Click the Deployment Sessions link.
iii. Create a new deployment session with the following parameter:
Project ABC PDQs
iv. Click Deploy. (If this button is grayed out, click Refresh and you should be able to
deploy.)
v. When prompted for a export path, enter:
Network D:\export
vi. Click Export.
vii. Navigate to D:\export and verify that this directory contains three files similar to those
shown here:
g. Log out of Siebel Call Center.

3. Next, you will import the provided workflow into Siebel Tools (sample database) and publish it.
This last step will allow you to export the workflow definition as part of a Hot-Fix, which you
will subsequently add to your package.
a. Start Siebel Tools and log in as SADMIN/SADMIN connecting to the Sample database.
b. First, you will lock the Workflow Process project. As a shortcut, you will simply lock this
project, rather than checking it out.
i. Select Project :: Workflow Process.
ii. Check the Locked property. Your user ID, SADMIN, should appear in the Locked By
Name property.
c. Select Workflow Process in the Object Explorer (Object Explorer).
d. Right-click in the Object List Editor (OBLE) and select Import Workflow Process.

e. Select D:\Labs\Essentials\ABC Test Workflow.xml and click Open.
f. Select Workflow Process from the project drop-down list and click OK.
g. Query for ABC Test Workflow in the OBLE.
h. From the WF/Task Editor Toolbar click Publish. The workflow’s status should change to
Completed.
4. You will now create a Hot-Fix containing the imported workflow object definition. A Hot-Fix is
preferable to a Mid-Level Release when the export contains a small number of customizations.
a. Right-click on the ABC Test Workflow record in the OBLE and select Add to Hot-Fix.
b. In the Generate Hot-Fix dialog, enter:
Hot-Fix Label ABC_HotFix_01
c. What directory is the Hot-Fix written to?
d. Click Export. Click OK after the hot fix has been successfully created.
e. Navigate to D:\OUsea\tools\ADM\ABC_HotFix_01. You should see files similar to those
shown here:
f. Exit Siebel Tools.
5. Now you will create an empty ADM package to populate with the application customizations.
a. Open a command shell. (Select Start > Run and enter cmd.)
b. Change directories to D:\OUsea\mgmtsrvr.
c. Enter the command:
D:\OUsea\mgmtsrvr>admpkgr init D:\export\ABC_Package
This creates an empty package in the path given.

d. Leave the command shell open.

6. Before you generate the package and its manifest, you will populate the package directory
structure with the PDQ export, the hot-fix, and the image file you wish to deploy.
a. Explore the D:\export\ABC_Package directory tree.
b. Into which package sub-directory should you put the predefined queries files?
c. Into which package sub-directory should you put the hot-fix you generated?
d. You have been given an updated image file, D:\Labs\Essentials\globe77_d.gif. Image files
in your Siebel installation are found in …\siebsrvr\webmaster\images\ENU. You will create
an analogous path in the package directory
i. In the ABC package directory, navigate to …file\AppServer\webmaster.

ii. Create a sub-directory named images.
iii. Open this new directory and create an ENU directory in it.
iv. Copy D:\Labs\Essentials\globe77_d.gif to the
D:\export\ABC_Package\file\AppServer\webmaster\images\ENU directory.
e. You will move the predefined queries files.
i. In Windows Explorer, navigate to D:\export.
ii. Select two files you generated during export of the PDQs, *_PDQ.xml and
*_PDQ_des.xml, right-click, and select Copy. It is not necessary to copy the .ini file.
iii. Paste these files into D:\export\ABC_Package\database.
f. Next, you will move the hot-fix to the ABC_Package tree.
i. In Windows Explorer, navigate to D:\OUsea\Tools\ADM\ABC_HotFix_01.
ii. Select the two files you created during the export from Siebel Tools,
ABC_HotFix_01.sif and ABC_HotFix_01_des.xml, right-click, and select Copy. It is
not necessary to copy the log file.
iii. Paste these files into D:\export\ABC_Package\repository.
g. You will complete your population of the package directory structure by deleting empty
package directories. This will speed up packaging and deployment of this package, as well as
avoiding warning messages during deployment.
i. From the package directory, delete (including sub-directories):
…\file\ReportServer
…\file\AppServer\objects
…\file\AppServer\reports
…\file\AppServer\webtempl
ii. The final package directory structure should be:

7. Finally, you will generate and ADM package.

a. At the command shell, enter:
D:\OUsea\mgmtsrvr>admpkgr generate D:\export\ABC_Package
This command creates the package descriptor file, which is a manifest of the customizations
in the package.
b. Open D:\export\ABC_Package\descriptor.xml with Notepad++. Verify that this package
descriptor lists all three customizations (predefined queries, workflow process, and image
file) that you put in the package directory structure.
c. Close Notepad++.
8. Your package is almost ready for deployment. The last step is to move it to the default package

directory, which you will do here. Copy the D:\export\ABC_Package directory and its contents
to D:\OUsea\mgmtsrvr\adm\packages. This latter directory is where the ADM command-line
interface (ADM CLI) expects to find packages to deploy.
9. Leave the command shell open for the next lab.

Solutions 53-1 Exporting and Packaging Application

Changes (Guided)
Answers
2.b.ii. How many records are returned by this query?
One – ABC Unavailable Offline
4.c. What directory will contain the Hot-Fix?

…\tools\ADM\

6.b. Into which package sub-directory should you put the predefined queries files?
...\database
6.c. Into which package sub-directory should you put the hot-fix you generated?
…\repository
6.d. Into which package sub-directory should you put this file?
…\file\AppServer\webmaster\images\ENU

Lab 53-2 Configuring ADM (Unguided)
Goals To configure ADM for package deployment
Instructions:

Guided version.


Lab 53-2 Configuring ADM (Guided)
Goals To configure ADM for package deployment
Instructions:
In this lab you will configure ADM for deployment. You start with a target enterprise – the Siebel

enterprise you have been using in labs – with the Siebel Management Server and Agent installed and
correctly configured. You will perform ADM-specific configuration steps.
ADM configuration requires several steps. The following presents a summary of these steps and the
corresponding lab steps that you will perform:
• Enable the ADM component group on the target enterprise, as well as other component
groups required by the package that you will create and deploy
• Configure target enterprise server parameters and profiles
• Activate ADM-related workflow processes on the target enterprise
• Restart the Siebel Server and start the Siebel Management Server and Agent
• Edit the ADM Enterprise Profile file to reflect target Siebel Server configuration, agent
settings, and deployment options
1. You will enable the ADM component group on your Siebel server, as well as other groups
needed for the package you will deploy in an upcoming lab. The package you will build and
deploy contains a workflow process, so you will need to enable the Workflow Management
component group. ADM deployment will use the Enterprise Application Integration (EAI)
component group, so you will also have to verify that it is enabled.
b. Navigate to Administration – Server Configuration > Enterprises > Component Groups.
c. In the list of component groups, query for Application Deployment Manager.
d. In the Component Group Assignments grandchild applet, click Enable.
e. Enable the Workflow Management and Enterprise Application Integration (EAI) component
groups as well, if necessary. Repeat steps c and d to enable these two groups.
f. If you have made any changes, synchronize the components.

2. Now you will configure the ADM and Call Center application object managers to support UI file
customizations. For both of these server components, you will set the EnableADMSupport
parameter to True. This parameter, when set, allows the Siebel Web server to be restarted after
deployment and activation of Web files or templates.
a. Navigate to Administration – Server Configuration > Enterprises > Component Definitions.
b. Select Application Deployment Manager Object Manager (ENU) in the Component
Definitions list.
c. In the Component Parameters grandchild applet, query for parameter EnableADMSupport.
d. Change its value to True. Note in the adjoining form applet that this parameter change will
be effective at component restart.
e. Select the Call Center Object Manager (ENU) component and repeat the previous steps.

3. You will also configure server parameters for the Siebel Management Agent. The agent is Java-
based, and uses a parameter, JVM Classpath, that must be properly configured. This path will be
set to include four Java archive (jar) files that have been copied from D:\OUsea\mgmtagent\lib to
D:\JAR.
a. Click the Profile Configuration tab.
b. Query for Profile ADMJavaSubsys.
c. In the Profile Parameters grandchild applet, select the parameter JVM Classpath.
d. You will set the value of this parameter using the contents of a text file provided to you.
i. Open D:\Labs\Essentials\classpath.txt with Notepad++.
ii. Copy the contents of this file (a single text line) to the Clipboard.
iii. Paste this string into the Value field in the Profile Parameters applet for the JVM
Classpath parameter.
iv. Close classpath.txt.
e. Set the JVM DLL Name parameter with the help Windows Explorer. The DLL is:
D:\Program Files\Java\jre1.5.<version>\bin\client\jvm.dll, where version is the particular
version of the Java Runtime Environment on your classroom machine. Example:
jre1.5.0_08.
Hint: Copy and paste the directory string from the Windows Explorer Address bar into the
parameter’s Value field.
f. Click the Parameters tab.
g. Query for the parameter JVM Subsystem Name.
h. Set the Value field for this parameter to ADM Java Systems.
4. You now will activate the ADM and related workflow processes. These Siebel-provided
workflows provide target environment support for the Siebel Management agent and are used
during deployment of ADM packages. While they are resident in the Siebel repository, they need
to be manually activated.
a. Navigate to Administration – Business Process > Workflow Deployment.
b. Select the ADM Deployment workflow in the top applet.
c. Click Activate. This workflow will appear in the child Active Workflow Processes applet.
d. Activate workflow ADM Restore.

e. You will also activate all UDA workflows. These workflow processes also provide target-
side support for ADM deployments.
i. In the Repository Workflow Processes applet, query for Name UDA*.
ii. Select all 9 matching workflows with CTRL+A.
iii. Click Activate.
5. Log out of Siebel Call Center and restart the Siebel Server service. This may take more than 5
minutes. Continue with the next step while you are waiting for the Siebel Server to restart.
6. Now you will modify the ADM enterprise profile file so that the ADM command-line interface
can connect to the Siebel Management Agent on the target enterprise. To do this, you will
specify your lab machine’s host name in an enterprise profile file provided to you.
a. Get your lab machine’s host name:

i. If necessary, open a command shell.
ii. Enter the command hostname.
iii. Write the result here. Case is important, as the ADM configuration files are case-
sensitive:
iv. Close the command shell.

b. In Windows Explorer, right-click on D:\Labs\Essentials\entprofile_Siebel.xml and select
Open With > Notepad.
c. Replace every occurrence of the string XXXX with your lab machine’s name as shown.
Remember that the entries in this file are case-sensitive:
d. Save the file and close Notepad.

e. Copy D:\Labs\Essentials\entprofile_Siebel.xml to
D:\Ousea\mgmtsrvr\adm\entprofile_Siebel.xml. Click Yes to replace the existing file.
7. When the Siebel server has restarted completely, right-click on the service Siebel Management
Agent. Click Start. Start the Siebel Management Server as well.


Lab 53-3 Deploying Application Changes (Unguided)
Goals To deploy and activate application customizations using the ADM command-line
interface (CLI)
Instructions:

Guided version.


Lab 53-3 Deploying Application Changes (Guided)
Goals To deploy and activate application customizations using the ADM command-line
interface (CLI)
Instructions:

In this lab you will deploy the package you generated in the previous lab to the server database on
your lab machine. You will then log in to check that the customizations in this package have
deployed successfully.
1. You will start by loading references your package into the management server database using the
load command. You will perform this deployment from the ADM command-line interface
(ADM CLI).
a. In your command shell, change directories to D:\OUsea\mgmtsrvr if necessary..
b. Enter the following command to load the ABC package:
bin\deploy_Siebel load SADMIN SADMIN ABC_Package
You should see a message claiming success.
2. Now you will create a deployment session for your package, as well as checking the status of the
session.
a. Create the session by entering:
bin\deploy_Siebel create SADMIN SADMIN ABC_Package
Tip: The keyboard up and down arrows can be used to move backwards and forward through
the command shell history buffer, and the right and left arrows move the cursor within the
current command.
b. Check the status of your deployment with the following command:
bin\deploy_Siebel status SADMIN SADMIN ABC_Package
3. Now you can deploy the customizations to the target enterprise with the copy command. Before
you do this, you will verify that the database and repository customizations are not present on the
target system.
a. Open Siebel Call Center using the Siebel Web client and log in as SADMIN.
b. Navigate to Administration - Business Process > Workflow Deployment.
c. In the Repository Workflow Processes applet, query for ABC Test Workflow. Verify that
no such workflow exists in your server database.
d. Navigate to Administration - Application > Predefined Queries.
e. In the Predefined Queries applet, query for a PDQ with Object Service Request and Name
ABC*. Verify that no PDQ matches this query.
f. Log out of the Siebel Web client.

g. To copy the package to the target environment, enter:

bin\deploy_Siebel copy SADMIN SADMIN ABC_Package
This command may take several minutes to complete.
h. After you see a success message for copy, open Siebel Call Center using the Siebel Web
client and log in again as SADMIN.
i. Repeat steps b through e above, and verify that:
i. The workflow ABC Test Workflow is listed in the Repository Workflow Process applet,
but is not listed in the Activated Workflows child applet.
ii. The ABC Unavailable Offline PDQ is now listed in the PDQ list applet.
j. Log out of the Siebel Web client and exit your browser.
4. To complete this deployment you will activate the deployment.

a. Activate the customizations contained in the package with the following command:

bin\deploy_Siebel activate SADMIN SADMIN ABC_Package
b. What do you expect activation to achieve on the target system?
5. You will check to see if the customizations have been deployed.

a. Log in to Siebel Call Center as SADMIN using the Siebel Web client. You should see a
different image on the login screen!
b. Navigate to Administration – Business Process > Workflow Deployment. Verify that ABC
Test Workflow appears in the list of activated workflows.
c. Navigate to Administration – Application > Predefined Queries and query for name ABC*.
You should see two PDQs that were just deployed.

Solutions 53-3 Deploying Application Changes (Guided)
Answers
4.b. What do you expect activation to achieve on the target system?
Activation won’t affect the predefined queries you deploy, but the other two customizations
will be affected. ABC Test Workflow will be activated (made available for invocation), and
the Siebel Web server will be reset so that the new image file will be published.


Lab Guide

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Lab Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lab Guide

Uploaded by

Copyright:

Available Formats

Oracle Internal & Oracle Academy Use Only

Siebel 8.0 Essentials

Volume I • Activity Guide

Siebel Curriculum Disclaimer

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using

Oracle Internal & Oracle Academy Use Only

U.S. GOVERNMENT RIGHTS

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Lab 0-1 Introduction

Time Less than 5 minutes

Guided and Unguided labs:

Oracle Internal & Oracle Academy Use Only

Use this format if:

Use this format if:

Siebel 8.0 Essentials 1

Oracle Internal & Oracle Academy Use Only

2 Siebel 8.0 Essentials

Lab 2-1 Navigating the User Interface (UI) (Unguided)

Goals To practice navigating in Siebel Call Center.

Oracle Internal & Oracle Academy Use Only

2. Examine service requests.

ii. What is the service request Area?

iii. What is the service request’s Reproducible value?

iv. Who is the owner of the SR?

v. What is the Organization?

vi. What is the SR# of the next service request?

Siebel 8.0 Essentials 3

4. Examine accounts and opportunities.

Oracle Internal & Oracle Academy Use Only

5. Leave Siebel Call Center open for the next lab.

4 Siebel 8.0 Essentials

Solutions 2-1 Navigating the User Interface (UI)

2.a.ii. What is the service request Area?

Oracle Internal & Oracle Academy Use Only

2.a.iv. Who is the owner of the SR?

2.a.v. What is the Organization?

2.a.vi. What is the SR# of the next service request?

4.b. How many opportunities exist for this account?

Siebel 8.0 Essentials 5

Oracle Internal & Oracle Academy Use Only

6 Siebel 8.0 Essentials

Lab 2-1 Navigating the User Interface (UI) (Guided)

Goals To practice navigating in Siebel Call Center.

Oracle Internal & Oracle Academy Use Only

1. You will log in to Siebel Call Center.

2. You will examine a service request.

b. What is the service request Area?

c. What is the service request’s Reproducible value?

d. Who is the owner of the SR?

e. What is the Organization?