Siebel 8.0 Essentials

Siebel 8.
0 Essentials
Volume I Student Guide
D46318GC10 Edition 1.0 April 2007 D49908
Oracle Internal & Oracle Academy Use Only
Author
Siebel Curriculum Development Team
Copyright 2007, Oracle. All rights reserved. Disclaimer 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 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 not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. 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, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Restricted Rights Notice
Technical Contributors and Reviewers

Siebel Review Team
Publisher
Joseph Fernandez
U.S. GOVERNMENT RIGHTS The U.S. Governments 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.
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:
Contents
Module i: Siebel 8.0 Essentials Training Module 1: Introducing Siebel Applications Module 2: Using the Siebel Web Client Module 3: Working With Siebel Data Module 4: Responsibilities and Views Module 5: Users, Positions, and Organizations Module 7: Catalogs and Master Data Module 8: The Siebel Web Architecture Module 9: Server Components and Parameters Module 10: Server Management Module 11: Siebel Client Types Module 12: Securing Access to the Application Module 13: Installing Siebel Applications Module 14: Siebel Application Architecture Module 15: Using Siebel Tools to Examine Object Definitions Module 16: The Siebel Data Model Module 17: Siebel Business Components Module 18: Siebel Party Business Components Module 19: Siebel Business Objects Module 20: Configuration Strategy Module 21: The Configuration Process Module 22: Managing Object Definitions Module 23: Editing and Compiling Object Definitions Module 24: UI Layer Configuration: Web Templates Module 25: UI Layer Configuration: Applets Module 26: UI Layer Configuration: Applications, Screens, and Views Module 27: UI Layer Configuration: Drilldowns Module 28: Business Layer Configuration: Joins Module 29: Business Layer Configuration: Existing Business Components and Fields
iii
Module 6: Controlling Access to Customer Data
Module 30: Business Layer Configuration: New Business Components and Fields Module 31: Business Layer Configuration: Picklists Module 32: Configuring Multi-Value Groups Module 33: Data Layer Configuration Module 34: Siebel Business Services Module 35: Building Siebel Workflow Processes Module 36: Testing and Deploying Workflow Processes Module 37: Executing Workflow Processes Module 38: Using Workflow Policies Module 40: Task UI: Creating a Task Module 41: Transient Business Components and Branching Module 42: Siebel Business Rules Module 43: Creating Business Rules Module 44: Introducing Siebel Assignment Manager Module 45: Creating Assignment Rules Module 46: Tailoring Assignment Manager Behavior Module 47: Invoking Siebel Assignment Manager Module 48: State Models Module 49: Introducing Enterprise Integration Manager Module 50: Creating Data Maps Module 51: Running Enterprise Integration Manager Module 52: Introducing Application Deployment Manager Module 53: Deploying Application Customizations Module 39: Siebel Task UI
iv
Siebel 8.0 Essentials Training
i.1
i
Siebel 8.0 Essentials
Module i: Siebel 8.0 Essentials Training
Copyright 2007, Oracle. All rights reserved.
i.2
Module Agenda
This module provides an introduction to the:

` Instructor and class participants ` Training site information ` Course:

2 of 18
Audience Prerequisites Goal Objectives Methodology Materials Agenda
i.3
Instructor and Class Participants
Who are you?

` Name ` Company ` Role
What is your prior experience?

` Siebel Applications ` Relational database
How do you expect to benefit from this course?
3 of 18
i.4
Training Site Information
Bathrooms
Class duration and breaks
Telephones
Meals and refreshments
Fire Exits
Questions?
4 of 18
i.5
Course Audience
This course is designed for implementation teams

` ` ` ` Application developers System architects and configurators Database administrators Systems administrators
5 of 18
i.6
Course Prerequisites
Basic Windows or NT navigation and file-management skills Understanding of basic relational database concepts Familiarity with application development Familiarity with Web-based and client/server applications
6 of 18
i.7
Course Goal
To enable participants to identify and perform tasks required for an initial Siebel 8 Application deployment
7 of 18
i.8
Course Objectives

8 of 18
Navigate the Siebel application user interface Secure access to Siebel applications and data Define your company structure Describe the Siebel application architecture Describe the steps required to install Siebel application software to set up your enterprise Configure a Siebel application Automate business rules in your Siebel application Populate and migrate data into the Siebel database Migrate data between environments
i.9
Course Methodology
Subject matter is delivered via:

` ` ` ` Lecture and slide presentations Software demonstrations Class discussions Hands-on labs
9 of 18
i.10
Course Materials
Student Guide
` All slides presented during lecture ` Notes that point to Siebel Bookshelf references
Lab Guide
` Hands-on lab exercises and solutions
10 of 18
i.11
Overview of Course Flow

1. Using Siebel CRM 2. Access Control and Organization Setup 6. Application Configuration 3. Physical Architecture and Management 7. Siebel Workflow 4. Installation and Security
9. Data Loads
10. Application Deployment
11 of 18
5. Siebel Application Architecture
8. Configuring Business Logic
i.12
Course Agenda
Using Siebel CRM

` 1: Introducing Siebel Applications ` 2: Using the Siebel Web Client ` 3: Working with Siebel Data
Access Control and Organization Setup

` ` ` ` 4: Responsibilities and Views 5: Users, Positions, and Organizations 6: Controlling Access to Customer Data 7: Catalogs and Master Data 8: The Siebel Web Architecture 9: Server Components and Parameters 10: Server Management 11: Siebel Client Types
12 of 18
Physical Architecture and Management

` ` ` `
i.13
Course Agenda Continued
Installation and Security

` 12: Securing Access to the Application ` 13: Installing Siebel Applications
Siebel Application Architecture

` ` ` ` ` ` ` ` 14: Siebel Application Architecture 15: Using Siebel Tools to Examine Object Definitions 16: The Siebel Data Model 17: Siebel Business Components 18: Siebel Party Business Components 19: Siebel Business Objects 20: Configuration Strategy 21: The Configuration Process
13 of 18
i.14
Application Configuration
` ` ` ` ` ` ` ` ` ` ` ` 22: Managing Object Definitions 23: Editing and Compiling Object Definitions 24: UI Layer Configuration: Web Templates 25: UI Layer Configuration: Applets 26: UI Layer Configuration: Applications, Screens, and Views 27: UI Layer Configuration: Drilldowns 28: Business Layer Configuration: Joins 29: Business Layer Configuration: Existing Business Components and Fields 30: Business Layer Configuration: New Business Components and Fields 31: Business Layer Configuration: Picklists 32: Configuring Multi-Value Groups 33: Data Layer Configuration
14 of 18
i.15
Siebel Workflow
` ` ` ` ` 34: Siebel Business Services 35: Building Siebel Workflow Processes 36: Testing and Deploying Workflow Processes 37: Executing Workflow Processes 38: Using Workflow Policies 39: Siebel Task UI 40: Task UI: Creating a Task 41: Transient Business Components and Branching 42: Siebel Business Rules 43: Creating Business Rules 44: Introducing Siebel Assignment Manager 45: Creating Assignment Rules 46: Tailoring Assignment Manager Behavior
15 of 18
Configuring Business Logic

` ` ` ` ` ` ` `
i.16
Configuring Business Logic (Continued)

` 47: Invoking Siebel Assignment Manager ` 48: State Models
Data Loads
` 49: Introducing Enterprise Integration Manager ` 50: Creating Data Maps ` 51: Running Enterprise Integration Manager
Application Deployment
` 52: Introducing Application Deployment Manager ` 53: Deploying Application Customizations
16 of 18
i.17
Summary
This module provides an introduction to the:

` Instructor and class participants ` Training site information ` Course:

17 of 18
Audience Prerequisites Goal Objectives Methodology Materials Agenda
i.18
Introducing Siebel Applications
1.1
1
Module 1: Introducing Siebel Applications
1.2
Module Objectives
After completing this module you should be able to:

` Describe Siebel Customer Relationship Management (CRM) applications and how they are classified ` Identify the common business entities found in Siebel CRM applications
Why you need to know:
2 of 22
` You need to be familiar with Siebel applications to understand the context of this course
1.3
Siebel Customer Relationship Management (CRM)
Enables you to manage interactions with customers, partners, and employees

` Typically deployed as a single application with broad functionality ` Supports multiple communication channels

Web and email Call center Field service
` Allow all users access to the same set of data
Example: The correct customer order status is seen by all relevant users Example: An address needs to be updated in only one place
` Ensure changes to data are made once and only once
Is a packaged application with built-in best practices
3 of 22
Siebel Bookshelf
Comprehensive documentation on Siebel applications is available in Siebel Bookshelf, which is available in book form and online on the Siebel support Web site. Access to the online version requires a SupportWeb login. References in this course materiel refer to Siebel Bookshelf titles.
Uses a single database to:
1.4
Siebel CRM Applications
Are available tailored for:

` Different types of customer, partner, or employee interactions and channels (horizontal applications) ` Different industries (industry applications)
Examples:
` Horizontal applications

` Industry applications

Siebel Finance Siebel Consumer Goods
4 of 22
References
Siebel Bookshelf includes titles on horizontal applications, such as Siebel Field Service Guide, as well as titles for industry applications, such as Siebel Finance Guide.
Siebel Sales Siebel Call Center Siebel Partner Portal Siebel Remote
1.5
Types of Siebel Enterprise Applications
Employee applications
` Are used by internal employees ` Examples include:

Siebel Call Center Siebel Sales
Customer and partner applications
Siebel eSales Siebel Partner Portal
5 of 22
` Are used by customers and partners ` Examples include:
1.6
Employee Application: Siebel Sales
Siebel Sales may be used by a companys sales representatives and managers to manage accounts, sales opportunities, and contacts
Siebel Sales Opportunities screen
6 of 22
1.7
Employee Application: Siebel Call Center
Siebel Call Center may be used by a companys telesales and service representatives
Siebel Call Center service screen
7 of 22
1.8
Customer Application: Siebel eSales

May be used by customers to purchase products over the Web Includes an interactive product catalog, search and product comparison mechanisms, and online ordering capabilities
Product catalog Shopping cart
8 of 22
1.9
Partner Application: Siebel Partner Portal
May be used by a companys partners to communicate, collaborate, and conduct business with a Web-based interface
Partner Portal opportunities screen
9 of 22
1.10
Comparison of Siebel CRM Applications
Siebel functionality is delivered as separate horizontal or vertical applications that:

` Have the same user interface and navigation ` Are based on the same underlying application architecture ` Use the same underlying technologies for automation, integration, and so on ` Share many of the same application screens
` Configuration files are used to specify application parameters ` Use Siebel Tools to generate input files that control behavior
This course will teach you how to modify these files to meet the specific requirements of your business
10 of 22
Applications use the same executable, but use different configuration and input files

0/2
1.11
Siebel User Interface (UI) Modes
The Siebel UI is rendered in one of two modes: High Interactivity Mode Standard Interactivity Mode
11 of 22

1/2
1.12
High Interactivity Mode

Is available for employee applications, supporting highly interactive users Uses additional code, such as Active X controls, to provide extra functionality
Requires Internet Explorer (check documentation for versions)
12 of 22
Reference
System Requirements and Supported Platforms
` ` ` `
Drag-and-drop for setting column widths Explorer-like hierarchy views Menu bar and tool bars Saving records by moving off the current line

2/2
1.13
Standard Interactivity Mode

Is available for customer and employee applications Designed to be less browser-dependent
` Behaves like a typical HTML-based Web application
Available on a wide variety of browsers (check documentation for supported browsers)
13 of 22
Reference
System Requirements and Supported Platforms
1.14
Common Siebel Application Business Entities
Siebel applications use common business entities

` A business entity is something of business interest in the real world
Siebel applications refer to these entities as business components Examples:
14 of 22
` ` ` ` `
Accounts Contacts Opportunities Service requests Assets

0/7 0/5
1.15
Common Siebel Business Components

Accounts Contacts Opportunities Service Requests Assets
15 of 22

1/5
1.16
Accounts
Are businesses external to your company Represent a current or potential client, a business partner, or a competitor Are associated with a team
16 of 22

2/5
1.17
Contacts
Are people with whom you do business Can be public or marked as personal Are associated with a team (public contacts) or a user (personal contacts)
17 of 22

3/5
1.18
Opportunities
Are potential revenue-generating events Have the following characteristics:
` A possible association with an account ` A probability of completion ` A close date
Are associated with a team
18 of 22

4/5
1.19
Service Requests
Are requests from customers or prospects for information or assistance with your products or services Have the following characteristics:
` A status ` A severity level ` A priority level
Are associated with a single owner
19 of 22

5/5
1.20
Assets
Are instances of purchased products Have the following characteristics:
` An asset number ` A product and part number ` A status level
20 of 22
1.21
Module Highlights
Siebel CRM applications allow you to manage all customer points of contact Types of Siebel CRM enterprise applications are:
` Employee applications: Siebel Call Center, Siebel Sales, and so on ` Customer applications: Siebel eSales, Siebel Partner Portal, and so on ` ` ` ` ` Accounts Contacts Opportunities Service requests Assets
21 of 22
Common Siebel business components include:
1.22
Using the Siebel Web Client
2.1
Module 2: Using the Siebel Web Client
2
2
2.2
Module Objectives

` Start and log in to a Siebel application ` Navigate screens and views in the application ` Identify major user interface (UI) features in a Siebel CRM application
2 of 24
` Understanding the UI enables you to effectively use and configure Siebel applications
2.3
Logging In to a Siebel Application

Start a Siebel application in a Web browser by entering the applications URL Log in using assigned user ID and password
2
Application URL
User ID and password
3 of 24
Reference
Siebel Fundamentals
2.4
Application URLs
A Siebel applications URL is formed from :

` Applications Web server name ` Application name ` Suffix identifying the application language
Examples:
` http://AppServer0.MyCompany.com/callcenter_enu Web server name: Appserver0.MyCompany.com Application name: callcenter (Siebel Call Center) Language suffix: _enu (American English) ` http://public.MyCompany.com/esales_fra Web server name: public.MyCompany.com Application name: esales (Siebel eSales) Language suffix: _fra (French)
4 of 24
2.5
Application Home Page
Displayed after log-in to a Siebel application
2
Personalize home page by clicking Edit Layout
Personalized data provides direct links to common tasks

Copyright 2007, Oracle. All rights reserved. 5 of 24
2.6
Siebel Application User Interface

Siebel applications consist of Web pages Each page displays Siebel data surrounded by tabs, toolbars and a top-level menu
Application-level menu helps navigation and manipulating data
Tabs provide easy navigation to related data
6 of 24
Global toolbar provides quick access to common tasks
2.7
Help Menu: Online Help and Technical Support

The application-level Help menu offers Online Help

` Documents common end-user tasks
Technical Support in the Help menu identifies useful technical information

` Includes current user ID and support contact information
2
7 of 24
2.8
Global Toolbar: iHelp and Reports
Access context-sensitive tasks and reports associated with the current screen
Click the How Do I button to access iHelp, which provides guidance with tasks Click the Reports button to access reports for the screen you are working in
8 of 24
2.9
Global Toolbar: Site Map
Access a list of all application areas available to the user
Site Map button
2
Site Map lists application areas Drilling down on an area shows detailed navigation
2.10
Screens
Represent groups of related data for a functional business area, such as accounts, contacts, or opportunities
Screen tab
10 of 24
Screen Tabs
The screen tabs that are visible are typically a subset of those available from the Site Map.
Link bar has links to other accountrelated data
2.11
Screen Home Pages
Some screens have home pages that provide quick access to common end-user tasks and data
2
Guided help with common tasks
Links to different sets of records
Links to recent records

2.12
Navigating
Click the different UI elements to navigate to different data

Screen tabs
Link bar
View tabs
Row indicator
Selected record
12 of 24
2.13
Views
A view consists of one or more applets displaying records
View
2
View tab
13 of 24
2.14
Drop-Down Menu Screen and View Navigation
Access additional tabs and links using drop-down arrows

` Available if needed for screen tabs, link bar, and view tabs
Click drop-down to display more choices
14 of 24
2.15
Hyperlinks
Drill down on a hyperlink to see more information
2
Clicking account hyperlink ...navigates you to the Account Detail Contacts view
15 of 24
2.16
List Applets and Form Applets
Views are made up of one or more applets

` List applet displays records in rows ` Form applet displays a single record in a two-dimensional layout
List applet
Selected record
Form applet
16 of 24
2.17
Navigating List Applets and Form Applets
Use the Menu button or scroll bars and arrows
Standard applet buttons
2
Right-click for context menu
Form applet navigation arrows
Applet-specific menu items
17 of 24
2.18
Freezing List Columns
Freeze position in list columns

` Freeze columns by double-clicking column headers within list applets
Enhances ability to work effectively with lists that contain many columns of data
` Drag and drop columns in and out of the frozen area
Double-click column header to freeze (or unfreeze) columns
Scrolling horizontally through columns leaves frozen columns in place
18 of 24
2.19
Changing Columns Displayed
Click the Menu button, or right-click and select Columns Displayed

Columns available to be used in the applet Columns visible in the applet
2
Right-click and select Columns Displayed Click to add or remove columns from applet
Click buttons to sequence columns

19 of 24
2.20
Displaying More Records
Click the Show More button in the top-right corner of a list applet to toggle display of more records
Click Show More ...
to see more records
20 of 24
2.21
Setting User Preferences
Allows users to set individual preferences for some application features

` ` ` ` Set time zone preferences Set a startup view Change default spell check options Customize aspects of the calendar
Select User Preferences from the application-level Tools menu
2
Link bar categorizes preferences
New screen tab appears
21 of 24
2.22
Module Highlights

A Siebel application consists of Web pages that display data A screen is a grouping of views in a major application functional area A view consists of one or more applets as well as links and tabs used to navigate within the view A list applet displays multiple records in table form A form applet displays a single record
22 of 24
2.23
Lab
In the lab you will:

` Practice navigating in Siebel Call Center
23 of 24
2.24
Working With Siebel Data
3.1
Module 3: Working With Siebel Data

3
3.2
Module Objectives

` Create, modify, and delete records ` Query for records in a Siebel CRM application

` Knowing these skills is important for understanding and configuring Siebel applications
2 of 28

0/5
3.3
Working with Data in the Siebel User Interface (UI)
Creating Data Modifying and Saving Data Using Picklists and Multi-Value Groups
Deleting Data
3 of 28
Sorting Data

1/5
3.4
Creating Data
Select Menu > New Record or click the New button to create a new record
4 of 28

1/5
3.5
Creating Data Continued

Enter data in list or form applet Some fields are required:
` Marked with a red asterisk in a form applet ` Default value may be provided automatically
Required field indicated by red asterisk Required field populated with default value
5 of 28

2/5
3.6
Modifying and Saving Data

Modify data
` Select field in the list or form and change it
Save data implicitly

` Step off the record in a list or a form to commit it to the database ` Available in High Interactivity interface
Save data explicitly
Explicit save
6 of 28
` Click Menu and select Save Record ` Keyboard: CTRL+S

2/5
3.7
Text Editor
Is an editable text area used to create, edit, or view large amounts of text Is accessed by clicking the Text Editor button in the top-right corner of a text field
Enter text and click OK Text Editor button
7 of 28

2/5
3.8
Attachments
Are files created in other applications that can be associated to records in Siebel applications Can be related to records wherever the Attachments view is available within a screen
` Drag and drop a file into the Attachments list view, or ` Use the New File or New URL button
Drag and drop file to create an attachment
Use New File or New URL to create an attachment
8 of 28

3/5
3.9
Using Picklists
Picklists allow user to select a field value from a list Two types of picklist:
` Static: User selects a value from a fixed drop-down list ` Dynamic: User selects a value from list of changing values
Examples: Accounts, Opportunities, Contacts

Static picklist uses drop-down list
Dynamic picklist
Select button opens pick applet

Constrained vs. Unconstrained Picklists
A picklist may be constrained, only allowing users to enter values that appear in the drop-down list or pick applet, or unconstrained, where the user is free to add any value.

3/5
3.10
Using Multi-Value Groups

Multi-value groups (MVGs) assign one or more values to a field in a record Only the primary value will be displayed in a list or form
MVG Select button
Primary
Associate members to the account team

4/5
3.11
Sorting Data
Click a column header to sort data in ascending or descending order

Click the column header for ascending (A Z) or descending (Z A) order
11 of 28

4/5
3.12
Sorting Data Continued
Select Menu > Advanced Sort to sort using values of up to three columns at once
12 of 28
Select sort columns and order

5/5
3.13
Deleting Data
Delete a record by:

` Select Menu > Delete Record ` Click Delete button ` CTRL+D
Some records may be read-only
Confirm delete
13 of 28

0/6
3.14
Querying for Data in the Siebel UI
Running and Executing a Query Using the Query Assistant Querying an MVG Field Refining a Query Saving a Query Executing Predefined and Saved Queries
14 of 28

1/6
3.15
Running and Executing a Query
Query for records inline within a form or list applet using one of the following methods:
` Query button on an applet ` Query from applet-level and application-level menus ` Run Query item in context menu (accessed by right-click)
Right-click for context menu
15 of 28

1/6
3.16
Wildcards
Wildcards can be used to search for matching characters * is a substitute for zero or more characters in a string query
` * cannot be used in date or numeric fields ` Examples:

Ma* matches Madrid, but not San Mateo *Ma* matches Madrid and San Mateo
? Is a substitute for exactly one character in a string query

` ? cannot be used in date or numeric fields ` Examples:

st?r matches star and stir, but not stair *st?r matches monster and rock star, but not tastier
16 of 28
Default Query Behavior
Default behavior for queries in list and form applets is to insert a trailing *. Example: A query for Ma, without an asterisk, would match Madrid.

1/6
3.17
Query Operators
Relational operators can be used on numeric or date fields

` ` ` ` ` < (less than) > (greater than) = (equal to) <= (less than or equal to) >= (greater than or equal to)
` Find dates on or after 1/1/2006
Date field in query is set to: >= 1/1/2006
17 of 28
<> (not equal to) can be used on all fields Example:

1/6
3.18
Query Operators Continued

OR allows match on any one of multiple values for a field AND allows match on all of multiple values for a field Other operators include
Examples:
` Find service requests with no description entered
Use IS NULL in Description field of service request In date field of query: >=1/1/2006 AND <= 1/7/2006
` Find dates on or between 1/1/2006 and 1/7/2006
18 of 28
` ` ` `
NOT IS NULL IS NOT NULL

1/6
3.19
Record Count
Provides the total number of matching records in the query
Select Record Count for count of records in current query


2/6
3.20
Using the Query Assistant
Provides a simplified way for users to execute queries from anywhere in a Siebel application
` Guides users through creating a query ` Users do not have to be familiar with query syntax or operators
Click Query Assistant button after clicking Query in a form or list

Select fields and operators using drop-down lists
Select any field from the current screen Two expressions combined with AND to form the query
20 of 28

3/6
3.21
Querying an MVG Field
Use EXISTS() to search for matches in multi-value groups (MVGs)

` Only way to query all child records in an MVG ` Example: Searching for the string *Street in the address of an account

MVG indicator
Search criterion
Queries Using Drop- A related issue involves queries on a field whose values are populated using a drop-down list. Best practice is to enter the value to be queried using the Down Lists drop-down list, rather than typing this value.
An account can have multiple addresses Query matches all accounts with one or more addresses ending with the sub-string Street

3/6
3.22
Querying an MVG Field Continued
Search results show records where at least one value in an MVG matches the search criteria
` Example:
Search results include accounts with string *Street in at least one address
These accounts all have addresses that match the query
Record detail for Ace Properties


4/6
3.23
Refining a Query
Use Refine Query to modify an existing query
1. Select Refine Query
2. Enter additional or modified criteria
Original criterion
3. Query results reflect original and modified criteria


5/6
3.24
Saving a Query
Use the application-level Query menu to save a query
1. Select Query > Save Query As
2. Name the query and click OK
24 of 28

6/6
3.25
Executing Predefined and Saved Queries

Predefined queries are provided by an application administrator

` Cannot be deleted by an end user
Additional saved queries are created and saved by the user All saved and predefined queries appear in the Saved Queries drop-down list
Predefined and saved queries in alphabetical order Created and saved by user
25 of 28
3.26
Module Highlights
Creating and editing data may involve using:

` ` ` ` Required and optional fields Drop-down lists MVG fields Attachments
Siebel applications support complex queries on data with:
The Query Assistant helps end users form complex queries Commonly-executed queries may be saved
26 of 28
` Wildcards ` Logical and numerical operators ` Support for searching multi-value group (MVG) fields
3.27
Lab

` Create, modify, and delete records ` Use basic querying skills
27 of 28
3.28
Responsibilities and Views
4.1
Module 4: Responsibilities and Views
4.2
Module Objectives
` Describe the purpose of a responsibility ` Create a new responsibility ` Modify an existing responsibility
2 of 22
` Access to views within the application is controlled by responsibilities ` Understanding responsibilities is required to properly configure users within the application
4.3
Business Challenge
Large-scale enterprise applications should not grant all users access to the entire application, for example:
` Most users should not have access to system administration views ` Most users should not have access to all data in the application, for example:

Employee salaries, sales contracts, and other sensitive data Data not related to the employees job function
` Ideally, the restriction mechanisms should be independent of one another:

One mechanism to restrict access to views A separate mechanism to restrict access to data
3 of 22
Application administrators require a mechanism to restrict access to views and data
4.4
Business Solution: Access Control
Siebel applications provide mechanisms known as Access Control to restrict views and data seen by users
` Responsibilities control access to views
Subject of this module Subject of subsequent module
` Positions control access to data
4 of 22
Positions
Positions will be discussed in a subsequent module
` These Access Control mechanisms are independent of one another
4.5
Views and Job Functions
Users should see only those views required to perform their job functions
` Improves efficiency for the user ` Improves business security by preventing unauthorized access to sensitive or administrative views
The System Administrator has many more administrative views than a Call Center Agent. Notice that even the set of screen tabs is different
5 of 22
System Administrator
Call Center Agent
4.6
Responsibilities

Are collections of views associated with a job function

` All of the views necessary to perform that particular job function
Are assigned to users according to their job functions Users may have more than one job function, hence may have more than one responsibility
Views Responsibilities contain one or more views
Responsibilities Assign users one or more responsibilities
Users
6 of 22
Reference
Siebel Security Guide: Configuring Access Control
4.7
Properties of Responsibilities
A view may be contained in multiple responsibilities

` For example, the Home Page View of an application should be included in every responsibility used to access that application
Multiple users may share the same responsibility

` For example, Call Center agents
Views
Responsibilities The same view may be contained by multiple responsibilities
Users
Multiple users may share the same responsibility
7 of 22
4.8
Seed Responsibilities

Are a set of responsibilities provided with the Siebel application

` Automatically created during application installation
Cannot be modified or deleted May be copied to create new, editable responsibilities
Seed responsibilities are created when the application is installed
8 of 22
4.9
Creating New Responsibilities
If the existing seed responsibilities are not sufficient for your business requirements, create new responsibilities as required
` New responsibilities may be edited or deleted
Create new responsibilities for customized, editable responsibilities
9 of 22
4.10
Assigning Responsibilities to Users
Assign responsibilities to users according to their job role(s)

` Users with multiple responsibilities see the union of the views ` Users with no responsibilities see nothing
Critical to remember to assign responsibilities to partners and Web customers
Click the Select button to bring up the Responsibilities list
CCHENG has many responsibilities, and is able to see all of the views in all of them
10 of 22
4.11
Primary Responsibilities
Assign each user a primary responsibility

` Determines the initial tab layout when the user logs in

Administrator determines the initial layout User can edit personal preferences to create a different layout
CCHENGs primary responsibility is Universal Agent (B2B+B2C), so she initially sees the tab layout for that responsibility

0/3
4.12
Creating a Responsibility
1. Copy or Create a Responsibility 2. Add or Remove Views 3. Test the Responsibility
12 of 22

1/3
4.13
1. Copy or Create a Responsibility

Navigate to the Administration Application > Responsibilities view Copy an existing responsibility with a set of views similar to your requirements Alternatively, create a new responsibility to start without any views
Right-click and select Copy Record to create a duplicate responsibility
13 of 22

1/3
4.14
1. Copying or Creating Responsibilities
Copying seed responsibilities:

` Provides a quick start in creating responsibilities with large numbers of views ` May provide far more views than your business logic requires

Seed responsibilities frequently contain hundreds of views Inefficient for inexperienced users May include inappropriate administrative views
` Allows fine-tuning of application logic to exactly match business requirements
Users see only those views that your company has decided they require to perform their job functions
` Requires determining exactly which views a user may require and adding those views to the responsibility
14 of 22
Creating new responsibilities:

2/3
4.15
2. Add or Remove Views

Add or remove views from the responsibility as necessary A pick applet provides querying functionality and improves efficiency when selecting views
1. Click Add to add views to a responsibility
2. Pick applet supports querying for and adding multiple views at once
15 of 22

2/3
4.16
2. Read-Only Views
After editing the set of views for the responsibility, mark views as read-only for that responsibility if desired
` Allows different responsibilities to have different levels of access to the same view
Mark views as Read Only Views to prevent editing
16 of 22

2/3
4.17
2. Clear the Cache
Clear the responsibility cache to ensure that users will see their updated responsibilities the next time they log in
Click Clear Cache to clear the responsibility cache after creating or modifying responsibilities
17 of 22

3/3
4.18
3. Test the Responsibility

Assign the responsibility to a sample user

` Use the Administration User > Users view
Log in as that user and verify the available views from the Site Map
` Users only see references to views that are contained in their responsibilities
Examine the Site Map to confirm that only views associated with the responsibility are shown
18 of 22
4.19
Additional Features
Use responsibilities to restrict access to business services, business processes, and tasks
` This prevents unauthorized users from invoking them
19 of 22
4.20
Module Highlights
Responsibilities
are collections of views used to limit the views
visible to a user Responsibilities have a M:M relationship with views and users Create responsibilities by copying and editing seed responsibilities or by creating new responsibilities Assign responsibilities to a user and clear the responsibility cache before testing a responsibility
20 of 22
4.21
Lab

` Explore seed responsibilities ` Create and test a new responsibility
21 of 22
4.22
Users, Positions, and Organizations
5.1
Module 5: Users, Positions, and Organizations
5.2
Module Objectives
` Describe how data access is controlled by users, positions, and organizations ` Implement the company structure using divisions, organizations, positions, users, and employees
2 of 22
` Access to some data within the application is controlled by users, positions, and organizations ` Implementing your company's structure enables role- and organization-specific functionality in Siebel CRM
5.3
Business Challenge
Large-scale enterprise applications should not grant all users access to all of the data within the application
` For example, sales representatives should see their own sales quota attainment, but no one elses ` On the other hand, sales managers should see all of their reports quota attainments
` This mechanism should be independent of the mechanism to restrict access to views
3 of 22
System administrators require a mechanism to restrict access to data within the application
5.4
Business Solution: Access Control
Siebel applications allow different users to see different data based on their user ID, position, or organization within the company
` Data access control is independent of responsibilities and views ` Example: Ted Arnold and Casey Cheng can access the same view based on their responsibilities, but see different data in the view
4 of 22
Reference
5.5
Users

Are individuals who use the Siebel application

` May be employees, customers, or partners
Require unique user IDs Require at least one responsibility to see views in the application
Note that multiple users can have the same name as long as their user ID is different
Users must have at least one responsibility or they will see no views
5 of 22
Reference
Developing and Deploying Siebel Business Applications: Required Application Administration Tasks
5.6
Employees
Are a special type of user representing employees of the company

` Employees have one or more positions within the company ` Each position belongs to an organization within the company
Employees are users who have positions that belong to organizations Positions Organizations
Users
Employees
Responsibilities
All users have responsibilities, whether or not they are employees
6 of 22
5.7
Positions
Positions are used to control access to data within the application

` For example, a sales representatives accounts are only visible to members of his or her sales team
Employees may have one or more positions

` One position is designated as the primary position, and is the position employees occupy when they log in ` Employees only see data for their current position ` Employees may change positions once they have logged in
7 of 22
5.8
Changing Positions
If an employee has more than one position, he or she can change position during a session
` From the application-level Tools menu, select User Preferences > Change Position ` Becomes the Active Position for that session
Changing the default login (primary) position for an employee is an administrator function
8 of 22
5.9
Position Hierarchy
Positions are arranged in a hierarchy

` Defines a reporting structure that allows managers to see data from their direct and indirect reports ` The Administration Group > Positions view shows this hierarchy
Also shows the primary for each position
The VP of Sales position can see data for the Eastern Sales Manager and Eastern Sales Rep positions
9 of 22
5.10
Divisions and Organizations

A company is divided into divisions representing lines of business, regions, or departments Divisions are arranged in a hierarchy Organizations are a special type of division used to restrict data access within that division
` Data is shared among divisions within an organization
10 of 22
5.11
Example: MegaCorp Organizational Structure
Here is a sample organizational structure of a sample company, MegaCorp Default

Default Organization
All divisions belonging to Default Organization share the same data access
MegaCorp HQ
Organization is the root of the hierarchy
NA Sales
EMEA Sales
Partner Sales
Customer Training
Internal Training
Financial Services
Public Sector
Telecoms & Media LEGEND

Division Organization
European Partners
ASIA/PAC Partners
Partner organizations created to segregate data
11 of 22
MegaCorp Sales
MegaCorp Training
MegaCorp Consulting
5.12
Positions and Divisions

A position is assigned to one, and only one, division A position is associated with one, and only one, organization:
` The organization to which the division belongs
The Eastern Sales Manager position is assigned to the MegaCorp East Sales division This position is associated with the MegaCorp East Sales division, which belongs to the Default Organization
5.13
Example: NA Sales with Positions and Users
The NA Sales division (part of Default Organization) might have users and positions that look something like this:
MegaCorp NA Sales VP of Sales Chris Miller MegaCorp West Sales Western Sales Manager Sean Murphy
LEGEND
Division Organization Position
Eastern Sales Manager Peter Summers
Western Sales Rep 1 Todd Oleak
Western Sales Rep 2 Marion May
Eastern Sales Rep 1 Kelly Wilson
Eastern Sales Rep 2 Wasaka Takuda

13 of 22
MegaCorp East Sales

0/5
5.14
Implementing the Company Structure
1. Create Divisions and Division Hierarchy 2. Label Some Divisions as Organizations 3. Create Positions 4. Create Employees 5. Create Users
14 of 22

1/5
5.15
1. Create Divisions and Division Hierarchy
Create divisions in the Administration Group > Internal Divisions view

` Required fields are division name and currency ` Be careful: Once divisions are created they cannot be deleted
15 of 22

2/5
5.16
2. Label Some Divisions as Organizations
Label divisions as organizations by clicking the Organization Flag check box

` Be careful: This cannot be undone
Organization Flag check box
16 of 22
Default Organization Default Organization is one of the seed organizations in the Siebel application. Because much of the seed data is assigned to Default Organization, it should not be modified.

3/5
5.17
3. Create Positions

Create Positions on the Administration Group > Positions view

` Positions require a name and a division
Siebel applications provide some seed positions such as Siebel Administrator Recommended practice: Do not delete positions, as they are related to data
The Siebel application has four seed positions, including Siebel Administrator
17 of 22

4/5
5.18
4. Create Employees
Use the Administration User > Employees view to create employees

` Employee will also appear as a user
Required fields are First Name, Last Name, User ID, Position, and Organization By default, new employee records are in the same organization as the person creating the record
18 of 22
` Used for access control of visibility of employee records ` Can be changed to reflect appropriate access control

5/5
5.19
5. Create Users

Some users will not be employees

` For examples, customers and partners
Create them in the Administration Users > Users view

` Customers and partners require responsibilities, but not positions
19 of 22
5.20
Module Highlights
Users
are individuals who log in to the application are special users representing employees of the
` Require responsibilities
Employees
company
` Hold at least one position ` Belong to at least one organization
Positions
20 of 22
are similar to job titles, and are used to determine what data an employee can see Divisions represent divisions within the company Organizations are specialized divisions used to limit data visibility
5.21
Lab

` Implement a company structure, including divisions, organizations, positions, and employees
21 of 22
5.22
Controlling Access to Customer Data
6.1
Module 6: Controlling Access to Customer Data
6.2
Module Objectives
` Describe the difference between customer and master data in Siebel applications ` Describe the different Access Control mechanisms used to restrict access to data in Siebel applications ` Identify the different view types used for different types of users
` To effectively use and administer Siebel applications, you need to understand how access to data is controlled ` Understanding view types is essential to properly assigning them to responsibilities
2 of 26
6.3
Business Challenge
Users often perform the same job functions but on different sets of data
` For example, sales representatives need access to the records for their own accounts, but not each others
Access to some data in the enterprise needs to be restricted

` Users should only see records they need to do their job ` Users should easily locate records of interest
3 of 26
6.4
Business Solution: Access Control for Data
Siebel applications provide mechanisms to restrict access to certain records based on:
` The employee ` The employee's position ` The positions organization
Limited access to data:
4 of 26
Reference
` Increases business security ` Increases user productivity
6.5
Relationship Between Views and Data
Access to views is independent of access to data

` But the view defines the Access Control mechanism that will be used to access data
Data displayed within a view is based on the Access Control mechanism for the view
` Example: Ted Arnold and Casey Cheng can access the same view based on their responsibilities, but see different data in the view
Casey Cheng (CCHENG) sees only her own service requests
Ted Arnold (TARNOLD) can access the same view but sees only his own service requests there
6.6
Data Classification
Data in a Siebel Enterprise is classified as either customer data or master data Customer data:
Master data:
` ` ` ` Includes static, referential data such as products and literature Is created and maintained by administrators Can be grouped into categories and catalogs Has access controlled according to catalog and category
6 of 26
` Consists of dynamic, transactional data such as service requests and opportunities ` Is typically created and managed by users of the application ` Has access controlled at the record level according to employee, position, organization, or a combination thereof
6.7
Accessing Customer Data
Individual records may be restricted by employee, position, organization, or a combination thereof

` Data visibility is determined by Siebel-set properties of the underlying business component (BC) ` Visibility may be restricted to an individual employee, position, or organization, or multiple employees, positions, or organizations
Position
Records
Employee Record visibility is restricted by a combination of employee, position, and organization, depending on the underlying BC
Employees are assigned to positions. Each position is assigned to one and only one organization
Organization
6.8
Viewing Customer Data
For customer data that is access controlled, visibility is determined using the following drop-down visibility filters:
` ` ` ` ` My views My Teams views All views All Across My Organizations views All Across Organizations views
The visibility filter dropdown list shows the views available according to the users responsibilities
Assigning the appropriate views to the appropriate responsibilities is critical for data access control
6.9
My Views
My views show records where you or your position is directly associated with the record
` For example, My Accounts or My Contacts
For some records such as Accounts or Opportunities there is a team of positions associated with each record
` The record appears in My View if your position is on the team
A sales agent only sees accounts for which the sales agents position is on the account team
9 of 26
Primaries
In order for a team-controlled record to be visible in the My views, a primary team member must be specified.
6.10
My Personal Views
Are used to display records directly owned by you or your position Are special-case views that are rarely used (for example, with Contacts)
A sales agent only sees contacts for which he or she is the direct owner
10 of 26
6.11
My Teams Views
Are an additional view for managers that allow them to see records assigned to their direct and indirect reports
` For records with teams of positions, only records where the primary is the direct or indirect report are displayed ` Manager does not have to be assigned to the record
Are typically assigned only to manager responsibilities Are implemented using the position hierarchy
Manager sees only the accounts for which the managers direct or indirect reports are the primary position on the account
11 of 26
6.12
All Views
Are used to show all records belonging to your current organization

` The organization of your current position ` Not related to My or My Teams views, which are person or position oriented
A service agent sees all the service requests assigned to his or her organization, regardless of the owner
12 of 26
Primaries
In order for a team-controlled record to be visible in the All views, a primary team member must be specified.
6.13
Customer Data and Organizations

By default, when a record is created it is associated with the organization of the creators current position To change the organization associated with a record, use the More Info view
` Records may be associated with multiple organizations
A records Organization is usually shown under the More Info tab in the detail view
13 of 26
6.14
All Across My Organizations Views
Are used to display all data from an organization and its child organizations
` Based on the relationships specified by the organizational hierarchy
Are typically restricted to users who need to access records at the enterprise level
Are typically used for only a few types of records

` For example, opportunities ` In the All Opportunities Across My Organizations view, a sales manager sees all opportunities in his or her organization and all of its child organizations
14 of 26
` Mid-level executives ` Partners
6.15
All Across Organizations Views

Are used to show all records in the enterprise that are assigned an organization Are typically restricted to only those users who need to access records across the whole company
` Top-level executives
A vice president of sales can see all service requests that have been assigned
15 of 26
6.16
Administration Views
Are used to display all database records, even those without a valid owner
` For example, records that have just been imported but not yet assigned or records where the primary position has been deleted
Administration views are separate from the visibility filter drop-down list
16 of 26
Are accessed from the Administration views for each major entity Should be restricted to a few users in the enterprise as they display all records in the database
6.17
Summary: Types of Views

Views My View My Personal View My Teams View (Managers View) Description Displays records directly assigned to you based on user ID or active position Only displays records you directly own Allows managers to see records assigned to their direct and indirect reports that are the primary owner based on reporting structure Displays all records associated with the users organization Displays records that are assigned to the users organization and its child organizations Displays all records in the enterprise with a valid organization Display all records in the database, even those without a valid organization
All View All Across My Organizations View All Across Organizations View Administration Views
17 of 26
6.18
Best Practices for Views
My Views:
` Individual contributors should always have access
Allows them to see records directly associated with them or their position Require access if they might be on a team associated with a record Do not require access if they will never be associated with a record
` Managers and executives may or may not require access

` Individual contributors should not have access unless they have people who report to them ` Managers should have access
Allows them to see records associated with their reports
` Executives may or may not require access
18 of 26
My Teams Views:
6.19
Best Practices for Views Continued
All Views:
` Individual contributors may or may not need access

Call center agents should be able to see all of a companys service requests, hence should have an All Service Requests view Sales representatives may or may not need to see all opportunities within their organization, depending on the business model
` All views are typically restricted to users who need to access records at the organization level

Executives, administrators Service agents who need to access all service requests
All Across Organizations Views:

` These views are usually reserved for upper managers and executives
Exception: Call center agents may need to see all service requests filed by a customer worldwide, hence may need access to these views
19 of 26
6.20
Review: Access to Customer Data
Can be restricted by assigning individual records to:

` Employees (specified by employees user ID) ` Positions ` Organizations
20 of 26
6.21
Using Multiple Access Control Mechanisms
A record can be restricted by more than one Access Control mechanism

` Mechanisms are not mutually exclusive
Each view is preconfigured to use only one mechanism at a time

` If you want to use another mechanism, you create and configure another view
21 of 26
6.22
Examples
An employees position may be assigned to an account that is not assigned to that employees organization
` Employee sees the account in the My View ` Employee does not see the account in the All View
Contacts have multiple access mechanisms: public (teambased), private (position- or employee-based), and manager
22 of 26
` Employee sees public contacts in the My View ` Employee sees private contacts in the My Personal View ` Manager sees contacts for self and subordinates in the My Teams View
6.23
Summary of Record Assignment
Standard Siebel business entities can be assigned to single or multiple employees, positions, or organizations
Access Method
Single-Valued Access Service requests Expense reports Contacts Forecasts Quotes Assets Consumers Forecasts
Multi-Valued Access Assets Activities Accounts Contacts Opportunities Accounts Opportunities Quotes Team Access Control
Employees
Positions
Organizations
23 of 26
6.24
Module Highlights
Access
to records may be restricted by employee, position, organization, or a combination thereof Which records are shown depends on the view selected from the visibility filter drop-down list Multiple Access Control mechanisms may be in place for a single record
24 of 26
` For example, both position-based and organization-based Access Control
6.25
Lab

` Explore record visibility in the application ` Add a position to a user an examine how it affects the various visibility filters
25 of 26
6.26
Catalogs and Master Data
7.1
Module 7: Catalogs and Master Data

7
7.2
Module Objectives

` Identify how master data is organized into catalogs and categories ` Identify how users are organized into access groups

` Administering master data requires an understanding of catalogs, categories, and access groups
2 of 26
7.3
Business Challenge
Companies have large amounts of data that must be:

` Classified, so that it is easy to organize, administer, navigate, and search ` Controlled, so that users only have access to appropriate data
Example: Companies want different sales divisions to have access to different product lists
3 of 26
7.4
Business Solution
Siebel applications provide mechanisms for:

` Organizing and classifying large amounts of static, referential data ` Organizing users into groups for appropriate access to data
4 of 26
7.5
Master Data
Is static, referential data managed by administrators

` ` ` ` ` ` ` ` ` Products Solutions Literature Resolution items Auction items Events Decision issues Competitors Training courses
Has its visibility controlled by:

` Catalogs ` Categories ` Access groups
5 of 26
7.6
Catalogs

Are containers for hierarchies of categories

` Do not contain master data themselves
Are created to contain a specific subset of the master data

` For example, customer documentation for credit card accounts Catalog A
Product 1 Product 2 Product 3 Literature Item 1 Product 4 Product 5
Subcategory A
Product 3 Product 6
Subcategory A
Product 2 Literature Item 2
Subcategory B
Literature Item 1
6 of 26
Reference
Siebel Order Management Guide: Creating and Managing Catalogs
Category A
Category B
Category C
7.7
Catalogs Continued
May be declared public or private

` Public catalogs are visible to all users
Categories within public catalogs may still be marked private
` Private catalogs have their visibility limited to privileged groups known as access groups
Catalog A (Public)
Catalog B (Private)
A public catalog is visible to all users; individual categories within that catalog may still be marked private
Categories within private catalogs are private
7 of 26
For example, a credit card documentation catalog might be public to allow users to see the service agreements and benefits However, a customer service documentation catalog might be private to restrict visibility to those with service agreements
7.8
Catalog Types
Are assigned to catalogs

` Catalogs should have a catalog type ` Seed catalog types include:

Are used when querying for master data
8 of 26
Infocenter Buying Partner eService FAQ Customer Multiselect Checkbox Training Partner Program Training Curriculum
7.9
Categories
Are nodes in a catalog that contain:

` Master data ` Other categories
Are not shared between catalogs

` However, multiple catalogs may contain categories with the same name
May be declared public or private
9 of 26
` If a category is declared private, all of its subcategories are also private ` Private categories also have their visibility limited to specified access groups
7.10
Categories: Example
Even though Category B and Category C both contain subcategories named Subcategory A, these two subcategories are distinct Since Category B is private, its Subcategory A is also private
Catalog A
Category A
Product 1 Product 2 Product 3 Literature Item 1 Product 4 Product 5
Category B has been marked as private
Subcategory A
Product 3 Product 6
Subcategory A
Subcategory B
Literature Item 1
10 of 26
Category B
Category C
7.11
Access Groups
Are collections of positions, organizations, user lists, and households used to access private catalogs and categories Cannot contain individuals such as employees and users
` To add an individual, create a user list with that individual as the only member
Create User Lists in the Administration Group > User Lists screen and add them to access groups
11 of 26
7.12
Access Group Hierarchies
Access groups can be organized into a hierarchy

` Child access groups inherit all of the access granted to their parents, hence have more privileges than their parents ` Useful for giving more privileged users greater access
Parent access group
Child access groups
12 of 26
7.13
Access Control

Assign access groups to catalogs or categories

` Unlike customer data, individual records are not controlled
Access groups must be assigned to every catalog or category to which they need access
` Access is not inherited along the category hierarchy Catalog A
Category A
Product 1 Product 2 Product 3 Literature Item 1 Assign Access Group X to Category B Product 4 Product 5
Subcategory A
Product 3 Product 6
Subcategory A
Product 2 Literature Item 2 Also assign Access Group X to subcategory A if access is required
Subcategory B
Literature Item 1
13 of 26
Category B
Category C
7.14
Access Control Continued
An access group can only be added to a category if:

` The access group is also assigned to the categorys parent, or ` The access group is a child of an access group assigned to the parent Catalog A
Category A
Product 1 Product 2 Product 3 Literature Item 1 Product 4 Product 5 Assign any access group to Category B because its parent (Catalog A) is public
Category B
Category C
Product 3 Product 6
Subcategory A
Subcategory B
Literature Item 1
Cannot assign Access Group Y to Subcategory A unless
Access Group Y is assigned to Category B, or Access Group Y is the child of an access group assigned to Category B
14 of 26
Subcategory A
7.15
Access Control Continued

Removing a parent access group from a category also removes all child access groups from all subcategories Example: Suppose Access Group Y is a child of Access Group X
Catalog A
Category A
Product 1 Product 2 Product 3 Literature Item 1
Removing Access Group X from Category B
Category B
Product 4 Product 5
Category C Subcategory A
Product 3 Product 6
Subcategory A
Subcategory B
Literature Item 1
removes Access Group Y from Subcategory A
15 of 26

0/6
7.16
Building a Catalog
1. Create the Catalog 2. Add Categories to the Catalog 3. Associate Master Data with Categories 4. Declare Catalogs or Categories Private 5. Create Access Groups 6. Assign Access Groups
16 of 26

1/6
7.17
1. Create the Catalog

Navigate to Administration Catalog > Catalogs Create a new catalog
` Specify a name ` Specify a catalog type ` Specify other options
By default, the catalog is active; mark it as inactive to make it unavailable, for example, during updates
Specify sequence numbers to change the order in which catalogs appear

17 of 26

2/6
7.18
2. Add Categories to the Catalog

Drill down on the catalog name in the Catalog view to navigate to the Categories view Add categories to the catalog
Drill down on a catalog to see its categories
Use buttons to promote and demote subcategories
18 of 26

3/6
7.19
3. Associate Master Data with Categories
Select the appropriate tab in the Categories view to add master data to a category
For example, select the Literature tab to add product literature
19 of 26

4/6
7.20
4. Declare Catalogs or Categories Private
Set the Private flag at the catalog or category level to restrict data access
` Subcategories are automatically marked as private
Marking the Gold category as private automatically causes the Premium and Regular Customers categories to be marked as Private
20 of 26

5/6
7.21
5. Create Access Groups

Navigate to Administration Group > Access Groups Create the access group hierarchy as required
` Create parents, then children ` Specify parents for child records
Specify the parent access group when creating the child access group; this requires creating the parent first

5/6
7.22
5. Create Access Groups Continued
Add positions, organizations, or user lists to access groups
Group type can be Position, Organization, User List, or Household
22 of 26
Click New to add parties to an access group

6/6
7.23
6. Assign Access Groups
Assign access groups to catalogs or categories

` Use the Cascade button to automatically assign an access group to all child categories
Add access groups using the Access Group tab under Categories or Catalogs
Select an Access Group and click Cascade to assign that access group to all child categories
23 of 26
7.24
Access Control Summary

Access Control
Controls access to Views
Determined by Responsibility
Data Customer Data
Master Data
Determined by Access Groups Catalogs & Categories
Examples: Products Literature Competitors etc.
Determined by UserID Examples: Service Requests Product Defects Activities
Determined by Position Examples: Accounts Opportunities Contacts Campaigns
Determined by Organization Examples: Accounts Opportunities Contacts Campaigns
Customer Data Is dynamic and transactional (can be updated) Is created and managed by users of the application Access is controlled at the record level
Master Data Is static, read-only material to the end user Is created and maintained by company administrators Access is controlled at the Catalog and Category level
24 of 26
Personal Ownership
Positions
Organizations
7.25
Module Highlights
Master data is static, referential data such as product catalogs or product documentation Catalogs are containers for categories
` Mark catalogs as private to restrict access to specific access groups
Categories contain master data
25 of 26
` Arranged in a hierarchy within the catalog ` Mark categories as private to restrict access to specific access groups
7.26
Lab

` Navigate catalogs, categories, and access groups ` Restrict access to master data contained in categories
26 of 26
The Siebel Web Architecture
8.1
Module 8: The Siebel Web Architecture
8.2
Module Objectives
` Identify the pieces that make up the Siebel Web architecture ` Identify the role of each piece of the architecture ` Describe how Siebel requests are processed
2 of 20
` Provides a foundation for understanding the relationship between the Siebel software components
8.3
Siebel Web Architecture Overview
At a high level, the Siebel Web architecture consists of:

` Siebel Web Clients that access and display the business data ` A Gateway Name Server that stores configuration information ` A Web server that handles interactions with the Web Clients and distributes requests to the Siebel Servers ` Servers that manage the business data and provide batch and interactive services for clients ` A relational database and file system that store business data
Siebel Web Client Web Server Enterprise Siebel Server(s) Siebel Gateway Name Server
Database Server
Siebel File System

3 of 20
Reference
Siebel Deployment Planning Guide: Siebel Architecture Overview
8.4
Siebel Web Client

Displays the interactive Siebel application used to manage the Siebel data Runs in a variety of environments
` Web browsers, Wireless Markup Language (WML) devices such as mobile phones, and personal digital assistants (PDAs)
Siebel Web Client
Enterprise Siebel Server(s)
Siebel Gateway Name Server
Database Server
Siebel File System
4 of 20
Web Server
8.5
Web Server
Identifies and passes Siebel requests from Siebel Web Clients to the Siebel Servers Passes completed HTML application pages back to Siebel Web Clients Provides load balancing for multi-server installations
` Supports either built-in or third-party load balancing

Database Server
Siebel File System
5 of 20
8.6

Is a Windows service or UNIX daemon process Stores component definitions and assignments, operational parameters, and connectivity information
` For example, connect strings to query servers for server/component availability ` Information stored in siebns.dat file on Gateway Name Server
Database Server
Siebel File System
6 of 20
Siebel Web Client
Web Server
8.7
Siebel Enterprise
Is a logical collection of Siebel Servers that support users and access a single database server and the Siebel file system Logically groups Siebel Servers for common administration via Siebel Server Manager Supports sharing of common configuration information
Database Server
Siebel File System
7 of 20
File System Partitioning
In Siebel 8, the file system may be partitioned over multiple directories and machines.
Siebel Web Client
Web Server
8.8
Siebel Servers
Execute tasks to manage the business data

` Programs known as server components perform specific functions or jobs for the server ` For example:

Importing and exporting data Configuring the database to monitor for user-defined conditions Processing of client requests
Siebel Web Client
Web Server Enterprise Siebel Server(s) Siebel Gateway Name Server
Database Server
Siebel File System

8 of 20
Interactive Tasks Background Tasks Batch Jobs
Interactive tasks wait for input from the user, such as the Siebel Web Client running Siebel Call Center. Background tasks always show as running and periodically perform system functions, such as invoking workflows or performing assignments. Batch jobs run once, either when scheduled or when invoked by an administrator, for example, to perform data imports or exports.
` Tasks may run interactively, in the background, or as batch jobs
8.9
Examples of Server Components
The application object manager (OM) is a server component that provides the environment in which Siebel user sessions run
` Users interact with an application-specific OM; for example, the Siebel Call Center Object Manager (SCCObjMgr) ` Runs in interactive mode
The Workflow Monitor Agent periodically checks the system to determine whether workflows or assignments need to be run Enterprise Integration Manager performs data imports and exports
` Runs in batch mode
9 of 20
` Runs in background mode
8.10
Siebel File System
Is one or more shared directories that store files used by Siebel applications
` Files are compressed in a proprietary format to save space and provide security ` Examples: Product literature, sales tools, presentations, user profiles
Database Server
Siebel File System
10 of 20
Siebel Web Client
Web Server
8.11
Database Server
Stores data used by Siebel applications in a predefined database schema

` Single database for Enterprise provides data consistency for users ` Data is accessed by components through a data manager layer
Supports a variety of third-party relational database management systems (RDBMS)

Database Server
Siebel File System
11 of 20
Supported RDBMSes See the Siebel System Requirements and Supported Platforms document for a list of supported RDBMSs.
8.12
Web Usage Login Scenario
Siebel Web Client (browser) sends the URL to the Web server
` URL specifies:

Either HTTP or HTTPS protocol Web server machine name Application and language
URL initially connects to a Siebel-specific virtual directory on the Web server

Siebel Web Client <browser>
http://websrvr1/callcenter_enu
Web Server Virtual Directory
1. Browser sends URL to Web server
[/callcenter_enu]
<websrvr1>
2. Connects to the virtual directory on the specified Web server

` Virtual directories are created as part of the Siebel installation
8.13
Web Usage Login Scenario Continued

Virtual directory forwards request to the Siebel Web Server Extension (SWSE) installed on the Web server SWSE uses the eapps.cfg configuration file to obtain connection parameters
Siebel Web Client <browser> 3. Virtual directory specifies to use SWSE
Virtual Directory
[/callcenter_enu]
SWSE <websrvr1>
Eapps.cfg
4. SWSE locates the requested section in eapps.cfg
13 of 20
Web Server
8.14
Eapps.cfg specifies the location of the server, server connection broker port, Enterprise, and Object Manager information for initial connection
` For multi-server installations provides load balancing information ` Also provides generic login information for initial anonymous access to database
5. eapps.cfg specifies connect string values
Enterprise <Siebel> Web Server <websrvr> Siebel Server <EMEJHG20> Object Manager SCCObjMgr_enu
14 of 20
8.15
Object Manager reads an application-specific configuration file and component parameters, which specify the application, the location of the Siebel Repository File (SRF), and so forth
` Siebel Repository File is a separate binary file that defines one or more Siebel applications
Discussed in greater detail in subsequent modules
Enterprise <Siebel>
Siebel Gateway Name Server 6. Object Manager reads CFG file on server and component parameters from Gateway Name Server
Siebel Server Object Manager SCCObjMgr_enu Database Database Server Server
CFG
SRF
15 of 20
` Most configuration information is specified by component parameters rather than in the configuration file
8.16

Object Manager retrieves data through data manager The Siebel Web Engine (SWE), part of the Object Manager, reads a set of Web templates that are stored on the Siebel Server and creates HTML pages for the data requested
` Siebel Web Templates (SWT) are a set of template files that specify how to render the UI in the users browser
HTML files with embedded Siebel tags defining content

Siebel Server Object Manager HTML login page CFG
SWE
SRF
Database Database Server Server
SWT
8. SWE reads Web Templates and creates HTML pages
16 of 20
Enterprise <Siebel>
7. OM retrieves data through data manager layer
8.17
The Object Manager sends the completed Web page to the Web server, which passes it back to the Siebel Web Client
Siebel Call Center
Enterprise <Siebel> Web Server HTML login page <websrvr1> Siebel Server <SS1> Object Manager SCCObjMgr_enu
17 of 20
8.18
Physical Architecture
The Siebel Gateway Name Server, Siebel Server, database server, and File System can be implemented on one machine or spread across multiple machines
` SWSE can be on that machine for development or test environments
The Siebel Server(s) should have a high-speed LAN connection to the database server
Siebel Gateway Name Server Enterprise Server Siebel Server
Web Server SWSE
Siebel File System Firewall Siebel Server Database Server

18 of 20
Firewall
Recommended Practice
For development or test environments (such as we use in this classroom), it is possible to bundle the entire application on a single machine. For production environments, the recommended practice is to have the Database Server, SWSE, and Siebel Enterprise on separate machines.
High-speed LAN
8.19
Module Highlights
A
19 of 20
Siebel Web Client displays the Siebel application in a standard Web browser A Siebel Web Server is a third-party Web server with the Siebel Web Server Extension (SWSE) installed and the Siebel application virtual directories created A Siebel Gateway Name Server stores parameters and connection information for Siebel Servers A Siebel Enterprise is a logical collection of Siebel Servers A Siebel Server is a set of processes that manage processing for all Siebel clients
8.20
Lab

` Examine the virtual directories and eapps.cfg ` Verify the information contained in the files against information retrieved from the application
20 of 20
Server Components and Parameters
9.1
Module 9: Server Components and Parameters
9.2
Module Objectives

` ` ` ` Define component groups Define components Describe parameters as inputs for components Describe the various levels at which you can set parameters and how to set them ` Describe named subsystems and job templates

` Server behavior is controlled by components and parameters, hence an understanding of how to find and configure them is essential
2 of 22
9.3
Review: Siebel Web Architecture
The Siebel Web architecture consists of a Web Client, Web server, Gateway Name Server, and Enterprise containing one or more Siebel Servers
` Each Siebel Server includes its own set of components: programs that run on the server to provide application functionality
Database Server
Siebel File System
3 of 22
Siebel Web Client
Web Server
9.4
Examining the Siebel Enterprise
View the Siebel Enterprise hierarchy using the Enterprise Explorer View of the Server Administration Configuration screen
3. OUsrvr has these components available
4 of 22
1. This Siebel Enterprise is named Siebel
2. The first server listed in the enterprise is OUsrvr
9.5
Component Groups

Are logical groupings of components

` Components are enabled or disabled in groups
Support major functional areas of the application

` For example, Siebel Call Center, Siebel Remote, or Assignment Management
The Enterprise Explorer lists the available component groups
The detail pane provides additional information such as the number of components in each group
5 of 22
Reference
Siebel System Administration Guide

0/3
9.6
Enabling and Assigning Component Groups
There are three steps to enable a component group on a server: 1. Enable the Component Group for the Enterprise 2. Assign the Component Group to the Server 3. Enable the Component Group on the Server
6 of 22

1/3
9.7
1. Enable the Component Group for the Enterprise
Click the Enable or Disable buttons in the detail pane of the Enterprise Explorer to enable or disable component groups
` By default, most component groups are enabled for the enterprise ` Components within disabled component groups are not available on any of the servers in the enterprise
Best Practice: Disable component groups which will never be used on any server
Click the appropriate button to Enable or Disable a component group for the enterprise
7 of 22
` Enabled component groups take a small amount of resources on the Siebel Gateway Name Server

2/3
9.8
2. Assign the Component Group to the Server
In Administration Server Configuration > Enterprises, select the component group and server and click Assign
` Stores component group information on the Siebel Gateway Name Server ` Allocates memory for the component group on the Siebel Gateway Name Server
1. Select component group to assign 2. Select server 3. Click Assign
8 of 22

3/3
9.9
3. Enable the Component Group on the Server
Once you have assigned a component group to a server, enable or disable it on the server
` By default, assigning a component group automatically enables it
Best practice: Assign and disable component groups that you are not using now but may use in the future on that server Select the desired server and click the Enable or Disable button
Click Enable to enable the selected component group on the selected server
9 of 22
` Enabling allocates memory on the server for that component group ` The component group is now available to the server
9.10
Synchronize Components
Synchronize components after enabling or disabling a component group that includes batch components
` Registers batch components with the Siebel Gateway Name Server ` Makes these components available to the Siebel Enterprise
Also possible to synchronize individual components
Synchronize every time a component group is enabled
Prior to initial synchronization, no components are available to run batch jobs

9.11
Manage Individual Components
Specify startup behavior for individual components

` Auto Start: The component automatically starts up when the Siebel Server service starts ` Manual Start: The component must be started manually
Prevents component from consuming memory or processor time until it is needed
Click Manual Start under Administration Server Configuration > Servers to set the component to manual startup
11 of 22
9.12
Executing Components

When a component executes, it is called a task

` Multiple instances of the same component may run simultaneously
Components execute in one of three modes:

` Batch components run once until completion

Batch component executions are also called jobs Usually initiated by user action, event, or workflow For example, data loads or database extracts Periodically wake up and execute For example, transaction processor for tracking changes to the database For example, application object managers
` Interactive components run in response to client requests
12 of 22
` Background components run continuously in the background
9.13
Component Parameters
Are input arguments for tasks Are set at one of five levels:
Enterprise parameters
Not shown: Task parameters are set when starting tasks, hence do not appear in the Enterprise Explorer
13 of 22
Examples
The language code, ODBC data source name, and communication parameters are enterprise parameters. The location of the server log file is a server parameter. The sleep time for a background component that runs periodically is a component definition parameter. Change the server component parameter to change that sleep time for one particular server. The user ID of a mobile user to extract is a task parameter.
` Enterprise parameters are set throughout the enterprise ` Server parameters are set at the individual server level ` Component Definition parameters are specific to a component, but enterprisewide ` Server Component parameters allow a server to override a component definition ` Task parameters are for an individual component when it is run
Server Component parameters Server parameters Component Definition parameters
9.14
Hidden and Advanced Parameters

More advanced parameters are classified as hidden or advanced Click the appropriate button to see these parameters Click the Reset button to return to the normal set of parameters
Click Advanced or Hidden to see advanced or hidden parameters
14 of 22
9.15
Component Definitions
Are sets of parameters associated with a component to determine its behavior when it is run
` Set enterprise-wide, so that the component performs the same no matter which server it is run on
Reconfigure definitions to modify component behavior Duplicate definitions to create new component definitions
Modify parameters or duplicate a definition to create a new component with different set of parameters
` Creates a duplicate component with a new name and a different set of input parameters
9.16
Parameter Inheritance
Parameters are set at any of five levels

` Parameters set at any level are inherited at all lower levels
For example, parameters set at the enterprise level are inherited for the levels below it
` Parameters set at any level override parameters set at a higher level
For example, parameters set when starting a task override those set at higher levels
Highest level
Enterprise Enterprise Server Server ComponentDefinition Definition Component ServerComponent Component Server
Lowest level
Task Task
16 of 22
9.17
Removing Parameters
Do not attempt to delete parameters by setting their value to zero or null

` Causes zero or null value to be passed to component
Use Delete Parameter Override to remove parameter settings at a given level
Select Delete Parameter Override to remove parameter values

9.18
Profiles
Are sets of parameters that may be used by multiple components

` Also referred to as named subsystems
Are edited to modify behavior of multiple components
For example, the set of parameters used to send email alerts to administrators is used by multiple components
Modify the profile parameters to change the behavior of all components using this profile
Profiles and Parameters
Parameters set in Profiles override those set at the Enterprise, Server, or Server Component level.
9.19
Job Templates
Job templates are predefined sets of parameters for use with batch components
` Recall: When a batch component is executed it is called a job
Multiple job templates can exist for the same component

` For example, weekly assignments versus daily assignments
Both assignment jobs run the same component; only the set of input parameters is different
For example, a job template containing parameters for a weekly batch assignment job
This job template is specific to the Assignment Manager component
19 of 22
Unlike profiles, job templates are specific to a single component
9.20
Job Templates Continued
Create job templates by specifying the batch component to be used and entering the job-specific parameters
` Located under Administration Server Configuration > Job Templates
1. Click New to create a new template 2. Select the component
4. Set parameter values
3. Click New to create a new parameter; a select applet lists parameters for that component
20 of 22
9.21
Module Highlights
Component Groups are logical groupings of server components Enable component groups on the enterprise, assign them to a server, and enable them on that server Set individual components to automatic or manual start up Set component parameters at one of five levels: Enterprise, Server, Component Definition, Server Component, or Task
Profiles are sets of parameters used by multiple components

` Also known as named subsystems
Job templates are sets of parameters used to execute batch components
21 of 22
` Parameter values are inherited from higher levels ` Use Delete Parameter Override to restore inheritance
9.22
Lab

` Use the Enterprise Explorer to examine component groups, components, and parameters ` Examine parameter inheritance ` Enable a component group on a server
22 of 22
Server Management
10.1
Module 10: Server Management

10
10
Server Management
10.2
Module Objectives

` Monitor the state of the enterprise, and individual servers and components within that enterprise ` Perform routine administrative tasks on the enterprise, including:


` These administrative tasks must frequently be performed while configuring and testing a deployment
2 of 26
Managing components Backing up and restoring the enterprise Setting logging options Submitting jobs
Server Management
10.3
Server Administration
Once components have been enabled and their parameters have been defined, perform common administration tasks:
` Monitor the system ` Change component parameters or component states, preferably without shutting down the server ` Back up the system after making these changes ` Submit batch jobs for processing
` A command-line interface is also available
Useful for using scripts to interact with the enterprise
3 of 26
Reference
Siebel System Administration Guide: Using the Siebel Server Manager Command-Line Interface
10
Perform these tasks using the Administration Server Management screen
Server Management
10.4
Server Groups
Add servers to a Server Group using the command-line tool:

change attribute groupname=<group name> for server <server name>
Connect to all servers in the group simultaneously:

srvrmgr /g <gateway> /e enterprise /z <group name> /u <user> /p <password>
change parameter NotifyHandler=newHandler ` Changes the parameter for all servers in the server group
Adding a server to a server group allows you to manipulate all servers in that group simultaneously from the command line interface
Performing groupwide manipulations such as changing parameters:
Server Management
10.5
Monitor the Enterprise
Monitor the enterprise from the Administration Server Management screen

` Provides status icons for servers, components, jobs, tasks, sessions, and the enterprise
Administration Server Management > Enterprises shows the states of servers and their components within the enterprise
5 of 26
10
Server Management
10.6
Monitor Sessions
Use the Session Monitor to monitor users logged in and their current activity
` Sessions are tasks running the associated Object Manager
Navigate to Administration Server Management > Sessions
MWEST is currently logged in to Call Center (SCCObjMgr_enu) and is looking at the Account List Applet
6 of 26
Server Management
10.7
Manage Component States

Manage components across the entire enterprise from the Administration Server Management > Components screen Manage components on a particular server from the Administration Server Management > Servers screen In either case, components may be paused, resumed, started up, or shut down
Current component state in the enterprise
7 of 26
10
Server Management
10.8
Component States

8 of 26
Running: The component is available and at least one component task is currently running Online: The component is available but no component tasks are currently running Unavailable: The component is unavailable and no component tasks are running Paused: The component is online but is not accepting new tasks Shutting Down: The server is shutting down; currently-running tasks will execute to completion, but no new tasks can be run Shutdown: The server component is shut down
Server Management
10.9
Change Component Parameters

Change component parameters by changing the Value or Value on Restart Examine the Effective setting to see when the parameter change will become effective
Effective setting indicates when parameter change will become effective

Immediately At Next Task At Component Re-Start At Server Re-Start Require Reconfiguration
The parameter change is effective immediately. The parameter change is effective for all new tasks running that component; currently-running tasks execute with the old parameter. The parameter change does not take effect until the component is stopped and restarted. The parameter change does not take effect until the Siebel Server is restarted. The component must be reconfigured to change the parameter. This is common for parameters that work with or are dependent on other parameters.
10
Server Management
10.10
Reconfigure Component Definitions
Modifies component parameters without shutting down the server(s)

` Useful during site migrations or application updates ` Useful when changing multiple parameters and changes should all be performed at once
For example, when changing both a user name and a password parameter, changing one at a time would lead to authentication issues
` Tasks started before and during reconfiguration continue to run with the old parameters ` Tasks started after the reconfiguration is committed run with the new parameters
10 of 26
During reconfiguration:
Server Management
10.11
Reconfigure Component Definitions Continued

From the Administration Server Configuration > Enterprises screen Start Reconfiguration:
` Opens existing component parameters for modification
Commit Reconfiguration:
Cancel Reconfiguration:
` Cancels the current reconfiguration; component definition remains unaltered
11 of 26
10
` Commits the updated Component Definition ` All tasks started after the commit run with the new parameters
Server Management
10.12
Back Up the Enterprise
Recommended practice: Back up the enterprise after making any configuration changes such as modifying component parameters
` Creates a backup copy of siebns.dat
siebns.dat stores information about components, parameters, and servers
File is in use as long as Siebel Gateway Name Server is running
12 of 26
` May also be used for backup or migration purposes ` Do not try to manually duplicate this file
Server Management
10.13
Restore the Enterprise
Restore a previous enterprise configuration with these steps:

1. Shut down the Siebel Gateway Name Server and the Siebel Server 2. Replace the existing siebns.dat file with a working backup 3. Start the Siebel Gateway Name Server and the Siebel Server
1. For Windows, right-click each service and select Stop
2. Restore a backup of siebns.dat to <siebeldir>\gtwysrvr\ADMIN
3. Right-click each service and select Start

10
Server Management
10.14
Server Event Logging

Monitor server events by setting their log levels Navigate to Administration - Server Configuration > Servers > Server Event Configuration
` Set the log level for each Siebel Server event of interest
Select the Siebel Server for which you want to log events
Select the event type you want to log and enter a logging level from 0 to 5 in the Log Level field
Reference
Siebel System Monitoring and Diagnostics Guide
Server Management
10.15
Log Levels
There are six available logging levels for server events:

` ` ` ` ` ` 0: Fatal 1: Errors 2: Warnings 3: Informational 4: Details 5: Diagnostic
15 of 26
10
Higher log levels generate larger log files and may affect system performance, hence the recommended practice is to only use these levels when troubleshooting
Server Management
10.16
Component Event Logging
Use the Component Event Configuration view to set the log level of component event types
Select the event type you want to log and enter a logging level in the Log Level field
16 of 26
Select the component for which you want to log events
Server Management
10.17
Examine Logs
Each task creates a log of its execution
to view the Task Information Log
17 of 26
10
Drill down on the task number
Server Management
10.18
Examine Log Files
View the log file on the Siebel Server
3. Examine the file
18 of 26
Log File Archiving
Whenever the Siebel Server service is restarted, the log files are moved from the log directory to the logarchive directory.
1. Note the task number
2. Locate the log file in the <Siebel>\siebsrvr\log directory
Server Management
10.19
System Alerts
System alerts collect information about the failure of tasks or unavailability of components, and send email alerts to administrators Examples:
` A component fails to restart ` Critical system throughput thresholds are achieved
1. Select System Alerts in Enterprise Explorer
2. Define new system alerts and alert parameters to notify additional individuals or to handle different types of alerts
Required Component The AdminNotify component must be enabled in order for system alerts to be processed. This component is part of the Auxiliary System Management component group and is enabled by default.
10
Create additional alerts to notify additional individuals or to handle different types of alerts
Server Management
10.20
Using System Alerts
To configure a component to use these system alerts:

` Navigate to Administration Server Configuration > Servers > Components ` Select the component of interest ` Specify the notification handler for that component
One of the system alert profiles previously created
Notification handler is a parameter for every component that specifies which system alert to use
Server Management
10.21
Submit Batch Jobs

Navigate to Administration Server Management > Jobs Create a new job or copy an existing job
` Job templates as well as components are listed for new jobs
Both job templates and batch components are listed in the pick applet
21 of 26
10
Server Management
10.22
Submit Batch Jobs Continued

Specify job parameters Optionally, schedule the job to repeat at regular intervals or to run on a preferred server if it is available Submit the job once all Submit the job
options have been set
Create and define job parameters
Specific parameters depend on the job you are submitting
22 of 26
Jobs can be set to repeat periodically or to have a preferred server on which to run
Server Management
10.23
Manage Batch Jobs
Cancel, pause (hold), or resume jobs from the Administration Server Management > Jobs screen
Cancel, hold, or resume jobs
Batch job appears as a task in the tasks list

10
Monitor the progress of the job from the Administration Server Management > Tasks screen
Server Management
10.24
Module Highlights
Monitor the state of the enterprise, servers, components, tasks, jobs, and sessions from the Administration - Server Management screen Change component parameters
` May require reconfiguring component definitions
24 of 26
Back up the enterprise after changing configurations Set logging options and system alerts to monitor the system Submit and monitor batch jobs
Server Management
10.25
Lab

` Perform common administration tasks
25 of 26
10
Server Management
10.26
Siebel Client Types
11.1
Module 11: Siebel Client Types

11
11
Siebel Client Types
11.2
Module Objectives
` Identify the various Siebel clients ` Describe files associated with each client, including configuration files and local databases ` Describe how each client accesses Siebel servers and data
2 of 18
` Not all users will be able to use the Siebel Web Client at all times, hence understanding other client types is essential
Siebel Client Types
11.3
Business Challenge
Not all Siebel application users have access to the Web at all times
` Some users spend a great deal of time traveling

Sales representatives Executives Instructors
3 of 18
11
Other users may want to access the application using their mobile phones or Personal Digital Assistants (PDAs) Developers may need to access Siebel data when a Siebel Server or even the entire enterprise is down
Siebel Client Types
11.4
Business Solution
Oracle provides five client types for use with the Siebel application:
` ` ` ` ` Siebel Web Client Siebel Wireless Web Client Siebel Mobile Web Client Siebel Handheld Client Siebel Developer Web Client
4 of 18
References
Siebel System Administration Guide Siebel Wireless Administration Guide Siebel Remote and Replication Manager Administration Guide Siebel Sales Handheld Guide
Siebel Client Types
11.5
Siebel Web Client Scenario

Wayne is an employee working from home, and connected to his companys network. He would like to frequently and quickly view and update the activities of his assigned accounts. Since his computer has a browser, but no Siebel software, he types the appropriate URL to access the account data.
Wayne is using the Siebel Web Client

11
Siebel Client Types
11.6
Siebel Web Client
Is a near zero footprint client

` Uses only a Web browser and a network connection ` For High Interactivity (HI) clients, includes ActiveX controls so not truly zero-footprint in HI mode
Siebel Web Client

Browser Siebel File System Database Server
Web Server
SWSE
Enterprise Siebel Server

Object Manager

CFG
SRF
6 of 18
Supported Browsers The Standard Interactivity (SI) client supports most Web browsers. Because the High Interactivity client requires ActiveX controls, it requires Internet Explorer. For details see the System Requirements and Supported Platforms Guide.
Accesses Siebel Servers through the Web Server running the Siebel Web Server Extension (SWSE) Accesses Siebel data through an Application Object Manager (OM)
Siebel Client Types
11.7
Siebel Wireless Web Client Scenario

Wendy is a salesperson. She has a meeting set up with one of her opportunities. Since she is running late, Wendy uses her Webenabled phone to retrieve the meeting information from the Siebel database. As an outcome of the meeting, she updates the sales stage of the opportunity.
Wendy is using the Wireless Web Client

11
Siebel Client Types
11.8
Siebel Wireless Web Client
Allows users to read from, write to, and search the Siebel database through a wireless connection between a mobile device and the Siebel Web Server
` Requires a wireless gateway to translate HTTP data generated by Siebel Wireless to Wireless Application Protocol (WAP)
Uses the same logical data model as the Siebel Web Client
` Same business objects, business components, and so forth ` Determined by the Wireless Object Manager
Siebel Wireless Web Client

Siebel File System Database Server
Wireless Gateway
Web Server
SWSE

Wireless Object Manager

CFG
SRF
8 of 18
Supported Markup Languages
For a list of supported Wireless Markup Languages, see the Siebel Wireless Administration Guide.
Uses wireless-specific applets, screens, and views
Siebel Client Types
11.9
Siebel Mobile Web Client Scenario

Mary is a consultant. She is at the airport waiting for her flight and would like to access contact information for an active opportunity. Since she cannot access the server, she is retrieving this information from a local database on her laptop.
Mary is using the Mobile Web Client

11
Siebel Client Types
11.10
Siebel Mobile Web Client
Is designed to provide full Siebel application functionality without requiring a network connection
` A local executable providing full application functionality must be installed on the client ` This local executable accesses local .cfg and .srf files, and stores its data in a local database and Siebel File System

Synchronization Manager Object Manager
Mobile Client
CFG
SRF
Database Server
Siebel File System

10 of 18
Directly connects to a designated Siebel Server for synchronization of data and files
Siebel Client Types
11.11
Siebel Mobile Web Client Caveats
Many users mistake the Mobile Web Client for the Web Client
` Application functionality is almost the same, so users forget which is which
To determine which application is running, check the URL

` The Mobile and Developer Web Clients have a port number in the URL, and no application name ` The Web Client usually does not have a port number in the URL, and includes the application name
Mobile Web Client URL has a port number and no application name Web Client URL has no port number and includes the application name
11 of 18
11
Siebel Client Types
11.12
Siebel Handheld Client
Architecture is similar to the Siebel Mobile Web Client:

` The handheld client includes local database, file system, and configuration files ` The handheld client synchronizes with a specific Siebel server
Architecture is not identical to Siebel Mobile Web Client:

` Only runs on Windows-based mobile devices ` Supports a focused subset of application functionality

Enterprise Siebel Server Handheld Client

Synchronization Manager Object Manager CFG SRF
12 of 18
Screens, views, and applets customized for Siebel Handheld Applications customized for Siebel Handheld
Siebel Client Types
11.13
Siebel Developer Web Client Scenario

Dana is a system administrator. She has the client software installed locally because she requires access to the application even when the servers are not available.
Dana is using the Siebel Developer Web Client

11
Siebel Client Types
11.14
Siebel Developer Web Client
Is used by developers and system administrators for direct access to the Siebel database
` Siebel servers do not have to be running ` Does not require a Web server
Is similar to the Siebel Mobile Web client in that:

` A local application must be installed on the client ` Local configuration files must be stored on the client
However, can access any Siebel database and file system, including a local one or the enterprises
Server Components
Dedicated Web Client

Object Manager
CFG
SRF
Database Server
Siebel File System

14 of 18
Siebel Client Types
11.15
The Big Picture
The Siebel application supports a mixture of clients, depending on your users business requirements
Siebel Wireless Web Client Wireless Gateway Web Server
SWSE
Siebel Web Client

Browser
Dedicated Web Client

Object Manager
Siebel Server
Server Components Object Manager Component Parameters
Mobile/Handheld Client
Object Manager
CFG CFG SRF Database Server Siebel File System CFG SRF SRF
15 of 18
11
Enterprise
Siebel Client Types
11.16
Module Highlights
The
16 of 18
Siebel Web Client accesses the Siebel Enterprise and Siebel Servers through a Web server running SWSE The Siebel Wireless Web Client connects to a WAP-enabled Web server, and is otherwise similar to the Siebel Web Client The Siebel Mobile Web Client is a local executable that connects to a local database and provides full Siebel application functionality The Siebel Handheld Client is similar to the Siebel Mobile Web client, but runs on handheld devices The Siebel Developer Web Client is used by developers and system administrators for direct access to the Siebel database and for development and administrative changes
Siebel Client Types
11.17
In-Class Discussion
Which client is best suited for:

` Disconnected remote users needing access to their data ` A user with a cell phone needing access to his or her data ` Users needing frequent and fast access to their data (easily scalable and maintained) ` Server administrator needing access (to shut down a server component)
17 of 18
11
Siebel Client Types
11.18
Lab

` Answer questions about client types ` Use the Developer and Mobile Web Clients
18 of 18
Securing Access to the Application
12.1
12
Module 12: Securing Access to the Application
12
12.2
Module Objectives

` Describe the types of user authentication supported by Siebel applications ` Explain the role of the security adapter ` Describe Single Sign On (SSO) security and how it differs from other authentication methods
` You must understand the security mechanisms in order to be able to implement them
2 of 18
12.3
Siebel Application Security
12
Siebel applications are secured at several levels:

` Data visibility and view access should be restricted so users see only the appropriate views and data
Subject of previous module Subject of this module
` Access to the application should be restricted to authorized users
Subject of subsequent module
3 of 18
` Communication between architecture components may need to be secured
12.4
Authentication
Is the process of validating a users identity Verifies the identity of users before they gain access to a Siebel application Typically consists of collecting a set of user credentials such as user ID and password and comparing them to pre-stored values
4 of 18
12.5
Supported Authentication Methods
12
Siebel applications support authentication by either the Siebel servers or the Web server:
` Siebel security adapters are software programs that allow Siebel servers to authenticate users ` Single Sign On (SSO) allows the Web server to authenticate users

5 of 18
Trust Token
Similar to an authentication certificate, a trust token is a software object confirming the identity of the sender. The trust token may contain additional information such as user identity or database login to be passed to the server.
Siebel Web Server Extension performs authentication check Security adapter is still involved in verifying the trust token passed to it by the Web server
12.6
Siebel Security Adapters
A security adapter is a piece of software that connects to an authentication service

` Implemented as part of the Application Object Manager (AOM)
1. User provides credentials in browser
Browser
SWSE Credentials
3. Security adapter authenticates credentials using authentication service Security Adapter Authentication Service
6 of 18
Siebel Object Manager
Authentication Service
An authentication service is a store of credentials (typically user IDs and passwords) plus a mechanism to compare user provided credentials against the stored credentials.
Web Server
2. Credentials are passed through Web server to AOM. Web server does not check the credentials
12.7
Authentication Services
12
Siebel applications support multiple authentication services:

` ` ` ` Database authentication Lightweight Database Authentication Protocol (LDAP) Active Directory Services Interface (ADSI) Custom authentication using the Siebel Security Adapter Software Developers Kit (SSASDK)

Security Adapter
Authentication Service
7 of 18
Creating custom security adapters is beyond the scope of this course Refer to the Siebel Security Adapter SDK in Bookshelf
12.8
Database Authentication
Users are authenticated against the underlying database The database Security Adapter is the default for Siebel applications
Browser
Web Server SWSE Credentials
1. User provides name and password
2. Password may be hashed to prevent direct database access
Siebel Object Manager Hash password
Security Adapter
3. Connect to database using user ID and (possibly hashed) password. RDBMS performs authentication
Connect using DB account
Siebel Database
Password Hashing
A hash function is an operation that generates a unique output value for each input, typically of a fixed length. This differs from encryption because the hash may lose information and is not reversible.
12.9
Database Authentication Considerations

Does not require additional infrastructure components such as directory servers Uses a separate database login for each user
12
` Requires ongoing support from a database administrator
May support account policies based on those of the RDBMS

` Password expiration ` Password syntax ` Account lockout
Supports minimal user self-management

` User cannot perform self-management without being granted direct access to the database server
9 of 18
12.10
Directory Server Authentication

Browser
Web Server SWSE Credentials 1. User provides information
Users are authenticated against an external directory service The directory service contains the users credentials and administrative information A single reserved database login is typically used for all users
2. Verify credentials Login Authentication Service Directory
Security Adapter
Connect using DB account 3. Connect to database
Retrieve reserved DB Account
Siebel Database
10 of 18
Default Login
The default database login for directory server authentication is LDAPUSER.
12.11
Directory Service Considerations
12
Reduces administrative overhead

` ` ` ` Eliminates maintenance of a separate database login for each user Allows Web users to self-register and maintain login information Allows automated creation of users from User Administration view Allows external delegated administration of users
` Password expiration ` Password syntax ` Account lockout
11 of 18
Allows credentials store to be shared across multiple applications May support account policies based on those of the directory service
12.12
Single Sign On
Browser User Credentials Web Server SWSE Authenticated User ID and Trust Token Siebel Object Manager Security Adapter 1. User provides information
Web Server provides credentials to third-party service Security Adapter looks up and retrieves Siebel user ID, DB account based on identity key from external source
Login Authentication Service 2. Verifies credentials Retrieves Siebel user ID and DB account
Connect Using DB Account
4. Verifies trust token and collects user ID
Directory
Siebel Database
5. Connects to database
12 of 18
3. Passes authenticated user ID and trust token
12.13
Single Sign On Considerations
12
Allows users to access multiple applications without any further login

` For example, Windows Integrated Authentication allows users to access Siebel applications directly once they have logged in to their Windows accounts
Uses credentials that are collected and verified by the Web server
Requires the use of a trust token

` Secret value shared by the Web server and Object Manager
Allows Siebel applications to be deployed into existing Web sites and portals
13 of 18
` Management of authentication can be performed from a single centralized location
12.14
Single Sign On Considerations Continued
Some Siebel User Administration features that are not available using SSO should be disabled for consistency, for example:
` User self-registration ` Delegated administration of users ` Change password
Requires synchronization of users between the Siebel application and the external authentication system
14 of 18
12.15
Comparing Authentication Methods

Database Authentication
Requires additional infrastructure Supports account policies such as password expiration Supports user selfmanagement Allows creation of users from within the Siebel application Allows using same credentials across multiple applications Allows single sign-on Allows external management of users
12
Single Sign On
Directory Service Authentication
No Depends on RDBMS No No No No No
Yes Depends on directory service Yes Yes Yes No Yes
Yes Depends on directory service No
Yes Yes Yes
15 of 18
No
12.16
Module Highlights
Siebel applications support three mechanisms for authenticating users:

` Database authentication is the default; the Siebel Server passes the authentication information to the RDBMS for authentication ` Directory Service authentication uses a directory service such as LDAP or ADSI to perform the authentication; the Siebel Server passes the authentication information to the directory service ` Single Sign On uses a directory service at the Web server level to allow single sign-on to multiple applications; the Siebel Web Server passes the authentication information to the directory service and passes the returned trust token to the Siebel Server
16 of 18
12.17
Lab
12

` Create a database account for a new user
17 of 18
12.18
Installing Siebel Applications
13.1
13
Module 13: Installing Siebel Applications
13
13.2
Module Objectives

` Describe pre-installation steps necessary to prepare your environment for a Siebel installation ` Install the Siebel application ` Perform post-installation steps to verify your Siebel environment ` Describe how to use the multi-server update tool to automate installations

` Successful configuration of the Siebel environment requires successful installation
2 of 34
13.3
Business Challenge: Enterprise Installation
Installing enterprise-level software requires careful planning and preparation

` Hardware and software prerequisites must be met ` Multiple installers must be run in the correct sequence ` Configuration parameters must be properly set before, during, and after installation ` Installation may be required on many machines
13
3 of 34
13.4
Business Solution: Siebel Installation Tools
Siebel provides several tools to assist with the installation of Siebel environments:
` Bookshelf documentation:

Deployment Planning Guide and System Requirements and Supported Platforms guide to prepare the system Installation Guide [Windows or UNIX] to perform the installation Guide you through the installation process itself Performs verification tests on system at any time during the installation to check:
` Prerequisites ` Configuration settings ` Installations
` Step-by-step installers ` Environment Verification Tool (EVT)
` Siebel Multi-Server Update Tool
Upgrades multiple server instances from a central administration point

4 of 34
Reference
Installation Guide for Microsoft Windows Installation Guide for UNIX System Requirements and Supported Platforms
13.5
Performing a Successful Installation
Has three separate phases:

` Pre-installation ` Installation ` Verification
13
5 of 34

0/3
13.6
Pre-Installation Tasks
Plan the System Topology Verify System Requirements Create Prerequisite Objects
6 of 34

1/3
13.7
Plan the System Topology
Identify where software will be installed

` Which machine(s)
Consider hardware and networking requirements

Siebel Gateway GS
13
` What naming convention ` What directory structure
Use the Deployment Planning Guide as an aid Example:
Enterprise Server E1 Web Client Siebel Server(s) S1 S2
Siebel File System
C1 Web Server W1 Machine/Host Names/Addresses: C1, GS, S1, D1, W1

D1 Database Server
7 of 34

2/3
13.8
Verify System Requirements
Verify that hardware and software meets Siebel requirements

` Consult the System Requirements and Supported Platforms Guide ` Check the Release Notes for any updates to these requirements
Confirm that required third-party software is installed

` For example, a third-party RDBMS on the database server machine
8 of 34
Installation Guide has recommendations for RDBMS configuration settings

2/3
13.9
Verify System Requirements Continued
Optionally, run the Environment Verification Tool (EVT) to verify prerequisites

` Command-line tool for checking environment ` Installed as part of the Siebel Server installation, so it must be copied from another installation to be run prior to server installation
Run EVT with no flags to check the pre-installation environment Checks system software, network settings, and recommended OS tools, but does not verify RDBMS
13
9 of 34

3/3
13.10
Create Prerequisite Objects
Create the Siebel database

` Install the proper version of your chosen supported RDBMS software ` Create an empty database/tablespace with appropriate space defined ` Consult the platform-appropriate Siebel Installation Guide for recommended database configuration parameter settings ` Create the Siebel file system as a directory on a disk with sufficient space
Alternatively, partition the file system across multiple directories and servers
` Must be accessible from machines running Siebel Servers ` Must support long and case-sensitive file names
10 of 34
Create the Siebel file system

3/3
13.11
Create Prerequisite Objects Continued
Create a Siebel service owner account

` Used to run Enterprise processes and components

Siebel Gateway Name service Siebel Server service Siebel Gateway Name Server Siebel Servers Server on which Siebel File System resides
13
` Name must be consistent across all servers:

` Recommended practice: On Windows use a domain account rather than separate accounts on each machine
Consult the platform-appropriate Siebel Installation Guide for exact steps and privileges
11 of 34

0/6
13.12
Installation Tasks
Create the Installation Image Install the Enterprise Configure the Server(s) Install the Database Install the Siebel Web Server Extensions Install Additional Applications
12 of 34

1/6
13.13
Create the Installation Image
Run the Siebel Image Creator utility provided on your media to generate an installation image
` Refer to the Siebel Installation Guide for detailed steps
13
13 of 34

2/6
13.14
Install the Enterprise
Use the Siebel Enterprise Server installer to install the Gateway Name Server, Siebel Servers, Database Configuration Utilities, and EAI Connectors
` Each component may be installed separately ` Parameters include the directory name, setup type, and language
14 of 34

2/6
13.15
Run Siebel Enterprise Configuration Tool
Once installation completes, the enterprise configuration tool runs automatically to set system parameters
` Alternatively, run <InstallDir>/gtwysrvr/bin/ssincfgw.exe manually at a later time
13
Create Gateway Name Server, Enterprise, and Siebel Web Server Extension logical profile
15 of 34

2/6
13.16
Key Enterprise Configuration Parameters
To configure a new Gateway Name Server requires:

` Gateway Name Server port, language for server messages and logs, and service account
To configure a new Enterprise requires:

` An existing Siebel Gateway Name Server ` An Enterprise name, Siebel file system, database platform and login information, and security type (database/LDAP/ANSI/custom)
` An existing Siebel Gateway Name Server and Enterprise ` A directory in which to store the profile, network configuration parameters such as HTTP and HTTPS ports, High Interactivity and Standard Interactivity default login names, and an Enterprise security token
16 of 34
To configure a new Siebel Web Server Extension logical profile requires:

3/6
13.17
Configure the Server(s)
Once enterprise configuration completes, the server configuration tool runs automatically to set system parameters
` Alternatively, run <InstallDir>/siebsrvr/bin/ssincfgw.exe manually at a later time
13
Configure a Siebel Server
17 of 34

3/6
13.18
Key Server Configuration Parameters
Configuring a new Siebel Server requires:

` ` ` ` ` ` An existing Gateway Name Server and Enterprise The Siebel Server name Which component groups to enable on that server The language for server messages The languages to deploy Various port settings, including:

` Server clustering information
18 of 34
The connection broker port, used by the Siebel Web Server Extensions and other server components for communication The Siebel Remote Synchronization Manager port The database connection port

4/6
13.19
Install the Database

Run grantusr.sql in the dbsrvr/<RDBMS> directory on the database created during pre-installation Manually run the database configuration utility and install a new database
13
` Creates appropriate schema and populates database with seed data ` Optionally, enter license key during database initialization
19 of 34

5/6
13.20
Install the Siebel Web Server Extensions
Use the SWSE installer to install the Siebel Web Server Extension on the machine hosting the Web server
` The Siebel Enterprise Server must already have been run to generate the Enterprise-specific SWSE profile ` Specify parameters, including load-balancing strategy for multiserver installations and connection broker port
Specify load balancing for multiple servers: Siebel native load balancing (supported by the SWSE) or thirdparty load balancing
20 of 34

6/6
13.21
Install Additional Applications
Install the Siebel Mobile or Siebel Developer Web clients on individual user machines
` Both applications use the Siebel Web Client installer
13
Install Siebel Tools on development machines (Optional) Install the Sample database on development machines
` Pre-populated database allowing testing of configuration changes
(Optional) Install Siebel Management Server to support the Application Deployment Manager (ADM) or Diagnostic Console (Optional) Install Siebel Update Server and clients to support multi-server updates
21 of 34

0/4
13.22
Verification Tasks
Check Installation Logs Verify Services Run EVT Log In to Applications
22 of 34

1/4
13.23
Check Installation Logs
Every step of configuration generates a log file:

` Siebel Gateway Name Server configuration log is /gtwysrvr/log/sw_cfg_util.log ` Siebel Server configuration log is /siebsrvr/log/sw_cfg_util.log ` Siebel Web Server Extention configuration log is /SWEApp/log/sw_cfg_util.log
13
Check these logs for severe or fatal errors

Informational messages are listed as GenericErrors with a severity level of 1
23 of 34

2/4
13.24
Verify Services
Verify that the Siebel Gateway Name Server service is running Verify that the Siebel Server services are running on each machine hosting a server
In this instance the Siebel Gateway Name Server and Siebel Server are co-located
24 of 34

3/4
13.25
Run EVT
Use the Environment Verification Tool to check the status of your enterprise
` Tool reads evt.ini file to determine what checks to perform ` Tool supports checking Siebel Gateway Name Server, Siebel Server, Siebel Web Server Extension, third-party Web server, and third-party database ` Output can be text, text file, HTML, or HTML file ` For complete details on using the EVT, see your platform-specific Installation Guide
13
25 of 34

3/4
13.26
EVT Example
The following example runs the EVT with the default options and outputs the results to output.html
The o flag specifies the output file format
26 of 34
The output is colorcoded for readability

4/4
13.27
Log In to Applications
Log in to the Siebel application to confirm connectivity to the Web server and Siebel server
Web server address Application SWE command appended to the URL by the applications default Web page
13
27 of 34

4/4
13.28
Browser Health Check
Is a utility that runs on the browser to verify that it is properly configured for High Interactivity
` Runs when the Web client is invoked if it is enabled in the [SWE] section of siebel.cfg
Checks the client environment on which the Siebel application is running

` Internet options ` Java setting ` Environment/registry settings
Set values in the [clientHealthCheck] section of the configuration file
Performs checks using values set in the application configuration file

` Each check can have one of the following values

Required Recommended Ignore

28 of 34
13.29
Multi-Server Updates
The Siebel Update Server provides a single administration point for patching and updating multiple Siebel servers Allows quick monitoring of each servers current patch level Supports both push and pull models of software updates
13
` Administrator can send updates out to all servers (push) ` Servers can periodically query the update server for updates (pull)
Siebel Update Server provides a centralized administration point for managing updates on Siebel servers
29 of 34
13.30
Siebel Update Server
Is a Web-based installation tool based on Macrovision Installshield

` Uses a Tomcat/JSP Web server on the Update Server ` Includes a local database on the Update Server for storing all product information across an enterprise
Currently supports server updates and patches
30 of 34
` Gateway Name Server, Siebel Enterprise, Siebel Server, Siebel Web Server Extension, and so forth
13.31
Siebel Update Server Architecture
A single update server provides a central access point to multiple clients

` Siebel Update Server software is installed on server ` Siebel Update Client software is installed on each client
13
Clients have other Siebel software installed, such as Siebel Server or Siebel Web Server Extension
Cloudscape Database Update Server includes Tomcat Siebel Update Server Web server and local database Siebel Update Clients
Clients are Siebel Servers or Siebel Web Servers
13.32
Siebel Update Server Functionality
Clients register current software information on server

` Currently installed software and version information ` Stored in database on server
Administrator publishes product update information to server

` Location of update, version information, and so forth
Clients register current product information on server
Update server stores client and update information in database Administrator publishes product information to server
13.33
Siebel Update Server Functionality Continued

Administrator may select client machines and schedule updates for them (push method) Clients may check for updates and download them when it is convenient (pull method)
Administrator may choose which clients to update
13
As clients are updated, their information is updated in the database Administrator may push updates to clients
Recommended Practice
The push method is recommended because the pull method may result in unexpected server restarts, for example, after downloading a patch that requires a restart.
Client may manually check for updates (pull)
13.34
Module Highlights
Installing Siebel applications is a three-step process:

` Perform pre-installation tasks ` Perform software installations ` Perform post-installation tasks
34 of 34
Pre-installation tasks include planning the topology, verifying prerequisites, and creating required objects such as the Siebel database Software installations require multiple installers, which guide you through the installation process step-by-step and automatically run the appropriate configuration tools Post-installation tasks include checking the installation logs, checking the services, running the EVT, and logging in to the application Siebel Update Server supports multi-server updates
14.1
Module 14: Siebel Application Architecture
14
14
14.2
Module Objectives

` Describe the major types of object definitions ` Describe the relationships between them

` Enables you to explore an existing application effectively ` Provides the foundation you need to configure the object definitions that form the basis of an application
2 of 22
14.3
The Siebel Application Architecture
Recall that the Siebel Application consists of:

` An execution engine that provides the application behavior
The Siebel Server(s); more specifically, their components
` Configuration files and the Siebel Gateway Name Server that specify operating parameters for the execution engine
Most configuration parameters are stored in the Gateway Name Server
14
` A relational database that stores user data ` A set of physical User Interface (UI) files that specify how to render the UI in the users ` A Siebel Repository File (SRF) containing compiled object definitions
3 of 22
Reference
Configuring Siebel Business Applications: Overview of Configuring Siebel Applications
14.4
The Siebel Application Architecture Continued
Object definitions are created, modified, and stored in special tables in the database and compiled to the SRF
User Interface No object definitions here
Siebel Application
UI files
Shape the UI via Specifies parameters to
Object Manager
Supplies compiled object definitions to
.cfg Configuration File

Serves data to
Object definitions compiled to here Object definitions stored here
SRF Siebel Repository File

4 of 22
Database Server
Siebel template files Cascading style sheets Image files
Generates
14.5
Siebel Repository File (SRF)
Contains compiled object definitions that specify:

` Presentation of data ` Business logic ` Physical table storage
14
UI layer definitions
Account Account Opportunity Product Contact
Business layer definitions
Data layer definitions

14.6
Object Definitions
Provide the foundation for application execution Are grouped in three layers with different purposes Refer to definitions in the next lower layer

UI Layer
List Column or Control
Applet
View
Screen
Application
Business Layer
Field
Business
Component
Business Object
1 or many References
Data Layer
Column
Table
6 of 22
14.7
Data Layer
Data layer object definitions specify the logical structure of the physical database
` Definitions are metadata, not data
In the Data layer, there are two principal data object definitions:
` Table definitions ` Column definitions
14
Table
S_ORDER
ORDER_NUM DISCNT_PERCENT STATUS_CD
Columns
7 of 22
14.8
Business Layer
Business object definitions specify the business logic for the application In the Business layer, there are two principal objects:
` Business component ` Business object
Business component
8 of 22
Business object
14.9
Business Component (BC)

Represents one fundamental business entity in the enterprise

` For example: Service Request, Contact, Activity
Represents a logical grouping of data from one or more tables Refers to a base table Consists of multiple fields that characterize the business component
` Many fields within the business component reference columns in the base table
Business component Order Entry - Orders
Order Number Discount Status
14
Field Base table S_ORDER

ORDER_NUM
Column
DISCNT_PERCENT STATUS_CD
9 of 22
14.10
Business Component Continued
Can include data from additional related tables

` Some fields map to columns in these related tables
Business component
Order Entry - Orders

Order Number Account Opportunity
Column
ORDER_NUM LOC NAME
S_ORDER Base table
S_ORG_EXT Additional tables
S_OPTY
10 of 22
Field
14.11
Business Object (BO)

Is a collection of related Business components (BCs) Represents a major functional area of the enterprise
` For example, order management
Contains specific details about the relationships between BCs

` One BC is the master or driving BC ` Organizes related business components
Order Entry
Business Object (BO) Business Component (BC) Order Entry - Orders Parent BC provides focus for BO
14
Action
Quote
Payments
11 of 22
14.12
Comparing Business Components and Business Objects

Business Objects provide focus to views and organize BCs Business Components provide data to applets and control data manipulation in tables
Business Component
Applet
Business Object
View
Field Control data manipulation
Business
Component
Business Object
Business
Component
Business Object
Table
Details relationships between BCs
Organizes BCs
12 of 22
Provide data
Provide focus
14.13
UI Object Definitions
There are five principal UI objects within the user interface
1. Application 2. Screen 4. Applet
14
3. View
5. List Column or Control
13 of 22
14.14
Control and List Column Object Definitions
Provide the ability to display and manipulate data
This control displays data in a field via a form
14 of 22
This column displays data in a columnar list
14.15
Applet Object Definition

A section of a view, such as a list or form References one business component whose data can be viewed and edited through the list or form Consists of list column or textbox control object definitions
` Refer to fields in the applet-referenced business component ` Specify how the data for the fields is displayed in the list or form
14
Business component

Order Number Account Opportunity
15 of 22
14.16
View Object Definition

Specifies a view in a Siebel application Contains multiple applet object definitions
View View references one BO BO Applet references one BC Order Entry My Orders View (Sales)
Order Entry
Action
Quote
Payments
BC
14.17
Screen Object Definition

Specifies a screen in a Siebel application

` Is associated with a major functional area of the enterprise
Contains multiple view object definitions that usually refer to the same business object
` Administration screens are an exception
Screens
14
Views in that screen
Same screen
17 of 22
14.18
Application Object Definition
Specifies a particular collection of screens available in a Siebel application

Application
18 of 22
14.19
Configuring Siebel Applications
Is accomplished by using:
` An HTML editor to modify template and other physical UI files ` Siebel Tools to modify object definitions
Configurable Layers
14
Use an HTML editor to modify template
Physical UI Files UI Object Definitions Business Object Definitions Data Object Definitions
Use Siebel Tools to modify object definitions
19 of 22
14.20
Module Highlights
Siebel architecture uses object definitions that specify application behavior Use Siebel Tools to:
` Create, store, and modify object definitions in the database ` Compile object definitions into the SRF for more efficient run-time access
Object definitions are grouped into three layers:
Includes applications, screens, views, applets and list columns/controls Includes business objects and business components Includes tables and columns
` Business Layer
` Data Layer
20 of 22
` UI Layer
14.21
Lab

` Examine how UI layer object definitions reference business layer object definitions
14
21 of 22
14.22
Using Siebel Tools to Examine Object Definitions
15.1
Module 15: Using Siebel Tools to Examine Object Definitions
15
15
15.2
Module Objectives

` Describe the differences between object types and object definitions ` Use Siebel Tools to examine parent and child object definitions

` Enables you to configure Siebel applications effectively ` Enables you to examine mappings that support bulk data transfer
2 of 20
15.3
Siebel Tools
Is an Integrated Development Environment (IDE) Is a declarative configuration tool
` Is used to create and modify object definitions (metadata) that define Siebel applications

Set properties for objects that control behavior No need to modify source code or write SQL
Configure objects instead of writing code
3 of 20
15
15.4
Object Definitions

Configured application Object Manager
Tools output is input for object manager
SRF Repository Data

Siebel Repository File

4 of 20
Are metadata that define elements of the user interface, business logic, and data storage Are stored in the Siebel Repository, a subset of tables in the Siebel database Are examined, created, and edited using Siebel Tools Are compiled into the repository file for a configured application
15.5
Object Definition
Consists of a set of properties with assigned values Is created from a template called an object type
Object Type View

Name: Title: Inactive:
Object Definition View

Name: Title: Inactive: Account List View FALSE
Template with empty properties
Object with values in properties
5 of 20
Object Terminology
The terms object type and object definition, as used here, should not be confused with similar terms (object, object class, object instance) found in object-oriented design and programming languages. Object definition properties describe characteristics of the object definition and have the following value types: user-defined names, numerical values, Boolean values (TRUE and FALSE), Siebel-defined constants, and references to the names of other object definitions. A property that references the name of another object definition must match the name exactly in spelling (spaces do count) and cases. A value of Prod is not the same as PROD.
Object Definition Properties
Referencing Names
My Accounts
15
15.6
Examining Object Definitions
Use the Object List Editor (OBLE) to display object definitions

` Select an object type in the Object Explorer (OE) ` Object definitions appear in the Object List Editor
OBLE
OE
Object property
Object definition
6 of 20
15.7
Siebel Tools User Interface

Differs from the client application Has toolbar icons for common user operations
Record navigation Query Sort
7 of 20
Menu invoked by right-clicking object definition
15
15.8
Properties Window
Displays the properties for the object definition selected in the OBLE
` Select View > Windows > Properties Window ` Properties are listed in alphabetical order ` The value is shown next to property name
OBLE
Properties window Same value
Does not show Changed or Project properties

15.9
Hierarchy of Object Types
Some object types contain child object types

` For instance, Field is a child object type of the Business Component object type
Object explorer displays hierarchy
Multiple hierarchy levels
9 of 20
15
15.10
Object Explorer
Displays by default a small set of the most commonly used object types
` Select View > Options and click the Object Explorer tab to add or remove object types from the Object Explorer
Some options displayed
All options displayed
10 of 20
15.11
Viewing Parent/Child Object Definitions
Select object types and definitions alternately to examine child object definitions
Use the Types tab 1. Expand the parent object type (BC) in the OE 2. Select the parent object definition in the OBLE
3. Select the desired child object type (Field) in the OE

4. View child object definitions for the selected parent definition in the lower pane of the OBLE
11 of 20
15

0/3
15.12
Additional Navigation Techniques
Hyperlinks Back and Forward Buttons Bookmarks
12 of 20

1/3
15.13
Hyperlinks
Drill down on a hyperlink to navigate to that object definition

` For example, applet to business component ` For example, business component to table
Underlined in blue
13 of 20
Using Drilldown
Siebel Tools users must have the Developer responsibility in order to drill down.
15

2/3
15.14
Back and Forward Buttons

Use the Back button to return to the object definition last examined Use the Forward button to return to the current object definition
14 of 20
Best Practice
The Forward and Back buttons have limited functionality; instead use bookmarks as a navigation aide. Bookmarks are discussed on the next slide.

3/3
15.15
Bookmarks
Use bookmarks to navigate directly to a specific object definition
Add a new bookmark
Display or hide bookmark window
Select desired bookmark from bookmarks window
15 of 20
Bookmarks
Bookmarks can serve very effectively as predefined queries.
15
15.16
Window Navigation
Use dockable windows and tabs for frequently-accessed tools such as the Properties window Undock windows to resize and place
Window tabs
Minimize, maximize, close
Autohide docking windows
16 of 20
Autohide
15.17
Object Explorer: Flat Tab

Removes all hierarchy and shows all object types in a single list Helps developers:
` Find a child object with an unknown parent ` See how object definitions and properties are typically used
Select any object type in the OE
Parent object definition displayed (parent applet for the control)
17 of 20
15
15.18
Module Highlights
Siebel Tools is a declarative configuration tool Object definitions consist of a set of properties with assigned values
` Are created from a template called an object type
18 of 20
The Object Explorer (OE) lists object types Object definitions appear in the Object List Editor (OBLE) Properties Window displays the object definition selected in the OBLE Flat tab removes all hierarchy and shows all object types in a single list
15.19
Lab

` Use Siebel Tools to examine object definitions in the Siebel repository
Tools navigation convention used in the labs
Select Business Component :: Account | Field :: Account Role

Parent Object Type in OE Child Object Type in OE
19 of 20
Parent Record in OBLE
Child Record in OBLE
15
15.20
The Siebel Data Model
16.1
Module 16: The Siebel Data Model

16
16
16.2
Module Objectives

` Describe the purpose of the Siebel Data Model ` Describe the role of primary and foreign keys, indexes, and user keys ` Identify prominent tables in the Siebel Data Model
2 of 28
` Enables you to understand how data is accessed in existing Siebel applications ` Enables you to understand how to map your business logic to the Siebel Data Model ` Enables you to configure the Data layer as necessary for your implementation
16.3
Defines how the data used by Siebel applications is stored in a standard third-party relational database
` Specifies the tables and relationships
Is designed to support the data requirements across Siebel applications
Defines business logic
Field
Component
Defines data storage organization (makes up the data model)
16
Column Table
3 of 28
Business
Business Object
16.4
Siebel Data
Is organized and stored in normalized tables in a relational database

` Each table has multiple columns storing atomic data (single-value, cannot be logically further sub-divided) ` The data schema is organized to eliminate repeated storage of data
Table S_PROD_INT
Columns (store single values only)
4 of 28
Reference
Configuring Siebel Business Applications: Configuring Tables and Columns
PART_NUM
ROW_ID
NAME
UOM_CD
16.5
Primary Key (PK)
Is a column that uniquely identifies each row in a table

` ROW_ID serves as the primary key for Siebel tables
S_PROD_INT
ROW_ID NAME PART_NUM UOM_CD
16
5 of 28
Primary key
16.6
ROW_ID
Is a column in every table

` Contains a Siebel application-generated identifier that is unique across all tables and mobile users
Is managed by Siebel applications and must not be modified by users
Is viewed by right-clicking the record or navigating to Help > About Record
6 of 28

0/6
16.7
Understanding the Data Model
Tables Columns User Keys
Relationships Between Tables Extension Tables
16
7 of 28
Indexes

1/6
16.8
Tables
Approximately 3,000 tables in the database Three major types: Data, Interface, and Repository
Data S_PROD_INT
NAME ROW_ID PART_NUM UOM_CD
Interface EIM_PROD_INT
ROW_ID NAME PART_NUM UOM_CD
Repository S_TABLE
NAME ROW_ID DESC_TEXT ALIAS TYPE
This module is focused on data tables
8 of 28
Creating the Schema The database schema is created during the Siebel database server installation. Additional tables can be created by developers using Siebel Tools. Type The type of a table is specified by its Type property.

1/6
16.9
Data Tables
Store the user data

` Business data ` Administrative data ` Seed data
Are populated and updated by:

` Users through the Siebel applications ` Server processes such as: Enterprise Integration Manager (EIM) and Assignment Manager
Have names prefixed with S_ Are documented in the Siebel Data Model Reference
16
9 of 28

1/6
16.10
Seven Prominent Data Tables
Store data for the major business entities

Opportunity
S_OPTY ROW_ID NAME BDGT_AMT PROG_NAME STG_NAME
Service Request
S_SRV_REQ SR_NUM ROW_ID DESC_TEXT ASGN_DT LAST_UPD ROW_ID
Contact
S_CONTACT LAST_NAME FST_NAME MID_NAME
Asset
S_ASSET ROW_ID NAME ASSET_NUM SERIAL_NUM MFG_DT ROW_ID
Account
S_ORG_EXT DEPT_NUM DESC_TEXT DIVISION EMP_COUNT ROW_ID
Activity
S_EVT_ACT ACTIVITY_UID TODO_CD PROJ_ID OPTY_ID
Internal Product
S_PROD_INT ROW_ID NAME PART_NUM ORDER_CST PROD_CD
10 of 28

2/6
16.11
Columns

Each table has multiple columns to store user and system data
` Defined by Column child object definitions
Columns determine the data that can be stored in that table
16
11 of 28

2/6
16.12
Column Properties
Determine size and type of data that can be stored in column Limit proposed modifications to a standard application Do not edit existing properties
Identifies data type and size
12 of 28

2/6
16.13
Data Type and Length Properties

Physical Type identifies the type of data to be stored Length determines the maximum size
16
13 of 28

2/6
16.14
System Columns
Exist for all tables to store system data Are maintained by Siebel applications and tasks
System columns
14 of 28

3/6
16.15
User Keys
Are used to determine the uniqueness of records when entering, importing, or integrating data Are predefined and cannot be changed
16
Column Combination provides a unique value
All columns in user key may not be required

15 of 28
User Keys
Customers cannot modify user keys. Expert Services can assist customers in evaluating strategies to remap data in their implementations to make use of the current user key structure within their specific business requirements. The information about the user keys for a table has been incorporated into data that support EIM and remote synchronization. In addition, there is a predefined index (see next slide) based on the Siebel-defined user key.

4/6
16.16
Indexes
Are a separate data structure that stores a data value for a column and a pointer to the corresponding row
` Used to retrieve and sort data rapidly
Are predefined by Siebel as a set of standard indexes

_P index based on primary key
_U index based on user key
Sequence affects sort order


5/6
16.17
Relationships Between Tables
Siebel tables have many predefined relationships to support the as-delivered application
` 1:M one-to-many ` M:M many-to-many
Product Line S_PROD_LN
ROW_ID NAME DESC_TEXT
Asset S_PROD_INT
PART_NUM ROW_ID NAME ORDER_CST PROD_CD
S_ASSET
16
M:M relationship
1:M relationship
17 of 28
SERIAL_NUM
ROW_ID
NAME
ASSET_NUM
MFG_DT

5/6
16.18
1:M Relationships
Are captured using foreign key (FK) table columns in the table on the many side of the relationship FK column on many side of the relationship references PK column on one side
Foreign key column for 1:M Product : Asset relationship S_PROD_INT

PART_NUM PROD_CD ROW_ID NAME PK ORDER_CST
S_ASSET
NAME ROW_ID ASSET_NUM SERIAL_NUM PROD_ID FK
18 of 28
Foreign Key Columns
Since a product could have many assets (product instances) associated with it, a foreign key column cannot be located in the S_PROD_INT table. It might then have to contain multiple ROW_IDs, which would violate the basic rule of a single value for a column.

5/6
16.19
Foreign Key Table Columns
Are columns in a table that refer to the primary key column of a related (parent) table
` Many are named with suffix _ID
Are maintained by Siebel applications and tasks to ensure referential integrity and should never be updated directly via SQL
16
Foreign key column Foreign key table
19 of 28

5/6
16.20
Finding Foreign Keys for 1:M Relationships
Inspect the Foreign Key Table property in a Column object definition to determine the column that serves as the FK
PK
FK
FK column
Parent table
20 of 28
S_PROD_INT
ROW_ID NAME PART_NUM ORDER_CST PROD_CD
S_ASSET
ASSET_NUM PROD_ID ROW_ID NAME SERIAL_NUM

5/6
16.21
M:M Relationships
Are captured using foreign key columns in a third table called the intersection table
Product : Product Line intersection table S_PROD_LN
ROW_ID NAME PK DESC_TEXT
S_PROD_INT
PART_NUM
S_PROD_LN_PROD
PROD_LN_ID PROD_ID ROW_ID FK
PK
16
FK
21 of 28
ROW_ID
NAME
UOM_CD

6/6
16.22
1:1 Extension Table
Is a special table that has a 1:1 relationship with a base table

` Foreign key for the relationship:

Is located in the extension table Is named PAR_ROW_ID
Provides additional columns for business components referencing the base table
Base Table
NAME PK PART_NUM UOM_CD
Extension Table
S_PROD_INT_X
ATTRIB_39 ROW_ID PAR_ROW_ID
S_PROD_INT
ROW_ID
FK
22 of 28
ROW_ID
The ROW_ID for a row in a 1:1 extension table is, by convention, the same as that of the related row in the base table, and is an exception to the general rule that ROW_IDs are unique across all tables. A row in an extension table is created only if there is data to store in one of its columns. For example, a new product record that does not have a value for any fields referencing the extension table would create a row in the base table, but not in the extension table.
Rows in Extension Tables
` A base and extension table can be considered as a single logical table

6/6
16.23
Standard 1:1 Extension Tables

Prebuilt for many major tables

` Have the name of the base table with suffix _X
Contain 40-plus generic columns of varying types

` Store data for new business component fields that are in addition to those mapped to the base table
16
23 of 28

6/6
16.24
1:M Extension Table

Is a special table for storing child data related to an existing parent table Allows you to track entities that do not exist in the as-delivered Siebel applications
S_ASSET
NAME PK ROW_ID ASSET_NUM SERIAL_NUM PROD_ID
S_ASSET_XM
ATTRIB_01
FK
24 of 28
ROW_ID
PAR_ROW_ID
TYPE
NAME

6/6
16.25
Standard 1:M Extension Tables

Are prebuilt for many tables Have the name of the main table appended with _XM
TYPE defines data classification PAR_ROW_ID stores FK to ROW_ID in main table NAME stores name of child entity ATTRIBs are predefined with varying types
16
25 of 28
16.26
Module Highlights
Siebel Data Model defines how data is stored in a third-party relational database A primary key (PK) is a column that uniquely identifies each table row ROW_ID is a column in every table
` Contains a Siebel application-generated unique identifier
26 of 28
User keys specify the columns used to determine uniqueness of records when entering, importing, or integrating data Foreign Key Table columns are columns in a table that refer to the PK column of a related table 1:1, 1:M, and M:M relationships are predefined within the model
16.27
Lab

` Examine tables, columns, indexes, and user keys that make up the Siebel Data Model ` Determine the form of relationships between tables in the Siebel Data Model
16
27 of 28
16.28
Siebel Business Components
17.1
Module 17: Siebel Business Components
17
17
17.2
Module Objectives

` Define a business component ` Describe how business component fields at the business object layer are mapped to columns at the data layer ` Describe how base and joined tables are used as a part of this mapping
` The business component is a fundamental object in the Siebel Application Architecture
2 of 18
17.3
Application Architecture: Business Components

Provide a way to group data according to business logic Are referenced by applets Specify access to tables (read, write, and update) Are used by business objects to provide data to views

or Control
Business Layer
Field
Business Component
Business Object 1 or many
Data Layer
Column
Table
References
17
3 of 18
UI Layer
List Column
Applet
View
Screen
Application
17.4
Business Component
A business component (BC) is a person, place, thing, or event about which data must be stored ` Represents a fundamental business entity Provides the foundation for controlling how data is selected, inserted, and updated in underlying tables
Opportunity
Opportunity
Quote
Product
Contact
= Business Component
17.5
Business Component Continued

Arranges data from one or more tables into a logical grouping Consists primarily of fields and joins
` Each field references a single column in a table
Is not a table
` Does not store data ` Stores metadata: data about data
Name
Description
Decision Level
Sales Stage
Sales Stage Phase
S_OPTY
ROW_ID NAME DESC_TEXT CURCY_CD
S_OPTY_X
ROW_ID PAR_ROW_ID ATTRIB_01 ATTRIB_09 ATTRIB_39
S_STG Field
ROW_ID NAME STG_ORDER PHASE_CD
17
5 of 18
Base Table
Joined Tables
BC
Opportunity
17.6
Business Component Reuse
A business component can be:

` Defined once in terms of a logical collection of columns from one or more tables ` Then used in many different business object contexts
Opportunity
Opportunity
Contact BC appears as master in Contact BO
Contact
Contact Contact
Quote
Product
Contact BC appears as child in Opportunity BO
Quote
Product
Account
6 of 18
17.7
Base Table
Contains the main columns for the business component Every business component references only one base table Many BC fields are mapped to base table columns Fields referencing base tables are editable in the UI
Opportunity
Name Description Decision Level Sales Stage Sales Stage Phase
S_OPTY
ROW_ID NAME CURCY_CD DESC_TEXT
Base table
Mapping Example
Field: Description Business Component: Opportunity
Column: DESC_TEXT
Table: S_OPTY
7 of 18
17
17.8
Business Component Table Property
Each business component contains a table property that specifies the base table
Base table
8 of 18
17.9
Fields That Map to a Base Table
Column property maps to a column in the base table

` Join property is blank
Status field references base table
Join is blank
17
Base table
17.10
Explicit Join
Is a join that brings in data from tables other than the base table to meet the business components data display requirements
` Most fields referencing explicitly joined tables are read-only in the applet
Includes a join definition and a join specification BC field references the join definition
Opportunity
Name Description Sales Stage
Base table
S_OPTY
ROW_ID DESC_TEXT CURCY_CD NAME
S_STG
Joined table
10 of 18
17.11
Fields That Map to a Joined Table

Join property specifies the join object definition being referenced Column property maps to a column in the joined table
Sales Stage field maps to Sales Stage join
Name of join that maps to S_STG table
17
The S_STG column, NAME, contains sales stage data
17.12
Joining Data from Joined Tables

Returns only one row from the joined table There is a 1:1 or 1:M relationship from the joined table to the BC Relationship is established using a FK column on the base table to join to the PK column on the joined table
FK column on base table S_OPTY

ROW_ID NAME DESC_TEXT CURCY_CD CURR_STG_ID
S_STG
ROW_ID NAME PHASE_CD STG_ORDER
Base Table
Joined Table
FK
PK
12 of 18
PK column on joined table
17.13
Displaying Fields from Joined Tables
The UI layer specifies how information joined at the business layer will be displayed
From Base Table
From Joined Table

Opportunity List Applet Opportunity BC
UI Layer Business Layer Data Layer

17
S_STG
13 of 18
S_OPTY
17.14
Join Definition

Specifies the joined table from which to retrieve data

` Is a child object of the business component
Defaults the alias property to the name of the joined table

` Modify alias when there is more than one join to same table
Alias of join
Joined table
14 of 18
17.15
Join Specification
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
Name Description
Sales Stage Id
S_OPTY
ROW_ID DESC_TEXT CURCY_CD NAME CURR_STG_ID
S_STG
NAME ROW_ID PHASE_CD STG_ORDER
Foreign Key field
Primary key column
17
FK
PK
15 of 18
Opportunity
17.16
Implicit Joins
Base tables are automatically joined to their extension tables

` Known as implicit joins ` Make extension table rows available to the BC ` An explicit join to describe the relationship is not needed
Come pre-configured as part of the Siebel object architecture

` Name of an implicit join is always the name of the _X table
S_OPTY_X does not appear here

S_OPTY_X Appears Here
S_OPTY_X does appear here

16 of 18
Do not appear as Join object definitions Do appear in the picklist for the Join property in an SVF
17.17
Fields That Map to an Extension Table

Join property specifies the extension table being referenced Column property references a column in the extension table Field is editable in the UI
17
The Budget Amt field references the S_OPTY_X table
The S_OPTY_X column, ATTRIB_44, contains budget amount data
17.18
Module Highlights

18 of 18
A BC is a person, place, thing, or event about which data is stored A BC can be defined once then re-used by different BOs Each BC references a single base table A BC can include data from joined tables A join definition specifies joined table A join specification specifies how to access joined table via PK/FK An extension table extends data in the BC Fields on extension tables use implicit joins
Siebel Party Business Components
18.1
Module 18: Siebel Party Business Components
18
18
18.2
Module Objectives

` Define a party business component ` Describe the role of S_PARTY and its extension tables in storing party business component data ` Describe how data is stored differently for non-party business components and party business components ` Describe how implicit and explicit joins are used with party business components

` Party business components are a fundamental element of the application architecture
2 of 26
18.3
Business Challenge: Modeling Party Data
Party data is the ubiquitous information found in most RDBMS

` Some prominent party types include Contacts, Employees, Positions, Accounts, User Lists, Organizations, and Access Groups
Party types are often related to each other

` ` ` ` Employees are related to positions Positions are related to accounts Access groups are related to organizations and so forth
Relationships may be dynamic or ad hoc

` A contractor becomes an intern, then an employee ` An access group is required for participants of the January 2007 Big Release Roll-Out Event
3 of 26
18
Reference
Siebel Security Guide: Configuring Access Control Configuring Siebel Business Applications: Configuring Tables and Columns: About the S_PARTY Table
18.4
Business Challenge: Modeling Party Data Continued
Representing these relationships could result in data models that do not have optimal normalization
` Multiple records may be created for each relationship
A separate record is created for a contractor, another for an intern, and a third for an employee
` A special entity may have to be created for each new ad hoc relationship
Contractor Table 1. An individual is a contractor. . . First Name Navdeep Last Name Singh Phone 321-654-0987 Phone 321-654-0987 Phone 321-654-0987
4 of 26
2. . . .becomes an intern . . . 3. . . then an employee.
Intern Table First Name Last Name Navdeep First Name Navdeep Singh Last Name Singh Employee Table
Same data, three different places
18.5
Business Solution: Party Business Component

Provides a way to create a network of relationships between party types to reflect changes and complexities in the business environment Infuses flexibility into the data model
` Can establish and change relationships between various party types, as needed
Organization Employee
Account Contact
Party business component
Access Group Position

User
5 of 26
18
18.6
Party Business Components
Are similar to standard business components; they:

` ` ` ` Group data according to business logic Are referenced by applets Specify access to tables Have fields that map to columns
Name
Party Type Code
Fields
Base table
S_PARTY
NAME PARTY_TYPE_CD
Columns
6 of 26
Party business component
Account
18.7
Differences Between Party and Non-Party BCs

In standard BCs, most data is stored in the base table In party BCs, data is stored in extension tables S_PARTY acts solely as a linking mechanism between types
Standard BCs
Standard BC: Opportunity S_OPTY
NAME ROW_ID DESC_TEXT CURCY_CD BDGT_AMT
Party BCs
Party BC: Account
Base Table Record data stored here

Base Table Relationship data stored here
Extension Table Record data stored here

7 of 26
18
S_PARTY
ROW_ID NAME PARTY_TYPE_CD
S_ORG_EXT
REGION ROW_ID NAME ASGN_DT DIVISION
18.8
S_PARTY and Its Extension Tables
Eight prominent S_PARTY extension tables store the data

Base Table S_PARTY Extension Tables S_CONTACT S_USER S_EMP_PER S_ORG_EXT S_BU S_USERLIST S_PARTY_GROUP S_POSTN Access Controlrelated Organizationrelated Person-related
8 of 26
Other S_PARTY Extension Tables
Tables such as S_CONTACT_X (which is the 1:1 extension table for the S_CONTACT table) are formally an S_PARTY extension table. To list the complete set of S_PARTY extension tables, execute a query in Siebel Tools to retrieve all tables with the Base Table property = S_PARTY.

0/3
18.9
Commonly Used Party Business Components
Represent a variety of entities that can be arranged into groups related to persons, organizations, or access control
Commonly Used Party Business Components

PersonRelated
Employee User Contact
Account Division
Position Access Group User List
Organization
9 of 26
18
OrganizationRelated
Access Control

1/3
18.10
Person-Related Party Business Components

Store their main data in S_CONTACT May store additional data in S_USER and S_EMP_PER
` Serve as logical extension tables
Stores majority of personrelated data S_PARTY

ROW_ID PK
Logical extension table to store userspecific data S_USER
Logical extension table to store employeespecific data S_EMP_PER
S_CONTACT
LAST_NAME EMAIL_ADDR ROW_ID PAR_ROW_ID FK FST_NAME
FK
FK
10 of 26
ROW_ID
LOGIN
PAR_ROW_ID
PASSWORD
ROW_ID
PAR_ROW_ID
HIRE_DT
BONUS_FLAG
CURR_SALARY

1/3
18.11
Person-Related Party Business Components Continued
Primarily reference person-related S_PARTY extension tables
Party Business Component (BC): User

Party Type Code Last Name Login Name
No record here for John. John is not a user.
ROW_ID 1 2 3
PARTY_TYPE_CD Person Person Person
PAR_ROW_ID 1 2 3
FST_NAME John Sally Chris
LAST_NAME Doe Smith Jones
PAR_ROW_ID 2 3
LOGIN SSMITH CJONES
A person. . .
. . .has contactrelated details. . .
. . .and user login data
11 of 26
18
S_PARTY
S_CONTACT
S_USER

1/3
18.12
Person-Related Party Business Components Continued
A number of person-related business components use these tables
Party BC: Contact

First Name Last Name
Party BC: Employee

Last Name Login Name Hire Date
S_CONTACT
PAR_ROW_ID 1 2 3 FST_NAME John Sally Chris LAST_NAME Doe Smith Jones
S_USER
PAR_ROW_ID 2 3 LOGIN SSMITH CJONES
S_EMP_PER
PAR_ROW_ID HIRE_DT
4-Sep
John is not a user or employee

Sally is not an employee

12 of 26

2/3
18.13
Organization-Related Party Business Components

Store their main data in S_ORG_EXT May store additional data in S_BU May include account, division, organization, or household data
=Y for ABC Company internal division S_PARTY

ROW_ID PK
Logical extension table to store organization data S_BU
S_ORG_EXT
ROW_ID PAR_ROW_ID FK NAME LOC EMP_COUNT PRTNR_FLG HIST_SLS_VOL INT_ORG_FLG
FK
13 of 26
18
ROW_ID
NAME
BU_FLG
PAR_ROW_ID

2/3
18.14
Organization-Related Party Business Components Continued
Multiple organization-related business components use these tables

Account
Name Location
Organization
Name Internal Org Flag Organization BU Name
S_ORG_EXT
PAR_ROW_ID 1 2 3 NAME ABC Company Sales Division ABC Company ABC Customer INT_ORG_FLAG Y N N LOC HQ
S_BU
PAR_ROW_ID NAME BU_FLG
2 3
ABC Company ABC Customer
Y Y
Sales is not an organization
14 of 26

3/3
18.15
Groupings for Access Control
Represent groupings of party instances

` User List ` Access Group ` Position
S_PARTY
ROW_ID PK
S_USERLIST
ROW_ID NAME PAR_ROW_ID FK
S_PARTY_GROUP
ROW_ID NAME PAR_ROW_ID
S_POSTN
NAME POSTN_TYPE_CD
FK
FK
15 of 26
18
ROW_ID
PAR_ROW_ID

3/3
18.16
Groupings for Access Control Continued
Access Group, User List, and Position are party business components
If a user list, populate S_USERLIST If an access group, populate S_PARTY_GROUP S_PARTY_GROUP
NAME 1 Consultants User List 2 Gold Customers PAR_ROW_ID NAME
S_PARTY
ROW_ID 1 2 3 PARTY_TYPE_CD User List Access Group Position
S_USERLIST
PAR_ROW_ID
User List
Name
Access Group
Name
Business component
18.17
Example, Relating Party Data

A user list can be associated with persons via the S_PARTY intersection table S_PARTY_PER There are relationships in S_PARTY
` They are represented in S_PARTY_PER ` ROW_ID in S_PARTY is used to relate party types
PARTY_ID 003 003
PERSON_ID 001 002
ROW_ID 001 002 003
PARTY_TYPE_CD Person Person User List
NAME Smith, Mary Smith, John ABC User List
17 of 26
18
S_PARTY_PER
S_PARTY
18.18
Example, Relating Party Data Continued
An access group can then be networked with those users, or other user lists, or most any other S_PARTY type
` Person, User List, Organization and Account party types can be related to an Access List party type
Network
Organization Employee
Account Contact
S_PARTY_PER
PARTY_ID 003 003 005 005 PERSON_ID 001 002 003 004
S_PARTY
ROW_ID 001 002 003 004 005 PARTY_TYPE_CD Person Person User List Organization Access List NAME
Position
Smith, John Smith, Mary ABC User List ABC Org ABC Access Group
18 of 26
Access Group
User
18.19
Party Implicit Joins

Used to populate the prominent S_PARTY extension tables Created automatically for these extension tables Are similar to implicit joins for standard business components
` Do not appear in join object definitions ` ROW_ID in base table is always the PK ` PAR_ROW_ID in extension is always the FK
S_PARTY
ROW_ID 1 2 3 PARTY_TYPE_CD Person Person Person
S_CONTACT
PAR_ROW_ID 1 2 3 FST_NAME John Sally Chris LAST_NAME Doe Smith Jones
S_USER
PAR_ROW_ID 2 3 LOGIN SSMITH CJONES
PK
FK
FK
Base Table
Extension Table
Extension Table
19 of 26
18
18.20
Explicit Join: Non-Party Business Component

Data in a party table can be joined into a non-party business component Example: Bringing account data into the Opportunity business component for display in an Opportunity applet
Non-Party BC: Opportunity

Name Description Account Account Location
20 of 26
18.21
Explicit Join Definition
References the extension table that contains data of interest
Opportunity
Name Description Account
FK
References PAR_ROW_ID
S_PARTY extension table

21 of 26
18
S_OPTY
PR_DEPT_OU_ID NAME ROW_ID DESC_TEXT CURCY_CD
S_ORG_EXT
PAR_ROW_ID ROW_ID LOC NAME
18.22
Explicit Join: Another Party Business Component
Uses an explicit join to the party table, and not the implicit one
` Example: Bringing parent account data into the Account business component for display in an Account applet
Account
Name Location Parent Account Name Parent Account Location
22 of 26
18.23
Explicit Join Definition
Select or create an explicit join to the desired S_PARTY extension table

` Use a join specification to specify the relationship
The Account party business component
has multiple explicit self-joins to S_ORG_EXT Select the one that specifies the relationship of interest
23 of 26
18
18.24
Module Highlights

24 of 26
Party types have dynamic or ad hoc relationships Party BCs create relationships between party types Party BCs are similar to standard BCs but data is stored in extension tables Eight prominent S_PARTY extension tables store data Person-related party BCs store data in S_CONTACT Organization-related party BCs store data in S_ORG_EXT Access Group, User List, and Position are party BCs Party implicit joins populate S_PARTY extension tables Explicit joins reference extension tables that contain data
18.25
Lab

` Examine how fields in a (non-party) business component map to columns in base and joined tables ` Examine how fields in a party business component map to columns in S_PARTY, its extension tables, and joined tables
25 of 26
18
18.26
Siebel Business Objects
19.1
Module 19: Siebel Business Objects

19
19
19.2
Module Objectives

` Describe how business objects focus data presented in the UI based on context ` Describe how views reference business objects ` Describe how links are used to relate parent business components to child business components
` Business objects enable you to configure your companys business logic
2 of 16
19.3
Application Architecture: Business Objects (BO)

Provide a way to organize BCs into major areas according to your business logic requirements Provide context to views

UI Layer
Applet
View
Screen
Application
Business Layer
Field
Business Component
Business Object 1 or many
Data Layer
Column
Table
References
3 of 16
Reference
Configuring Siebel Business Applications: Configuring Business Objects
19
19.4
Business Challenge
Business components provide a way to group data according to business logic, but they do not address the need for context
` For example, the opportunity BC defines how to retrieve opportunity data, but not related activity data
?
How is it that the Activities view shows only activities related to the Kaboom opportunity?
4 of 16
19.5
Business Solution: Business Objects Provide Focus
Business objects contain relationships used to access records from a child business component
` Identifies records to display depending on context in which they are viewed ` Ensures that only records related to parent BCs are returned from queries
Activities pertaining to Kaboom opportunity, and only Kaboom, are displayed
5 of 16
19
19.6
Business Objects
Are a collection of related business components that represent a major area of the business
` Contain parent and child business components ` Relate parent and child components via links ` Links focus records displayed based on the context in which they are viewed
Business Object
Opportunity
Opportunity
Link focuses data in view Children BCs provide data related to parent
Parent BC provides most data; data is specific to the BO
Action
Product
Source
6 of 16
Provide a container for grouping business components Provide context for views
19.7
Business Object Component
Contains Link and BusComp properties that relate the parent and child business components to each other
Link relates parent to child
Child BC
Parent BC
7 of 16
19
19.8
Link Definition
Identifies the PK/FK relationship

` Identifies which records to retrieve from the child business component ` Identifies the foreign keys to populate when new child records are created
Is used with both 1:M and M:M relationships between parent and child data
Opportunity
Opportunity
Link Definition
Action
Product
Source
8 of 16
19.9
1:M Link
Used for 1:M relationship between parent and child business components
Link Definition
FK field in child BC
Defaults to parent BC/child BC
PK field in parent BC (defaults to ROW_ID if blank)
9 of 16
19
19.10
M:M Link
Used for M:M relationship between parent and child business components Uses an intersection table to resolve the link
Intersection table with FK columns
10 of 16
19.11
Cascade Delete Property
The Cascade Delete property of a link specifies whether child records of a 1:M relationship are deleted when the parent record is deleted
` None: Neither deletes nor clears the foreign key column ` Clear: Does not delete, but clears the foreign key column ` Delete: If a parent record is deleted, all child records are deleted
11 of 16
19
19.12
Cascade Delete Property Continued
Determined by your business logic

` Should all activities be deleted if parent contact is deleted? ` Should all child opportunities be deleted if the parent account is deleted?
Deletion cascades
12 of 16
19.13
Grandchild Business Components

Business objects may include grandchild business components Used in parent-child-grandchild views
Parent BC: Account
Activities for selected Art.net activity plan
Child BC: Activity Plan
Grandchild BC: Activity Plan Action

19
Activity plans for Art.net
19.14
Links for Grandchild Data
Specify how the grandchild and child business component are related
` Used to retrieve grandchild records on parent-child-grandchild views
Parent/Child
Child/Grandchild
19.15
Module Highlights
Business objects
` Provide a way to group BCs according to business logic ` Provide context to views ` Contain parent and child BCs associated via links
` A M:M link uses an intersection table to resolve the link
BOs may include grandchild BCs
15 of 16
19
Links provide a way to focus records based on context Links relate parent and child BCs Link definitions specify which records to retrieve from child BCs A 1:M link is used for a 1:M relationship between parent and child BCs A M:M link is used for a M:M relationship between parent and child BCs
19.16
Configuration Strategy
20.1
Module 20: Configuration Strategy

20
20
20.2
Module Objectives

` List the critical elements of the Siebel configuration strategy

` Following a reasonable configuration strategy can expedite your configuration efforts and make your configured application robust and upgradeable
2 of 16
20.3
Configuring a Siebel Application

Configuring is the process of using Siebel Tools to modify an as-delivered Siebel application to meet business needs Object definitions are edited and created
` Developers do not modify code in siebel.exe ` Developers do not write SQL directly
Object Manager SRF Repository Data Siebel Repository File

3 of 16
Reference
Using Siebel Tools Developing and Deploying Siebel Business Applications: Setting Up a Developers Local Database
20
20.4
Siebel Applications
Siebel as-delivered applications include a predefined set of screens, views, lists, forms, and their associated templates
A predefined view
4 of 16
20.5
Tailoring the Logical User Interface
Developers tailor the as-delivered Siebel screens, views, lists, and forms to better support users business needs
A tailored view
5 of 16
20
20.6
Tailoring the Physical User Interface

Use the existing physical UI files whenever possible When necessary, copy existing files and modify as needed
Use an HTML or a text editor to modify layout Use a text editor to modify colors, fonts, etc. Siebel template files Cascading style sheets Image files UI files Use a graphics program to add your organizations images Object Manager SRF Database Server Siebel Repository File
6 of 16
20.7
Siebel Business Entities
Siebel as-delivered applications utilize a set of Siebel business components that implement the defined business logic
Account
Service Request
Contact
Action
Product
7 of 16
20
20.8
Tailoring the Business Logic
Developers also tailor the application by modifying the definitions of the business components to implement the business logic appropriate to the users organization
Account
Add fields
Modify form of the relationship
Service Request
Contact
Action
Modify properties of existing fields
Product
8 of 16
20.9
Extending the Data Layer

Siebel as-delivered applications contain a large, predefined set of database tables Developers can tailor the application by extending the set of database tables
` Recommendation is to perform this in a limited and controlled manner
CX_OPTY
S_OPTY CREATED ROW_ID Siebel 8.0 Essentials CREATED_BY CURCY_CD
S_OPTY_X
9 of 16
20
Use existing extension tables to store additional attributes, or
create custom tables on a very limited basis
MID_NAME MID_NAME FST_NAME FST_NAME LAST_NAME LAST_NAME ROW_ID ATTRIB_44 ROW_ID ROW_ID
20.10
Make minimal changes to the as-delivered application Use existing object definitions in the as-delivered repository whenever possible
` Ensures that a new configuration can be upgraded with minimal effort
Modify definitions as required, rather than creating new ones
10 of 16
` Creating new object definitions can lead to redundant configuration and increase the maintenance effort
20.11
Configuration Strategy Continued
Do not delete, make inactive, or rename seemingly unused object definitions

` Other object definitions might reference them ` Deleting does not save memory, storage space, or improve performance
Use existing template files
11 of 16
20
` Modify only when changes are essential ` Modifying a template for one view or applet can have unexpected consequences if another view or applet uses the same template
20.12
Plan your configuration project from the top down

` First, determine UI and application functionality ` Then, determine what changes are necessary at the Business layer to implement UI functionality ` Finally, determine what changes are necessary at the Data layer to implement Business layer changes
Keep changes to a minimum

Determine UI Functionality
Determine Required Business Layer Changes
Determine Required Data Layer Changes
12 of 16
20.13
Make changes from the bottom up

` First, edit Data layer definitions, if necessary ` Then, edit Business layer definitions, as required ` Finally, edit or create the templates and UI layer definitions to display the data correctly
Edit Business Layer Definitions, as Required
Edit Data Layer Definitions, if Necessary
13 of 16
20
Edit or Create UI Layer Templates and Definitions
20.14
Create a Separate Development Environment

To isolate the development effort from the enterprises production database, set up a development environment Each developer or group can work on a different aspect of the development effort
` Use Siebel-supplied mechanisms to separate the development effort into projects
Server Machine
Developer Workstation
14 of 16
Test all customization and extensions thoroughly before deploying to end users
20.15
Develop on the Local Repository
Always make changes to the object definitions in the local repository

` Cannot undo or back out changes when made directly on the server ` Changes made directly on the server are immediately available to other developers
Incomplete changes on the server cause problems
Server Machine
Server repository
Local repository
15 of 16
20
Use Siebel-supplied mechanisms to copy definitions between server and local databases
20.16
Module Highlights
Configuring is the process of using Siebel Tools to modify an as-delivered Siebel application Recommended configuration strategy:
` Tailor existing logical UI, physical UI, and business entities to minimize development and support effort ` Do not delete, make inactive or rename unused object definitions ` Use existing template files
` Enables developer or group to work independently ` Enables developer to test customizations before deploying
16 of 16
Plan configuration project from the top down, make changes from the bottom up Development and production environments are separate
The Configuration Process
21.1
Module 21: The Configuration Process
21
21
21.2
Module Objectives

` Describe the development environment architecture ` Set up the development environment

` Being able to set up the development environment is critical to carrying out a successful configuration
2 of 20
21.3
The Development Environment

Siebel Remote is used to establish a local development environment Siebel Developer Web Client provides full Siebel application functionality in a local environment
Enterprise
Server CFG Server SRF
Siebel Server
Synchronization Manager
Developer Web Client

Object Manager
Local CFG Local SRF
Server Database
Siebel File System
Local Database
Local SFS
3 of 20
Reference
Using Siebel Tools Siebel Remote and Replication Manager Administration Guide Developing and Deploying Siebel Business Applications: Setting Up a Developers Local Database
21
` Accesses a local DB containing a subset of the server database ` Synchronizes with the server database, as necessary ` Implements a development and testing environment for individual developers

0/8
21.4
Procedure for Setting Up the Development Environment

1. Enable the Development Environment 2. Create the Developer 3. Create a User Login 4. Generate the Local Database Template 5. Extract User Data 6. Modify and Verify Configuration Settings 7. Initialize Local Database 8. Extract Repository Data

1/8
21.5
Enable the Development Environment
Enable the Siebel Remote component group to enable development using a local database
` After enabling a component group, do not forget to restart the Siebel Server and synchronize components
Enable Siebel Remote
5 of 20
21

2/8
21.6
Create the Developer

Add the developer as an employee Associate a position and responsibility Register the developer as a mobile client
Add employee record
Register mobile client


3/8
21.7
Create a User Login

If necessary, create a corresponding database login using RDBMS tools and the grantusr.sql script as a template Example:
Screen shot from Microsoft SQL Server Management Studio Express copyright Microsoft Corporation
21

4/8
21.8
Generate the Local Database Template
Run the Generate New Database server task to generate a local database template
` Snapshot of the current version of the database schema (tables, columns, indexes, and so forth)
8 of 20

5/8
21.9
Extract User Data
Run the Database Extract server task to extract user data

` Generates compressed data files
Stored on the server
` User data is extracted for the user(s) specified in the job parameters
Data is extracted to the specified mobile users directory
9 of 20
21

6/8
21.10
Modify Configuration Settings
Modify configuration information for Siebel Tools in ..\tools\BIN\<Language Code>\tools.cfg

` For example, ..\tools\BIN\ENU\tools.cfg
Modify configuration information for Siebel Developer Web Client in ..\client\BIN\<Language Code>\<application>.cfg
` For example, ..\client\BIN\ENU\uagent.cfg for the Siebel Call Center Developer Web client
` ` ` `
Native client connection information for the local database ODBC connection for the server ODBC connection for the local database Location of the local Siebel file system
10 of 20
Both configuration files hold critical information to ensure proper behavior of local executables:

6/8
21.11
Example Configuration Settings
Example: tools.cfg (edited for length)

Overall configuration: Name of SRF file, application name, root directory, and ODBC connections to local and server databases for testing connectivity Available data sources. Add more if needed.
Server connection information

Local connection information, including native connect string. Note absolute path. Modify if local database is in a different location.
11 of 20
21

6/8
21.12
Verify Web Client ODBC Connections
Ensure that the Web Client ODBC connection references the local database
` The database file parameter of SEAW Local Db default instance must match ConnectString in [Local] section of uagent.cfg ` ConnectString must point to local DB: \client\LOCAL\sse_data.dbf
Web Client connection. . .
. . .must match
Must point to local DB


6/8
21.13
Verify Tools ODBC Connections
Ensure that the Tools ODBC connection references the local DB

` The database file parameter of SSD Local Db default instance must match ConnectString in [Local] section of tools.cfg
Tools connection ...
. . .must match
13 of 20
21

6/8
21.14
Test Tools ODBC Login
Check user IDs and passwords, and then test the connection
1. Check
2. Test
14 of 20

7/8
21.15
Initialize Local Database
Local database is initialized upon first login to client

` Creates local database (sse_data.dbf) from template ` Populates local database with data from compressed files
Local db
15 of 20
21

8/8
21.16
Extract Repository Data
Perform a Get to extract repository data

` Copies all objects from the server repository to the local repository ` Must be performed before compiling
SRF must be based on the full set of Siebel objects
Get all projects to extract repository data
16 of 20
21.17
The Big Picture
Steps to create a usable local database
Server
Template provides schema 3. Use templates to initialize local DB and populate user data 1. Generate DB template Compressed files provide user data 2. Extract user data Server database provides repository data
Server Database
Local Database
Repository Data
4. Extract repository data

17 of 20
21
Client
21.18
Additional Developers
For each additional developer:

1. 2. 3. 4. 5. Create the developer Create a user login Extract the local database Initialize the local database Verify login and data sources
Developer Workstation Developer Workstation Developer Workstation
Server Machine
Server
Local
Local
Local
18 of 20
21.19
Module Highlights
Siebel Remote is used to establish a local development environment An individual developer uses Siebel Developer Web Client to develop and test custom configurations Create the development environment by:
19 of 20
21
` ` ` ` `
Installing Siebel Tools on the client Enabling Siebel Remote on the server Creating a developer, login, and remote user on the server Generating, extracting, and initializing a local database Verifying login and data sources
21.20
Lab

` Set up an employee as a developer ` Extract a local database for the developer ` Populate the developers local database with user and repository data
20 of 20
Managing Object Definitions
22.1
Module 22: Managing Object Definitions
22
22
22.2
Module Objectives

` Explain the role of projects ` Manage object definitions using Check Out and Check In ` Lock projects locally
2 of 22
` Checking projects in and out are critical tasks that enable multiple developers to work together on a configuration effort
22.3
Projects

Are named sets of object definitions in a repository

` Only one version of a project exists in a repository at a time
Are a mechanism to organize object definitions so that a single developer can exclusively work on them as a group Project
Account (SSE)
Screen
Accounts Screen
Applets
Account List Applet Account Entry Applet
Views
Account List View All Account List View Managers Account List View Account Profile View
Object definition with Project property = Account (SSE)

Reference
Using Siebel Tools
22
22.4
Existing and New Projects

The as-delivered Siebel application contains a large number of existing projects New projects are created by:
` Selecting the Project object type, and ` Creating a new record in the Object List Editor
4 of 22
22.5
Assigning Object Definitions to Projects
Every object definition must belong to one, and only one, project
` Either a Siebel-supplied project, or ` A user-created project
A top-level object definition has a Project property

` Child object definitions belong to the parents project
Child belongs to parents project. It does not have a project property.

22
22.6
Viewing Object Definitions by Project
View object definitions in a project using the Project drop-down list

` Displays object types for which there are object definitions in the selected project ` Select **All Projects** at the top of list to see all projects
1. Select project
2. Select object type
3. Object Type with project property = Account (SSE) displayed
6 of 22
22.7
Repositories

Master copy of repository resides on server database

` Stores tested object definitions for entire development team
Each developer has repository copy on local developer (client) workstation

` Developers perform all editing on their local repository
Server Machine Developer Workstation Developer Workstation Developer Workstation
Server
Local
7 of 22
22
22.8
Copying Projects
Check In and Check Out safely manage concurrent use by multiple developers Object definitions in one or more projects can be copied:
` From the server to the local developer repository (Use Get or Check Out to retrieve definitions) ` From the local developer repository to the server (Check In)
Overwrites the version in the destination repository

Project 1. Developer uses Get, Check Out 2. Developer modifies objects
Server
3. Developer uses Check In
Local
8 of 22
22.9
Getting Projects
Get populates a local database with a copy of projects from the server repository Use Get to bring object definitions modified by other developers to your local database Use Get with All Projects selected to populate a newly-initialized local database
9 of 22
Note
First select Check Out from the Tools menu, and then click Get in the Check Out dialog box.
22
22.10
Check Out
Click Check Out to copy projects from the server repository to the local repository
` The projects Allow Object Locking property must be disabled
10 of 22
22.11
Check Out Continued
Use Check Out in order to edit object definitions in a project

` Copies all object definitions in project on server to local database
Local copy of project is overwritten by server version Prevents other developers from modifying that project Permits developer to make changes to object definitions in that project
` Locks project on server repository
` Locks the project in the local repository
Pencil indicates writable
Property is editable
11 of 22
22
22.12
Check Out Objects

Allows for checking out individual objects

` Quicker than checking out entire projects
To enable object-level Check Out

` Enable object-level Check Out in the [Siebel] section of tools.cfg

Ensure ToolsConstrain parameters = TRUE Add EnableObjectCOCI=TRUE
1. Enable objectlevel Check Out in tools.cfg

2. Log in as SADMIN to server, then enable Allow Object Locking

12 of 22
` Log in to Tools as SADMIN to the server database and enable the projects Allow Object Locking property
22.13
Canceling Check Out
Discards changes made to checked-out project if:

` Changes are no longer required ` Local project has become corrupted
To cancel a Check Out of a project:

` Check out the project from the server again

` Then check in the project to unlock the project on both the local and server repositories
13 of 22
22
Replaces modified object definitions in local repository with original version from server repository Repeating Check Out is permitted for person who last checked out project
22.14
Undo Check Out
Use Undo Check Out to release lock on a project on the server without checking in edited object definitions
` Makes the original project available to another developer ` Can be followed by Get to restore original definitions in local DB
Alternate way to cancel Check Out

Cannot publish definitions
Undo Check Out:
Developer can continue to modify object definitions but will not be able to check them in to the server
14 of 22
` Releases lock on server ` Retains lock on local database
22.15
Check In
Is used when object definitions in the project have been edited and tested
` Copies object definitions from local repository to server repository ` Replaces versions of checked out object definitions with new versions and unlocks projects
Can also check in object definitions in newly created projects Maintain Lock leaves project locked for further local modification by current developer
` Releases locks on both server and local copies of project
15 of 22
22
22.16
Check In Continued
Click Check In to copy projects and objects from the local repository to the server repository
16 of 22
22.17
Locking Projects
You can directly lock and unlock projects in the current repository (local or server)
Click to set Locked property directly
Or Select Tools > Lock Project
17 of 22
Project Drop-Down
You can select **My Locked Projects** in the Project drop-down list to display only those projects you have locked (either by checking them out or locking them directly).
22
22.18
Locking Projects Locally

Allows developer to make and test modifications locally Prevents developer from checking changes into server repository
` However, locking does not prevent other developers from checking out and modifying a project
Consider when:
Server Machine
Server
Local
18 of 22
` Prototyping your ideas without preventing other developers from checking out the project ` Intending to discard (rather than save) your work
22.19
Do Not Lock Projects on the Server
Oracle recommends that developers never directly lock projects on the server
` Prevents the developer from undoing changes and restoring original definitions ` Allows other developers to get object definitions in an incomplete, inconsistent, and untested state
Always use Check Out and modify the object definitions locally
Server
Local
19 of 22
22
22.20
Module Highlights

Projects organize object definitions so a developer can work on them exclusively The as-delivered application contains many projects Every object definition must belong to one, and only one, project Developer edits a copy of master repository residing on local client Check Out and Check In are used to modify object definitions
` Project locking ensures only one developer can modify a given object
20 of 22
22.21
Lab

` Explore how projects work in Siebel Tools ` Check out a project from the server
21 of 22
22
22.22
Editing and Compiling Object Definitions
23.1
Module 23: Editing and Compiling Object Definitions
23
23
23.2
Module Objectives

` ` ` ` ` Create new and edit existing object definitions Validate edited object definitions Archive object definitions and projects Back up the local database Compile object definitions into a repository file
` These are fundamental activities that occur during all configuration efforts
2 of 24
23.3
Editing Object Definitions
Use the Object Explorer and Object List Editor to edit object definitions
` Ensure that the project has been locked
Type in a value, or. . . Pencil indicates object is locked and editable
. . .select a value
3 of 24
Reference
Using Siebel Tools
23
23.4
Creating a New Object Definition

Select the desired object type in the Object Explorer Create a new record in the Object List Editor
1. Enter a unique name 2. Select a project from the picklist 3. Assign values to the remaining properties, as necessary
Only locked projects are available for object creation
4 of 24
23.5
Changed Flag
Indicates records that have been modified since the changed date Is set whenever a record is edited Is cleared by resetting the changed date value
5 of 24
Changed Flag
The Changed flag indicates only that the record has been touched. A developer may change the value of a property and then undo the change. The Changed flag will still be set. Some developers will select an object type and then query for all object definitions with the Changed flag set. Only those definitions that have been edited will display in the OBLE.
23
23.6
Validating Object Definitions
Determines the correctness of selected object definitions in the repository

` Includes all child object definitions for the selected parent definitions
Is based on a set of Siebel-defined rules

Error
Warning
User can enable or disable a Siebeldefined rule
6 of 24
23.7
Validating Object Definitions Continued
Select the object definition to validate
Right-click and select Validate

Click Start in the Validate dialog box
Violations appear in Errors list
Click to access the Validate Options dialog box
7 of 24
23
23.8
Archiving Projects
Projects can be archived to .sif files

` ` ` ` Select the project (or projects) to be archived Select Tools > Add to Archive Select an existing (or create a new) archive file Click Save in the Export to Archive File dialog box
8 of 24
23.9
Archive Files

Contain projects exported from a repository

` Available for importing into other repositories
Have .sif extension by default Are used to share projects among developers Are used to back up projects Can be version-controlled using source code control systems
Archive file
9 of 24
23
23.10
Archive Recommendations
Archive the entire project Do not archive individual objects
` Could result with inconsistent object definitions ` Difficult to recover from a partial or incomplete archive ` Will only save a few minutes per day compared to archiving the project
Archive at appropriate intervals
10 of 24
` Prior to implementing a large amount of work ` After testing a section of work ` Several times per day during heavy development
23.11
Importing Object Definitions
Object definitions in an archive file can be imported into the local repository on the developer workstation
` Appear in the current active repository
To import object definitions

` Select Tools > Import from Archive ` Select the archive file ` Indicate how to resolve conflicting object definitions
11 of 24
23
23.12
Resolve Import Conflicts
Set the default conflict resolution
12 of 24
Adjust individual resolutions by right-clicking them in the Object differences list
23.13
Compare Objects
Displays differences between the selected object definition and another one:
` In the current local repository ` In an archive file ` In the repository on the server
Allows developers to identify differences while comparing objects
13 of 24
23
` Delete individual child object definitions ` Copy individual child object definitions in either direction
23.14
Compare Objects Continued
To compare an object definition to one in an archive or repository:

` ` ` ` Select the object definition to be compared Select Tools > Compare Objects Select type of comparison Select the archive or repository
14 of 24
Note
Typically there will only be one repository available, and this repository defines an application. This repository is the Siebel repository and it will be available on a local database and on a server database. However, there are circumstances when multiple repositories will be available: when a group is upgrading to a new version of Siebel Applications, or working with multiple applications. There can not be multiple repositories in a production environment because some run-time components read repository objects directly from repository tables, not the SRF. There can be multiple SRF files, compiled from different repositories, provided that they do not compromise data integrity. Refer to Bookshelf for more information.
23.15
Examine the differences in the Compare Objects window
Differences displayed
15 of 24
23
Definitions with difference highlighted
23.16
To compare two object definitions in the developer repository

` Select two object definitions to be compared (by SHIFT-clicking) ` Select Tools > Compare Objects > Selected
Modifying definitions is supported

Copy selected control
Delete selected control
16 of 24
Modifying Definitions
A child object definition in either parent object definition can be deleted or copied to the other definition.
23.17
Source Code Control Integration
Automate integration with source code control for repository data

Creates archive when project is checked in
17 of 24
23
Check archive into code management system
ODBC to server and local databases
23.18
Backing Up the Development Database
Is achieved by copying the local database file (.dbf)

` Backs up the entire database
Windows copy/paste
18 of 24
23.19
Compiling
Compile to produce an .srf file to test the configuration

` Reads object definitions from repository and creates a flat file representation to be accessed by siebel.exe at run time
Compile into .srf file located in the objects directory of the client application
Configured application Compiling Object Manager SRF Repository Data Siebel Repository File
19 of 24
23
23.20
Compile Projects

When starting and at milestones

` Use Compile All Projects to generate a new .srf file
Compile only selected projects or locked projects for incremental compile Back up the .srf file prior to full compile To compile projects:
` Select Tools > Compile Projects ` Select project or projects
Compile into the client directory
20 of 24
Get Projects
Remember to compile any projects after using Get; this ensures that the object definitions edited by your fellow developers are compiled into your .srf file.
23.21
Backing Up the Configuration File
Copy the .srf file to create backups

` Create an initial backup copy before starting development ` Create additional backups after major milestones
Rename the copies and compile into siebel.srf

` Using the original siebel.srf name for development eliminates the need to edit .cfg files to point to a renamed .srf
Compile into siebel.srf Original .srf
Copy .srf file after major milestones to create backups

23
23.22
Rapid Unit Testing

Allows developers to test changes in a local instance of the Developer Web Client Run-time behavior when user compiles SRF
` If Web client is running:

` If Developer Web Client is not running:
If user checked auto-start, Web client is started using debug setting
22 of 24
At end of the compile, the browser window refreshes The user is brought back to the view that was displayed before the compile
23.23
Module Highlights
Object definitions can be created and edited once the project is locked Validation determines correctness of object definitions Developer can generate archives that contain exported projects
` Share projects for back-up and version-control ` Export projects to and import from archive ` Highlight import conflicts and project differences
Compile to produce the .srf used to test a configuration Compiling:
` Reads object definitions from repository tables ` Creates a flat file (.srf) accessed by the Siebel application at run time
Rapid Unit Testing allows developers to test changes using the Developer Web Client
23 of 24
23
23.24
Lab

` Practice editing and validating object definitions in Siebel Tools ` Explore the use of diff and archive options in Siebel Tools ` Compile an .srf file
24 of 24
UI Layer Configuration: Web Templates
24.1
24
Module 24: UI Layer Configuration: Web Templates
24
24.2
Module Objectives
After completing this module you will be able to:

` ` ` ` Describe the role of Siebel Web template files Describe the role of Siebel tags in template files List the types of templates Describe how to register, associate, and bind a template file
Why you need to know

` Understanding template structure and how to register, associate, and bind template files is necessary in order to customize the look and feel of your Siebel application
2 of 28
24.3
Tailoring the Physical User Interface (UI)
24
Is performed by editing template files and cascading style sheets

Use an HTML or a text editor to modify layouts Use a text editor to modify colors, fonts, etc. Siebel template files Cascading style sheets Image files UI files Object Manager SRF Database Server Siebel Repository File
3 of 28
Reference
Siebel Developers Reference
24.4
Siebel Web Template Files

Are HTML files that specify how to render the views for a Siebel application in the users browser Specify the formatting and layout of:
` Graphic and text elements ` User data
Consist of standard HTML tags and Siebel-specific swe: tags
<table width="100%" class="banner" cellpadding='0' cellspacing='0' border='0'> <tr>
<td><img src="images/spacer.gif" height="29" width="10"></td> Siebel tag
<td><swe:menu type="Default" width="275" height="29" bgcolor="#ccccff" fgcolor="#000000" /></td>
4 of 28
Sample HTML
The sample HTML tags shown in the slide are excerpted from the CCFrameBanner.swt template file.
Standard HTMLHTML tag table tag
24.5
Siebel Web Template Files Continued
24
Are stored as separate files outside the Siebel repository

` Located in the WEBTEMPL directory in a Siebel installation ` Have an .swt extension
Are edited using text or HTML editor of your choice Can include other template files via swe:include tag Reference Cascading Style Sheet files (.css)
Siebel tag to include another Siebel template file
5 of 28
24.6
Siebel Tags
Are special tags inserted into template files

` They specify how objects defined in the repository should be laid out and formatted in HTML for display in the users Web browser
Control layout repetitively through iteration Serve as placeholders for Siebel-specific content
<swe:for-each-screen> Siebel tag to iterate over all screens
<swe:this property= FormattedHtml"> <swe:screenname/> </swe:this><img src="images/tb1_cls_1_d.gif" align="absmiddle" width="5" height="19" alt=""></td> </swe:screenlink> </swe:for-each-screen> Siebel tag to insert the name of the screen
6 of 28
Sample HTML
The sample HTML tags shown in the slide are excerpted from the CCScreenbar_Tabs.swt template file.
<swe:screenlink state="Active"><td id="swe:this.Id" <img src="images/tb1_mid_1.gif"><img src="images/tb1_opn_1_d.gif" align="absmiddle" width="5" height="19" alt="">
24.7
Cascading Style Sheets

24
Can be modified to define global parameters

` Fonts, foreground and background colors, and so forth
Style sheets:
` Are located in PUBLIC\enu\FILES directory in a Siebel installation ` Can be modified by customers
Edit style sheet files to achieve the desired look and style for your implementation
` Backup the current .css files ` Edit .css files with your preferred HTML editor
/*globalMenu Definitions*/ /*----------------------*/ TR.globalMenu, TD.globalMenu, TD.globalMenu A, TD.globalMenu A:visited, TD.globalMenu A:hover { font-size: 8pt; Adjust fonts color:#000000; background-color: #ccccff; Adjust colors font-weight:normal; }
7 of 28
File Locations
Cascading style sheet files (.css files) are located in: The Siebel Server installation directory [siebsrvr_root]\WEBMASTER\files\[language_code] The Mobile or Dedicated Web Client installation directory ]client_root]\PUBLIC\[language_code]\FILES The Tools installation directory ]tools_root]\PUBLIC\[language_code]\FILES
From main.css
24.8
Web Template Object Definition

Is a layer of abstraction between a UI object definition (View, Applet, or Web Page) and the file itself UI object definitions reference Web Template object definitions References an HTML Web template file
Changes are propagated to all objects that reference the file

24.9
Web Template Placeholders

Contain placeholders for Siebel logical UI definitions Definitions map to Siebel Web templates
24
Placeholder
24.10
Web Template Explorer
Is used in Tools to:

` Identify template files included in a template file ` Examine the contents of a template file ` Invoke an editor to modify the template file
Filter
swe tag highlighted
Highlights Siebel-supplied tags for easy viewing Navigate to View > Windows > Web Templates Window
10 of 28
Parent template
Child template

0/4
24.11
Types of Web Templates
24
Form Applet Web Templates List Applet Web Templates View Web Templates
11 of 28
Note
This list of Web Templates is not comprehensive; there are also Tree Applet Web Templates and Specialized Web Templates. Refer to Siebel Bookshelf for more information.
Web Page Web Templates

1/4
24.12
Form Applet Web Templates
Define the layout of form applets

` Placeholder provides starting point for building applet ` Tools Web Layout Editor assists you in setting template file Account Entry applet parameters
Web Layout Editor uses Applet Form Grid Layout
Object Manager uses template to build applet
UI
12 of 28
Tools

2/4
24.13
List Applet Web Templates
24
Define the layout of a list applet

` Standard Interactivity list applets use Base and Edit modes
Base Mode
A read-only list of data with buttons for editing
Edit Mode
An editable form for querying and data entry
13 of 28

2/4
24.14
List Applet Web Templates Continued
High Interactivity clients use EditList mode

EditList Mode
An editable list of data
EditList mode supports querying and data entry directly in the list
14 of 28

3/4
24.15
View Web Templates
24
Define the layout of a view

` Common view templates include:
View Detail (Parent with Pointer) View Basic View 50 50
15 of 28

4/4
24.16
Web Page Web Templates
Define the layout of Web pages such as:

` Login Page ` Error Page ` Container Page
16 of 28
The Login Web template defines the layout of the Login page
24.17
Using Template Files
24
Requires three types of relationships:

` Registering creates an object definition in the repository ` Associating identifies the Web template used to render an applet or view ` Binding fastens a control to a specific position on the page or an applet to a view View Example
Applets View
Associating Binding
(View) Web template

Registering swt
17 of 28
Applet placeholders
(View) Template file
24.18
Registering a Template File

Creates a Web Template object definition to define the logical name for the template Creates a Web Template File object definition to reference the actual physical file
Logical name in repository for template
Type of Web template
Actual name of the physical template file

Registering
Siebel applications are delivered with hundreds of template files, all of which are registered. You will only need to register a template file in the unlikely event that you need to create a new file.
24.19
Associating an Applet with Its Template
24
Creates an Applet Web Template object definition to specify the associated Web template
` Different applet modes can reference different Web templates
Mode for the applet
Applet template used to render applet for mode
19 of 28
24.20
Associating a View with Its Template
Creates a View Web Template object definition to specify the associated Web template
` Each view references a single view Web template
Web template used to render view

24.21
Associating a Web Page with Its Template
24
Creates a Web Page object definition and sets the Web Template property
21 of 28
Web Page Template
Web page templates are templates that are not view or applet Web templates. Examples of common Web page templates are login page, error page, and container page.
Web page template used to render Web page
24.22
Binding
Maps the components of an applet or view to placeholders in the corresponding template file Information is specified in the repository
` ` ` `
View Web Template Item Applet Web Template Item Web Page Item Results in the corresponding element being displayed at run time Binding Applets to Views
Applets Binding (Applet) Web template (View) Web template View Applet
Binding Controls to Applets

Controls/Lists Binding
Control placeholders
(Applet) Template file
Applet placeholders
(View) Template file

22 of 28
24.23
Applet Web Template Items

24
Are created by the binding process

` Item Identifier is the id attribute value in the swe:control tag
Are used at run time by the Siebel Web Engine to identify the controls that make up an applet
<swe:for-each count="6" startValue="1300" iteratorName="currentId"> <swe:control id="swe:currentId" hintMapType="FormItem">

swe:control Tag
The swe:control tag shown in the slide is in the dCCForm1Col.swt template file. This file is included in the dCCApletForm1Col.swt template file which is registered as the Web Template File for the DotCom Applet Form 1-Column Web Template. This tag illustrates the use of the swe:for-each tag. In this case the swe:control tag is executed repeatedly with values from 1300 to 1305.
24.24
View Web Template Items

Are created by the binding process

` Item Identifier is the id attribute value in the swe:applet tag
Are used at run time by the Siebel Web Engine to identify the applets that make up a view
<swe:applet hintMapType="Applet" id="1" hintText="Parent Applet"

swe:applet Tag
The swe:applet tag shown in the slide is in the CCViewDetail_ParentPntr.swt template file. This file is registered as the Web Template File for the View Detail (Parent with Pointer) Web Template.
24.25
Web Page Items

24
Identify the links and buttons appearing on a Siebel Web page

` Item Identifier is the id attribute value in the swe:pageitem tag
Are used at run time by the Siebel Web Engine to position the links and buttons
25 of 28
swe:pageitem Tags
The HTML and SWE tags shown in the slide are excerpted from the dCCFrameBanner.swt template file.
24.26
Summary of Object Definitions
Registering, associating, and binding adds object definitions to the repository
Associating 2. Identifies the logical template used to render an applet, view, or container page
Binding
1. Identifies the physical template file Registering
26 of 28
3. Specifies how the components of an applet, view, or container page are mapped
24.27
Module Highlights
24
Siebel Web Template Files are HTML files that specify how to render views for a Siebel application in a users browser
` Can include other template files ` Can reference CSS files
27 of 28
Siebel Tags are a Siebel-developed library of tags in Web template files processed at run time CSSs can be modified to define global parameters such as fonts and colors The four Web Template types are Form Applet, List Applet, View, and Web Page Template files require three types of relationships: Associate, Register, and Bind
24.28
Lab

` Examine Web templates
28 of 28
UI Layer Configuration: Applets
25.1
25
Module 25: UI Layer Configuration: Applets
25
25.2
Module Objectives

` Create and modify a list applet ` Create and modify a form applet

` You may want to display new data in the UI
2 of 24
25.3
Primary Applet Types: List Applet

Displays one or more records simultaneously in a list Fields for one record are displayed in a single row Typically displays fewer fields than a form applet due to width of monitor Supports drilldown to other views through hyperlinked fields
25
3 of 24
Reference
Configuring Siebel Business Applications: Configuring Applets
25.4
Primary Applet Types: Form Applet

Displays a single record Fields for the record are displayed in a grid or form Can show more fields at once than a list applet
4 of 24
Additional Applet Types
The following are some additional applet types (see Siebel Bookshelf for a complete list): Catalog list Chart Explorer view Hierarchical list Message Multi-value group applet Pick applet Rich list Salutation
25.5
Creating a List Applet
Follow these steps to create a new list applet

1. 1.Create Createnew newapplet appletobject objectdefinition definition 2. 2.Associate Associateapplet applettemplate templatewith withobject objectdefinition definition
25
Or use the List Applet Wizard

` ` ` ` ` ` Automates these steps Generally the preferred method Ensures that object definitions and properties are created Ensures that steps are not omitted Increases developer productivity Speeds project completion
5 of 24
Highly recommended
3. 3.Bind Bindcontrols controlsand andlist listcolumns columnsto totemplate template
25.6
List Applet Wizard
Use the List Applet Wizard to create a new applet

` Select File > New Object, select the Applets tab, select List Applet, and then click OK Wizard
6 of 24
25.7
List Applet Wizard Inputs
The List Applet Wizard requires the following inputs:

` ` ` ` Project the new applet will be part of Applet name and display title Business component the applet will reference The upgrade behavior
25
Admin, Non-preservable, Preservable
` The Web templates that will be used for each mode
` The business component fields that will appear in the Web layout ` Additional controls that will be added to the applet
By default, all of the standard buttons are selected
7 of 24
Base and EditList mode are commonly built using Applet List (Base/EditList) Edit mode is commonly built using Applet List Edit (Edit/New/Query)
25.8
List Applet Wizard Outputs

Creates required object definitions for controls, lists, and list columns Associates applet Web templates to the applet Binds list columns to templates
` Appear as applet Web template items
Invokes the Web Layout Editor

New applet object definition created
List Web Layout Editor invoked
8 of 24
25.9
Web Layout Editor
Is used to add, remove, and reorder applet Web template items

` Placeholders correspond to item identifiers of applet Web template items
25
Can be invoked from the right-click menu
1. Select the mode
2. Drag and drop items from the Controls/Columns window Select and rightclick to delete controls that you have added
25.10
Applet Web Templates

Specify which template is used when the applet is displayed in a given mode Contains Applet Web Template items
` The controls or list columns that have been bound to the template ` The item identifier that describes where in the applet the controls or list columns should appear
Specifies which template to use
Specifies where list column will appear
10 of 24
25.11
List Column Definitions
Specify:
` The field that is displayed ` The display name that appears at the top of the list column
25
May reference a symbolic string
11 of 24
25.12
Symbolic Strings
Ensure that the same name appears exactly the same way throughout the application Define it once, reference it anywhere Provide a way to manage updates, globally Are used by user interface objects such as:
Are stored in the repository containing words and phrases used in UI definitions
` Global Dictionary contains many commonly used terms ` Symbolic String Locale object type allows language translation
12 of 24
` Labels ` List columns ` Applet titles
25.13
Using Symbolic Strings
String reference:
` Refers to symbolic string object definitions ` Is selected from a picklist ` Refers to the name of the symbolic string
25
String override:
` Used for exceptions when strings are infrequently displayed ` Can be converted to symbolic strings using a Siebel-supplied string conversion utility
Reference to object in repository
13 of 24
String Conversion Utility
A string conversion utility is available that exports from local tables and imports to the Symbolic String table. It allows symbolic strings to be exported to a file, translated in another application, then imported back to the Siebel application with translated values for the appropriate language. The utility also allows developers to export string overrides and re-import them as string references, and it consolidates redundant local definitions. The utility file is Strconv.bat and is located in the Tools\bin directory.
25.14
Form Applet Wizard
Use the Form Applet Wizard to create a new form applet

` Select File > New Object, select the Applets tab, select Form Applet, and then click OK
14 of 24
25.15
Form Applet Wizard Inputs
The Form Applet Wizard requires the following inputs:

` ` ` ` Project that the new applet will be part of Applet name and display title Business component that the applet will reference Upgrade behavior
25
` Modes to use
` Uses the Applet Form Grid Layout template
Base mode is required for Standard Interactivity clients only Creates controls and binds them to applet Web templates By default, all standard buttons are selected
` Business component fields to appear in Web layout
` Additional controls to be added to applet
15 of 24
Edit mode is required for all clients
25.16
Form Applet Wizard Outputs
The Form Applet Wizard

` Creates required object definitions for Controls ` Associates applet Web templates to the applet ` Binds columns to templates
Appear as applet Web template items

New applet object definition created
` Invokes the Grid Layout Editor
Grid Layout Editor invoked

25.17
Grid Layout Editor
Is used to:
` ` ` ` Create new control object definitions Bind controls to the Web template Resize controls Reposition controls
25
Grid Layout Editor
17 of 24
25.18
Grid Layout Editor Continued

Allows drag-and-drop layout editing Supports formatting options such as:
. . .arranges selected controls
18 of 24
` Align controls ` Make same size ` Horizontal spacing ` Vertical spacing
Format menu. . .
25.19
Web Controls Toolbar

Supports drag-and-drop creation of controls Contains icons for:
` Text controls ` Check boxes ` Labels
25
HTML label
HTML text
19 of 24
25.20
Properties for Editing
No Delete, No Insert, No Merge, No Update are set to restrict the behavior of the applet
` Can also be set at the business component level ` Most restrictive settings are always used
Business Component
Applet
Affects all applets referencing this BC, or. . .
. . .can be customized for each applet
20 of 24
25.21
Preview the Applet
Right-click and select Preview to see how the applet appears

` When finished, right-click and deselect Preview to return to the Grid Layout Editor
25
21 of 24
Right-click to preview the applet
25.22
Module Highlights
List applets:
` Display records simultaneously in a list ` Contain fields for one record displayed in a single row
22 of 24
Form applets display a single record and contain fields for the record in a grid or form Applet wizards ensure object definitions are created and steps are not omitted Web Layout Editor is used to add, remove, and reorder Web template items List column definitions specify field displayed and display name Symbolic strings ensure that the same name appears exactly the same way throughout the application
25.23
Lab

` Modify a form applet using the Grid Layout Editor ` Create a new list applet using the wizard
25
23 of 24
25.24
UI Layer Configuration: Applications, Screens, and Views
26.1
Module 26: UI Layer Configuration: Applications, Screens, and Views
26
26
26.2
Module Objectives

` ` ` ` ` Tailor applications Configure how a view is accessed on a screen Change the order of screen views for a screen Create and administer a view Associate a view with a template
` Enables you to modify the user interface
2 of 24
26.3
Logical User Interface

Specifies the layout of the Siebel application Consists of:
` Applications, screens, views, applets, controls/list columns
This module focuses on views, screens, and applications

26
UI Layer
Applet
View
Screen
Application
Business Layer
Field
Business
Component
Business Object
Focus of this module 1 or many
Data Layer
Column
Table
References
3 of 24
Reference
Configuring Siebel Business Applications: Configuring Screens and Views Configuring Siebel Business Applications: Configuring Applications
26.4
Applications
Are collections of screens through which users can navigate Use a container page to display the Siebel Web page Specify the application-level menus
Application -level menus
Container page
4 of 24
26.5
The Container Page

Is a Web page that displays the menus, toolbars, screen tabs, and views that appear in the application Is specified in the Application object definition One container page per application Container Web page specifies
the container page
26
5 of 24
26.6
Container Page Example: Employee Application
Container page specifies application layout

Applicationlevel menu Screen tabs Link bar View Toolbar
Message bar
Links
Links on the link bar and links used with business objects are two entirely different concepts. Links used with business objects are used to establish a relationship between parent and child business components in the business object. Link bar links on the container page are used merely as a navigation device.
26.7
Application-Level Menus
Are specified in the Menu object type

Application uses Generic WEB menu
26
which contains
a list of menu items
Caption specifies text displayed
Position specifies order of appearance

26.8
Screen Tabs
Contain links to screens Are defined as page tabs
` Child object of the application
Specifies text that appears on the page bar
Specifies default page tab order appearance in screenbar
8 of 24
26.9
Screens
Have a child object type called Screen View that specifies the views and categories that appear in the screen
` Sequence property specifies where the view appears in the screen ` Menu Text property defines the text that appears in Site Map ` Type property defines the type of view within the screen
Four types: Aggregate category, aggregate view, detail category, and detail view
26
Specifies where the view appears in the screen
Specifies the type of view for this definition
9 of 24
26.10
Type Property for Screen View
An aggregate category is a container for a set of views accessible via a link in the linkbar
` May also contain subcategories
An aggregate view is a container for a set of views accessible via the visibility filter drop-down list, a link in the link bar, or the Home Page
Aggregate views
Aggregate category
26.11
Type Property for Screen View Continued
A detail category is a container for a set of detail views

` Each view is represented as a tab on the view tab bar ` Used to provide an additional layer of navigation
A detail view is a single view that displays data in a list or form that can be queried and edited
26
Aggregate category
Detail category. . .
. . .displays detail view tabs
Detail view
26.12
Sequence Editor
Assists in defining where view appears in the application

` Updates the sequence property of the screen view object definition ` Lists four screen view types in hierarchy
Right-click to invoke editor
Right-click to edit sequence

26.13
View
Consists of one or more applets References a business object that defines the relationships between data in the view Is associated with a Web template that defines its layout
26
13 of 24
26.14
View and Templates
Views use templates to organize data layout

Container Page Template Control placeholders
Form Applet Web Template
Menu
Branding Toolbars List Applet Web Template
Screen Tabs View
View Web Template

Web Template
Tree Applet Web Template Ticker Applet placeholder
14 of 24
26.15
Selecting a View Template

Find an existing view that has desired layout Examine the View Web Template object definition to determine the view template to use
The Account list view
26
uses the View Detail (Parent with Pointer) template
15 of 24
Best Practice
Siebel best practice is to modify an existing template. Steps to create and register a view template: Create a Web Template object. Create a Web Template file. Point to the view template file in the webtempl directory. Give a logical name to the template file so that it can be referenced by other objects. Registering the template creates a logical reference in the repository. It tells the repository that the template file exists.
26.16
View Wizard
Use the View Wizard to create a new view

` Select File > New Object, select View, and then click OK
Wizard
16 of 24
26.17
View Wizard Inputs
The View Wizard requires the following inputs:

` ` ` ` Project that the new view will be part of View name and display title Business object that the view will reference The upgrade behavior
26
` The Web templates that will be used ` The applets that make up the view
These applets will appear in the Web layout
17 of 24
26.18
View Wizard Outputs
The View Wizard:

` ` ` ` Creates a view object References view to a business object Associates Web templates to the view Invokes the Web Layout Editor
Creates view
References business object
Invokes Web Layout Editor
18 of 24
26.19
Web Layout Editor

Is launched by the View Wizard Can be launched by right-clicking a view definition in the OBLE
26
Right-click and select Edit Web Layout
19 of 24
26.20
Web Layout Editor Continued

Displays the current layout of the view Applet window shows the applets available for display within the view
` Constrained by the views business object property
1. Drag applet from Applet window
2. Drop onto applet placeholder
20 of 24
26.21
View Web Template Items
Are applets that have been bound to a view

` Item identifier specifies where they are to appear
Used in the markup language tag that specifies corresponding control in a template
26
Binds a control to specific position on Web page

26.22
Register and Assign View
Views must be administered in the client to make them available to users

` Navigate to Administration - Application > Views in the client application to register the view
Copy and paste the view name from the object definition in Tools to the view record
` Navigate to Administration - Application > Responsibilities to assign the view to one or more responsibilities
Assign the view to developers for unit testing and to users for system testing and production
3. Clear the cache
1. Register the view
2. Assign the view

22 of 24
26.23
Module Highlights
Applications are groups of screens through which users navigate Screens are containers for views
` Screen views come in four types: aggregate view, aggregate category, detail category, and detail view
Views:
` Consist of one or more applets ` Reference a BO that defines the relationships between data in the view ` Are associated with a Web template that defines their layout
26
23 of 24
26.24
Lab

` Create a view ` Add the view to a screen using a specified view navigation mechanism ` Administer the new view
24 of 24
UI Layer Configuration: Drilldowns
27.1
Module 27: UI Layer Configuration: Drilldowns
27
27
27.2
Module Objectives

` Configure drilldown to a related view ` Enable the thread bar

` Enables you to add drilldowns to assist users with navigation ` Enables you to activate the thread bar to assist users
2 of 16
27.3
Navigation Using Drilldown
You can configure list columns or controls for drilldown

` When the user clicks the hyperlinked value, the application navigates to another view
You can configure drilldown as static or dynamic

` Static: Clicking the hyperlink always navigates to the same target view ` Dynamic: Clicking the hyperlink navigates to a target view determined by values shown in the current view
3 of 16
Reference
Configuring Siebel Business Applications: Configuring Screens and Views Configuring Siebel Business Applications: Configuring Applications
27
27.4
Static Drilldown: Same Business Component
Drill down to another view, keeping the business component (BC) context
Same contact record in Contact Detail view
4 of 16
Contact record in Visible Contacts list view
27.5
Configuring Drilldown Within Same Business Component
Create a new drilldown object

` Set the Hyperlink Field and View properties to enable static drilldown ` Drilldown object is child of an applet object
Specifies the BC field to be highlighted for drilldown

Specifies the target view

5 of 16
27
27.6
Static Drilldown: Different Business Component
Drill down to another view, changing the business component context

The account field of the contact record in the Contacts list view
Related account record in the Account Detail - Contacts view
6 of 16
27.7
Configuring Drilldown to Different Business Component
Create a new drilldown object for the applet

` Set Hyperlink field and View properties as before ` Set Business Component, Source Field, and Destination Field properties to enable drilldown to a view based on a different parent record
BC in target view
Foreign Key field in record pointing to target BC

Primary Key field in target BC (default is ROW_ID)

7 of 16
Reference
Configuring Siebel Business Applications: Configuring Screens and Views: About Drilldowns Siebel Security Guide: Configuring Drilldown Visibility
27
27.8
Dynamic Drilldown
Enables drilldown to multiple views from the same hyperlink field, depending on value of a field in the active record of the list
For business contacts, go to the Contact Detail view
For personal contacts, go to the Personal Contact List view

Note
The single value field that controls which view the dynamic drilldown navigates the user to is configured when the business component is created. In the example here, the business component is Contact and the single valued field is Personal Contact. For Adams, Personal Contact = Y (yes), while for Abboline Personal Contact = N (no).
27.9
Matching Conditions
Identify one or more matching conditions to trigger drilling down to a specific target view
` For example:
Personal Contact? N Contact Detail View Y Personal Contact Detail View
Determine the order to check the matching conditions

` Conditions can involve different fields ` Multiple matches could occur for a given record
9 of 16
27
27.10
Configuring Dynamic Drilldown

Create the drilldown objects for each view

` Multiple drilldown objects with same hyperlink but different views
Set sequence number to determine where to look for dynamic drilldown destinations
` The drilldown object with the lowest sequence number is checked for dynamic drilldown destination child object definitions
The Original and Personal drilldown objects have the same Hyperlink field but different views
10 of 16
The Original drilldown object has the lower sequence number, so it is checked for dynamic drilldown destinations
27.11
Configuring Dynamic Drilldown Continued
Create a dynamic drilldown destination definition for each condition

` Each condition specifies a destination drilldown object to use ` Recommended practice: Create a default dynamic drilldown destination to specify a desired view if there are no matches
If no default is configured, navigates to the view specified by the parent drilldown object
Contact Detail view is default
Separate definition for each destination

Field to check
Value to check for
Destination
Order in which to check

11 of 16
27
27.12
Thread Bar
Tracks previous business object (view) and active record Updates whenever the user navigates to a different business object Provides hyperlinks to previous views
` Allows user to backtrack easily

Hyperlink to prior active record in the thread
12 of 16
Note
The thread bar allows the user to navigate to a specific view or record previously visited, by selecting the item of interest in the thread bar. Drilldowns implement the users business logic; they are always parts of business processes. When a part of a business process is completed, the user will usually return to an earlier view or record, and the thread bar facilitates this navigation.
27.13
Thread Properties
Specifies the text that appears in the thread bar
Thread title
Thread field
Thread Title property specifies prior business object in hyperlink; if not entered, application uses Title property
Specifies the record to remember in the hyperlink
27
27.14
Module Highlights
List columns or controls can be configured for drilldown Drilldowns can be static or dynamic
` Static drilldowns always navigate the user to the same target view ` Dynamic drilldowns navigate the user to a target view determined by the values shown in the current view ` Static drilldowns can be configured to drill down to the same business component or to a different business component ` Configured in Tools
14 of 16
Thread bar allows user to easily backtrack
27.15
Lab

` Create and configure dynamic drilldowns ` Enable and configure thread support
15 of 16
27
27.16
Business Layer Configuration: Joins
28.1
Module 28: Business Layer Configuration: Joins
28
28
28.2
Module Objectives

` Create a join that brings data from a standard table into a standard business component ` Create a join that brings data from a party table into a standard business component ` Create a join that brings data from a party table into another party business component

` Enables you to configure your companys business logic
2 of 24
Reference
Configuring Siebel Business Applications: Configuring Joins
28.3
Joined Tables Review
Business components can include data from related joined tables

` Brings in data as needed to meet the business components data requirements

For display in applets For use in processing by the business component

Opportunity
Name Description Sales Stage
S_OPTY Base table DESC_TEXT

CURCY_CD ROW_ID NAME
S_STG Joined table

28
3 of 24
28.4
Three Definitions Are Used to Implement a Join Review

Join definition specifies the joined table Join specification specifies the FK and PK used to relate the base and joined tables Single-value field (SVF) references the join object definition
1. Join definition
2. Join specification
3. Singlevalue field
28.5
Join Example
Will bring Sales Stage data from S_STG into the Opportunity BC
` S_OPTY is the base table, S_STG is the joined table
From S_OPTY
From S_STG
28
5 of 24

0/6
28.6
Building a Join
1. Locate the Data Source 2. Examine Existing Joins 3. Diagram the Join 4. Create the Join Definition 5. Create the Join Specification 6. Map the Single Value Field(s)
6 of 24

1/6
28.7
1. Locate the Data Source
Identify potential data sources

` Peruse application for data that you seek
The required data could exist in another business component
` Trace down from the UI element to the table column
For assistance, use the job aid from the Business Component lab
Identify table and column that contains data you seek
28
7 of 24
Once you find the data in the UI, identify the specific table and column where the data resides

2/6
28.8
2. Examine Existing Joins
Determine if a join already exists

` Peruse existing joins for joins that might be candidates ` Oracle has already provided many commonly-used joins
If a join exists that meets data display requirements, use it Otherwise, create a new join
Examine alias for candidates
8 of 24

3/6
28.9
3. Diagram the Join

The Join Diagram template simplifies join creation

` Gather information first, then create the join
Indicate each of the numbered items

Join Diagram Worksheet
Business Component: Opportunity Single Value Field: Sales Stage Id 2. Base table 1. Business component
S_OPTY ROW_ID Base Table CURR_STG_ID ROW_ID NAME
S_STG
3. Joined table 4. Joined table column 6. Primary key column
28
5. Foreign key column
FK
PK
Joined Table
9 of 24
Procedure Quick Start
1. Enter business component name. 2. Enter base table name: value of Table property for BC. 3. Enter joined table name. 4. Enter joined table column name that contains data to be brought into this BC. 5. Enter foreign key column name. Select Table :: [base table] | Column. Query Foreign Key Table property for [joined table name]. For example, Table :: S_OPTY | Column. Foreign Key Table = S_STG. 6. Enter primary key column name. Select Table :: [joined table] | Column. Query Primary Key property for TRUE. For example, Table :: S_STG | Column. Primary Key = TRUE. 7. Enter SVF name. Select [business component] :: Single Value Field. Query Column property for [FK column]. For example, Opportunity :: Single Value Field. Column = CURR_STG_ID.
7. Single-value field

4/6
28.10
4. Create the Join Definition

Table property specifies joined table Alias property is the name of join definition
` Alias always defaults to the joined tables name
Displayed in ALL CAPS
` Additional aliases for self-joins or multiple joins to the same table are specified by the developer
Recommended practice is to use Initial Caps
Name of join
Default alias value: joined table name
Joined table

5/6
28.11
5. Create the Join Specification

Specify foreign key field of the base business component in the Source Field property Specify primary key column of the joined table in the Destination Column property
Base Table S_OPTY ROW_ID FK CURR_STG_ID ROW_ID NAME

11 of 24
Joined Table S_STG
28
PK

6/6
28.12
6. Map the Single Value Field(s)
Specify business component field name, the joined table, and column name of the joined table
` SVF specifies the data you seek ` The join determines how you access that data
Base Table S_OPTY ROW_ID CURR_STG_ID FK NAME ROW_ID PK Data you need Joined Table S_STG
How to get the data
BC SVF field name
Sales Stage join references S_STG joined table
Sales Stage SVF references NAME column in joined table

12 of 24
28.13
Outer Join Flag

An option in the join definition Set Outer Join Flag to TRUE to return all records from the base table, even when there is no related row in the joined table Outer joins will affect performance
` Do not enable outer join if there is always a related row in the joined table
Outer join enabled
28
13 of 24
28.14
Outer Join Flag Continued
When Outer Join Flag is TRUE (checked), a left outer join is used
` All records in source table are displayed
Even if there is no related record in the target table
` Records with no related record in target table display target values as null
S_OPTY ROW_ID 001 002 003 NAME 200 PCS CS Laptop units 200 PCS Puma Laptop EB 200 PCS Puma Laptop EB DESC_TEXT AT&T Imperial Tobacco Broadband e2e CURR_ STG_ID 105 106 NULL ROW_ID 101 102 103 104 105 106 NAME 03 - Closing 05 Won 07 - Selected 06 Short List 01 - Prospecting 02 - Qualification S_STG 9/7/2001 9/18/2001 2/20/2004 9/18/2001 9/18/2001 9/7/2001
FK
All records displayed from source
PK
No corresponding record for Broadband e2e
14 of 24
PHASE_CD

0/3
28.15
Joins and Party Business Data
Joins and Party Business Components Bringing Party Data into a Standard Business Component Bringing Party Data into a Party Business Component
28
15 of 24

1/3
28.16
Joins and Party Business Components Review

Party Business Components have S_PARTY as the base table, but store main data in S_PARTY extension tables An implicit join is used to reference fields from extension tables
` Used when relationship between tables is known ` Appears in Join property on SFV ` Does not appear as Join object definition
Contact
First Name Last Name Birth Date
Main columns use implicit join to S_CONTACT
S_PARTY
ROW_ID NAME PK PARTY_TYPE_CD PARTY_UID
S_CONTACT
BIRTH_DT ROW_ID FST_NAME LAFST_NAME PAR_ROW_ID
FK
Base Table
Extension Table
16 of 24
S_PARTY Extension The following tables are some of the extension tables for S_PARTY: Tables S_BU S_CONTACT S_ORG_EXT S_POSTN S_USER

2/3
28.17
Bringing Party Data into a Standard Business Component
Example: Bringing account data into the Opportunity business component for display in an Opportunity applet
Opportunity
Name Description Account
28
Standard business component
Data from an S_PARTY extension table
17 of 24

2/3
28.18
Three Definitions Bring Party Data into a Standard BC

The Join definition specifies which S_PARTY extension table to use The Join specification specifies to use PAR_ROW_ID The SVF is the desired column from the joined extension table
1. Join definition
2. Join specification
3. Singlevalue field
18 of 24
PAR_ROW_ID
PAR_ROW_ID is referenced in the join specification and identifies the primary key of the related account record.

2/3
28.19
Join Specification with Party: Similar to Standard But

Destination references PAR_ROW_ID, not ROW_ID Keys reference base to extension to join, rather than base to join Typically references
Standard
Typically references ROW_ID
Party
PAR_ROW_ID
S_OPTY ROW_ID CURR_STG_ID FK ROW_ID PK
S_STG NAME
S_OPTY ROW_ID PR_DEPT_OU_ID FK 001
S_ORG_EXT ROW_ID NAME Data resides in _EXT PK
S_PARTY ROW_ID
28
FK
FK 001
PK 001
Oppty Base Table
Joined Table
Oppty Base Table
Joined / Extension Table
Party Base Table

19 of 24
PAR_ROW_ID
PAR_ROW_ID is referenced in the join specification and identifies the primary key of the related account record.
PAR_ROW_ID

3/3
28.20
Bringing Party Data into a Party Business Component
Example: Bringing parent account data into the Account BC for display in an Account applet
` A join in a BC that refers back to data in that same BC
Account
Name Location Parent Account Name Parent Account Location
20 of 24
This Account references top account

3/3
28.21
Join Definition, Bringing Party Data into a Party BC
Must use an explicit join to an extension table based on the appropriate foreign keys
` The alias must be different from those used by implicit joins in this BC
Must not use an existing implicit join to that extension table
Since an implicit join to S_ORG_EXT already exists. . .
. . .an explicit join must be used, and it must have an alias
28
21 of 24
Implicit Joins
Remember that there is an implicit join available for each extension table for a base table. S_PARTY has many extension tables, including S_ORG_EXT, S_CONTACT, S_POSTN, and S_USER. These implicit joins are used in other party business components to map their main data.

3/3
28.22
Map Field to Column in Party Table

Select the appropriate explicit join

` Do not use an implicit join to the table
Select the desired column in the joined table Set the appropriate type (DTYPE_TEXT, etc.)
Select the explicit join instead of S_ORG_EXT
22 of 24
28.23
Module Highlights
BCs can include data from related joined tables Join definitions and join specifications define how to access joined table data Single-value fields reference the join definition and define the field to access in the joined table To create a join:
Joins that involve party data are similar to standard data; however, when bringing party data into:

A non-party BC, create a join specification based on PAR_ROW_ID A party BC, use the appropriate explicit join
28
23 of 24
` Locate the data source, examine existing joins, diagram the join, create the join definition, create the join specification, and define the SVF
28.24
Lab

` Examine references when a join is not present as well as when a join is present ` Create a join that brings in data from joined table and display it in the UI
24 of 24
Business Layer Configuration: Existing Business Components and Fields 29.1
29
Module 29: Business Layer Configuration: Existing Business Components and Fields
29
Module Objectives

` ` ` ` Edit business component properties to capture business logic Describe business component view modes Edit field properties to capture business logic Specify business component and field user properties
2 of 30
` Editing the properties of business components and fields helps you to more accurately and fully capture your business logic
Business Component Properties

Capture business logic Include:
` Properties for editing

No Delete No Insert No Merge No Update
29
Reference
Configuring Siebel Business Applications: Configuring Business Components
` Owner Delete ` Search Specification ` Sort Specification
Business Layer Configuration: Existing Business Components and Fields

0/4
29.4
Business Component Properties
Properties for Editing Owner Delete Property Search Specification Property Sort Specification Property
4 of 30

1/4
29.5
Properties for Editing

Set editing properties at the business component level to prevent deleting, inserting, merging, and updating records in all applets Example: To maintain record continuity, users cannot delete or change price lists once they have been created
29
No Delete No Insert No Merge No Update
If TRUE, once a record is created and committed, users cannot delete it. If TRUE, users cannot add new records. If TRUE, users cannot merge records. If TRUE, users cannot change existing records.

1/4
29.6
Properties for Editing Continued
These properties also appear on applets

` Most restrictive settings are always used ` Set these properties to FALSE at the business component level so you can make exceptions at the applet level Business Component Applet
Affects all applets referencing this BC, or. . .
. . .can be customized for each applet
6 of 30

2/4
29.7
Owner Delete Property
Set the Owner Delete property to TRUE to enable only the owner of a record to delete it
` The primary on a team-based business component is the owner of the record
JRUBIN is primary owner; only JRUBIN can delete
29

3/4
29.8
Search Specification Property
Specifies records to be retrieved by the business component

` Typically used when there are multiple business components based on the same table
BC field
Conditional statement
8 of 30

3/4
29.9
Search Specification Expression

Consists of field names, constants, functions, logical operators, and comparison operators Example: For a given user, Contact(All) retrieves:
` All contacts where the Personal Contact flag is N ` All personal contacts belonging to the user
. . .must match exactly
Logical operator
Function
29
Field name in [ ]. . .
Operator

3/4
29.10
Search Specification Considerations
Appear on business component properties and applet properties

` Search specifications are part of the WHERE clause for all applets that display this business component
Predefined queries may also contribute to the WHERE clause
` Search specifications on the applet are combined with search specifications on the business component with an AND in the resulting SQL statement ` Avoid competing search specifications that preclude record display
UI Layer
Applet
View
Screen
Application
Business Layer
Field
Business
Component
Business Object
10 of 30
Reference
Object Types Reference
Avoid mutually exclusive search specifications

4/4
29.11
Sort Specification Property
Determines the sort order of the retrieved records

` Use (DESC) or (DESCENDING) to sort that field in reverse order ` Cannot be set at the applet level
To sort by last name, then first name. . . . . .configure a sort specification
Must match exactly
Ensure that an index exists to support the sort specification

29
BusComp View Mode
Specifies that the BC is subject to Access Control

` Owner Type property identifies the Access Control mechanism that limits records a user can access
BCs may have multiple access mechanisms

` Allows records to be associated with different owner types ` Supports multiple view modes
Identifies the Access Control mechanism
BC field used to specify visibility
12 of 30
Reference
Object Types Reference Security Guide for eBusiness Applications
BusComp View Mode, Example
The Opportunity business component has a position-based BusComp View mode

` Invoked when user navigates to the My Opportunities or My Teams Opportunities view
Visibility MVField property is set to Sales Rep, so application reads list of positions from Sales Rep MVF to determine record visibility
Person- or position-based BusComp View modes are invoked by My views
For each record, the application compares the users current position to positions in Sales Rep MVF
29
13 of 30
` The My Opportunities view shows records with the users current position listed in the Sales Rep MVF ` The My Teams Opportunities view shows records where users direct or indirect reports are primaries on the Sales Rep MVF
Field Properties
Customize fields by editing property values Setting field properties at the business component level sets them across all applets that reference the business component
` Each applet references one, and only one, business component
Properties set at the business component level affect all applets that reference the business component
14 of 30
Reference
Object Types References

0/4
29.15
Business Component Field Properties
Required and Read Only Validation Default Values Calculated Fields
29

1/4
29.16
Required and Read Only Properties

Setting Required to TRUE prevents user from leaving field blank Setting Read Only to TRUE prevents user from editing the value
2. Required field marked with asterisk 1. Contacts require last names
3. Attempting to save without last name causes error message

Note
To display custom error messages, you must use Data Validation Manager.

2/4
29.17
Validation Property
Checks the rule when a record is saved to ensure that the field data is valid Message is customizable Can refer only to business component fields in the same record
Birth date must be prior to the current date
Text displayed when validation fails
Specify existing string in SRF. . .
. . .or enter a custom message
Option to include system error message
29
17 of 30
Reference
Object Types Reference Siebel Developers Reference

2/4
29.18
Validation Property Continued
Rules are expressed as a combination of logical operators, constants, field names, and predefined functions
Constant Field name
Operator
Logical operator
18 of 30

3/4
29.19
Default Values for Fields

Pre Default Value

` Automatically assigns a value to a field for a new record
Post Default Value

` Assigns a value to a field, if not entered by the user, before the record is inserted into the database
Example: If the user does not designate a contact as personal, the system assumes it is not personal, and sets it to N
29

4/4
29.20
Calculated Fields
Derive their value from values in other fields in the same record of the business component in which the calculated field resides Cannot be stored in the database; therefore, there is no associated column To enable, set Calculated property to TRUE (checked)
Column property is empty because calculated fields are not stored in the database
20 of 30

4/4
29.21
Restrictions on Calculated Fields

Calculated fields are read-only System does not validate values of calculated fields Sorting on calculated fields is not supported Querying on calculated fields is supported
` Performance depends upon whether functions in the query expression can be incorporated into the SQL statement
29

4/4
29.22
Calculated Value Property
Is an expression built from:

` Field names in the same business component ` Field names from the parent business component
Current BC must have the child in a detail view
` Standard functions ` String, numeric, and logical operators
System functions
22 of 30
Reference
Object Types Reference Siebel Developers Reference
User Properties
Are object definitions added as children to an applet, business component, control, field, or list column Used to configure specialized behavior beyond what is configured in the parent object definition's properties Each user property contains its own conditional logic
` Can implement specific, custom IF/THEN logic ` Many use their own unique syntax
Can be used as a declarative alternative to scripting A wide variety of user properties exist, such as:
` BC Read Only Field, Field Read Only Field, and On Field Update Set
29
User Properties
There are a large number of user properties, each with its own specialized behavior. For additional information, refer to Siebel Developers Reference.
BC User Property Scenario
Business challenge
` Based on values the end user enters at run time, dynamically disallow updates to record
Business solution
` Use the BC Read Only Field user property
Allows you to specify a field on the business component that determines whether individual records are read-only
Order has shipped, and it is too late to add more line items to the order
BC Read Only Flag N Order Entry - Line Items Target BC Writable
24 of 30
Field that flags whether record is read-only
Order Entry - Line Items
Read-only
` Example: Shipped orders cannot accept changes to order entry line item records in an existing order
User Property, BC Read Only Field Example
Create a calculated field on the Order Entry Line Items business component whose value is either Y or N
` BC Read Only Field user property requires an input value of Y or N, so create a calculated field whose values are limited to those two values
For this example, create a calculated field named BC Read Only Flag with the expression: IF([Status] = "Shipped", "Y", "N")
BC Read Only Flag SVF has a value of Y if the status of the item is shipped, N otherwise
29
` This sets the value of the calculated field to Y if the status is shipped, N otherwise
User Property, BC Read Only Field Example Continued
Add the BC Read Only Field user property

` Set the Value property to BC Read Only Flag
Value is the name of the calculated field on the BC
` When the value of this field is Y, the current record is read-only
Create User Property which references the calculated field
26 of 30
User Property, Field Read Only Field
Sets a specific field in a business component to be read-only

` Field Read Only Field: Location sets Location field as the target of a conditional statement ` Value is the name of a field that contains a Boolean value
At run-time, if condition is met, field is set to read only
This condition affects. . . . . .this target field. . . . . .depending on the Boolean value in this field
S_ORG_EXT ROW_ID 1 INT_ORG_FLG Y
INT_ORG_FLG N Location is not read only
Location is ready only
29
27 of 30
Adding a User Property
Is done via a picklist in the Name property in the Business Component User Properties window
` Only those user properties allowed for parent BC are displayed
Displays user properties allowed for this BC
28 of 30
Module Highlights
BC properties are set to control behavior:

` Editing properties, Owner Delete, Search Specification, and Sort Specification
BC field properties are set to control behavior:

` Required, Read Only, Validation, Pre and Post Default, and Force Case
` Declarative alternative to scripting
29
BusComp View Mode specifies BC is subject to access control Calculated fields derive their value from other fields in the same record of the BC in which the calculated field resides User Properties have their own specialized logic that can be added to a BC
Lab

` Incorporate business logic into the application by configuring properties of business components and fields
30 of 30
Business Layer Configuration: New Business Components and Fields 30.1
30
Module 30: Business Layer Configuration: New Business Components and Fields
30
Module Objectives

` Create a new business component (BC) ` Add a business component to a business object

` Enables you to incorporate additional business entities that do not correspond to business components in a standard Siebel application ` Enables you to tailor your business logic
2 of 22
Business Challenge
Siebel-provided business components capture most commonlyused business entities, but they do not cover every possibility Example: Sales organizations might record personal data about contacts, such as:
` What colleges the contact attended
Name of college, years attended, major field of study, sports played, honors received, and so on Name and location, price range, type of cuisine, and so on
To capture this kind of information may require:

` Multiple fields to capture the details ` 1:M or M:M relationship to the parent
3 of 22
30
Reference
Configuring Siebel Business Applications: Configuring Business Components
` The contacts favorite restaurants
Business Solution: Create New Business Components
To capture this sort of information, create new business components

` For example, create college and restaurant child BCs of the Contact parent BC
` ` ` `
Standard Extension 1:M M:M
4 of 22
Used to add entities specific to your organization that are not in the Siebel repository You can base these business components on tables supplied by Oracle
Scenario: 1:M Relationship With Existing Table

Example: Create Colleges Attended and Favorite Restaurants business components for sales organization Colleges Attended and Favorite Restaurants have a 1:M relationship with Contact
` Requires two business components, Colleges Attended and Favorite Restaurants

When creating a BC with a 1:M relationship with the parent business component, consider using a 1:M extension table
Colleges Attended
Contact
Favorite Restaurants
5 of 22
30
One for Contact : Colleges Attended One for Contact : Favorite Restaurants
Review: Standard 1:M Extension Tables

Predefined in the repository for many business components Have name of parent table appended with _XM
Contains many predefined ATTRIB columns of varying type
PAR_ROW_ID column stores foreign key to ROW_ID in main table TYPE column identifies the child business component
NAME column stores the name of the child entity
User Key
TYPE, PAR_ROW_ID, and NAME serve as a user key for the table
` These three columns are required
Must provide values for all three columns when creating a new record
` Combined value of the three columns must be unique
S_CONTACT_XM
PAR_ROW_ID ROW_ID TYPE NAME
User Key
7 of 22
30
Ensuring that NAME For BCs with data that cannot be stored in a Varchar 100 column, you must Is Unique still provide a unique value for NAME NAME has physical type varchar 100 If two rows in table share same TYPE & PAR_ROW_ID, then NAME must be unique Workaround is to store value of ROW_ID in NAME
Business Component Wizard
Use the Business Component Wizard to create a new business component

` Select File > New Object, select BusComp, and then click OK
Wizard
8 of 22
Business Component Wizard Inputs
The Business Component Wizard requires the following inputs:

` Project new business component will be part of ` Business component name
Must be unique among all business components in all projects
` The business components table name ` Fields that will be part of this BC
` ` ` `

Specify TYPE column and relate it to Type field Specify PAR_ROW_ID column and relate it to Id field Specify NAME column and relate it to Name field Use ATTRIB_ columns for additional data
Establishes User Key
Columns are limited to the table you select in wizard Use a separate column for each field
9 of 22
30
Selected in the wizard by specifying Table Column, then entering a field name
Business Component Wizard Outputs
The Business Component Wizard:

` Creates a business component object and its child object definitions ` Creates fields and relates them to table columns
Aside from what you specify in the wizard, uses default field and table values; for example, Owner Delete is set to FALSE
Creates new fields and relates them to columns
Creates the business component object definition
10 of 22
Set the Pre-Default Value
Automatically assigns a value to a field for a new record

` For extension tables, set Predefault Value property of the Type field to the value used in the BC search specification ` Can be used to ensure that the user key is populated
Matches the value in the Search Specification
Ensures that all new records have a type of Restaurant
11 of 22
30
Set Search Specification
Manually set the search specification to match the unique TYPE value for the business component
` Specifies the records to be retrieved by the business component
Typically used with extension tables

` Supports the case where multiple BCs are based on the same extension table
Search retrieves only records with a Type of Restaurant
12 of 22
Multiple Business Components

You can use one table to map multiple user-defined child business components Each BC has a unique TYPE value
` Stored in the TYPE column of the table
Each BC retrieves only those rows with its TYPE value Specify properties on business components and fields
Colleges Attended
Type = College
S_CONTACT_XM
ROW_ID PAR_ROW_ID NAME TYPE
Type = Restaurant
13 of 22
30
` Search Specification ` Pre Default Value
Business Layer Configuration: New Business Components and Fields

0/3
30.14
Post-Creation Tasks
1. Relate Child and Parent BCs 2. Reference Business Component in Business Object 3. Enable Display Data in UI
14 of 22

1/3
30.15
Relate Child and Parent BCs
For each child/parent relationship, associate the newly configured child business component to the parent:
` Create a link definition to relate child and parent records
Parent
Contact
Contact/Favorite Restaurants Link Contact/Colleges Attended Link
Child
Colleges Attended
Child
15 of 22
30

1/3
30.16
Relate Child and Parent BCs Continued
Create a separate link for each child/parent relationship

` In our scenario, Contact/Favorite Restaurants and Contact/Colleges Attended
Child is Restaurant
Parent is Contact
16 of 22
Link creation is same as with any standard BC This will be the link you specify in the business object

2/3
30.17
Reference Business Component in Business Object
Create a Business Object Component definition for each new business component
` The business object defined for the parent is the one to use ` The business component is the child you just created ` Set the Link property
Parent BC
Child BC
Link you just created

17 of 22
30
New Parent BCs and If you create a parent business component you must also create an entirely Business Objects new business object.

3/3
30.18
Enable Display Data in UI
Build applets and views as required to display data from the business component
` To prevent users from changing the value, do not display the Type field
List Applet Wizard
18 of 22
Creating a Standalone Business Component
May be necessary when your company's business logic requires a new table be added to the database
` In most cases, Siebel's extensive database should meet most of your needs. There could be exceptions.
To create a standalone BC:

` ` ` ` ` ` Create a new table to hold BC data Add appropriate columns to this table Create a new BC and add BC fields Create a new Business Object and reference the BC in this BO Enable data display in the UI Standalone BCs are based on standalone tables and have no relationships to other BCs or tables
19 of 22
30
Creating a Table
The new steps of creating a table and adding columns is covered in a later module.
Module Highlights
Create a new BC as child of an existing BC to capture new information When possible, use predefined _XM tables to store data Use the BC Wizard to create a new BC When using extension tables, use one extension table to map to multiple child BCs
Include required fields, such as Type and NAME
Create a link definition to associate new child BCs with parent Add new BC to a BO, then create applets and views to display data Create a standalone BC, when necessary
20 of 22
` Each BC has a unique TYPE value ` Specify properties on BC and fields
Lab

` Create and display a new business component based on a 1:M extension table
21 of 22
30
Business Layer Configuration: Picklists
31.1
Module 31: Business Layer Configuration: Picklists
31
31
31.2
Module Objectives

` Describe the differences between dynamic and static picklists ` Administer a list of values ` Configure a static or dynamic picklist

` Enables you to add picklists to your Siebel application
2 of 22
31.3
Picklists
Allow users to populate one or more single-value fields by selecting a value from a list
` Enforces business rules and policies ` Makes data entry faster ` Reduces errors
Can be either static or dynamic
3 of 22
References
Configuring Siebel Business Applications: Configuring Picklists and Pick Applets Configuring Siebel Business Applications: Creating and Administering Lists of Values
31
31.4
Static Picklist
Displays values in a drop-down list for user selection Copies the selected value into destination field
` No link to the original picklist data
Can be bounded or unbounded

` Bounded picklist forces users to enter only a value in the picklist ` Unbounded picklist permits users to enter any value into the field
Draws values from picklist data managed by an administrator

` Values displayed in static picklists do not change during run time
Drop-down list
UI visual cue for static picklist
4 of 22
31.5
Static Picklist Values

Are stored for all static picklists in the S_LST_OF_VAL table Appear in List of Values or LOV Explorer administrative views
` Administration Data > List of Values (or LOV Explorer)
Each have a type, which indicates which static picklist the value belongs to
Values for the MR_MS static picklist
5 of 22
31
31.6
Administering a Static Picklist
Use Administration Data > List of Values Explorer view
Select an existing picklist or create a new picklist type in the List of Values - Types applet Expand the type and select the child Values folder Edit the picklist values in the List of Values (LOV) applet
6 of 22
31.7
Dynamic Picklist
Displays values in a pick applet Draws values from a business component (BC) with records edited by users
` Values are dynamic and depend on current BC records
Is used to update joined fields

` Copies foreign key reference to the selected value into destination field
UI visual cue for dynamic picklist Pick applet displayed when select icon clicked
7 of 22
31
31.8
Picklist Terms
Siebel picklists:
` Are associated with a field in the originating business component ` Draw values from a pick business component
Opportunity: originating business component
Account: pick business component

31.9
Create a New Picklist
Use the Pick List Wizard to create a new static or dynamic picklist
` Select File > New Object > Pick List
9 of 22
31
31.10
Wizard Inputs for a Static Picklist
The Pick List Wizard requires the following inputs:

` Project the created picklist object will be part of ` Business component and field populated by the picklist ` Picklist name and type (Static)
Picklist type is static
10 of 22
Business component and field populated by the picklist
31.11
Wizard Inputs for a Static Picklist Continued
The Pick List Wizard requires the following inputs (continued):

` Bounded or unbounded picklist ` Type value (example: MR_MS) ` Pick list values
May use existing type and/or values in S_LST_OF_VAL

Enter values for static picklist
11 of 22
31
31.12
Pick List Wizard Outputs for a Static Picklist
The Pick List Wizard creates:

` A picklist object ` A pick map that specifies values copied to the S_LST_OF_VAL table ` Values in S_LST_OF_VAL for the picklist ` Activated drop-down list column or control in applets containing the originating field
Picklist Pick map for originating field
Drop-down control
PickList Generic
Static picklists all share a common pick business component, PickList Generic. This very simple, Siebel-provided business component provides a connection between the originating business component and field and the values that appear in S_LST_OF_VAL. PickList Generic contains fields corresponding to each of this tables columns, such as Type and Value. Notice in the middle picture above that the pick map is mapping the originating field M/M to the PickList Generic field Value, which links the MR_MS entries in S_LST_OF_VAL with the M/M field of Contact.
31.13
Activating a Drop-Down List Column or Control
The Pick List Wizard may activate drop-down control for picklist field
` The wizard displays all applets displaying the originating field ` Only the applets locked by developer will be activated
Wizard sets list column or control Runtime property to TRUE

` A drop-down arrow appears as a cue
Runtime set to TRUE
13 of 22
31
31.14
Wizard Inputs for Dynamic Picklists
The Pick List Wizard requires the following inputs:

` Project the created picklist object will be part of ` Originating business component and field for the picklist ` Picklist name and type (Dynamic)
Set type to Dynamic
14 of 22
Originating business component and field
31.15
Wizard Inputs for Dynamic Picklists Continued

` ` ` ` A pick business component A field in the pick business component to sort on A picklist name A search specification
Pick business component
Business component field to sort on
15 of 22
31
31.16
Wizard Inputs for Dynamic Picklists Continued

` Pick applet properties (No Delete, No Insert, No Update, No Merge) ` Values for a pick map, mapping fields between originating and pick business components
Define a pick map
16 of 22
31.17
Pick List Wizard Outputs for a Dynamic Picklist
The Pick List Wizard creates:

` ` ` ` A picklist object A pick map constructed in the wizard A new pick applet, if needed Activated list column or control in applets containing the originating field
Picklist
Pick map for originating field Field with select icon

31
List column or control for originating field must have Runtime property set to TRUE
31.18
Constrained Picklist
Filters values dynamically based on value in parent picklist

Parent picklist Constrained child picklist
Values available when Area is Network
Values available when Area is Printer
18 of 22
31.19
Constraining a Picklist
Create a pick map definition for each field that must match Set the Constrain property to TRUE for each of the matching fields
` Filters the pick business component records for matches ` Does not copy values for the field
Constrained to return only SubAreas whose Parent is equal to the Current Area
19 of 22
31
31.20
Module Highlights
Picklists allow selection of values from a list for one or more single-value fields in an originating business component Static picklists:
` Display values in a drop-down list ` Contain static values, which are managed through List of Values administrative views ` Store values in S_LST_OF_VAL table ` Display values in a pick applet ` Contain dynamic data, which is typically the result of user transactions ` Access data in pick business component using a foreign key
Picklists are created using Siebel Tools Pick List Wizard
20 of 22
Dynamic picklists:
31.21
Lab

` Create a new static picklist ` Create a new dynamic picklist
21 of 22
31
31.22
Configuring Multi-Value Groups
32.1
Module 32: Configuring Multi-Value Groups
32
32
32.2
Module Objectives

` Describe multi-value groups and their benefits ` Use Siebel Tools to configure a multi-value group

` Enables you to incorporate child data directly in an applet

2 of 22
More child data can be available within a view More effective use of screen space
32.3
Multi-Value Group
A multi-value group (MVG) is a set of detail (child) records associated with a parent record
` The Parent applet displays only one of the child records ` The MVG applet opens on demand to display all child records
MVG applet
3 of 22
Reference
Configuring Siebel Business Applications: Configuring Multi-Value Group and Association Applets
32
32.4
Multi-Value Group Continued
Is an alternative to a detail view for managing parent and related child records
` Makes effective use of space
Does not require dedicated space on a view
` Allows for multiple sets of detail records to be available from a single view
Business Address MVG
Account Team MVG
Industries MVG
4 of 22
Territory MVG
32.5
Allows users to access child records for multiple parent records in a single list view
Business Address MVG Territory MVG Industries MVG
5 of 22
32
32.6
Allows for creating queries that include values for fields in both parent and child records
Query on Organization
Query on Territory
6 of 22
Query on Industries
32.7
Primaries
Primary key allows fast retrieval of the primary child record for display in the parent applet
` A primary refers to a designated child record ` Designating a primary allows one child record to be retrieved quickly for display
Supported by a primary foreign key field in the parent business component to reference the childs primary key (ROW_ID)
S_ORG_EXT
ROW_ID NAME PR_ADDR_ID LOC
Parent BC
S_ADDR_ORG
ADDR CITY ROW_ID OU_ID
Child BC
Primary foreign key
Foreign key
7 of 22
32
` Siebel Data Model includes many primary foreign keys
32.8
Primaries Performance Example
Three MVGs on a list applet displaying 10 parent records requires 31 queries to populate without primaries
` One query to populate parent fields in list applet ` 30 queries (three per parent record) to populate the MVGs
Multi-value groups
8 of 22
32.9
Primaries Performance Example Continued
Using primaries, one query will populate all the fields on the list applet
` A query using SQL joins populates each MVG with its primary child record
Multi-value groups
9 of 22
32

0/3
32.10
Object Types Supporting MVGs
MVGs are implemented in Siebel applications using the following object types: Link Multi-Value Field (MVF) MVG Applet
10 of 22

1/3
32.11
Link
Must exist between parent and child business components in the MVG
` Specifies how to get data from child business component
Parent business component
Account
Name Location City
Child business component Business Address

City Street Address
11 of 22
32

2/3
32.12
Multi-Value Field (MVF)

Is a field in the parent business component that references a field in the child business component Is required for an MVG
Single-value field Multi-value field Parent business component Child business component
Account
S_ORG_EXT
ROW_ID NAME EMP_COUNT LOC
Business Address
City Street Address
S_ADDR_ORG
ADDR ROW_ID CITY ZIPCODE
12 of 22
Name
Location
City

3/3
32.13
MVG Applet
Displays child business component records

` Displays list columns that allow the user to distinguish the desired record
MVG applets type is MVG
13 of 22
MVG Applet
There is no requirement that the MVG applet display only those multi-value fields that are displayed on the parent applet. This allows an MVG applet to be used in other MVGs throughout the application.
32
32.14
Creating a Multi-Value Group
Use the MVG Wizard in Siebel Tools to create a multi-value group

` Verify that a link between the parent and child business components exists ` Select File > New Object > MVG
14 of 22
32.15
Inputs to the MVG Wizard
Provide the following information to the MVG Wizard:

` ` ` ` ` The project that the MVG will belong to The master (parent) and detail (child) business components The name of the multi-value link The Auto Primary property (discussed later) The link properties
15 of 22
Link Properties
The following properties can be set to TRUE or FALSE for a link: No Associate, No Copy, No Delete, No Insert, No Update. No Associate equals TRUE specifies that no new associations can be created through the link. New child records may be added.
32
32.16
Setting Auto Primary Property in the MVG Wizard
Set the Auto Primary property to either:

` Default (the first child record becomes the primary) ` Selected (the highlighted record becomes the primary) ` None (the user must specify the primary)
16 of 22
32.17
MVG Wizard Output

The MVG Wizard creates an MVG If no suitable MVG applet exists suitable for the choice of parent and child business components and MVFs, the wizard will open the MVG Applet Wizard
17 of 22
32
32.18
Multi-Value Groups for M:M Relationships
MVGs can be built on M:M relationships as well

` Link must specify the Inter Table property
Parent BC Multi-value field Industry
Location Industry Name SIC Code
Child BC
Account
Name
S_ORG_EXT Intersection table Primary

ROW_ID NAME PK FK
S_INDUST
SIC DESC_TEXT _ NAME
S_ORG_INDUST
INDUST_ID ROW_ID OU_ID
PK FK
18 of 22
LOC
PR_INDUST_ID
ROW_ID
32.19
Configuring MVGs for M:M Relationships

Create object definitions required for 1:M MVGs Specify an association applet for the MVG applet
` Allows users to select other child records to add to the MVG
19 of 22
32
Association applet
32.20
Module Highlights
A multi-value group (MVG) is a set of detail (child) records associated with a parent record A primary is a designated child record that is displayed in the parents applet
` Speeds retrieval of parent record with primary child record for display in UI ` Supported by a primary foreign key ` Multi-value fields (MVFs) ` A multi-value link ` A MVG applet
Use the MVG Wizard to create an MVG in Siebel Tools
20 of 22
Objects needed to support an MVG are:
32.21
Lab

` Create a new MVG ` Create an MVG applet to display the MVG
21 of 22
32
32.22
Data Layer Configuration
33.1
Module 33: Data Layer Configuration
33
33
33.2
Module Objectives

` Create extension columns in a table ` Create custom tables

Standalone table 1:1 extension table 1:M extension table Intersection table

` Enables you to incorporate additional attributes and business entities into a Siebel application
2 of 24
33.3
Incorporating Additional Data
Your business requirements may include:

` Adding new fields to capture additional data ` Creating new business components to capture additional business entities
Extending the Siebel database can satisfy these requirements

` Adding one or more columns to an existing table ` Creating new database tables to support new business components
3 of 24
33

0/2
33.4
Evaluate the Existing Database Tables
Prior to extending the Siebel database, consider using: Unused Columns in an Existing Table Existing 1:M Extension Table
4 of 24

1/2
33.5
Unused Columns in an Existing Table
Consider mapping new fields to unused columns in an existing base or 1:1 extension table
` Verify that the candidate column has the desired type ` Consider possible upgrade conflicts in future releases ` Consider performance impact of a join to the 1:1 extension table
1:1 extension table of S_OPTY Unused columns Find desired type and length
5 of 24
33

2/2
33.6
Existing 1:M Extension Tables
Consider mapping the new business component to an appropriate 1:M extension table (as discussed in an earlier module)
` Verify that the business component has the correct M:1 relationship to the candidate parent business component
New business component has M:1 relationship to parent (Contact)
6 of 24
Contact
33.7
Extending the Database
Changes the database schema and requires propagating the changes to:
` Other developers during development ` Mobile users after development for applications in production ` Production enterprise at completion of development and testing
Requires creating additional object definitions to:
7 of 24
33
` Map columns in the EIM tables needed to import and export data to the extension columns and tables ` Specify how data for these extension columns and tables are to be routed to remote users (Dock Objects)
33.8
Using Siebel Tools to Extend the Database
Supports creating new:

` ` ` ` ` Extension columns on tables Standalone tables 1:1 extension tables 1:M extension tables Intersection tables
Creates new object definitions for the database extension

` Invokes a wizard to build new tables
Makes the corresponding physical database changes

` Developers do not create, use, or maintain SQL scripts
8 of 24
33.9
Best Practices for Extending the Siebel Database
General suggestions:
` When adding a new column:

If column is not often populated, use an existing column in an extension table if available If field often populated, avoid join overhead by using adding an extension column to base table A form applet, prefer an existing column in an extension table A list applet, prefer an extension column in the base table
` Join overhead can be significant when displaying many records
` If data for column appears in:

9 of 24
Reference
Siebel Bookshelf, Configuring Siebel Business Applications, Configuring Tables and Columns
33
33.10
Creating a Custom Extension Column
Make logical changes to the Data layer

` Check out the appropriate project ` Select the table to be extended ` Create a new column record with the desired properties
Name automatically prefixed with X_
Extension column
Select data type and length
10 of 24
33.11
Creating a New Table
Use the Table Wizard to create a new table

` Select File > New Object > Table
Four types of table can be created:

` ` ` ` Standalone table 1:1 extension table 1:M extension table Intersection table
11 of 24
Table Name
A table name must start with CX_ and cannot exceed 15 characters.
33
33.12
Creating a Standalone Table
Table wizard creates a standalone table with:

` Data (Public) as its type ` Nine system columns ` One index P1 on ROW_ID
System columns
12 of 24
33.13
Creating a 1:1 Extension Table
Provide a base table as input to the Table Wizard

` Choice restricted to the Data (Public) type ` Multiple extension tables relate directly to the base table, and not to each other
13 of 24
Extension Tables
1:1 extension tables cannot be created for tables such as S_ORG_EXT and S_CONTACT, which are already extension tables of S_PARTY. Rather, create the new table as an extension table of S_PARTY.
33
33.14
Creating a 1:1 Extension Table Continued
The Table Wizard creates an extension table with:

` Ten system columns

Required nine system columns PAR_ROW_ID column as the foreign key column to the base table P1 index on ROW_ID U1 index on PAR_ROW_ID and CONFLICT_ID
S_PROD_INT
NAME ROW_ID PART_NUM UOM_CD
` Two indexes:

CX_PROD_INT_X
ROW_ID NEW COLUMN PAR_ROW_ID
14 of 24
Indexes
Indexes allow fast retrieval and sorting of records using one or more designated columns. Inserts and updates on indexed columns are costlier than on un-indexed ones. Is used by Siebel Remote to resolve synchronization conflicts between remote clients. See Siebel Bookshelf, Remote and Replication Manager Administration Guide for further details.
CONFLICT_ID
33.15
Creating a 1:M Extension Table

Create if the parent table does not have an existing 1:M table Provide a parent table as input to the Table Wizard
` Choice restricted to the Data (Public) type
15 of 24
33
33.16
Creating a 1:M Extension Table Continued
Table wizard creates an 1:M extension table with:

` Data (Public) as its type ` Ten system columns

Nine required columns PAR_ROW_ID column as the foreign key column to the base table
` TYPE and NAME columns ` Three indexes:

16 of 24
P1 index on ROW_ID U1 index on PAR_ROW_ID, TYPE, NAME, and CONFLICT_ID M1 index on TYPE and NAME
33.17
Creating an Intersection Table

Select both parent tables

` Choices restricted to the Data (Public) type
Specify the foreign key column name for each parent table
17 of 24
33
33.18
Creating an Intersection Table Continued
Table Wizard creates an intersection table with:

` ` ` ` Data (Intersection) as its type Nine system columns Two foreign key columns as specified Three indexes:

18 of 24
P1 index on ROW_ID U1 index on two foreign key columns, TYPE, and CONFLICT_ID F1 index on foreign key to second parent table

0/3
33.19
Applying and Propagating Database Changes
Test changes locally before applying them to the server database

` Reduces the likelihood of undesired changes to the server schema
Best practices for changing the schema: 1. Apply Changes to the Local Database
3. Propagate Changes to Other Developers
19 of 24
33
2. Propagate Changes to the Server Database

1/3
33.20
1. Apply Changes to Local Database
Click Apply/DDL to make the physical database changes

` Choice to apply schema changes or generate DDL script ` Changes are preserved across Siebel application upgrades
Compile relevant objects and projects Test changes locally before checking in to the server
` Query tables/columns using a database SQL utility
New table
20 of 24
DDL
Stands for Data Definition Language, the subset of SQL statements used to define and manipulate database objects. Typical SQL commands used in DDL are CREATE, DELETE, ALTER, and so on.

2/3
33.21
2. Propagate Changes to Server Database
Check project into the server

` Copies the table and column object definitions ` Does not apply those changes to the server database schema
Apply changes to the server database

` To make changes visible, press the Activate button on the Table object on the server machine
Compile and test against the server database

Apply
Check in
33

3/3
33.22
3. Propagate Changes to Other Developers
Other developers need to apply changes to their local databases

` Have other developers Get or check out the project and apply changes locally ` Alternatively re-extract developers and have them get all projects
Get/ Check out
Get/ Check out
22 of 24
33.23
Module Highlights
Alternatives to extending Siebel database schema:

` Utilize unused columns in an existing table ` Use an existing 1:M extension table if appropriate
Extend the Siebel database in Siebel Tools:

` Add an extension column to an existing table ` Use the Table wizard to create a new table:

Best practices to modify Siebel database schema:

` Apply changes locally and test ` Propagate changes to the server database ` Propagate changes to other developers
23 of 24
33
Standalone 1:1 extension table 1:M extension table Intersection table
33.24
Lab

` Create a custom extension column on a table ` Check in configuration and apply to the server database
24 of 24
Siebel Business Services
34.1
Module 34: Siebel Business Services
34
34
34.2
Module Objectives

` Describe a business service ` Describe the structure and role of property sets ` Use the business service simulator to test a business service
2 of 18
` Business services are an important building block for Siebel workflow
34.3
Automating Business Processes
A business process is a series of activities executed to achieve a specific business objective

` Example: the Quote to Cash business process (how an enterprise creates a quote and converts it to an order for submission)
Automation options within the Siebel application can address such challenges as:
3 of 18
34
` Maintaining and standardizing consistent business processes across all business units ` Routing and assigning tasks accurately and efficiently ` Responding in a timely, effective manner to customer inquiries and service requests ` Assisting users with the implementation of best practices ` Offering consistent and personalized service to customers
34.4
Siebel Workflow
Is a set of capabilities to extend the functionality of Siebel applications by automating business processes Includes capabilities such as:
` Workflow Processes
Automates steps in a business process Invokes workflow process under specified conditions Guides users through a series of views to complete a step in business process Automates assignment of data (such as opportunities and service requests) to the desired people Enforces a limited life cycle for select business entities
` Workflow Policies
` Assignment Manager
` State Model
4 of 18
` Tasks
34.5
Business Service
Is a unit of functionality that is reusable and globally accessible

` Example: The ISS Shipping Cost Service computes shipping charges corresponding to a companys shipping policies
Enables business logic to be executed repeatedly in multiple different contexts

` Business logic is not restricted to a specific object (business component, applet, and so forth)
5 of 18
Reference
Integration Platform Technologies: Siebel EAI : Business Services
34
Can be invoked in a Siebel workflow process or a Siebel task
34.6
Prebuilt Business Services
Siebel repository contains many prebuilt business services to support processing in areas such as
` Customer order management

ISS Credit Check Service ISS Shipping Cost Service ISS Tax Calculation Service EAI Siebel Adapter EAI HTTP Transport XML Hierarchy Converter XML Converter Business Rule Service
` Enterprise application integration
` XML document processing

` Enforcing customer business rules
6 of 18
34.7
Repository-Stored Business Services
Some business services are stored in the Siebel repository

` Siebel-developed business services

Are written in C++ Cannot be modified by customers Are written in Siebel Visual Basic or eScript Are created and modified by customers using Siebel Tools
` Custom business services developed by users

Custom business service
7 of 18
34
34.8
Client-Stored Business Services
Some business services are stored in the client database

` Siebel-developed business services ` Custom business services developed by users
Client-stored business services

` Are written in Siebel Visual Basic or eScript ` Are created and modified by customers using the Administration Business Services screen ` Are never executed if there is a repository-stored business service of the same name
8 of 18
Client Database
The term client database refers to tables in the Siebel database that store user data.
34.9
Methods
A business service consists of one or more operations called methods

` Each method has a set of input and output arguments, each with a specified type
Business service
StringManipulation
Argument name Length
InputString String InputString String String1 String Length Number String2 String
Truncate
OutputString String OutputString String
Argument type
Concatenate
Method
Input arguments
Output arguments
9 of 18
34
Length
Number
34.10
Identifying Methods for a Business Service
In Siebel Tools, navigate to Business Service | Business Service Method
Name that appears in client when selecting a business service method
10 of 18
34.11
Identifying Arguments and Types for a Method
In Siebel Tools, navigate to Business Service | Business Service Method | Business Service Method Arg
11 of 18
34
34.12
Invoking a Method
Involves:
` Assigning values to the input parameters
Not all input parameters are required to have values
` Retrieving the values assigned to the output parameters

StringManipulation
InputString String
Length Number
Truncate
OutputString String
Concatenate
12 of 18
Siebel
Length
Sieb
34.13
Property Set
Is the in-memory data structure used to:

` Pass a set of input arguments into a method ` Receive a set of output arguments from a method
Input property set
StringManipulation
Output property set
InputString String
Length Number
Truncate
OutputString String
Concatenate
13 of 18
34
Siebel
Length
Sieb
34.14
Property Set Continued

Represents data using name/value pairs Has two predefined properties: Type and Value Has an array for storing user-provided name/value pairs Is automatically created and populated when invoking most business services from a Siebel workflow or task
Values for predefined properties Predefined property names Array of user-provided name/value pairs InputString Length
Type Value
Siebel 4
Input property set
14 of 18
34.15
Testing a Business Service
Use the business service simulator in the Siebel Client

` Navigate to Administration - Business Service > Simulator ` Select the business service and method ` Create the property set name/value pairs
Optionally load data from an input file
Input property set
15 of 18
34
34.16
Testing a Business Service Continued
Use the business service simulator in the Siebel client

` Click Run on One Input ` Examine the output property set name/value pairs ` Optionally save the output to a file
16 of 18
34.17
Module Highlights
A business service is a unit of functionality that is reusable and globally accessible

` Can be stored in the repository or in user database tables ` Consist of one or more methods
Each method is specified by a set of input and output arguments
` Is invoked by passing in the input arguments in a property set ` Returns the output arguments in a property set
Use the business service simulator to test a business service
17 of 18
34
A property set is an in-memory data structure consisting of name value pairs A business service
34.18
Lab

` Import a custom business service into the repository ` Examine the methods and arguments for a business service ` Use the business service simulator to test a business service and examine the output property sets
18 of 18
Building Siebel Workflow Processes
35.1
Module 35: Building Siebel Workflow Processes
35
35
35.2
Module Objectives

` List the types of workflow processes and workflow steps ` Create a new workflow process and configure business service, Siebel operation, and decision steps
2 of 26
` Siebel workflow processes are one of several declarative techniques to automate business logic
35.3
Workflow Process
Is an ordered set of steps executed in response to a defined set of conditions Is used to automate parts of a business processes in a Siebel application
3 of 26
Reference
Siebel Business Process Framework Workflow Guide: Introduction to Workflow Processes
35
35.4
Workflow Designer
Siebel Tools includes a Workflow Designer used to create, examine, and modify Siebel workflow processes
` Contains a palette, workspace, and associated property windows
Workspace for editing workflows
Properties window (displays properties of selected item)
Palette of workflow steps Multi Value Property Window (displays properties of child records of selected item)
4 of 26
Reference
Siebel Business Process Framework Workflow Guide: For Developers: Basics of Building Workflow Processes
35.5
Workflow Process Steps
Siebel workflow processes consist of different types of steps

Start step
eSales Complete Checkout Process

Decision point step User interact step
Sub process step
Business service step
End step
5 of 26
35
35.6
Workflow Process Steps Continued
All workflow processes have a:

` Start step ` End step
Workflow processes often include the following common steps:

` Business service step ` Siebel operation step ` Decision point step
Start step End step
6 of 26
35.7
Siebel Operation Step
Performs the following operations on a business component

` ` ` ` Insert Update Delete Query
Next record and previous record operations supported for iteration over multiple records returned by a query
Queries the Contact business component
7 of 26
35
35.8
Business Service Step
Invokes a method of a business service
Invokes the Truncate method of the StringManipulation business service
8 of 26
35.9
Decision Point Step
Allows a workflow to branch to one of multiple steps based on the value of inputs
If input = no
9 of 26
35
If input = yes
35.10
Process Properties
Process properties are variables that store inputs used by and outputs produced by workflow steps Each workflow process has a set of process properties that persist while the workflow process is executing
` Some are populated when the workflow process is invoked ` Some return data to invoking workflow process or business service upon completion
Specific to this workflow
Some of default properties that appear in all workflows

35.11
Process Properties Continued

Provide inputs to workflow steps Receive outputs from workflow steps
` Can be used as inputs for following steps

FirstName LastName ContactCode
Process Properties
StringManipulation
Length
Truncate
String1 String String2 String OutputString String Business service step
Concatenate
11 of 26
35

0/5
35.12
Configuring a Siebel Workflow
1. Create a New Workflow Process 2. Specify the Process Properties 3. Add Workflow Steps 4. Configure the Steps 5. Validate the Workflow Process
12 of 26

1/5
35.13
1. Create a New Workflow Process

In Siebel Tools, select the Workflow Process object type Create a new workflow process definition
` Enter the process name ` Assign the process to a locked project ` Assign a business object
Provides context for references to business components and fields
13 of 26
Business Object
A business object must be specified whenever you use a workflow step (such as a Siebel Operation step) that references a business component. In addition if a workflow references a business object, then the workflow must be executed in the context of that business object.
35
Right-click and select Edit Workflow Process to invoke the Workflow Designer

2/5
35.14
2. Specify the Process Properties

Select the Process Properties tab in the Multi Value Property Window (MVPW) to display the default process properties Edit the default set of process properties
` Add new process properties to store additional values created and used by the workflow steps ` Leave the default process properties as is
Default process properties for all workflows
14 of 26

3/5
35.15
3. Add Workflow Steps

Add a start and end step to the designer

` Drag steps from the palette to the workspace
Add other steps as required Add connectors to sequence the steps

` Make sure that connector ends are anchored (red box appears)
Connector anchored
Dynamic connectors (are drawn automatically with right angles as necessary)

35

4/5
35.16
4. Configure the Steps (Siebel Operation)
For each Siebel operation step

` Specify the business component and operation
Use the properties window Field names Search spec input arguments Output arguments
` Specify additional child arguments as required in the MVPW

Operation Fields retrieved
16 of 26
Business component

4/5
35.17
4. Configure the Steps (Business Service)
For each business service step

` Specify the business service name and business service method
Use the Properties window

Business service and method
17 of 26
35

4/5
35.18
4. Configure the Steps (Business Service) Continued
For each business service step

` Specify inputs to use in the workflow

Select the Input Arguments tab in the MVPW Assign a literal value or a process property to each input Select the Output arguments tab in the MVPW Assign each output to a process property
` Specify outputs of the business service step

Input arguments defined for method
Constant value assigned as input
Value of process property assigned as input
Value of output argument assigned to process property
18 of 26

4/5
35.19
4. Configure the Steps (Decision Point Step) Continued
For each decision point step, set conditions on each branch (connector) originating at the step
` Select connector ` Right-click and select Edit Conditions
19 of 26
35

4/5
35.20
4. Configure the Steps (Decision Point Step)

Enter the condition criteria for each branch in the Compose Condition Criteria dialog box Do not create a condition criteria for the default branch
` Execution path taken if no other branches are satisfied
20 of 26
Does contact have a middle name

5/5
35.21
5. Validate the Workflow Process

Save all the configuration performed in the Workflow Designer Return to the Workflow Process List Right-click the workflow and select Validate Click Start to perform the validation checks
` Syntactic errors are displayed in the Errors window
21 of 26
35
35.22
Additional Workflow Steps
Siebel workflows may contain additional types of steps

` Sub process
Invokes another workflow process as a sub process Navigates the user a view and waits for user activity Pauses the workflow for a specified period of time before proceeding Stops the workflow process instance if a predefined exception occurs Invokes a Siebel task (subject of a subsequent module)
` User interact
` Wait
` Task
22 of 26
` Stop
35.23
Workflow Modes
Workflows are characterized by modes that describe their runtime behavior

` Service Flow

Executes a discrete set of steps and completes Is the default mode for a new workflow Cannot include wait or user interact steps Designed to navigate users through a set of views Is being replaced by Siebel tasks Is a workflow that is intended to persist for some indeterminate period of time Can be paused and resumed as an inbox item Cannot include a wait step Provided for backward compatibility of workflows defined prior to Siebel 7.5 release Should not be used for any new workflows
23 of 26
` Interactive flow
` Long running flow
` 7.0 flows
Interactive Flows
Siebel Task UI provides significantly enhanced capabilities to guide users through a series of views. However interactive flows may still be used if all you wish is to navigate a user from one regular Siebel view to another. In addition, Task UI is applicable in only the High Interactivity client. Interactive flows must be used for the Standard interactivity client.
35
35.24
Module Highlights
A workflow process is an ordered set of steps executed in response to a defined set of conditions
` Is used to automate parts of a business processes in a Siebel application
` ` ` ` `
Creating a new workflow process Specifying the process properties Adding workflow steps Configuring each step Validating the workflow process
24 of 26
Siebel workflow processes consist of different types of steps (Business service, Siebel operation, decision point, etc.) Process properties are variables that store inputs used by and outputs produced by workflow steps Build a workflow process by:
35.25
Lab

` Configure a workflow process that includes business service steps ` Configure a workflow process that includes a decision point step
25 of 26
35
35.26
Testing and Deploying Workflow Processes
36.1
36
Module 36: Testing and Deploying Workflow Processes
36
36.2
Module Objectives

` Test a Siebel workflow process using the simulator ` Deploy a Siebel workflow process

` Workflow processes should be tested to verify that they behave as desired prior to deployment ` Deployment is a critical step in making a new workflow process available for use
2 of 26
36.3
Managing Siebel Workflow Processes
36
Workflow process differ from most other object definitions

` Are not compiled into an .srf file ` Cannot be archived into .sif files ` Can be exported to and imported from XML files
After a workflow process has been configured in Siebel Tools

` Simulate the workflow ` Deploy the workflow
3 of 26
36.4
Workflow Simulator
Use the workflow simulator to verify that the workflow performs as desired
` Workflow simulation is controlled in Siebel Tools ` Workflow is actually executed in an instance of a Siebel client
Tools and the Siebel client must be connected to a common database
DB
Reference
Siebel Business Process Framework Workflow Guide: For Developers: Testing Workflow Processes
36.5
Enabling Workflow Simulation
36
Configure the connection to the Siebel run-time instance

` In Siebel Tools, select View > Options > Debug
Simulator shares the connection parameters used by Tools Debugger
` Specify the run-time Siebel instance ` Provide a valid login

Executable: Location of siebel.exe file for the Mobile Web Client CFG file: Location of the Mobile Web Client configuration file Working directory: The Mobile Web Client directory Arguments: Use default, opens communication between Tools and Mobile Web Client Login information: Login name, password, data source

0/4
36.6
Test a Workflow Using the Workflow Simulator
1. Specify the Test Record 2. Start the Simulator 3. Start the Simulation 4. Execute the Workflow
6 of 26

1/4
36.7
1. Specify the Test Records

36
In the Siebel client, create test records to support the simulation

` Use About Record to determine the row ID
In Siebel Tools, enter the row ID of the test record as the default string for the Object ID process property
` When the workflow is invoked in production, row ID of the record is passed in as an input argument
7 of 26

2/4
36.8
2. Start the Simulator

Make sure that all instances of the Siebel client application are closed Right-click the Workflow Designer workspace and select Simulate
` Workflow Designer displays the workflow in the simulator window
8 of 26

3/4
36.9
3. Start the Simulation

36
Click the Start Simulation button in the simulation toolbar

` Use View > Toolbars > Simulation to display the simulation toolbar
A new instance of the Siebel client is launched

Start simulation
Wait until Siebel client application starts and displays the Workflow Simulator view
9 of 26

4/4
36.10
4. Execute the Workflow
Execute the workflow in either

` Single step mode using the Simulate Next button ` Continuous mode using the Complete Simulation button
Verify that the workflow branches correctly at decision steps

Simulate next Complete Simulation
10 of 26

4/4
36.11
4. Execute the Workflow Continued
36
Inspect the watch window to verify that process properties have the expected values
` Values of user added process properties can be edited during a simulation
Inspect process properties in watch window


4/4
36.12
4. Execute the Workflow Continued

Complete the simulation

` Use either Simulate Next or Complete Simulation buttons
Verify that the final values of process properties are correct Click the Stop Simulation button Inspect the client and verify that the desired changes occurred
Stop simulation
12 of 26
36.13
Workflow Simulator Considerations
36
Cannot simulate workflow processes that invoke server components

` Must test these workflows directly on the Siebel Web Client
Cannot simulate workflows with run-time events on start steps (discussed in a subsequent module) Can simulate workflows with user interact steps
13 of 26
` Requires the developer to perform the activity in the client application to allow the simulation to proceed
36.14
Managing Siebel Workflow Processes
After a workflow process has been configured in Siebel Tools

` Simulate the workflow ` Deploy the workflow
14 of 26
36.15
Deploying Workflow Processes

Transfers the workflow from the repository to run-time tables to make it available for use Consists of:
36
` Developer setting the workflow complete in Siebel Tools ` Administrator activating the workflow in the run-time client
15 of 26
36.16
Publish the Workflow
In Siebel Tools, click the Publish button in the Workflow toolbar

` Sets the status to Completed
Prevents any further editing of the workflow process
` Makes the workflow available for activation

Publish
16 of 26
36.17
Checking in the Workflow Process
36
In Siebel Tools, check in the completed workflow process to the server repository
` Siebel Web Client can now access the workflow
17 of 26
36.18
Activating the Workflow
In the Siebel Web Client, activate the workflow

` Navigate to Business Process - Administration > Workflow Deployment ` Select the newly deployed workflow and click Activate
Transfers the workflow definitions in the repository tables into corresponding run-time tables
18 of 26
36.19
Publishing/Activating a Workflow Process

Developers can deploy and activate a workflow process from Siebel Tools to expedite testing of the deployed workflow In Siebel Tools, click the Publish/Activate button in the Workflow toolbar
36
` Sets the status to Completed ` Transfers the workflow definitions in the repository tables into corresponding run-time tables
Publish/Activate
19 of 26
Siebel client (for testing) must use the same database as Siebel Tools
36.20
Workflow Monitoring
Navigate to Business Process - Administration > Workflow Deployment

` Select the active workflow process ` Set the monitoring level in the active workflow process as required
The value assigned is used whenever the workflow process is invoked or resumed
20 of 26
36.21
Monitoring Level
36
Monitoring levels can be set as follows to record differing degrees of detail

` Performance can degrade as level of detail recorded increases
Levels Record Process Instance N Y Y Y Y Record Step Instance None None All Steps All Steps All Steps Record Process Properties None None All steps All Steps
0-None 1-Status 2-Progress 3-Detail* 4-Debug**
* In Detail, data is written at the end of the workflow ** In Debug mode, data is written to disk after every step
21 of 26
None
36.22
Deployment Considerations
Deploy all child workflows (sub processes) first to make them available to the deployed workflow Compile any new repository objects referenced in the deployed workflow such as business components, fields, and views
22 of 26
36.23
Revising Workflows

36
Workflows are versioned

` Existing versions are kept and a new version is created
To revise a workflow
` In Siebel Tools, select the desired workflow (check out if necessary) ` Click the Revise button in the Workflow toolbar
Creates a copy of the workflow
` Edit and test the workflow ` Deploy the workflow

Revise
23 of 26
` Increments the version number ` Sets status to In Progress
36.24
Administering a Revised Workflow

In the Siebel Web Client, activate the workflow as before

` Sets the deployment status of the prior version to Outdated
After being activated the new version will be invoked

` Any instances of the prior workflow version running at the time of activation run to completion
24 of 26
36.25
Module Highlights
36
Use the workflow simulator to verify that the workflow behaves as designed
` Workflow simulation is controlled in Siebel Tools ` Workflow is executed in an instance of a Siebel client
Deploy a workflow to make it available for use in the run-time client
Revise a deployed workflow to edit it

` This creates a new version
25 of 26
` In Siebel Tools, publish the workflow ` In the run-time client, activate the workflow to make the workflow available for invocation
36.26
Lab

` Simulate workflows you previously configured
26 of 26
Executing Workflow Processes
37.1
37
Module 37: Executing Workflow Processes
37
37.2
Module Objectives

` ` ` ` Describe the workflow execution architecture List several ways to invoke workflow Invoke a workflow process using a run-time event Invoke a workflow process using a custom control

` There are multiple ways to invoke a workflow process and you need to understand the choices available
2 of 24
37.3
Workflow processes are executed either in

` The users application object manager
Supports synchronous processing
37
` A separate server component known as the Workflow Process Manager component
Supports asynchronous processing
` Is often referred to as the Workflow Engine
3 of 24
Reference
Siebel Business Process Framework: Workflow Guide: Introduction to Workflow Processes
In both cases workflow processes are executed using the Workflow Process Manager business service
37.4
Synchronous Workflow Processing
Is typically executed in the users application object manager

` User is forced to wait until the workflow completes (or pauses)
Hourglass icon appears
Can be triggered by an action on the part of the user:

` Directly by clicking a button or menu item ` Indirectly by performing a record or applet operation
Is used to execute specific business logic that:

` Is triggered by the users activity ` Should be completed before the user continues activity
4 of 24
37.5
Asynchronous Workflow Processing
Is executed in the Workflow Process Manager server component

` User (if any) is not prevented from continuing activity
37
Is typically triggered by a change in the value of some column in a database table

` Can respond to changes not associated with user activity
` Can respond to conditions that exist for some threshold period of time
Is used to execute specific business logic when a specified condition is satisfied Will be discussed in the following module
5 of 24
For example: updates resulting from Enterprise Integration Manager imports
37.6
Invoking Workflow Processes
A workflow process can be invoked by a variety of mechanisms

` ` ` ` Run-time events Custom buttons and menu items Workflow policies Programmatically (that is as part of script)
This module Next module Beyond scope
6 of 24
37.7
Run-Time Events
Are a mechanism that allows customer-configured processing to be triggered by user activity Consist of:
37
` A specification of some user activity such as:

Record being updated Navigating to/from an applet
` The resultant processing
` Known as an action set
7 of 24
Reference
Siebel Personalization Administration Guide: Tracking Run-Time Events Run-time events were introduced as part of Siebel Personalization and are therefore described in the Personalization Administration Guide.
Workflow One or more calls to business services
37.8
Run-Time Events Continued
Can be defined for three types of objects:

` Application
Examples: logging in, logging out Examples: displaying an applet, displaying a record Examples: Querying, deleting a record, setting a field value
` Applet
` Business component
8 of 24
Are fired when a user performs the corresponding activity
37.9
Business Component Events
Business component events often come in pairs such as:

` PreDelete/Delete ` PreSetField/SetField ` PreWriteRecord/WriteRecord
37
The Pre- event is fired immediately prior to object manager executing the operation
Allows for possible verification of field values
The other event is fired immediately after the object manager executes the action
` Example: WriteRecord executes customer processing after the record is written
Allows for follow-on processing after a record is saved
9 of 24
` Example: PreWriteRecord executes customer processing before the record is saved
37.10
Adding a Run-Time Event to a Workflow Process
A run-time event can be added to a workflow process as a condition on the connector out of a:
` Start step
Used to invoke the workflow Used to resume the workflow
` Wait step
` User interact step
Add run-time event here
Add run-time event here
10 of 24
Reference
Siebel Business Process Framework: Workflow Guide: For Developers: Understanding How Workflow Processes Are Designed
Used to resume the workflow

0/3
37.11
Invoking a Workflow Using a Run-Time Event
1. Add the Run-Time Event 2. Deploy and Activate the Workflow 3. Reload the Run-Time Events
37
11 of 24

1/3
37.12
1. Add the Run-Time Event

Create the workflow process as usual Select the connector to attach a run-time event
` Must be a start, wait, or user interact step
In the properties window, specify the triggering event Caution: A workflow with a run-time event on the start step cannot be tested with the workflow simulator
Select connector Specify the event type, business component, and event to monitor

2/3
37.13
2. Deploy and Activate the Workflow

In Siebel Tools, deploy the event In the Siebel client, activate the event
37
13 of 24

2/3
37.14
2. Deploy and Activate the Workflow Continued
Activating the event automatically registers the run-time event and associated workflow with the Siebel run-time event engine
` Creates an action set that invokes the Workflow Process Manager
Row ID of activated workflow
Business Service, method to invoke
Arguments to pass in

3/3
37.15
3. Reload the Run-Time Events

Navigate to Administration - Runtime Events > Events Select Menu > Reload Runtime Events
` Updates the run-time event engine with the new run-time event ` Not necessary to query for the specific run-time event
37
Run-time event created by activating the workflow process
15 of 24
37.16
Invoking Workflows Using a Custom Control

User explicitly clicks a custom button or menu item to invoke the workflow Configuration involves applet user properties
Custom menu item that invokes a workflow

37.17
Invoking a Workflow Using a Custom Menu Item

Create a command object

` Specify a value for the Method property
Add an applet method menu item to reference the command
37
17 of 24
37.18
Invoking a Workflow Using a Custom Menu Item Continued
Add a new Applet User property that associates the workflow to be invoked with the new named method
Invoke this business service and method and
pass in these pairs of argument names and values
18 of 24
37.19
Invoking a Workflow Using a Custom Button

Create a custom control for the button

` Specify a value for the Method Invoked property
Add a new Applet User property that associates the workflow to be invoked with the new named method
Specify a userdefined name for a Method to invoke on the control
37
Create an applet user property specifying the workflow to execute when the named method is invoked
19 of 24
37.20
Invoking a Workflow Process Explicitly
The Workflow Process Manager business service can be referenced explicitly:

` In a script ` As parameters in declarative configuration
Developers must specify:

` The name of the business service and method ` The name of the workflow process and other parameters as input arguments
Often the RowId parameter must be passed in
20 of 24
37.21
Invoking a Workflow Process Explicitly Continued
A workflow process can also be executed using the business service simulator
` Is an alternative way of testing new workflows
37
Business service that executes workflow processes
Provide name of workflow process as input argument
21 of 24
37.22
Module Highlights
Workflow processes are executed in the Workflow Process manager in either the application object manager or in a server component
` Can be executed either synchronously or asynchronously
A workflow process can be invoked by a variety of mechanisms

` Run-time events ` Custom buttons and menu items ` Workflow policies
Run-time events are a mechanism that allows customerconfigured processing to be triggered by user activity
22 of 24
37.23
Lab

` Invoke a workflow from a custom menu item ` Invoke a workflow using a run-time event
37
23 of 24
37.24
Using Workflow Policies
38.1
Module 38: Using Workflow Policies
38
38
38.2
Module Objectives

` Create a workflow policy that invokes a workflow process in the Workflow Process Manager server component ` Enable the workflow policy using workflow server components
2 of 24
` Some workflow processes are best executed asynchronously on the Siebel server
38.3
Asynchronous Workflow Processing
Some workflows need to be executed asynchronously

` They might run for a long time and should not execute in the users object manager ` They might need to wait for the invoking condition to be satisfied for some period of time
Example: If a critical service request remains unassigned for more than two hours, notify the service manager and set the priority to High
38
Workflow policies are a mechanism for asynchronous execution of workflow processes
3 of 24
38.4
Workflow Policies
A workflow policy is a rule consisting of:

` One of more policy conditions ` A policy action
Action is invoked when all conditions are true Example: When a service request priority = Critical AND substatus = Unassigned:
` Send urgent message to service manager

Workflow Workflow Policy Policy
IF True then execute
Conditions: Conditions: Substatus Substatus= =Unassigned Unassigned Service Request Service RequestPriority Priority= =Critical Critical
Actions: Actions: Update Updatepriority priorityto toHigh High Send message to Send message toservice servicemanager manager
4 of 24
Reference
Siebel Business Process Framework: Workflow Guide: Workflow Policies
38.5
Workflow Policy Conditions

Policy condition specifies a logical relationship between a workflow policy column and a value All policy conditions must be satisfied for a condition to apply Policy may have a duration specified
` Conditions must apply for the duration before the action is executed
Workflow Workflow Policy Policy
38
Duration == 22 hours Duration hours
IF True for at least two hours
then execute
Conditions: Conditions: Status Status= =Open Open Service ServiceRequest RequestPriority Priority= =High High
Actions: Actions: Update Updatepriority priorityto toVery VeryHigh High Send message to owner Send message to owner
5 of 24
Workflow Policy Column
A workflow policy column is an object definition configured in Siebel Tools that identifies a column in a Siebel database table that can be monitored by a workflow policy.
38.6
Workflow Policy Actions

A workflow policy action is the response to be executed Consists of:
` Type of program to be executed
Examples: Run workflow process, send email, send message broadcast
` One or more program-specific arguments

Multiple types of programs are supported Actions are defined separately

` Can be used in multiple workflow policies
6 of 24
` Not restricted to running workflow processes
38.7
Workflow Policies
Leverage:
` A separate server component known as the Workflow Process Manager component
Is a server component optimized for executing workflows

` Behaves like an object manager
Can access the business and data layers
38
` Does not have a user interface for direct user interaction
` Database triggers:

A trigger is a process or a stored procedure attached to a database table that fires when a specified data modification event occurs Are created by the Generate Triggers server component
7 of 24
38.8
Executing Workflow Policies

Generate Triggers creates the database triggers required to monitor conditions in policies Workflow Monitor Agent checks for fired triggers
` Identifies policy conditions that are satisfied ` Invokes the desired workflow process
Workflow Process Manager executes the workflow process
Execution is asynchronous
S_ESCL_REQ
Generate Triggers
Create triggers corresponding to policy conditions Executes the workflow process specified in action
EIM
Siebel Database
Triggers fire when conditions satisfied and inserts record
Retrieves records and executes the action
Workflow Process Mgr

Server Request Broker
Workflow Monitor Agent

8 of 24
End-user activity or server process
38.9
Workflow Policy Groups
A workflow policy group is a collection of workflow policies that are monitored as a group by a workflow monitor agent process
` Typically workflow policies that can be monitored at the same frequency are assigned to the same policy group
38
9 of 24
38.10
Prerequisite for Executing Workflow Policies

Enable the Workflow Management component group on the enterprise Assign and enable the component group on a server
` Navigate to Administration - Server Configuration > Enterprises > Component Groups
10 of 24
Enable Component Group
If the Workflow Management component group is not enabled as part of installation, it can be enabled using the Server Configuration Administration screen.
38.11
Workflow Component Definitions
Workflow Component Group consists of six server component definitions
38
11 of 24
Generate Triggers Workflow Action Agent Workflow Monitor Agent Workflow Process Batch Manager Workflow Process Manager Workflow Recovery Manager
Creates insert, update, and delete triggers on base tables based on defined workflow policies. Optional component with email consolidation. Executes actions associated to a workflow policy. Monitors workflow policies to invoke workflow processes. Enables workflow processes to be run in batch mode, allowing actions to be executed for multiple records. This is the workflow engine for workflow processes and is used for real-time process automation. Recovers crashed instances and resumes instances that have been waiting beyond a due date.

0/5
38.12
Implementing a Workflow Policy
1. Create a Workflow Group 2. Create a Workflow Policy Action 3. Create a Workflow Policy 4. Generate Database Triggers 5. Start Workflow Monitor Agent
12 of 24

1/5
38.13
1. Create a Workflow Group

Navigate to Administration - Business Process > Policy Groups Create a new policy group
38
13 of 24

2/5
38.14
2. Create a Workflow Policy Action

Navigate to Administration - Business Process > Actions Create a new action
` Specify Run Workflow Process
Provide workflow process as an argument
Specify the Run Workflow Process program Specify the workflow process to invoke
14 of 24

3/5
38.15
3. Create a Workflow Policy

Navigate to Administration - Business Process > Policies Create a new policy
` Specify conditions ` Add one or more actions
38
Create a policy
Create a condition
Associate an action to invoke the workflow process
15 of 24

3/5
38.16
3. Set Duration
Set duration for the workflow policy

` All conditions must be met and the policy duration must be satisfied to trigger the workflow policy actions ` Defaults to 0
The workflow policy actions are triggered as soon as the policy conditions are met
16 of 24

4/5
38.17
4. Generate Database Triggers
Run a Generate Triggers batch job to create database triggers corresponding to the policy conditions
` When a trigger fires against a Policy Condition, a record is inserted in the Escalation Request Table (S_ESCL_REQ) ` S_ESCL_REQ contains all the rows in the database that could trigger a policy to take action
38
Generate Database Triggers
Record is inserted, updated, or deleted
S_ESCL_REQ Table updated
17 of 24

4/5
38.18
4. Generate Database Triggers Continued

Navigate to Administration - Server Management > Jobs Create a new job
` Select Generate Triggers ` Specify parameters
Submit job
Create new Job and select Generate Triggers
Click Submit Job to start Component Job
Specify parameters
18 of 24
Privileged User
Credentials for a privilege user must be specified in order to allow the generation of triggers on the Siebel database tables. Most often the database owner for the Siebel database is specified.

5/5
38.19
5. Start Workflow Monitor Agent
Create a custom Workflow Monitor Agent component definition to specify a Workflow group
` Monitors all policies within a single Workflow group
Activate the new component definition to make it available
38
19 of 24
38.20
Verify the Workflow Policy

Create a test record (or modify an existing record) that violates the policy condition Wait for at least the policy duration Verify that the desired workflow actions are executed
20 of 24
38.21
Comparing Different Methods
Use different methods for different needs
Workflow Workflow Policies Policies

Generate Triggers WF Monitor Agent Runtime Event Synchronous Runs on Mobile Client Required Required Not Used Asynchronous (runs in background) No (runs on Siebel Server)
Runtime Runtime Events Events

Not Required Not Required Invokes process Synchronous (runs in user session) Yes
Custom Custom Control Control

Not Required Not Required Not Used Synchronous (runs in user session) Yes
38
21 of 24
38.22
Module Highlights
A workflow policy is a rule consisting of one or more conditions and a policy action to be executed when the conditions are satisfied Workflow policies implement asynchronous execution of workflow processes Workflow policies require the use of:
22 of 24
` Generate Triggers to create the database triggers ` Workflow Monitor Agent to check for fired triggers ` Workflow Process Manager to execute the associated workflow policy
38.23
Lab

` Create a workflow policy ` Enable the workflow management group components ` Test the workflow policy
38
23 of 24
38.24
Siebel Task UI
39.1
Module 39: Siebel Task UI

39
39
Siebel Task UI
39.2
Module Objectives

` Describe the role and benefits of Siebel Task UI ` Invoke and complete a task

` Siebel Task UI provides an alternate style of user interaction that assists successful completion of business tasks and incorporates automation of activities
2 of 20
Siebel Task UI
39.3
Business Challenge
Many tasks require users to perform several steps to complete the task
` Users may not be familiar with the sequence of steps ` Users may inadvertently skip a step ` Users often require additional training to complete the task
Companies would like to implement a user interaction style that assists users in completing such tasks
3 of 20
39
Siebel Task UI
39.4
Business Solution: Siebel Task UI
Uses a wizard-like interface to guide users through steps in a task

` Consists of a sequenced set of views, each of which collects a small set of relevant data from the user
Extends business process automation to the UI layer

` Users are directed to complete some steps in a task in a prescribed order
4 of 20
Siebel Task UI
39.5
Features of Siebel Task UI
Supports forward and backward navigation through a sequence of views

` Allows for a set of records to be reviewed and corrected prior to completion of the task
Supports branching based on user input Supports pausing and resuming tasks if users are interrupted
` Instance of the partially completed task is saved in the users inbox ` Task is resumed from the Universal Inbox
Supports transfer of paused tasks to other users
5 of 20
Task UI
Task UI refers to both the wizard-like style of the user interface as well as to the underlying Task UI framework which consists of the development, runtime, and administrative features that support this type of user interface. The term task (in the context of task UI) refers in general to a unit of work to be preformed by a user as part of larger business process. The term task is also used to refer to a specific task developed using the Task UI framework.
Task
Context and all data are maintained
39
Siebel Task UI
39.6
Using Task UI
Click the Task button to expose the Task pane

` Displays links to tasks that can be invoked in the current application context
Task button
Task group (a collection of related tasks)
Task link
6 of 20
Reference
Siebel Business Process Framework: Task UI Guide: Task UI Concepts
Task pane
Siebel Task UI
39.7
Invoking a Task
Click the link for the desired task

` A task view replaces the standard Siebel view ` Task pane displays other views in the task to provide context for the overall task
Views may be grouped into chapters
Enter data in fields in the first view Click Next to proceed to subsequent views
Click Next to proceed Task pane shows current position in task

Enter data
7 of 20
39
Siebel Task UI
39.8
Invoking a Task Continued
Task views are typically characterized by:

` Small number of fields in each applet in the view
Each view focuses the user on a specific set of data to edit Known as a Playbar applet
` A set of navigation buttons located above and/or below the applets
` Absence of navigation options such as view tabs and hyperlinks
Small number of related fields
Click Next to proceed
Playbar applet Task view
8 of 20
Siebel Task UI
39.9
Progressing Through a Task

Enter data in each subsequent view Click Next to proceed Click Back to return to a previous view to inspect or modify previously entered data
Task views in chapter are listed as user navigates to the view
9 of 20
39
Siebel Task UI
39.10
Branching in a Task

Tasks can branch based on data the user inputs

` Example: branching based on lead quality of an opportunity
Some views may explicitly present to the user a choice about the next step to be executed
` Select the desired activity and click Next
User makes a selection
10 of 20
Siebel Task UI
39.11
Pausing a Task
Click Pause to suspend task activity

` All data and context is retained ` A link to the paused task is added to the users inbox
Navigating outside the task view implicitly pauses a task

` For example clicking a screen tab or the site map button
Inbox
11 of 20
39
Siebel Task UI
39.12
Resuming a Task
Click the link in the Inbox to resume the task

` Task resumes exactly where it was paused
Inbox
Task view reappears
12 of 20
Siebel Task UI
39.13
Completing a Task
Review the data if a final summary view is provided Click Submit or Finish to complete the task
` Commits all remaining uncommitted data to the database
The task view is closed and the previous standard view is displayed
13 of 20
39
Siebel Task UI
39.14
Persistent Data in Task UI
All data entered during a task is initially stored in temporary storage managed by the Object Manager
` Is not automatically written to the database as user proceeds to next view
Persistent data is committed to the database:

` When the task completes ` At intermediate points in the task flow if the underlying task flow contains explicit commit steps
Records can not be rolled back after being committed Data created or modified is not available to others until it is committed Data in temporary storage:
` Is maintained while the task is paused ` Is cleared only when the task is cancelled or completed
14 of 20
Siebel Task UI
39.15
Transient Data in Task UI
Refers to data collected and used during the execution of a task but not saved afterwards
` Example: user choice about the next step
Transient data may be mapped to persistent data in a later step in the task
` User enters name of a contact to retrieve ` If no contact is found, a new contact record is created and saved
Task applet
Users selection does not need to be stored persistently

Transient data disappears when the task ends
39
Siebel Task UI
39.16
Tasks and Workflow Processes

A workflow process can invoke a task

` Invokes a task step in the workflow process
A task can invoke a workflow process

` Invokes Workflow Process Manager business service in a task flow ` Invokes a workflow using event handlers associated with a Playbar button
16 of 20
Siebel Task UI
39.17
Tasks and Long-Running Workflow Processes

Initial task can start a long-running workflow upon completion Long-running workflow can assign a task to a users inbox and then go to sleep User can invoke the assigned task from the inbox and upon completion will wake up the long-running workflow
Views of Expense Report Submitter Home Page Create Expense Submit Expense Home Page Views of Expense Report Approver Inbox View Approve Expense Inbox View
Create Expense Report Task
Approve Expense Report Task

End View End
Task to create an expense report
View
View
Inbox
- Task: Approve Expense Report - Task: Approve Transfer
Task to approve an expense report

Resume Workflow
Start Workflow
Create/Assign Task
Workflow (Business Process )
Workflow may pause; waits for second task to complete

End
Check Limit (Bus Service )
Approval Needed?
Yes
Task Step
No
Process Expense Report
Workflow initiated by first task

17 of 20
Launch Task
Launch Task
39
Siebel Task UI
39.18
Comparison of Task UI and the Standard UI
Consider using Task UI for tasks that:

` Are inherently complex
Lengthy, complex sets of inputs, lots of branching
` ` ` `
Are performed by novice or infrequent users Can take advantage of the the ability to pause and transfer tasks Involve transactional processing Might be integrated with workflows
` Are simpler ` Are performed frequently by power users ` Do not involve transactional processing
18 of 20
Consider using the standard UI for tasks that:
Siebel Task UI
39.19
Module Highlights
Siebel Task UI is a wizard-like interface that guides users through steps in a task Invoke a task from a link in the task pane Use the buttons in the Playbar applet to proceed, return to the previous view, pause, or complete the task
` Paused tasks are resumed from the users inbox
Data collected during a task is not committed to the database
19 of 20
` Until the task is completed ` Or is explicitly committed at specific points in the task
39
Siebel Task UI
39.20
Lab

` Execute a task
20 of 20
Task UI: Creating a Task
40.1
Module 40: Task UI: Creating a Task

40
40
40.2
Module Objectives

` Identify the major components of a task ` Configure a task ` Administer a task

` These are the steps to create and deploy a task
2 of 30
40.3
Creating a Task
Consists of the following activities:

` Configuring several types of Task UI components in Siebel Tools ` Deploying the task to the run-time client ` Administering the task in the run-time client
40
3 of 30

0/3
40.4
Components of a Task
Task Flow Task View Task Group
4 of 30
Reference
Siebel Business Process Framework: Task UI Guide: Task UI Concepts

1/3
40.5
Task Flow

Specifies the flow of a task as a sequence of task steps

` Examples: Siebel operation, business service, and so on
Includes one or more task view steps that display a view to the user Is configured in Siebel Tools using the Task Flow Designer
` Is a visual, declarative editor similar to the workflow designer
40
5 of 30

2/3
40.6
Task View
Is a special type of view used in a task

` Displays data to a user ` Allows user to enter data ` Allows user to navigate using the buttons in the Playbar applet
Consists of one or more applets and the Playbar applet Is invoked in a task view step in a task flow
6 of 30

2/3
40.7
Task View Continued
Differs from standard views

` The view is not displayed in the context of a screen ` The user must use buttons in the Playbar applet to navigate
Clicking any UI element outside the task view and task pane pauses the task and displays the prior standard Siebel view An applet menu The standard record controls such as New, Delete, and Query
` Applets in a task view do not have

40
7 of 30

3/3
40.8
Task Group
Represents a collection of related tasks that can be displayed as a set in the task pane Can be configured to be:
` ` ` `
Associated with a single standard view Available independent of the standard view Restricted to a single application Available across all applications
A task group
Another task group
8 of 30

0/9
40.9
Configuring a Task
1. Configure the Task Flow 2. Create Applets for Task Views 3. Configure the Task Views 4. Bind the Task Views 5. Configure Remaining Task Steps 6. Assign Chapters
40
9 of 30
Reference
Siebel Business Process Framework: Task UI Guide: Configuring Task UI

0/9
40.10
Configuring a Task Continued
7. Create the Task Group 8. Compile the Configured Objects 9. Publish the Task Flow
10 of 30

1/9
40.11
1. Configure the Task Flow
Use the Task Wizard to create a Task object

` Select File > New Object ` Select the Task Tab and click the Task icon ` Enter fields as below:
Name that appears in the task pane Identifies the business object for this task
40
11 of 30

1/9
40.12
1. Configure the Task Flow Continued
In the task Designer, add steps as required

` Drag connectors and anchor them to the steps
12 of 30

2/9
40.13
2. Create Applets for Task Views

Use the Form Applet Wizard to create applets that display a small set of focused data Alternatively, copy an existing applet and delete the unnecessary fields
40
13 of 30

3/9
40.14
3. Configure the Task Views
Use the Task View Wizard to create one or more task views
` View objects with type = Task
14 of 30
Upgrade Behavior
Upgrade behavior is a property of several object types that specifies how the object should be processed when a repository merge is run with an Incorporate custom layout.

3/9
40.15
3. Configure the Task Views Continued

Select a view Web template Assign one or more customized applets Add the Playbar applet to the top and/or the bottom of the view
40
15 of 30

4/9
40.16
4. Bind the Task Views
For each task view step in the flow, assign a task view
` Right-click the task step and select Bind Task View ` Select the view from the list of available views ` Set the button properties for the view
Determines which buttons are disabled in a view Set to Next for all but the final view
16 of 30

5/9
40.17
5. Configure Remaining Task Steps
Configure other types of steps such as:

` Siebel Operation

Identify the business component and operation Set the Defer Write property to TRUE if necessary Set the conditions on each branch
` Decision Point step
Prevents Object Manager from rejecting the record because some required business component fields are not populated
40
17 of 30

6/9
40.18
6. Assign Chapters
Optionally, create chapters to group steps in the task pane Assign each step to a chapter
Assigned to chapter 1
Assigned to chapter 2
18 of 30

7/9
40.19
7. Create the Task Group

Assign the task to an existing (or new) task group

` Groups several tasks in the task pane
Assign the task group to a view

` Assign to the Task Pane View to make the tasks visible in all views
Assign task to task group
40
Assign task group to view Assign to single application if required

8/9
40.20
8. Compile the Configured Objects
Compile the configured objects into the target SRF file
20 of 30

9/9
40.21
9. Publish the Task Flow
Validate the task flow to identify any possible errors

` Right-click and select Validate
40
21 of 30

9/9
40.22
9. Publish the Task Flow Continued
Click the Publish button in the Deployment toolbar to deploy the task flow
` Sets the task flow to complete ` Makes it available for activation
22 of 30

0/3
40.23
Administering a Task
1. Activate the Task Flow 2. Register the Task Flow 3. Add Responsibilities
40
23 of 30
Reference
Siebel Business Process Framework: Task UI Guide: Administering Task UI

1/3
40.24
1. Activate the Task Flow

Navigate to Administration - Business Processes > Task Deployment Select the published task and click Activate
` Makes the task available for use in the client
Alternatively, publish/activate directly from Siebel Tools
24 of 30

2/3
40.25
2. Register the Task Flow

Navigate to Application - Administration > Tasks Create a new record and select the task from the list of published tasks
40
25 of 30

3/3
40.26
3. Add Responsibilities
Add one or more responsibilities to the registered task

` Allows users with the responsibility to see the task in the task pane ` Click Clear Cache to make the task immediately available
Adds task to the Siebel Administrator responsibility
26 of 30
40.27
Testing the Deployment

Click the Tasks button to display the Task pane Verify that the desired task appears Click the task link and execute the task
40
27 of 30
40.28
Module Highlights
Creating a task in Siebel Tools consists of:

` Configuring a task flow

Creating and binding task view steps Assigning steps to chapters
` Adding the task to a task group ` Assigning the task group to a view ` Publishing the task to the run-time client ` Activating the task ` Registering the task ` Adding the task to one or more responsibilities
28 of 30
Administering the task in the run-time client consists of:
40.29
Lab

` Create a task ` Deploy and administer the task
40
29 of 30
40.30
Transient Business Components and Branching
41.1
Module 41: Transient Business Components and Branching
41
41
41.2
Module Objectives

` Describe the role of transient business components and task applets ` Configure branching logic in a task
2 of 24
` Transient business components allow you to incorporate branching logic into task flows and to manage user data that is not mapped immediately to a business component field
41.3
User-Entered Data
Is typically persistent
` Maps immediately to regular business component fields ` Is written to the database during or at the end of the task flow
May be transient
` Is entered and then referenced in a subsequent step in the task flow ` Does not need to be stored persistently
41
41.4
Transient Business Component (TBC)
Is used to represent user input and other data that does not need to persist beyond the lifetime of the task
` ` ` ` ` ` Type is Transient Has one or more single-value fields Does not support joins or multi-value fields Maps to a special table: S_TU_LOG Is based on a special class: CSSBCTaskTransient Stores one record at most
Is managed by the Object Manager
4 of 24
Reference
Siebel Business Process Framework: Task UI Guide: Configuring Transient Business Components
41.5
Uses for a Transient Business Component

Capture user selections that control the flow of a task at run-time Collect data that will be incorporated into persistent data later in the task such as:
` Postal code or telephone area code ` Data that may be conditionally mapped to business component fields in subsequent task steps
Example: an applet that needs to show some quote and order fields
41
Support applets that display data from several business components
41.6
Task Applet
Is a special type of applet used to display and collect transient data

` Maps to a transient business component ` Displays data from only that business component
Can be assigned only to a task view

` Can appear in a view by itself or with one or more standard applets
Task Applet
6 of 24
41.7
Task Applet Continued
Differs from standard applets

` Is always a form applet displaying a single record ` Must be based on grid Web templates
Applets do not display an applet title or applet menu
` Is based on a specialized class: CSSSWEFrameTask
Task applet
41
7 of 24
41.8
Branching in a Task
Task UI framework supports branching (in a task) based on user input Input can be persistent data such as the account type Is implemented by configuring a decision point step
` Follow the same procedure as in a workflow process

Decision point step for branching
Task flow with branching
8 of 24
41.9
Branching in a Task Continued

Input can also be transient data, such as the selection that the user makes when presented a choice about the next step Requires the use of a transient business component Is implemented by configuring a decision point step
User selection is transient data
41

0/7
41.10
Configuring Branching in a Task Using a TBC

1. Modify the Task Flow 2. Create a Picklist 3. Create the Transient Business Component 4. Create the Task Applet 5. Create the Task View 6. Configure the Decision Point Step 7. Complete the Configuration

1/7
41.11
1. Modify the Task Flow

Add a task view step to the flow to allow the user to make a choice Add a decision point step to evaluate the users choice Add connectors to implement the desired business flow
` Example of direct branching

Task view to allow user to make choice Decision point step to evaluate choice
Each branch corresponds to a member in an LOV
A separate task view for each user choice

41

1/7
41.12
1. Modify the Task Flow Continued

` Example of iteration
Loop that adds a note and then asks user to choose again
Decision point step to evaluate choice
Task view to allow user to make choice
Each branch corresponds to a member in an LOV
12 of 24

2/7
41.13
2. Create a Picklist
A picklist is required when the user is presented a set of choices Select an existing picklist if available Alternatively create a new picklist
` Represent the choices as members of a List Of Values type ` Configure the PickList object
41

3/7
41.14
3. Create the Transient Business Component
Use the Transient BusComp Wizard to create the transient business component
` Should use the wizard since it assigns required values to multiple TBC properties
14 of 24

3/7
41.15
3. Create the Transient Business Component Continued
Add one or more fields

` Assign name, type, and length as required ` Do not assign a column
Will be assigned automatically after the record is saved Create the single-value field pick map
` If required, assign the picklist
Assigned automatically by Siebel Tools
Provides choices for user selection
41
15 of 24

4/7
41.16
4. Create the Task Applet
Use the Task Applet Wizard to create the task applet

` Identify the transient business component ` Identify the task in which the applet will be used ` Select the TBC field(s) that are to be displayed
16 of 24

4/7
41.17
4. Create the Task Applet Continued

Inspect the applet in the Web Layout Editor

` Wizard assigns a radio button control to all fields
For fields with a picklist, the radio button control:

Displays the members of the underlying list of values (LOV) Allows users to select a value by clicking a radio button
Control caption, can be edited to include instructions

Radio button control (displays the members of a LOV)

17 of 24
41
For other fields, manually change the HTML type to the desired value Reposition and/or resize the label and control for each field

5/7
41.18
5. Create the Task View
Use the Task View Wizard to create a new task view

` Assign zero or more regular applets as required ` Assign the task applet
Selection is restricted to task applets assigned to the task
` Select and position the Playbar applet
Alternatively, add the task applet to an existing task view
18 of 24
` Drag a Task Applet icon from the Applet pane to an applet placeholder ` Select the desired task applet

6/7
41.19
6. Configure the Decision Point Step

Right-click the decision point step

` Set the name property to a meaningful value
Right-click each connector leading from the decision point step

` Set the label property to a meaningful value as well
41

6/7
41.20
6. Configure the Decision Point Step Continued
Compose the conditions for each connector

` Right-click each connector leading from the decision point step and select Edit Conditions ` Select TBC, field, and desired value for this branch
TBC LOV member
Field
20 of 24

7/7
41.21
7. Complete the Configuration

Configure remaining steps (task views, Siebel operation, and so on) For each task view step, bind the corresponding task view
` Remember to set the Forward Button Type to Next
Assign each step to a chapter Compile all new and modified objects
41
41.22
Test the Modified Task

Validate the task Publish and activate the task Invoke the task in the client and verify that the task applet appears and branches as desired
22 of 24
41.23
Module Highlights
Tasks may include transient data

` Data entered by users that does not need to be stored once the task completes
41
A transient business component is required to store data entered by a user that is not required after the task completes A task applet is required to display data stored in a transient business component A task can include branching based on user entered values including transient data Branching requires adding a decision point step to the task flow
41.24
Lab

` Extend a task to include branching
24 of 24
Siebel Business Rules
42.1
Module 42: Siebel Business Rules

42
42
42.2
Module Objectives

` Describe the Siebel Business Rules architecture ` Use HaleyAuthority to examine business rules

` Siebel Business Rules provides a powerful way to automate business decisions and logic in a Siebel application
2 of 22
42.3
Implementing Business Logic in Siebel Applications
Can often be done using declarative configuration such as:

` Properties in business components and fields
Example: validation and post-default values
` Siebel workflows ` Siebel state models
Occasionally requires custom scripting Can result in:
Difficult to understand the complete set of implemented logic
` Business logic that is represented in multiple ways with different syntax
Difficult to modify to meet new requirements
` The need to compile and deploy a new Siebel repository file (SRF)
3 of 22
42
` Business logic that is distributed throughout the application
42.4
Business Challenge
Companies want a more unified way to implement business logic

` Centralized store of business rules or logic that can be easily modified to incorporate changing business processes ` Reviewable by non-implementers such as business analysts ` Deployable without recompiling the SRF file
Allows updating of business logic at run time
4 of 22
42.5
Solution: Siebel Business Rules
Provides the ability for companies to create and enforce rules that capture their business policies
` Rules are expressed in natural English rather than a script or SQL statements
Rules can be specified and reviewed by business experts
` Rules are centrally developed and administered ` Rules are enforced globally throughout the Siebel application
` Allows rules to be created, updated, and deployed during run time
5 of 22
42
Reference
Siebel Business Rules Administration Guide: About Business Rules
Uses client-side configuration rather than repository-based configuration and compilation
42.6
Examples of Uses of Siebel Business Rules

` Determine if a warranty applies ` Determine if a customer is eligible for a discount or offer and explain why ` Approve or reject an application for insurance ` Compute a limit for loans or insurance coverage
6 of 22
Perform validation of data Provide default values for fields in records Provide default child records Update records Implement dynamic read-only/required behavior Compute values of parameters to be used in decision steps in workflow process and UI tasks Perform business calculations
42.7
Siebel Business Rule
Is a conditional or qualified statement about business entities and characteristics that apply in a business environment
` Is written using the rules of English grammar
if an expense has any expense item which does not have a description then invalidate the expense with "All expense items must have a description"
Conditional rule statement
Set Reimbursable Flag of an expense item to false if the expense items expense item type is Personal unless the expense items description is Pre-approved
Qualified rule statement
7 of 22
42
42.8
Concepts

Are nouns that represent the entities and their characteristics

` Are used to build rule statements
Correspond to business components and fields in the Siebel data model

Concept (represents a business component) Concept (Field)
if an expense has any expense item which does not have a description then invalidate the expense with "All expense items must have a description"
Rule statement
8 of 22
Noun
In traditional grammar, a noun is described as a word or expression that refers to a person, thing, event, place, concept, and so forth.
42.9

Are created using HaleyAuthority Are executed in the Siebel client using a run-time inference engine
9 of 22
42
42.10
HaleyAuthority
Is a separate third-party application used to examine and develop Siebel business rules
` Is installed as part of a Siebel Tools installation ` Is invoked from the Siebel Tools program group
10 of 22
42.11
HaleyAuthority Continued

11 of 22
42
Imports relevant object definitions from the Siebel development repository Generates the corresponding Haley concepts Is used to author the rule statements based on the generated concepts Stores concepts and statements in a separate database referred to as a knowledge base Deploys rules to a set of tables in the Siebel run-time client
42.12
Run-Time Inference Engine

Is a third-party rules engine used to evaluate and execute business rules at run time Is installed automatically in the Siebel client during a standard client installation Is accessed by calling the Business Rules Service business service
` Serves as the interface to the inference engine ` An action set in a run-time event ` A business service step in a Siebel workflow or task ` A business service call in a script
12 of 22
Can be invoked using:
42.13
Exploring Rules
Use HaleyAuthority to examine rules

` Click the Modules & Statements tab to display rule statements
13 of 22
42
42.14
Structure of Rules

Rules are written using English grammar (natural English)

` A given rule can be expressed in several ways
Common practice is to create statements followed by qualifiers that determine if the statement applies
` If: statement applies when at least one if qualifier is true ` Unless: statement does not apply when unless qualifier is true ` Only if: statement applies when all only if qualifiers are true
14 of 22
42.15
Rule Statements
A statement can be either a:

` Statement of fact
Example: An expense report is a valid expense report Set Reimbursable Flag of an expense item to false
` Statement of action
Siebel-specific actions consist of three action types

` Actions: Produce output or modify data in the Siebel application ` Functions: Return a value from the Siebel application
Get profile attribute, get active view name User in task mode, currency is equal to
` Predicates: Return a Boolean value
15 of 22
42
Invalidate with Reason Reference
This action raises an error but does not stop evaluation of rules. Accordingly the message displayed upon completion might contain multiple such error messages. For a list of all of the Siebel supported actions, functions, and predicates refer to Siebel Business Rules Administration Guide: :Reference Topics for Siebel Business Rules.
Set a field value, invalidate with reason
42.16
Concepts
Click the Concepts tab in HaleyAuthority to display the concepts

` Entity: Describes entities (things) in the business model ` Value: Describes characteristics of entities in the business model
16 of 22
Siebel Business Rules uses only these two types of concepts
42.17
Entities
Expand Entity to display the entities

` Represent the business components imported from the Siebel repository
17 of 22
42
Expense and Expense Item business components imported for these rules
42.18
Value
Expand Value and its children types to display the values

` Represent business component fields imported from the Siebel repository ` Are grouped by the type of the field
Expense Item (Boolean) fields imported for these rules
Expense and Expense Item (text) fields imported for these rules
18 of 22
42.19
Phrasings
Consist of short expressions that capture a relationship between concepts

` Typically represent the relationship between a business component and one of its fields or a child business component
Are used to build rule statements
Capture relationship between business component and one of its fields
Capture relationship between parent and child BCs
19 of 22
42
42.20
Concepts in Siebel Business Rules
Concepts are generated automatically using the Siebel Object Importer in HaleyAuthority
` Entities correspond to Siebel objects ` Values correspond to single-value fields of objects
Rules developers must not modify or extend the concepts in any way
20 of 22
42.21
Module Highlights
Siebel Business Rules allows users to create and enforce rules that capture business policies
` Rules are expressed in natural English ` Rules are developed by client-side configuration
Siebel Business Rules consist of:

` Authoring tool accessible from Siebel Tools ` A run-time execution engine accessed by calling a business service
A rules module consists of multiple statements based on a set of predefined concepts, actions, functions, and predicates
` Concepts correspond to business components and fields in the Siebel repository
21 of 22
42
42.22
Lab

` Examine an existing rule
22 of 22
Creating Business Rules
43.1
Module 43: Creating Business Rules

43
43
43.2
Module Objectives

` Create rules using HaleyAuthority ` Deploy and administer rules in the Siebel client ` Invoke rules in the Siebel client

` You perform these steps to create business rules
2 of 28
43.3
Creating Siebel Business Rules
Concepts are generated in HaleyAuthority

` Are based on object definitions in the Siebel repository ` Are created by invoking the Siebel Object Importer
Statements are then written based on the concepts

` Rules developers must not:

Modify the underlying concepts Create additional concepts manually
3 of 28
43

0/4
43.4
Developing Rules
1. Create a New Knowledge Base 2. Import Siebel Object Definitions 3. Create a Rule Module 4. Deploy the Rule Module
4 of 28
Reference
Siebel Business Rules Administration Guide: Creating and Deploying Rules

1/4
43.5
1. Create a New Knowledge Base

Start HaleyAuthority from the Siebel Tools program group Select the ODBC connection string for the new knowledge base
5 of 28
AKB Files
HaleyAuthority also supports using an Access local database for single developer prototyping.
43

1/4
43.6
1. Create a New Knowledge Base Continued
Verify that a base set of Haley concepts appears
No entities yet
6 of 28

2/4
43.7
2. Import Siebel Object Definitions

Invoke the Siebel object importer

` In HaleyAuthority, select File > Import > Siebel Object
Provide the connection information for:

` Master repository data source (source of object definitions) ` Run-time data source (environment where rules will be run)
Example of configuration for importing from sample repository

43

2/4
43.8
2. Import Siebel Object Definitions Continued
On the first import for a new knowledge base the following occurs immediately:
` Object definitions relating to currency and currency code are imported ` Concepts to support Siebel currency calculation procedures are created ` Siebel-specific actions, functions, and predicates are created
8 of 28
Currency Calculations
Siebel applications manage currency using amounts, currency codes, and exchange rates. Rules that include references to currencies must use callbacks (actions and functions) to the Siebel application for currency operations. These operations are not supported using the base set of Haley actions and functions.

2/4
43.9
After currency-related concepts are created:

` Select Import Siebel Objects ` Specify the Siebel Business Object ` Select the business component and, possibly, child business components ` For each selected business component, select one or more fields
Business components and fields required for the expense report rules discussed in the previous module
43

2/4
43.10
2. Inspect Concepts
Inspect the output window to verify that corresponding nouns, concepts, and phrasings were created
10 of 28

2/4
43.11
2. Inspect Concepts Continued

In the Concepts tab, expand entity and value Verify that the entities and values corresponding to the objects and fields have been created Inspect the phrasings
` Should be of the form a <BusComp> has a <Field> and equivalents
11 of 28
43

2/4
43.12
Additional import considerations

` Entities are used to represent business components

Parent and child business components that are selected explicitly Business components that are referenced in multi-value fields
` Values are used to represent singlevalue fields
Are categorized by the field type

` Example:

DTYPE_TEXT value: string DTYPE_PHONE value: string DTYPE_INTEGER value: number
` Several Siebel field types cannot be converted
Are not displayed in the list of selectable fields
12 of 28
Field Mappings
For a list of all of the mappings (including fields types that can not be converted) refer to Siebel Business Rules Administration Guide: Reference Topics for Siebel Business Rules.

3/4
43.13
3. Create a Rule Module
A module is a collection of rule statements that are deployed together

` Suggestion:

Create a rule module to contain only the statements that need to be evaluated as a set by the rules engine Name the rule module to indicate how the module will be invoked
A module can be divided into submodules to improve readability
13 of 28
43

3/4
43.14
3. Create a Rule Module Continued

Click the Modules & Statement tab Add a new module (and submodules if desired)
Module
14 of 28
Submodules

3/4
43.15
Add one or more statements

` Use the Edit Statement dialog box to enter the statement

Text is bolded if it can be parsed, that is if the words entered correspond to defined concepts and phrases A list of eligible words is presented at all times
Enter text Allowable words based on phrasings
15 of 28
43

3/4
43.16

Add applicability conditions to specify when the statement applies Edit statements until all content parses
Right-click Applicability to select condition
16 of 28

4/4
43.17
4. Deploy the Rule Module
Invoke the Siebel Deployer

` In HaleyAuthority select Tools > Siebel Deployment ` Verify the connection parameters for the run-time data source ` Select the modules to deploy and click OK
17 of 28
Siebel Deployer
The Siebel Deployer is a HaleyAuthority plug-in that allows developers to deploy to a run-time environment rule modules that they created.
43
43.18
Administer Deployed Rules

In the Siebel client, navigate to Administration - Business Rules > Rule Modules List Select the deployed rule module Specify the business object that will provide data to the run-time rules engine
` Should be the business object specified for object import
18 of 28
Reference
Siebel Business Rules Administration Guide: Configuring and Activating Rule Modules
43.19
Administer Deployed Rules Continued
Create one or more Rule Module Relation records

` They identify the business components necessary to evaluate the rules
Click New and select the records that specify the parent-child relationships captured in the rules
19 of 28
Inconsistent
A value of Y in the Inconsistent field indicates that the data model and Siebel repository and the concepts in the knowledge base are no longer consistent. In this event, the models need to be resynchronized before the rule module can be administered.
43
Data Assertion Mode This fields indicates whether the complete set of Siebel data should be provided to the rules engine at once or smaller sets of data can be provided. This is relevant when the rules iterate over a set of records.
43.20
Activate Rules
Click the Activate button in the Rule Modules list applet to set the status to active
` Only active rules are evaluated by the rules engine
20 of 28
Status changes to Active
43.21
Invoking the Rules Engine
The rules engine is accessed by calling the Business Rule Service business service
` Can be invoked using an action set for a run-time event
21 of 28
43
43.22
Creating a Run-Time Event Action Set

In the Siebel client, navigate to Administration - Runtime Events > Action Sets Create a new action set, and a child action of BusService type
Action set
Action for the action set

Reference
Siebel Business Rules Administration Guide: Integrating Rules with Siebel Runtime Events
43.23
Creating a Run-Time Event Action Set Continued
In the More Info applet

` Specify Business Rule Service and RunRules as the business service name and method ` Specify the rule module name as the context
23 of 28
43
43.24
Creating a Run-Time Event Action Set Continued

Navigate to Administration - Runtime Events > Events Create an event record for the business component
` Specify the desired run-time event ` Assign the action set
Select Reload Runtime Events from the applet menu
Action set
Run-time event
24 of 28
43.25
Test the Rule Module

Create a record and trigger the run-time event

` Verify that the desired business logic is executed
Create additional records as required to fully test the rules
25 of 28
43
43.26
Additional Ways to Invoke the Rules Engine
The business rules service can be invoked:

` In custom scripts ` In business service steps in Siebel workflows and tasks
Invokes rules engine to determine the lead quality
26 of 28
Invoking the Rules A limitation of this release is that custom scripting is required to extract the Engine in a Workflow arguments returned by the Business Rules Service business service. Consult Bookshelf for an example of such a custom script.
43.27
Module Highlights
Create rules by:

` Creating concepts by importing business components and fields from the Siebel repository ` Building statements based on the concepts
Deploy the rules module to the Siebel run-time client Activate the rules in the client Invoke the rules by using a run-time event
27 of 28
43
Configure an action set
43.28
Lab

` Create a new rule

Import a set of Siebel objects Create the rule module Deploy and administer the module Create an action set triggered by a run-time event
28 of 28
Introducing Siebel Assignment Manager
44.1
Module 44: Introducing Siebel Assignment Manager
44
44
44.2
Module Objectives

` Explain the role of Siebel Assignment Manager ` List the elements used to create rules that assign business data

` Your company may have rules and policies about how to assign data that can be automated using Siebel Assignment Manager
2 of 20
44.3
Business Challenge
Companies need to assign business data in a timely fashion and in a way that consistently follows their business rules and policies
` ` ` ` Sales leads Contacts Accounts Service requests
` Large volumes of data ` Short response times ` Multiple rules and policies

Complex Conflicting
3 of 20
44
Typical characteristics
44.4
Business Solution: Siebel Assignment Manager

Allows companies to automatically assign business data to the most appropriate positions, people, and organizations Consists of:
` Administrative functionality to define assignment rules ` Server components to automatically assign business data according to the rules
4 of 20
Reference
Siebel Assignment Manager Administration Guide
44.5
Assignment Rules
Assignment Manager uses assignment rules to assign data

` Rules assign one or more candidates to assignment objects based on one or more criteria
Assignment Objects
Skills Expertise Availability Product Workload Sales Territory
Criteria
5 of 20
44
Accounts Campaigns Service Requests Product Defects Opportunities Activities
Candidates
Employees Positions Organizations
44.6
Assignment Objects
Assignment objects identify the type of data being assigned Several assignment objects are pre-configured in the asdelivered application
` Examples:

Account Contact Service Request
6 of 20
44.7
Assignment Candidates
Candidates are instances of entities to which data can be assigned

` Position ` Employee ` Organization
Examples of candidates for pre-configured objects:
Types of candidates must be consistent with the allowed access control mechanisms for the object
7 of 20
44
` Accounts can be assigned to both positions and organizations ` Activities can be assigned to employees ` Service Requests can be assigned to both employees and organizations
44.8
Assignment Criteria
Criteria express conditions that must be satisfied for data to be assigned

` Are expressed in terms of attributes of objects and/or candidates ` Examples:

Account State = CA Account Product = a product that candidate has expertise for
Rules often include multiple criteria
8 of 20
44.9
Administering Assignment Rules
Rules are created and administered using the Siebel Web Client
` Are not part of the Siebel repository ` Are not compiled into the .srf file ` Can be deployed during run time
9 of 20
44

0/2
44.10
Examples of Assignment Rules
Assign Accounts by Sales Region Assign Service Requests to Skilled Agents
10 of 20

1/2
44.11
Assign Accounts by Sales Region

ABC Company assigns accounts to its sales organization ABC Company also assigns accounts to its sales reps by sales region
` Opportunities in the Western Region (CA, OR, WA) are assigned to Sales Rep West ` Opportunities in the Eastern Region (CT, MA, ME, NH, RI, VT) are assigned to Sales Rep East
ABC Sales Organization VP Sales - US Pat Sales Rep West Alex Sales Rep East Jane
11 of 20
44

1/2
44.12
Rule to Assign Accounts by Sales Region
Rule includes
` Candidates (desired organization and positions) ` Criteria for determining region to assign the account
Rule: Assign East Accounts
Object: Account
Position candidate Organization candidate Rule applies when
Criteria: Account State is one of CT,MA,ME,NH,RI,VT
12 of 20
Candidates: Sales Rep East Sales Organization

1/2
44.13
Rule to Assign Accounts by Sales Region Continued
A separate rule is required for each sales region
Rule: Assign West Accounts

Object: Account Candidates: Sales Rep West Sales Organization Criteria: Account State is one of CA,OR,WA
This rule applies when
Rule: Assign East Accounts

Object: Account Candidates: Sales Rep East Sales Organization Criteria: Account State is one of CT,MA,ME,NH,RI,VT
This rule applies when
13 of 20
Territory
Territory is another name for sales region. Formally, a territory is a collection of accounts, contacts, and or assets that are managed by a team of positions. Most often a territory is based on a geographical area such as states.
44

1/2
44.14
Candidates for Rules

Two assignment rule records are created Candidates are listed in the Position Candidates view
14 of 20

1/2
44.15
Criteria for Rules
Applicable states are listed in the Criteria view
15 of 20
44

2/2
44.16
Assign Service Request to Skilled Agents
XYZ company assigns service requests to employees with the correct skills to resolve them
` Skills are properties that reflect the candidates abilities in various areas such as:

Product expertise Installation and upgrade skills Languages Service Organization
VP Service Chris (no skill)
Service Agent 1 Craig (Network)

Service Agent 2 Ellen (CPUs)
Service Agent 3 Jack (Power supplies)

16 of 20

2/2
44.17
Assign Service Request to Skilled Agents Continued
Rule includes
` Criteria for assigning request
Employee skill matches the area of the service request Can list select employees or consider all available employees Rule: Assign Service Request
Candidates: All service agents Criteria: Candidates product skill = product associated with Service Request
` Candidates to be considered
Employee candidates Rule applies when
17 of 20
44
Object: Service Request
44.18
Running Assignment Manager
Assignment Manager can be invoked in three modes

` Batch Assignment: Can be used to submit batches of data for onetime assignment or reassignment ` Dynamic Assignment: Automatically invokes Assignment Manager to assign data in near real time as records are created or modified ` Interactive Assignment: Can be used to manually assign candidates in real time
18 of 20
Enabled for Service Request and Activity assignment objects
44.19
Module Highlights
Siebel Assignment Manager allows companies to automatically assign business data to the most appropriate positions, people, and organizations Assignment rules are used to assign candidates to objects
` Include assignment objects, candidates, and criteria
19 of 20
44
44.20
Creating Assignment Rules
45.1
Module 45: Creating Assignment Rules
45
45
45.2
Module Objectives

` Create an assignment rule that assigns sales data to a sales team ` Create an assignment rule that assigns service data to a skilled employee ` Test assignment rules
2 of 28
` Assignment Manager uses rules to assign data to candidates
45.3
Assignment Rules
Assign one or more candidates to assignments objects based on one or more criteria Are specified using several key concepts
Who to consider as candidates
Captures the criteria aspect of the rule
3 of 28
Reference
Siebel Assignment Manager Administration Guide: Assignment Rule Administration
45
How to pick the assignee from the qualified candidates
45.4
General process to create assignment rules:

` ` ` ` Design the rule Create the rule record Define the criteria Specify the candidates
4 of 28

0/4
45.5
Example: Assigning Data by Sales Region
1. Design the Assignment Rules 2. Create the Rule 3. Specify the Criteria 4. Specify the Candidates
5 of 28
45

1/4
45.6
1. Design the Assignment Rules
Determine the criteria to identify each sales region

` Example: Sales regions are based on account state
East region includes MA, VT, NH, ME, RI, CT
Determine the candidates to be assigned in each sales region

Region
East (CT, MA, ME, NH, RI, VT)
Positions
Sales Rep - East Sales Mgr - East Sales Rep - West 1 Sales Rep - West 2
West (CA, OR, WA)
6 of 28

2/4
45.7
2. Create the Rule

Navigate to Administration - Assignment > Assignment Rules List Create a new rule for each sales region
` ` ` `
Select the assignment object Set Person Candidate Source to From Rule Select the Assignee Filter Assign a rule group
Consider only the candidates listed in rule
Specify Default Group if not rule groups
Assigns multiple qualifying candidates

7 of 28
45

3/4
45.8
3. Specify the Criteria

Drill down on the rule In the Criteria view, create a new Rule Criterion to be used to assign data
` Example: Only opportunities with an account state in the East region will be assigned
Specify the Comparison Method Specify the attribute value(s) to be used in the comparison
Compares Account State to the list below
8 of 28

4/4
45.9
4. Specify the Candidates

Navigate to the Position Candidates view Add a new record for each position to be assigned Optionally assign organizations using the Organization Candidates view
Specify one or more positions

45

0/5
45.10
Example: Assigning Service Data to Employees
1. Design the Assignment Rule 2. Create the Rule 3. Specify the Criteria 4. Specify the Candidates 5. Associate Skills with Candidates
10 of 28

1/5
45.11
1. Design the Assignment Rule
Determine the criteria to assign a candidate to a service request

` Matching criteria include:

Skill match Location Availability Workload
Determine the set of eligible candidates
Object: Service Request Candidates: All service agents Criteria: Candidates product skill = product associated with service request
11 of 28
45
` Alternatively consider all available employees

2/5
45.12
2. Create the Rule

Navigate to Administration - Assignment > Assignment Rules List Select the assignment object Set Person Candidate Source to All People Set Assignee Filter to One, Best Fit Assign a rule group
Consider all employees
Assign only one candidate
12 of 28

3/5
45.13
3. Specify the Criteria

Drill down on the rule In the Criteria view, create a new rule criterion to be used to assign data
` Example: Consider employees only if they are skilled in the product associated with the SR
Specify the comparison method
Qualify only employees with product skill
13 of 28
45

4/5
45.14
4. Specify the Candidates
When considering a restricted set of candidates for assignment, set Person Candidate Source = From Rule
` Navigate to the Employee Candidates view ` Add a new record for each employee to be considered
Otherwise set Person Candidate Source = All People

` Do not explicitly add any employees to rule
Do not add any employees


5/5
45.15
5. Associate Skills with Candidates
Navigate to Administration - User > Employees Assignment Skills

` Skills are employees attributes that can be used in assignment
Select a skill and assign one or more values that apply to the user
Areas of expertise
Specific skills in the area

45

0/4
45.16
Overview of Key Concepts
Person Candidate Source Comparison Method Scoring Assignee Filter
16 of 28

1/4
45.17
Person Candidate Source
Determines the set of possible candidates that can be assigned to data by this rule
Candidate Source All People Action Consider every employee/position as a candidate Consider only employees/positions listed explicitly as a candidate in the rule Consider the members of a team as candidates Implements dynamic assignment
From Rule
Team Name
17 of 28
45

2/4
45.18
Comparison Method
Determines how a rule is evaluated

` Expressed in terms of object and candidate attributes
Comparison Method Compare to Object Compare to Person Compare Object to Person Compare to Organization Compare Object to Organization Action Checks if a record attribute matches a value specified in rule Checks if a person attribute matches a value specified in a rule Checks if a record attribute matches that attribute of an employee or position candidate Checks if an organization attribute matches a value specified in a rule Checks if record attribute matches that attribute of an organization candidate
18 of 28

3/4
45.19
Scoring
Is a mechanism used to rank candidates for potential assignment

` Rules can specify passing scores ` Assign higher scores to more important criteria and lower scores to less important criteria
Add this value to candidates score if candidate qualifies
19 of 28
45

4/4
45.20
Assignee Filter
Determines how candidates that qualify are selected for assignment

` Multiple candidates might qualify ` Some rules may allow multiple candidates to be assigned
Assignee filter All, above minimum All, must assign Action Assign all candidates with a score higher than the rules passing score Assign the highest scoring candidate as well as any others with scores higher than the rules passing score Assign the candidate with the highest score (must score higher than the rules passing score) Assign a single qualifying candidate by random selection
One, best fit One, random
20 of 28

0/5
45.21
Testing Assignment Rules
After creating a rule, run Batch Assignment to test the rule 1. Release Assignment Rules 2. Enable Detailed Logging 3. Run a Batch Assignment 4. Examine the Assigned Records 5. Inspect the Assignment Log Files
21 of 28
45

1/5
45.22
1. Release Assignment Rules
In the Assignment Rules List view:

` Verify that the rule has not expired ` Click Release to update the list of rules used by Assignment Manager
A rule must be released again every time it is modified
All rules are active and are released
22 of 28

2/5
45.23
2. Enable Detailed Logging
Navigate to Administration - Server Configuration > Servers > Components

` Select Batch Assignment ` Set Log Level for Object Assignment and Rules Evaluation to 4
Log levels can range from 0 to 5 in order of increasing detail
23 of 28
45

3/5
45.24
3. Run a Batch Assignment

Navigate to Administration - Server Management > Jobs Create a Batch Assignment job and submit the request
Specify assignment object for this job


4/5
45.25
4. Examine the Assigned Records

Navigate to the list view for the data assigned Inspect the records and verify that the desired assignments were made
Has expertise in this product
25 of 28
45

5/5
45.26
5. Inspect the Assignment Log Files
Navigate to the Siebel Server log directory to locate the log file generated by the Batch Assignment job
` Detailed log files document:

How each rule is evaluated and why it failed or passed Whether the candidates from each passed rule qualify How the assignees are determined from the list of qualified candidates
26 of 28
45.27
Module Highlights
General process to create assignment rules:

` ` ` ` Design the rule Create the rule record Define the criteria Specify the candidates Releasing the rule Running a batch assignment Examining the assignment records Inspecting the assignment log files
Test assignment rules by:
Enable an appropriate level of detailed logging
27 of 28
45
` ` ` `
45.28
Lab

` Create assignment rules ` Test the rules
28 of 28
Tailoring Assignment Manager Behavior
46.1
Module 46: Tailoring Assignment Manager Behavior
46
46
46.2
Module Objectives

` Describe the steps in the assignment methodology ` Prioritize rules using exclusive rules and rule group sequencing ` Modify the behavior of an assignment object
2 of 28
` Developing effective rules requires an understanding of the ways assignments rules can be tailored
46.3
Assignment Methodology
Refers to the steps followed by Assignment Manager to assign candidates to objects Simplified representation (does not contain all steps)
` Identify rules that apply ` Identify a list of qualified candidates for the applicable rules ` Determine primary assignee and assign candidates
3 of 28
Reference
Siebel Assignment Manager Administration Guide: Overview of Siebel Assignment Manager
46
For more details, consult the Assignment Methodology section in the Siebel Assignment Manager Administrative Guide
46.4
Identify Rules That Apply
Assignment Manager evaluates all rules that apply to the object

` Eliminates rules that fail the Compare to Object criteria
Example: Value of Required field determines if rule qualifies
` Multiple rules may survive
Always: Rule qualifies if and only if State = CA, OR,or WA Never: Rule qualifies regardless of state When Available: Rule qualifies if state not specified or State = CA, OR,or WA
4 of 28
46.5
Identify Qualified Candidates
For each rule that passes, Assignment Manager generates a list of qualified candidates
` Evaluates the candidates specified in the rule using criteria:

Compare to Person/Organization Compare Object to Person/Organization
` Scores each candidate ` Applies the Assignee Filter
Determines how to process qualifying candidates for the rule
5 of 28
46
46.6
Score Candidates
Scores can be defined for many parameters:

Item Scored Action To apply the score to the candidates total score when the candidate meets the rule criteria To rank criteria from the most important to the least important To rank criteria values from the most important to the least important To rank the best candidate from a group of qualified candidates To distribute workload across all candidates
The higher the candidates current workload is, the lower his/her score is
Assignment rule Criteria Criteria values Candidate Workload distribution
6 of 28
46.7
Score Candidates Continued
A candidates score is the sum of the individual scores
Candidate total score = 40 Candidate total score = 35 so both candidates qualify as each score exceeds the passing score
7 of 28
46
46.8
Assign Candidates
Assignment Manager:
` Generates assignments using the Assignees Filter from the rule with the highest scoring assignee ` For team-based assignment, the highest-scoring qualifying candidate from the highest-scoring rule is made primary
Rule may optionally identify the primary explicitly
Will be assigned as primary (total score = 40)
8 of 28
46.9
Workload Distribution

Is used to distribute work among qualified candidates

` Prevents individuals from being overloaded with work
Consists of:
` Workload Distribution Rule ` Maximum Workload ` Score
9 of 28
46
46.10
Service Scenario
Business Rule: Assign service requests to agents based on product skill and current workload
Assign incoming service requests to the appropriate candidate
Employee: Craig Skill: Network Workload: 18 SRs
Employee: Ellen Skill: CPU Workload: 10 SRs
Employee: Jack Skill: Network Workload: 20 SRs
10 of 28
46.11
Workload Distribution Rules

Balance workload across candidates Assign a computed score to candidates based on:
` Maximum Workload: the maximum number of service requests that a candidate should own at any time ` Score: the weight assigned to workload in comparison to other criteria
11 of 28
46
46.12
Calculating Scores for the Scenario
Compute a workload score and add it to other scores

` Assign a score for product skill
Service Request Product = Network
Assign incoming network service request to Craig
Employee: Craig Skill: Network Workload: 18 SRs Employee: Ellen Skill: CPU Workload: 10 SRs Employee: Jack Skill: Network Workload: 20 SRs
Employee Craig Ellen Jack
Product Score 20 0 20
Employee Workload Score Score * [1 (Current Workload / Max Load)] 45 * [1 (18 / 20)] = 4.5 Craig is 45 * [1 (10 / 20)] = 22.5 assigned 45 * [1 (20 / 20)] = 0
Total Score 24.5 22.5 20

12 of 28
46.13
Rule Prioritization
Multiple assignment rules may exist for the same assignment object
` Can result in qualified candidates from both rules being assigned
Business policies may require that candidates from only a single rule be assigned
Assign Opportunities based on Account State to the state sales office Assign Opportunities based on Account Industry to only the industry specialists
Only positions from this rule should be assigned
13 of 28
Reference
Siebel Assignment Manager Administration Guide: Assignment Rule Administration
46
46.14
Exclusive Rules
Rules can be marked exclusive to prioritize them

` Results in only the qualified candidates from that rule being assigned
All rules are first evaluated and scored as before

` Exclusive rule must first pass and have qualifying candidates
Set flag to make rule exclusive
14 of 28
46.15
Multiple Exclusive Rules
When several exclusive rules have qualifying candidates, the rule with the highest scoring candidate prevails
` Keep qualifying assignees from only that rule
When two or more exclusive rules tie for highest score, none of the rules prevail
` Only the default candidate is assigned ` Design exclusive rules carefully to avoid such behavior
15 of 28
46
46.16
Sequencing Rules
Rules within a rule group can be sequenced to prioritize them

` A rule group is a named collection (or subset) of assignment rules

A rule can appear in one and only one group Rules not explicitly assigned to a group belong automatically to the Default Rule Group
16 of 28
Defines rules groups
46.17
Rule Sequence
Specifies the order in which Assignment Manager evaluates rules in a group

` Rules with the same sequence number are evaluated in unspecified order ` Rules with no sequence number are considered to have a sequence number of 0
Rule evaluated first
Two rules evaluated next Rule evaluated last
17 of 28
46
46.18
Rule Sequence Continued
Assignment Manager pauses after evaluating rules with a given sequence number
` Stops if an assignment can be made ` Otherwise, continues to rules with next higher sequence number
Permit hierarchical assignment strategies

` For example:

18 of 28
Assign opportunity first to a qualifying local office If not, then to a district office If not, then to a regional office If not, then to headquarters
46.19
Run-Time Behavior of Assignment Manager
Is determined by the Assignment object definition

` Is located in the repository ` Is configured individually for each assignment object
70 plus properties
19 of 28
Reference
Siebel Assignment Manager Administration Guide: Advanced Assignment Manager Configuration
46
46.20
Assignment Mode
Specifies how candidates are assigned when a rule assigns both positions and organizations
Assign positions and organizations independently Assign only positions/organizations pairs that both qualify
Assign organizations first and consider only corresponding positions Assign positions first and consider only corresponding organizations
20 of 28
46.21
Default Candidate
Is a predefined position/employee who is assigned in the following situations:

` Conflict between two rules with same score

Assigns candidates for both rules and assigns the default candidate to the team Makes default candidate the primary for team-based assignments Assigns default candidate to the team as primary Assigns default candidate to the team as primary
` Conflict between two exclusive rules with the same score ` Rules do not identify any candidates to assign
21 of 28
46
46.22
Default Candidate Continued
Is specified as properties of the Assignment Object definition

` ` ` ` Default Employee Default Group Default Org Default Position
22 of 28
46.23
Keep Creator
If this property is set to TRUE, Assignment Manager keeps the creator of the record on the team regardless of which rules pass
Keep creator on team
23 of 28
46
Assign positions/employees Assign to data positions/employees to data
46.24
Configuring Assignment Manager Objects
Use Siebel Tools to edit object definitions to modify the behavior of Assignment Manager
` Same as editing other object definitions
24 of 28
46.25
Assignment Manager
Reads Assignment object from repository tables (not the repository file) at run time
` No need to compile the Assignment object itself ` Can deploy a modified Assignment object at run time
25 of 28
46
46.26
Module Highlights
Assignment methodology refers to the steps followed by Assignment Manager to assign candidates to objects
` ` ` ` Identify rules that apply Identify a list of qualified candidates for the applicable rules Scoring candidates Determine primary assignee and assign candidates
` Rules can be prioritized by

Marking a rule as exclusive Sequencing rules
Run-time behavior of Assignment Manager is specified by the configuration of the assignment object
26 of 28
Workload rules can be used to distribute work among qualified candidates Multiple assignment rules may exist for the same assignment object
46.27
Lab

` Create prioritized rules ` Modify the run-time behavior of Assignment Manager
27 of 28
46
46.28
Invoking Siebel Assignment Manager
47.1
Module 47: Invoking Siebel Assignment Manager
47
47
47.2
Module Objectives

` List the modes in which Assignment Manager can be invoked ` Invoke Assignment Manager in dynamic mode

` You need to enable your Siebel environment to support dynamic assignment management
2 of 16
47.3
Running Assignment Manager
Assignment Manager is invoked in three modes:

` Batch Assignment ` Dynamic Assignment ` Interactive Assignment
All modes require that the Assignment Manager component group be enabled
3 of 16
Reference
Siebel Assignment Manager Administration Guide: Running Assignment Manager
47
47.4
Batch Assignment
Is used to submit batches of data for one-time assignment or reassignment Is implemented via a server task Business scenarios:
4 of 16
` Change assignment rules and reassign existing objects that are already assigned ` Sales region or territory realignment ` Existing assignments are inaccurate ` After a batch data load
47.5
Dynamic Assignment
Automatically invokes Assignment Manager to assign data in near real time as records are created or modified Business scenarios:
` Whenever a service request is created, assign it to a service agent with the appropriate product skill ` Whenever an opportunity is created, assign it to the sales representative who handles that territory
5 of 16
47
47.6
Dynamic Assignment Continued
Is implemented using:
` ` ` ` Assignment policies Generate Triggers Workflow Monitor Agent Assignment Manager
Is similar to workflow policies

` Both execute asynchronously on the server
6 of 16
47.7
Assignment Policies
Specify which objects are to be assigned Are expired by default
` Navigate to Site Map > Administration Assignment > Assignment Policies ` Remove the expiration date to activate policies
7 of 16
47
47.8
Generate Triggers

Is a server task that creates database triggers

` Builds triggers for all active assignment policies
Must be run after policies are activated
Requires a user with privileges to add triggers to the database

47.9
Start Workflow Monitor Agent and specify:

` Group Name (the group of assignment policies you activated) ` Sleep Time (interval in seconds between iterations)
Follow steps used in enabling workflow policies
9 of 16
47
47.10
Assignment Manager

Is invoked by Workflow Monitor Agent

` Assignment Manager server component must be online
Performs the assignment of data to candidates
10 of 16
47.11
Dynamic Assignment Process Flow
Is similar to the flow for workflow policies

Account created Triggers fire when conditions satisfied and write record
Create triggers corresponding to assignment policies
S_ESCL_REQ
Generate triggers
Makes assignments
Assignment Manager
Evaluate the assignment rules
Server Request Broker

Monitors S_ESCL_REQ table for changes and invokes Assignment Manager
11 of 16
47
Siebel Database
47.12
Interactive Assignment

Is used to assign candidates in real time

` Enabled for Service Request and Activity assignment objects
Business scenarios:
` A customer service representative receives a call and creates a new service request, then clicks Assign to find the right person to work on that service request ` A field service supervisor wants to find the right person to work on a repair activity, and uses Interactive Assignment to obtain a list of people with the right skills to perform the repair
12 of 16
47.13
Using Interactive Assignment
Implemented via user interaction and tasks on server

` User makes assignment from a generated list of candidates
1. Select the work to be assigned
2. Click Menu and select Assign
3. Select employee and click Assign
13 of 16
47
47.14
Requirements for Interactive Assignment
Verify that Assignment Manager is online and Server Request Broker is running
Performs Assignment
Brokers client requests

47.15
Module Highlights
Assignment Manager is invoked in three modes

` Batch Assignment: Is used to submit batches of data for one-time assignment or reassignment
Is implemented by submitting a job request
` Dynamic Assignment: Is used to assign data in near real time as records are created or modified
Is implemented using:
` Interactive Assignment: Is used to assign candidates in real time
Is implemented via user interaction and tasks on server
15 of 16
47
` ` ` `
Assignment policies Generate Triggers Workflow Monitor Agent Assignment Manager
47.16
Lab

` Create new service records and verify that they are dynamically assigned to the desired employee
16 of 16
State Models
48.1
48
Module 48: State Models

48
State Models
48.2
Module Objectives

` Describe how state models can enforce business logic ` Create a new state model

` A state model is a simple declarative way to enforce business logic that involves changes to values of certain fields in a business component
2 of 18
State Models
48.3
Business Entities and Life Cycles
48
Many business entities have a defined life cycle described by:

` A set of states named by the values of one of the entitys fields ` A set of allowed transitions between the states
For example: A service request could have a life cycle defined in terms of these values of the status field:
` Open, Pending, Closed, Cancelled
Arrow indicates a permitted transition State
Open
Pending
Closed
Cancelled
State Models
48.4
Business Challenge
A companys business policies may restrict transitions between states

` Direct transitions between all pairs of states may not be permitted ` Not everyone may be permitted to invoke a specific transition ` There may be conditions that must apply before a transition can occur
Open
Owner must be assigned
Pending
Closed
Permitted only if severity <> critical
Permitted only by call center manager
Cancelled
Need a way to easily incorporate such restrictions into the life cycle of an entity
State Models
48.5
Business Solution
48
A state model captures and enforces such restrictions on transitions

` Uses a set of rules and conditions that specify allowed transitions
Uses declarative configuration as opposed to script Does not involve compiling and deploying a new SRF file
` Is implemented in the Siebel client and not Siebel Tools
5 of 18
Reference
Siebel Applications Administration Guide: State Models
State Models
48.6
State Model
A state model consists of:

` A set of states corresponding to the values of a single-value field
Must have a bounded picklist declared in the List Of Values table
State field
States for this state model
6 of 18
State Models
48.7
State Model Continued
48
A state model also consists of:

` A set of allowed transitions that can be restricted

Only can be executed by authorized positions Only can be executed when a condition is satisfied
Unrestricted Condition on transition Only selected positions allowed to make transition

State Models
48.8
Enabling Siebel State Model
Only a small number of business components are enabled for state model in the as-delivered application
` Indicated by a business component user property (State Model, Y)
Other business components can be enabled for state model

` Business component class is restricted to CSSBCBase
8 of 18
State Models
0/6
48.9
Creating a State Model
48
1. Define the Desired Life Cycle 2. Create a New State Model 3. Specify the Allowed States 4. Specify the Allowed Transitions and Restrictions 5. Specify Authorized Positions 6. Test the State Model
9 of 18
State Models
1/6
48.10
1. Define the Desired Life Cycle

Review relevant business policies to identify restricted transitions Document the allowed transitions and corresponding restrictions
Permitted only if severity <> critical
Owner must be assigned
Permitted only by call center manager
Cancelled
10 of 18
Open
Pending
Closed
State Models
2/6
48.11
2. Create a New State Model

Navigate to Administration - Application > State Models Create a new state model record
48
` Specify the business component and state field
11 of 18
State Models
3/6
48.12
3. Specify the Allowed States

Navigate to the States view Create a record for each allowable value of the state field
` Specify one state as the default initial state in which new records are created
Set by default
State Models
4/6
48.13
4. Specify the Allowed Transitions and Conditions

Navigate to the Transitions view Create a record for each allowable transition
48
` Select the from and to states using the drop-down list ` Indicate if there are restrictions on who can execute the transition ` Specify any conditions to be satisfied before transition can occur
1. Select the from state
2. Select the to state
3. Deselect Public if transition restricted
4. Add any additional conditions on transition
13 of 18
State Models
5/6
48.14
5. Specify Authorized Positions
For any transitions not marked Public, specify the positions that are permitted to execute the transition in the Authorized Positions applet
Transition restricted
Specify positions allow to make the transition

State Models
6/6
48.15
6. Test the State Model
48
Make sure the state model activation and expiration dates are valid
` Only one state model based on a given field can be active at any given time
Create one or more test records and verify that the business policy is correctly implemented
New process reads the updated state model cache
15 of 18
` New state model is effective when a new application object manager process starts
State Models
48.16
Module Highlights

A state model restricts the life cycle of a business component

` Defines a set of states and allowed transitions between the states
State models:
` Are built in the Siebel client using declarative configuration ` Do not require recompiling the .srf file
Transitions between states can be restricted as follows:
A few as-delivered business components are enabled for state model

` Customers can enable others for state model if the business component class is CSSBCBase
16 of 18
` Not allowed at all ` Allowed under only certain conditions ` Allowed by only certain positions
State Models
48.17
Lab
48

` Create and test a state model
17 of 18
State Models
48.18
Introducing Enterprise Integration Manager
49.1
49
Module 49: Introducing Enterprise Integration Manager
49
49.2
Module Objectives
After completing this module you will be able to:
` Describe the features of Enterprise Integration Manager (EIM) ` Describe how EIM supports referential integrity ` Describe why direct SQL statements must not be used to insert user data
2 of 16
` EIM enables you to properly import external data into the Siebel database
49.3
Enterprise Integration Manager (EIM)
Business Challenge: To exchange large volumes of data between an external application and the Siebel database
` Implementation project challenge: To perform an initial data load for a Siebel application
49
Business Solution: Enterprise Integration Manager (EIM)

` Is a server component that moves large volumes of data in batch mode between Siebel interface tables and Siebel base tables
Siebel Database External Database SQL Utility Siebel Interface Tables
EIM
Siebel Base Tables
Exchanging Data
To exchange large volumes of data, a SQL utility copies mainframe updates to EIM interface tables, and then EIM runs a batch job to synchronize the Siebel account data.
Interface tables act as a staging area for external data
49.4
User Data
The Siebel database contains several types of data:

` Seed data: application data populated during product installation ` Repository data: metadata initialized at installation and modified during application configuration ` User data: user-supplied data, such as account records, contacts, price lists, or assignment rules
EIM is only used to move user data

Siebel Database
Seed data
Repository data
User-supplied data such as account information, contacts, or price lists

User data
4 of 16
49.5
Populating and Managing User Data

Use the client application to enter, update, or delete small amounts of user data directly in the base tables Use EIM to: ` Import large amounts of data from external sources through interface tables ` Delete large amounts of data
49
5 of 16

0/4
49.6
Components of EIM
Important components of EIM are: Base Tables Interface Tables EIM Server Component EIM Configuration File
Non-Siebel loading tool Siebel Database
Prepared and cleansed external data
Interface table
Server component
Base table
Siebel client
6 of 16

1/4
49.7
Base Tables
User data is stored in one or more base tables in the Siebel database
` Relationships between base tables (referential integrity) rely upon primary keys (PKs) and foreign keys (FKs) based on ROW_IDs

49
ROW_ID is the system primary key for every base table ROW_ID is a system-generated value
PK
PK
FK
FK
S_BU
S_ORG_EXT
S_ADDR_ORG
7 of 16
Base Tables
There are two types of base tables: Target base tables (also known as a parent tables); examples include S_PARTY, S_PROD_INT, and S_OPTY. Non-target base tables (also knows as secondary base tables); examples include S_ORG_EXT, S_ADDR_ORG, AND S_ACCT_POSTN.

2/4
49.8
Interface Tables
Interface tables store external data inside the Siebel database

` Staging area for data to be imported, updated, or merged into base tables by EIM ` Staging area for data exported by EIM ` Staging area for data to be deleted in the base table by EIM
External database
EIM Server Component
S_ADDR_ORG
Interface Tables
External data
Base Tables
Data Cleansing
During imports, EIM attempts to import data from the interface table to the base tables. It is important to note that if the data loaded in the interface table is faulty, it will remain faulty in the base table(s). EIM does not perform data cleansing.
EIM_ACCOUNT
S_ORG_EXT

2/4
49.9
Interface Tables Continued

Are meant to represent typical business entities Typically map to multiple Siebel base tables
` Are denormalized ` Example: EIM_ACCOUNT interface table maps to eight base tables
49
9 of 16

3/4
49.10

Manages the exchange of data between interface tables and user data in base tables Belongs to Enterprise Application Integration (EAI) component group
S_ORG_EXT EIM_ACCOUNT
S_ADDR_ORG
External data
Reference
Siebel Enterprise Integration Manager Administration Guide

4/4
49.11
EIM Configuration File
EIM server component reads a configuration file (.ifb) to determine:

` Whether data should be imported, merged, deleted, or exported ` Which interface table(s) and base table(s) are used and affected
Import, merge, delete, or export
49

Configuration file (.ifb)
11 of 16
Course Focus Archiving
This course focuses on import (insert) and delete. EIM deletes are useful for archiving old data and deleting obsolete data. During delete processing, deleted rows are written to interface tables, from which they can be archived in a format allowing easy re-import if necessary.
49.12
User Keys
Based on multiple columns, user keys are used to uniquely identify a row for EIM Primary and foreign keys based on ROW_ID are used for system-wide referential integrity
PK ROW_ID User Key NAME LOC FK BU_ID
S_ORG_EXT
S_BU
12 of 16
49.13
Referential Integrity
User key column mappings in interface tables are used to resolve ROW_IDs for base tables, maintaining referential integrity
PK (ROW_ID) User key 1-8D Acme FK (ROW_ID)
49
Interface Table
1-8D
Base Tables
49.14
SQL
You must not use SQL to populate user data in base tables
` Relationships between tables are complex ` Referential integrity is maintained programmatically through ROW_IDs, not using constraints on the database ` SQL statements cannot generate Siebel ROW_IDs
PK
SQL
S_ADDR_ORG
FK
S_ORG_EXT
14 of 16
49.15
Module Highlights
Enterprise Integration Manager (EIM) is a server component that supports bulk imports and exports to and from a Siebel database
` Useful for initial data loads
49
The main components of EIM are:

` ` ` ` Base tables Interface tables EIM server component EIM configuration files (.ifb)
You must not insert user data into Siebel base tables using SQL!
15 of 16
49.16
Creating Data Maps
50.1
Module 50: Creating Data Maps
50
50
Creating Data Maps
50.2
Module Objectives
` Determine correct interface (EIM) tables and columns to use to import data into and delete data from Siebel base tables and columns ` Document data mappings between EIM tables and Siebel base tables
` Enables you to construct a strategy for successfully importing data into and deleting data from the Siebel database
2 of 26
Creating Data Maps
50.3
Data Mapping
The first step in using EIM to import external data is data mapping Data mapping determines:
1. Which Siebel base table columns will store external source data 2. Which interface (EIM) table columns will be used to import from source to destination
1. Decide where data ends up Source (external) Destination (base table)
50
2. Determine how to get there
Interface (EIM) table

3 of 26
Creating Data Maps
50.4
Source Data
Analyze external source data

` Decide which attributes to store ` Determine which entity the collection of attributes represents ` Analyze relationships between entities M:M M:M Decision Maker Name...
Entity Attribute
Customer Name...
Name...
4 of 26
Sales Person
Creating Data Maps
50.5
Siebel Destination
Analyze Siebel destination tables and columns

` Start with applets and fields used, and work down to business layer ` Use Siebel Tools to view tables and columns, business components (BCs), and relationships
Table BC
50
Account
Position
Contact
5 of 26
Party Business Components Siebel Tools
Account, Position, and Contact entities are person- and organization-related. Therefore, their business components share the S_PARTY table. Relationships between business components and BC fields and base tables and columns can be examined easily in Siebel Tools. Select the business component object definition of interest in Tools Object List Editor, right-click, and choose View Details. The mapping of BC fields to database tables and columns will be graphically depicted.
Creating Data Maps

0/3
50.6
Identify and Verify Destination Tables and Columns

1. Determine Destination Applet 2. Identify BC Fields 3. Map BC Field to Database Column
6 of 26
Creating Data Maps

1/3
50.7
1. Determine Destination Applet
Use the Siebel client to identify applets and controls where external data is to be displayed
` Determine applet and business component names
Example: Verify mapping for Main Phone # field of an account

` Data to appear in Account Entry Applet
Applet name
50
Desired destination applet BC Name
Control to map
Creating Data Maps

2/3
50.8
2. Identify BC Fields
Use Siebel Tools to map the applet control to the BC field

Locate control in Web Layout view Properties window displays field name
8 of 26
Creating Data Maps

3/3
50.9
3. Map BC Field to Database Column
Examine BC field properties in Siebel Tools to determine which Siebel base table and column it maps to
50
BC field being mapped
Table and column
9 of 26
Creating Data Maps
50.10
Map Source to Siebel Destination
Specify the source mapping to the Siebel destination

` Identify business component mapped to external entity ` Determine Siebel base tables and columns that will store source attributes
BC External entity Table
Account Customer Sales Person
Position
Attribute
Name... Contact Decision Maker Name...
Name...
10 of 26
Creating Data Maps
50.11
Document Mappings
Document mappings between source and base so that everyone has a common understanding
` EIM and configuration tasks are often performed by different people ` Can reduce need to re-do tasks if team members leave the project
50
Source Entity
Customer Customer
Source Attribute
Name Phone Address
EIM Table
EIM Column
Base Table
S_ORG_EXT S_ORG_EXT S_ADDR_ORG S_ADDR_ORG S_ADDR_ORG
Base Column
NAME MAIN_PH_NUM ADDR CITY ZIPCODE
11 of 26
Creating Data Maps
50.12
How to Get There: Determine Interface Tables
After verifying and documenting the source-to-base mappings, determine and document EIM-to-base mappings
Source Attribute
Name Phone Address
Source Entity
Customer Customer
EIM Table
EIM Column
Base Table
S_ORG_EXT S_ORG_EXT S_ADDR_ORG S_ADDR_ORG S_ADDR_ORG
Base Column
NAME MAIN_PH_NUM ADDR ZIPCODE CITY
Source
9
Interface (EIM)
How to get there?
Destination
?
12 of 26
Reference Base Table
Siebel Tools Reference A base table is the destination table in the Siebel database for your data import.
Creating Data Maps
50.13
Table Relationships
An interface table may populate more than one base table A base table may be populated by more than one interface table
EIM_ACCOUNT
50
S_ORG_EXT
EIM_ADDR_ORG S_ADDR_ORG
13 of 26
Creating Data Maps
50.14
Locate EIM Tables
Locate candidate EIM tables using Siebel Tools

` Example: Locate EIM tables that populate S_ORG_EXT
Flat tab Query Result
EIM tables that populate S_ORG_EXT
Note: Use EIM_ tables, not _IF tables

Creating Data Maps
50.15
Interface Table Documentation
Mappings from interface tables to base tables are documented by:

` EIM Interface Table report available in Siebel Tools ` EIM Table Mapping objects
Less convenient than using report
50
select Reports > EIM Interface Tables
15 of 26
Query for interface table and
Creating Data Maps
50.16
Interface Table Documentation Continued
Table report documents EIM Table Mapping attributes

Interface table report for EIM_ACCOUNT
16 of 26
Creating Data Maps
50.17
Interface Table Documentation Continued
The EIM Interface Table report shows mapping from a single EIM table to one or more Siebel base tables
` EIM column (source) to base table column (destination) mapping ` Column attributes (user keys, foreign key tables, required fields)
EIM table name
50
Base column EIM column
Base table Base table Destination column attributes

Creating Data Maps
50.18
Select EIM Table
Select the EIM table that best maps to the target base tables and columns
` Pick the EIM table that maps the most columns that you need to migrate
Example:
` EIM_ACCOUNT can be used to map Account-related Position data because it maps to the intersection table S_ACCNT_POSTN
S_ACCNT_POSTN columns mapped by EIM_ACCOUNT
18 of 26
Creating Data Maps
50.19
EIM to Base Mappings

Determine EIM columns that populate target base columns Determine other EIM required columns to populate the target base table
` Other columns may be required based on required fields in the base table
50
EIM table
Base table
EIM column
Base column
19 of 26
Creating Data Maps
50.20
Determine EIM Columns
Determine which EIM column populates the target base column in Siebel Tools
` Example: MAIN_PH_NUM on EIM_ACCOUNT populates MAIN_PH_NUM on S_ORG_EXT
Base column
EIM column
20 of 26
Column Names
Column names are often the same, but not always.
Creating Data Maps
50.21
Determine EIM Columns Continued
Alternate method is to query Attribute Mappings in Siebel Tools to determine which EIM column populates the base column
` Example: MAIN_PH_NUM on EIM_ACCOUNT populates MAIN_PH_NUM on S_ORG_EXT
Use Flat tab to query Base table and column
50
Query Result EIM table and column
21 of 26
Creating Data Maps
50.22
Determine Base Required Columns
Determine required base table columns that do not have defaults (EIM does not recognize non-system default values)
Query Column
Result = required base columns Defaults not recognized by EIM
22 of 26
Finding Non-System An alternative method of locating required, non-system columns is to query Columns for required columns with Type equals Data(Public).
Creating Data Maps
50.23
Mapping Considerations
Understand how to enter organization data

` Fill in _BU column with name of the organization ` Leave _BI column blank
Populated with foreign key during import processing
Understand additional columns that must be populated for party business components
` Use EIM Interface Table report to identify these ` Examples:
PARTY_UID PARTY_TYPE_CD ROOT_PARTY_FLG
50
23 of 26
ROOT_PARTY_FLG
ROOT_PARTY_FLG is for Oracle implementations only. It was added to support performance for Oracle. A query to obtain top-level Positions, Organizations, or Access Groups can use either: 1. WHERE ROOT_PARTY_FLG='Y' or 2. WHERE PAR_PARTY_ID is NULL Oracle cannot use an indexed access path for option 2 because there are no index entries for NULL, so ROOT_PARTY_FLG was added. ROOT_PARTY_FLG is set to 'Y' for top-level Positions, Organizations, and Access Groups as it applies only to these Party sub-types. It is set to 'N' for other party subtypes.
Creating Data Maps
50.24
Mapping Considerations Continued
Be aware of access control and data visibility issues

` Set access control by:

Importing ownership information, or Using assignment manager
` If ownership is not set or is set incorrectly, data visibility will be incorrect
Example:

Product visibility is determined by organization Map product and ownership information to EIM_PROD_INT (Product interface table) Be sure to map from EIM_PROD_INT to both S_PROD_INT (Internal product base table) and S_PROD_INT_BU (Product/BU intersection table)
` Mapping documented in EIM Interface Table report
24 of 26
` Import product information to Siebel database
Creating Data Maps
50.25
Module Highlights
Data
mapping specifies:
` Which base tables and columns will hold external data ` Which interface tables and columns will be used by EIM during data movement
Steps
to create data mappings for EIM:
Data
mappings should be clearly documented
25 of 26
` Map external entities to Siebel business-layer objects ` Use the Siebel Web Client to identify and verify mapping of external attributes to BC fields ` Select the interface table used by the mapping ` Use Siebel Tools EIM Interface Table report to perform column-tocolumn mappings between interface tables and base tables ` Map all external attributes of interest plus required non-system columns
50
Creating Data Maps
50.26
Lab

` Map external solutions data to EIM tables and base tables ` Map external product data to EIM tables and base tables
26 of 26
Running Enterprise Integration Manager
51.1
Module 51: Running Enterprise Integration Manager
51
51
51.2
Module Objectives
` ` ` ` Populate interface (EIM) tables for imports Modify configuration (.ifb) files for imports Invoke an Enterprise Integration Manager (EIM) server task Modify configuration (.ifb) files to optimize imports

` To successfully import external data into the Siebel database
2 of 28
51.3
Interface Table Structure
All interface tables have three required columns:

` IF_ROW_BATCH_NUM and ROW_ID are set by the user to uniquely designate a record ` IF_ROW_STAT is used by EIM to return status after an EIM run
Number to identify all records that should be processed in the batch
IF_ROW_BATCH_NUM 100 100 200 200
Unique number to identify the record in the batch

Row_ID 1 2 1 2 IF_ROW_STAT IMPORTED IMPORTED IMPORTED IMPORTED
Non-null character value that is reset during the run

NAME Photocopier Fax Machine Shredder Toner Cartridge
If import job is successful, system sets value to IMPORTED

EIM T_ Columns
All EIM tables have columns to hold temporary values used by EIM during a job. These columns start with T_, and include some that end with the suffix _STA. These latter columns may provide troubleshooting assistance.
51

0/5
51.4
Running an EIM Task for Data Imports
1. Populate EIM Tables 2. Determine Processing Order 3. Run an EIM Task
5. Remove Data from EIM Tables
4 of 28
4. Verify EIM Task Results

1/5
51.5
1. Populate EIM Tables
Populate source data into EIM tables using a non-Siebel process

` Use database vendor utilities to load data from flat files ` Use SELECT INTO to pull data from other SQL databases ` Use direct SQL insert, update, or delete statements to update columns in EIM tables ` Use SQL queries to verify that EIM tables populated correctly
External data EIM_PROD_INT Non-Siebel process
5 of 28
51

2/5
51.6
2. Determine Processing Order
Determine the correct processing order for EIM tables

` When importing, tables referenced via foreign key must be loaded first ` Refer to the default.ifb for recommended processing order
Order of imports
6 of 28
Reference
The recommended processing order for EIM imports is also described in Siebel Bookshelf, Enterprise Integration Manager Administration Guide, Importing Data.

3/5
51.7
3. Run an EIM Task
Creates an operating system (OS) process that reads the .ifb file, loads the dictionary, executes EIM steps, and writes log entries
Dictionary .ifb
Log
7 of 28
EIM Dictionary
The dictionary used by EIM is a set of files used to speed EIM processing.
51

3/5
51.8
3. Run an EIM Task Continued
Direct the execution of an EIM task using a configuration (.ifb) file

` Specifies the batch, order, and type of processing ` Use default.ifb as a template
IF_ROW_BATCH_NUM value (rows to process) EIM table
Destination table
Default column values
8 of 28
.ifb File Location Parameters for EIM Deletes
The template EIM configuration file, default.ifb, is located in {SiebSrvr_Base_Dir}\ADMIN. Because the focus of this module is on EIM imports, which are of critical importance as part of initial data loads in a Siebel implementation project, this module does not cover the details of configuring an EIM delete job. However, parameters in the .ifb file, deletes allow control over the tables and rows to be deleted. See the details for the parameters DELETE EXACT, DELETE MATCHES, and DELETE ALL ROWS in Bookshelf, Siebel Enterprise Integration Manager Administration Guide.
Section to process

3/5
51.9
3. Turn Off Transaction Logging

Siebel Remote logs transactions to allow synchronization of mobile clients Transaction logging reduces EIM performance
` Before initial loads, turn off logging
Navigate to Administration Siebel Remote > Remote System Preferences Turning off transaction logging in a running production system will require subsequent re-extraction of all mobile user databases
` After initial loads, turn on logging to support mobile clients
Logging disabled during initial loads
9 of 28
51

3/5
51.10
3. Create and Run an EIM Job
Navigate to Administration - Server Management > Jobs

3. Click Submit Job
1. Create a new job and select Enterprise Integration Manager
2. Specify job parameters, including EIM configuration file
10 of 28

3/5
51.11
3. Monitor the EIM Task
Navigate to Administration - Server Management > Tasks

` Query to view progress ` Review Task Information Log
Log displays diagnostic information, including task parameters
11 of 28
51

4/5
51.12
4. Verify EIM Results
Run SQL SELECT statements to verify the table data
Select from EIM table
Select from base table
12 of 28

4/5
51.13
4. Verify EIM Results Continued
After import, IF_ROW_STAT will contain a value that describes the status of each imported row
IF_ROW_STAT Value IMPORTED PARTIALLY_IMPORTED REQUIRED_COLS DUP_RECORD_EXISTS FOREIGN_KEY PICKLIST_VALUES Description
Success for all destination tables
Failed because required column has NULL value Failed because target table has row with same values Failed because a required foreign key could not be resolved Failed because required picklist value not found in S_LST_OF_VAL
13 of 28
Success for target base table; failure for secondary table
51

4/5
51.14
Verify imported data in the application using appropriate views

` Example: Products > Internal Product List
Verify that products were imported successfully
14 of 28

4/5
51.15
For troubleshooting:
` Navigate to Administration Server Management > Tasks ` Find task number for EIM task ` Examine log file in Siebel server log directory
Find EIM task number
Examine task log file
15 of 28
51

4/5
51.16
Job parameters can override component-level event logging to create additional information in the log
` Trace Flags = 1
Records processing steps Records summary SQL Should only be done in test environment Dramatically impedes EIM performance and generates large log file Records details regarding failed rows
EIM logging flags used for troubleshooting
` SQL Trace Flags = 8

` Error Flags = 1
16 of 28
Troubleshooting Flags
SQL Trace Flags = 8 should only be used for test EIM jobs with a small number of records. This option produces a very large log file and has a significant performance impact.

5/5
51.17
Remove Data from EIM Tables
You are responsible for removing records from the EIM tables
` Use SQL to delete EIM table records once they have been successfully processed
17 of 28
51

0/3
51.18
Additional Configuration (.ifb) Parameters
Use enhanced configuration parameters to speed EIM processing and reduce elapsed time: Process Options Import Options
18 of 28
Primaries

1/3
51.19
Process Options
Explicitly include or exclude tables and columns to avoid unnecessary processing

` Use ONLY BASE TABLES, ONLY BASE COLUMNS or ` Use IGNORE BASE TABLES, IGNORE BASE COLUMNS
Example:
19 of 28
Directs task to process only these target tables
51

1/3
51.20
Process Options Continued
Set options to control processing and enhance performance

` Set USING SYNONYMS to FALSE to avoid unnecessary processing
USING SYNONYMS applies to accounts only
` Use SHELL to process multiple EIM tables/sections in a single run
Example:
Directs task to ignore account synonyms
20 of 28
Synonyms
Some business components have a MVG field that contains synonyms, which are variations in the BC name. For example, the Account named IBM could have synonyms: International Business Machines, Intl Bus Machines, IBM Co., and so on. Use of synonyms prevents multiple records being created based on misspelling or inconsistent usage.

2/3
51.21
Import Options
Set options to preprocess EIM rows and columns

` Use FILTER QUERY to select a subset of EIM rows for processing ` Use DEFAULT COLUMN or FIXED COLUMN to set values for EIM columns
Example:
EIM column, operator, and value
21 of 28
51

3/3
51.22
Primaries
Improve performance by eliminating sub-queries when displaying data from parent and child tables If primaries are not used, a new query needs to be executed to identify any child records each time a parent record is displayed Two types of Primary settings:
` Explicit Primary ` Implicit Primary
22 of 28

3/3
51.23
Set Primaries: Explicit Primaries
Use the Primary flag to set explicit primaries through EIM

` Use when the external system knows which child should be primary
EIM table column for primary
EIM table Columns
EIM_ACCOUNT
NAME Acme Acme ADDR_ADDR Elm Street Main Street ADDR_CITY Boston Fremont Y
ACC_PR_ADDR
S_ORG_EXT
ROW_ID NAME 1-WEZ Acme PR_ADDR_ID 2-AB4
Base tables
S_ADDR_ORG
OU_ID
1-WEZ 1-WEZ
ROW_ID ADDR 2-AB8 2-AB4 Elm Street Main Street
CITY Boston Fremont

23 of 28
Set the PFK to point to this child data
51

3/3
51.24
Set Primaries: Implicit Primaries
Allow EIM to implicitly set primaries

` Use when the external system does not know the primary ` Sets the primary to be the child with the lowest ROW_ID ` Mimics auto primary in the application
EIM table Columns
EIM_ACCOUNT
NAME Acme Acme ADDR_ADDR Elm Street Main Street ADDR_CITY Fremont
Base table
S_ORG_EXT
ROW_ID NAME 1-WEZ Acme PR_ADDR_ID 2-AB8
Base table
S_ADDR_ORG
OU_ID 1-WEZ 1-WEZ ROW_ID ADDR 2-AB8 2-AB4 Elm Street Main Street CITY Boston Fremont
24 of 28
Boston
51.25
Using EIM with Database Modifications
To populate base table extension columns through EIM:

` Add an extension column to the EIM table ` Map the EIM column to the base column ` Test the mapping by running EIM on the server
Use the Interface Table Mapping Wizard
EIM table
Base table
EIM Extension Column
Base Extension Column
25 of 28
51
51.26
Using EIM with Database Modifications Continued

Update EIM table mappings to include columns or tables you have added using the Interface Table Mapping Wizard Select the table in Tools, right-click, select EIM Table Mapping and complete the wizard
26 of 28
51.27
Module Highlights
All
EIM tables have three special columns:
` IF_ROW_BATCH_NUM ` ROW_ID ` IF_ROW_STAT

EIM
import steps are:
Parameters
that can speed EIM processing:
` No transaction logging ` Process and import options in .ifb file

Can
set primaries during EIM import

27 of 28
` ` ` ` `
Populate EIM tables Create an EIM configuration file (.ifb) Run an EIM job Verify job results Remove EIM table records
51
51.28
Lab

` Load solutions data into the interface table ` Import solutions data from the interface table to base table ` Load company data into the interface table and import it to the base table
28 of 28
Introducing Application Deployment Manager
52.1
Module 52: Introducing Application Deployment Manager
52
52
52.2
Module Objectives

` Describe the Application Deployment Manager (ADM) architecture ` Describe how deployment options are configured

` ADM provides a framework to deploy application customizations efficiently and predictably
2 of 18
52.3
Business Challenge: Application Migration
Deploying a customized Siebel application typically involves:

` A development enterprise (a collection of Siebel servers), where customizations are created ` A QA/test enterprise used to test application functionality ` One or more production enterprises that require tested and stable software
May involve many production Siebel enterprises
` May involve hundreds of customizations ` Source and target enterprises may have different configurations
Development enterprise may be simpler than test enterprise Example: A new state model needs to be deployed after the modified business component object definition the model uses
` Customizations may have dependencies on each other
52
` Development and testing often occur concurrently

The migration of customizations may be very complex:
52.4
Business Solution: Application Deployment Manager (ADM)

Is a framework for deploying application customizations to a target Siebel enterprise Is designed to provide an extensible facility for quick, reproducible deployment of a wide range of customizations
4 of 18
Reference ADM Data Types
Application Deployment Manager Guide A complete list of data types supported by ADM can be found in Application Deployment Manager Guide: ADM Supported Data Types. ADM features and architecture have been significantly enhanced from prior versions.
ADM in Siebel 8.0
` Includes support for many data types ` Supports deployments ranging from a small patch with only a handful of application modifications to a major release with a new SRF file ` Allows creation of reusable deployment packages that can be applied to multiple target enterprises

0/3
52.5
Types of Customization
ADM recognizes three types of application customizations:

` Database customizations ` Repository customizations ` File customizations
The steps to export and deploy each type differ
52
5 of 18

1/3
52.6
Database Customizations
Are changes to administrative and master data records in the Siebel database
` Does not include repository table changes ` Use EIM to migrate application records, such as Accounts, Contacts, Opportunities
ADM supports deployment of many data types, including:
6 of 18
` ` ` `
Lists of Values (LOVs) User Lists Assignment Rules Access Groups

2/3
52.7
Repository Customizations
Are changes to object definitions made in Siebel Tools
New or modified repository objects
52
7 of 18

3/3
52.8
File Customizations
Are files modified as part of application configuration Examples:
` ` ` `
Web Template files (.swt) Image and Cascading Style Sheet (CSS) files Siebel Repository file (.srf) Reports files
Example: image files
8 of 18

0/3
52.9
ADM Architecture
The three major parts of the ADM architecture are the:

` Source enterprise ` Orchestration environment ` Destination enterprise(s) (can be multiple targets)
Source Enterprise
Deployment package Package
Orchestration Environment
52
Destination Enterprise

1/3
52.10
Source Enterprise

Is the Siebel enterprise containing modifications to be deployed

` Example: a development enterprise
Source enterprise components related to ADM include:

` Siebel client and Siebel Tools functions to export customizations ` A packager utility to bundle application customizations
Source Enterprise

2/3
52.11
Is a system used to execute ADM deployment Orchestration environment components include:
Command line interface
52
Deployment package
11 of 18
` The Siebel Management Server ` A database containing records on all deployments and data types contained in ADM packages ` An ADM command line interface (CLI) ` An ADM registry file ` A target enterprise profile file, which describes the target environment and deployment steps

2/3
52.12
Orchestration Environment Continued
Siebel Management Server is a service that supports:

` The ADM orchestration environment ` The Diagnostic Tool, which allows performance measurement of Siebel servers
Siebel Management Server is the primary component of ADM orchestration environment
12 of 18

2/3
52.13
Orchestration Environment Continued
The enterprise profile file:

` Specifies target enterprise parameters ` Is used to configure deployment options ` Is discussed later in this module
The ADM registry file:

` ` ` ` Lists data types supported by ADM Defines ADM operations for each data type Defines deployment validation rules Is usually not modified
52
ADM registry file
13 of 18

3/3
52.14
Is the target for deployment using ADM

` Example: a QA/test Siebel enterprise ` Can be multiple destination enterprises
Source Enterprise
14 of 18

3/3
52.15
Destination Enterprise Continued
Destination enterprise components for ADM include:

` A Siebel Management Agent for each Siebel Server in the target enterprise ` ADM server components on each Siebel Server
Siebel Management Agent is a service that runs in combination with a Siebel Server and provides support for Management Server requests
Siebel Management Server Orchestration Environment
52
Siebel Mgmt Agent Siebel Server Siebel Mgmt Agent Siebel Server Siebel Mgmt Agent Siebel Server
15 of 18
52.16
ADM Enterprise Profile File
The enterprise profile file contains:

` Parameters that specify target enterprise configuration ` Parameters that control deployment orchestration
Parameters that describe target enterprise configuration include:

` Siebel Server connect string(s) ` Siebel Management Agent name(s) and port number(s)
Enterprise profile file opened in Microsoft InfoPath
16 of 18
Editing the Enterprise Profile File
The recommended way to modify the enterprise profile file is to use Microsoft InfoPath, a component of Microsoft Office. XML form templates are provided for use with InfoPath. To install the InfoPath form and its descriptor as trusted forms, execute two batch files: <mgmt server install dir>\adm\installentprofile.bat and <mgmt server install dir>\adm\installdescriptor.bat.
52.17
ADM Enterprise Profile File Continued
Complex deployments can be customized by setting parameters to control:

` Deployment sequence (some deployment units have dependencies)
Example: A modified assignment object may need to be deployed before a new assignment rule ADM supports parallel deployment of file and database type customizations Specifies deployment groupings by deployment unit or group, target Siebel server, or a collection of servers Sets behavior of deployment on error
` Serial versus parallel deployment
` Staging
` Stop on error
52
17 of 18
52.18
Module Highlights
ADM may be used to move Siebel application modifications from a development environment to a test environment
` Database changes (LOVs, assignment rules, and so on) ` Repository changes (objects definitions, workflows, and so on) ` Files changes (Web templates, CSS files, .srf files, and so on)
The ADM architecture includes components on:
Advanced deployment options are set by modifying the enterprise profile file EntProfile_<EnterpriseName>.xml
18 of 18
` Source environment ` Orchestration environment ` Target environment
Deploying Application Customizations
53.1
Module 53: Deploying Application Customizations
53
53
53.2
Module Objectives

` Use the packager utility to bundle application customizations ` Deploy a package using the ADM command-line interface

` ADM provides a framework to deploy application customizations efficiently and predictably
2 of 30

0/6
53.3
Steps in Using ADM
Identify All Customizations to Deploy Export Database Customizations Export Repository Customizations Move File Customizations Create an ADM Package Deploy the Package
53
3 of 30

1/6
53.4
Identify All Customizations to Deploy
The first step in planning the deployment of application customizations is to identify changes
` Examination of software configuration management or development logs may suffice
Identify repository customizations within Siebel Tools:

` Use Tools > Compare Objects to compare objects and/or archives ` Generate a mid-level release (covered later in this module)
4 of 30
Identify database changes using the Siebel client or development logs Determine file changes using operating system (OS) timestamps or third-party tools like diff

1/6
53.5
Identify All Customizations to Deploy Continued
Analyze data dependencies to ensure successful deployment

` Some ADM supported data types (parent types) are dependent on other data (child types) ` Deploy parent types after child types ` Examples:

Specify the order of deployment before exporting database changes using the Siebel client (covered later in this module)
53
User List depends on Users Access Group depends on User Lists State Model depends on List of Values

2/6
53.6
Export Database Customizations
Use the Siebel Web Client to export database modifications to files suitable for ADM packaging
` Example: Export a collection of new User Lists
Exported files include:

` A file containing the exported data (XML) ` A descriptor file (XML) ` A log file giving export details and status
To export database changes:

` Create and enable a deployment project ` Specify data dependencies ` Create and deploy a deployment session
6 of 30

2/6
53.7
Export Database Customizations Continued

Navigate to Application Deployment Manager > Deployment Projects Create, specify, and enable a deployment project
` A deployment project is a specification of data to deploy

1. Specify Name and Export to File
4.Enable project
2. Specify Data Type Name
3. Specify a deployment filter to limit records exported
53
7 of 30

2/6
53.8
Use a deployment filter to limit the records to be exported:

` Save a query that selects the records to be exported
Example: Save a query that selects User Lists with Name = AAA*
` In the ADM Deployment Projects view, enter saved query name in the Deployment Filter field
Data types applet in Deployment Projects view
Select saved query
8 of 30

2/6
53.9

Determine order of data type deployment in the Application Deployment Manager > Data Type Explorer view Select parent data type in the Data Types applet, then add child type in child applet
State Model (parent) type
depends on LOV (child) type
53
9 of 30

2/6
53.10

Navigate to Application Deployment Manager > Deployment Sessions Create a new session and specify project name Deploy the session
` Select Export to File, then specify export destination

2. Click Deploy
1. Select Project Name
3. Specify export path
4. File prefix is Session Id


3/6
53.11
Export Repository Customizations

Use Siebel Tools to export repository customizations Files created during export include:
` A .sif file containing the changes ` A deployment descriptor file (XML) ` A log file of export steps and status
Tools offers two methods for exporting customizations:
List of objects may be edited after it is generated
53
` Hot fix: typically a small set of hand-selected modifications ` Mid-level release: repository changes after a specified cutoff date

3/6
53.12
Export Repository Customizations Continued
To create a hot fix in Siebel Tools:

1. 2. 3. 4. Select the object definition to add to the hot fix Right-click and select Add to Hot-Fix Specify a name for the hot fix Return to Tools Object Explorer and List Editor to add additional object definitions 5. When done, click Export
12 of 30
Hot fix output is saved in \Tools\ADM\<HF Name>

3/6
53.13
Export Repository Customizations Continued
To create a mid-level release in Siebel Tools:

1. Navigate to View > Options > General and set Changed Date to specify the cutoff date for the release 2. Select Tools > Generate Mid-Level Release 3. Provide a name for the release and click Generate List 4. Verify list contents and delete entries if necessary 5. Click Export
Objects modified since Start Date

53
Package is created in \Tools\ADM\<MLR name>

4/6
53.14
Move File Customizations
File type customizations do not need to be exported using the Siebel client or Siebel Tools
` Move files to the correct directory in the package tree (discussed later)
The type for a custom Siebel Repository File (.srf) is File, not Repository
14 of 30

5/6
53.15
Create an ADM Package
An ADM package is a collection of application customizations and includes:

` A directory structure that organizes different types of customization (database, repository, and file ) ` An ADM package descriptor file describing its contents
ADM includes a utility, admpkgr, which can create and verify an ADM package
Steps to create a package:

A. B. C. D. Create an empty package structure Populate the package directory structure Generate the package descriptor file Validate the package
15 of 30
53
` Runs from command line ` ADM packager syntax: % admpkgr <init | generate | validate> <pkg_name>

5/6
53.16
A. Create an Empty Package

Invoke admpkgr with the init command to create an empty package directory structure Command syntax:
% admpkgr init <package name with path>
Example:
Empty package directory structure
Package location
16 of 30
Optional Switch
Set the language sub-directories in the empty package directory structure using the optional switch, g <lang>. Example: admpkgr init g ESP <pkg_name> This command would create Spanish language subdirectories, which would be named ESP. The default language is American English (ENU).

5/6
53.17
B. Populate the Package Directory Structure
Database and repository exports and file modifications need to be moved to the new package directory tree
` For database type, move the .xml file containing data + descriptor file ` For repository type, move the .sif file + the descriptor file ` For file type modifications, the package sub-directory depends on the file category:

Unused package sub-directories should be deleted
53
Repository file (.SRF): <pkgdir>\file\AppServer\objects\<lang> Web templates: <pkgdir>\file\AppServer\webtempl\<lang> Images, CSS files, browser script files: <pkgdir>\file\AppServer\webmaster\<lang> Report files: <pkgdir>\file\ReportServer\<lang>

5/6
53.18
C. Generate the Package Descriptor File
Invoking admpkgr with the generate command:

` Validates package directory contents ` Calculates a checksum to ensure future integrity of the package ` Creates a package descriptor file for the package
Command syntax:
% admpkgr generate <package name with path>
Example:
Package descriptor file
18 of 30

5/6
53.19
D. Validate the Package
Invoking admpkgr with the validate command:

` ` ` ` Verifies the existence and format of package descriptor file Checks for empty folders and redundant units Performs consistency checks for units Checks for the existence of valid unit files and descriptor files for database and repository types
% admpkgr validate <package name with path>
Example:
53
Using validate is optional Command syntax:

6/6
53.20
Deploy the Package
The ADM command-line interface (CLI) command set is executed on the Management Server host
` Commands contained in a batch file created by a Perl script bundled with the Management Server ` Batch file is named deploy_<enterprise name>.bat

ADM commands take command-line arguments:

` ` ` ` ` Command name User name Password Package name Optional switches
20 of 30
CLI Optional Switches A complete list of command-line switches may be found in Siebel Bookshelf, Siebel Application Deployment Manager Guide.
Example: if enterprise name = Siebel, then ADM CLI batch file is named deploy_Siebel.bat Typically created in \<mgmt server install dir>\bin

6/6
53.21
Deploy the Package: Commands Overview

The ADM CLI supports both required and optional commands Commands execute in a specific order
Management Server valent load create validate backup copy activate required optional covered in this course
21 of 30
Target Enterprise delete acknowledge status restore_activate restore_copy restore_session
53

6/6
53.22
Deploy the Package: Load
Call load command to put references to package contents into the orchestration environments database
` Validates package structure and checksum ` Uses package descriptor file to map package contents to Management Server database ` Command syntax: deploy_<enterprise> load <user> <password> <package name> User/password ` Example:
Source Enterprise Orchestration Environment
22 of 30
Package name

6/6
53.23
Deploy the Package: Create
Call create to initiate a deployment session

` Command syntax: deploy_<enterprise> create <user> <password> <package name> ` Example:
New Session
53

6/6
53.24
Deploy the Package: Copy
Call copy to move package contents to destination enterprise

` Uses the appropriate copy method for each type of customization

Repository changes are copied to target repository Database changes are loaded into target database File changes are moved to correct location in target file system
` Example:
24 of 30
` Command syntax: deploy_<enterprise> copy <user> <password> <package>

6/6
53.25
Deploy the Package: Activate
Call activate to perform any steps required to make customizations available to users
` Most data types do not require activation
Example: Proposal Template LOV activation clears the LOV cache Workflow process activation sets the process to Active Image, CSS file, or Web template file activation propagated to Web server
` Activation examples:

` Command syntax: deploy_<enterprise> activate <user> <password> <package name> ` Example:
53

6/6
53.26
Deploy the Package: Status and Acknowledge
Call status to get information about the deployment status of a package

` Gives a summary of deployment status of units in the package ` Use status_detail to see status information for each unit
To complete a command-line deployment, call acknowledge:

` Ends deployment session ` Sets session status to complete in Management Server local DB ` Removes backup package data from Management Server DB
Status example:
26 of 30

6/6
53.27
Deploy the Package: Other Commands
Other optional ADM CLI functions include:

Command valent validate backup restore_session, restore_copy, restore_activate list delete Description Validates enterprise profile file Performs checks on target enterprise before deployment
Sequence of commands that allows rollback of a deployment Lists packages deployed by Siebel Management Server Deletes package references and session info from Siebel Management Server
27 of 30
53
Reference
Further information about ADM package deployment using the ADM CLI can be found in Siebel Bookshelf, Application Deployment Manager Guide.
Creates backup copy of target enterprise data that will be affected by deployment
53.28
Module Highlights
Export application customizations using:

` Siebel Tools for repository modifications ` The ADM screen in the Siebel client for database modifications ` File copy into package for file modifications
` ` ` ` ` `
Load the package Create a deployment session Copy the package to the target environment Activate the customizations (optional) Status to verify correct deployment Acknowledge to end the deployment session
28 of 30
Use the ADM packager utility to bundle modifications for deployment to the target enterprise Execute commands from the ADM CLI to deploy an ADM package:
53.29
Lab

` Export repository and database customizations ` Create an ADM package ` Use the ADM CLI to deploy this package
53
53.30

Siebel 8.0 Essentials

Uploaded by

Copyright:

Available Formats

Siebel 8.0 Essentials

Uploaded by

Document Information

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

Siebel 8.0 Essentials

Uploaded by

Copyright:

Available Formats

Siebel 8.

Volume I Student Guide

D46318GC10 Edition 1.0 April 2007 D49908

Oracle Internal & Oracle Academy Use Only

Technical Contributors and Reviewers

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Module 6: Controlling Access to Customer Data

Oracle Internal & Oracle Academy Use Only