Siebel 7 Essentials Student Guide Vol2-1

Siebel Systems, Inc.
Siebel 7 Essentials
Student Guide, Volume 2 Version 7.0 November 2001
Part # 10PO2-PLT02-07000
10PO2-PLT02-07000
Copyright 2001 Siebel Systems, Inc., 2207 Bridgepoint Parkway, San Mateo, CA 94404. All rights reserved. No part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, including but not limited to photocopy, photographic, magnetic, or other record, without the prior agreement and written permission of Siebel Systems, Inc. Siebel Systems, Inc. considers information included in this document to be Confidential and Proprietary. Your access to and use of this Confidential and Proprietary Information is subject to the terms and conditions of the Siebel License Agreement or Non-Disclosure Agreement which has been executed and with which you agree to comply.
Re: Training Materials Siebel Systems Confidential and Proprietary Information
Dear Siebel Education Student: This letter will serve to confirm that all information that is disclosed orally, visually, and in printed form during your visit to Siebel Systems, Inc. for formal training classes is to be treated as Confidential in accordance with the terms of the applicable confidentiality agreement (the Agreement) between Siebel Systems, Inc. and your Company. Under the terms of the Agreement, please be advised that you may not: 1. disclose such information or materials except as specified in the Agreement, nor 2. use such information or materials other than for the specified purpose set forth in the Agreement. Also, the materials you receive during your visit are copyrighted works of Siebel Systems, Inc. (regardless of whether they bear a copyright mark) and may be used only for the purpose of supporting the training of your employees who attend Siebel System training courses. You may not reproduce, disclose, or distribute these materials, in whole or in part, nor may you prepare derivative works of them. These copyrighted works include the Student Guides, Labs Manuals, Instructor Guides, and all course materials used in Siebel Systems, Inc. courses and workshops.
Copyright 2001 Siebel Systems, Inc.
Siebel 7 Essentials
Table of Contents
Volume 1 Foundations Module i: Module 1: Module 2: Module 3: Siebel 7 Essentials Training Introducing Siebel eBusiness Applications Using the Siebel Client Organizing Data Behind the User Interface
Architecture and Installation Module 4: Module 5: Module 6: Module 7: Exploring the Siebel Architecture How Clients Access Siebel Data Installing Siebel Software Server Administration
Access Control and Organization Setup Module 8: Module 9: Module 10: Module 11: Module 12: Access Control and Views Access Control and Data Access Control and View Types Creating an Organization Authenticating Users
Exploring Siebel Applications Module 13: Module 14: Module 15: Module 16: Understanding Object Definitions Behind a Siebel Application Using Siebel Tools to Examine Object Definitions Understanding the Siebel Data Model The Siebel Data Model: Party Business Components
Configuration Module 17: Module 18: The Configuration Process Managing Object Definitions
Siebel Systems, Inc. COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Siebel 7 Essentials
Volume 2 Configuration, Continued Module 19: Module 20: Module 21: Module 22: Module 23: Module 24: Module 25: Module 26: Module 27: Module 28: Module 29: Module 30: Module 31: Module 32: Module 33: Module 34: Module 35: Module 36: Editing and Compiling Object Definitions Understanding Siebel Template Files Configuring Applications and Screens Configuring Views Configuring List Applets Configuring Form Applets Understanding Business Components and Joins Business Components and Joins: Party Extension Tables Understanding Business Objects and Links Configuring Business Components and Fields Creating a New BC Using the Standard 1:M Extension Table Configuring Navigation Extending the Database Configuring Picklists Configuring Multi-Value Groups Configuring Access Control Localizing an Application Configuration Guidelines Volume 3 Data Loads Module 37: Module 38: Module 39: Module 40: Module 41: Introducing Enterprise Integration Manager Data Mapping Invoking Enterprise Integration Manager Setting Enterprise Integration Manager Options Access Control and Access Groups
ii COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Siebel 7 Essentials
Business Process Automation Module 42: Module 43: Module 44: Module 45: Module 46: Module 47: Module 48: Module 49: Module 50: Deployment Module 51: Module 52: Module 53: Conclusion Module 54: Final Words Using Siebel Remote to Support Mobile Clients Additional Siebel Remote Topics Migrating Data Between Environments Introducing Siebel Workflow Invoking Workflow Processes Additional Workflow Topics Introducing Assignment Manager Creating Sales Assignment Rules Creating Service Assignment Rules Invoking Assignment Manager Personalizing View and Applet Access Personalizing Content and Behavior
Siebel Systems, Inc. COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
iii
Siebel 7 Essentials
iv COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Editing and Compiling Object Definitions
19.1
Module 19: Editing and Compiling Object Definitions
19
Siebel 7 Essentials
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
19.2
Module Objectives
After completing this module you will be able to:
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
Why you need to know

These are all fundamental activities that occur during all configuration efforts
2 of 28
Siebel 7 Essentials
19.3
Editing Object Definitions

Select the object definition to edit using the Object Explorer and Object List Editor
Make sure that project has been locked
Edit the property

Type in a value Pick a value from a picklist (if provided)
Indicates project locked Type Select
3 of 28
Reference
Siebel Tools Reference
19
Siebel 7 Essentials
19.4
Creating a New Object Definition

Select the desired object type in the Object Explorer Create a new record in the Object List Editor
Create a unique name Select a project from picklist Assign values to remaining fields
Locked projects only
4 of 28
Siebel 7 Essentials
19.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 28
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. This then displays in the OLE only those definitions they have edited.
19
Siebel 7 Essentials
19.6
Validating Object Definitions

Determines correctness of selected object definition in the repository
Includes all child object definitions for the selected parent definition
Is based on set of Siebel-defined rules
User can enable/disable a Siebel-defined rule
Error
Warning
6 of 28
Siebel 7 Essentials
19.7
Validating Object Definitions Continued

Select object definition to validate
Right-click and select Validate
Click Start in Validate window
Violations appear in Errors list window
Click to access Validate Options window
7 of 28
19
Siebel 7 Essentials
19.8
Archive Files
Contain object definitions exported from a repository
Available for importing into other repositories
Have .sif extension by default Are used to share object definitions in multiple repository development Are used to back up object definitions Can be version-controlled using source control systems
8 of 28
Siebel 7 Essentials
19.9
Exporting Object Definitions

Top-level object definitions can be exported to an archive file
Includes all child object definitions for selected parent definition
To export object definitions

Select the object definition or definitions Select Tools Add to Archive Select an existing (or create a new) archive file Click Save in the Export to Archive File window
9 of 28
19
Siebel 7 Essentials
19.10
Exporting Projects
Projects can also 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 window
10 of 28
Siebel 7 Essentials
19.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 Objects Import from Archive Select the archive file Indicate how to resolve conflicting object definitions
11 of 28
19
Siebel 7 Essentials
19.12
Resolve Import Conflicts

Set the default conflict resolution
Adjust individual resolutions by right-clicking them in the Object differences list
12 of 28
Siebel 7 Essentials
19.13
Compare Objects
Displays differences between selected object definition and another one:
In current local repository In archive file In repository on server
Allows developers to reconcile differences while comparing objects

Delete individual child object definitions Copy individual child object definitions in either direction
13 of 28
19
Siebel 7 Essentials
19.14
Compare Objects Continued

To compare object definition to one in archive or repository
Select object definition to be compared Select Tools Compare Objects Select type of comparison Choose the archive or repository
14 of 28
Siebel 7 Essentials
19.15

Examine the differences in the Compare Objects window
Definitions with difference highlighted
Differences displayed
15 of 28
19
Siebel 7 Essentials
19.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 field
Delete selected field

Module 19: Editing and Compiling Object Definitions 16 of 28
Modifying Definitions
A child object definition in either parent object definition can be deleted or copied to the other definition.
Siebel 7 Essentials
19.17
Source Code Control Integration

Automate integration with source code control for repository data
Creates archive when project checked in Check archive into code management system
ODBC to server and local databases
17 of 28
19
Siebel 7 Essentials
19.18
Backing Up the Development Database

Developers can back up local work by:
Using archive files to back up repository data Checking in projects into the server in order to back up repository data Copying the local database file (.dbf) in order to back up the entire database
Add to archive
.sif
Windows copy/paste
Server
Check in
Repository Data
18 of 28
Siebel 7 Essentials
19.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 runtime
Compile into .srf file located in the objects directory of the client application
Database Repository Data
Tools Application Compiling
Application Object Manager
.srf
Configured Application
19 of 28
19
Siebel 7 Essentials
19.20
Compile Options
Developers can compile
Projects Individual object definitions
20 of 28
Siebel 7 Essentials
19.21
Compile Projects
When starting and at milestones, compile All Projects to generate a new .srf file Subsequently, compile only Selected Projects or Locked Projects for an incremental compile To compile projects
Select Tools Compile Projects Select project or projects
Compile into client directory
21 of 28
Get Projects
Remember to compile any projects that you get to ensure that object definitions edited by your fellow developers are compiled into your .srf file.
19
Siebel 7 Essentials
19.22
Compile Objects
Top-level object definitions can be compiled individually
Compiles all child object definitions for the selected parent
To compile individual object definitions

Select the object definition or definitions Right-click and select Compile
22 of 28
Siebel 7 Essentials
19.23
Configuration File
Copy the default .cfg file for the application being customized Edit it to refer to the new .srf file
Copy .cfg file Change Repository File to refer to new .srf file
23 of 28
19
Siebel 7 Essentials
19.24
Testing a Modified Configuration

Test a modified configuration by launching a local Siebel remote Web client from Siebel Tools
Avoids having to migrate the modified .srf file to the server and restarting the object manager on the server
24 of 28
Siebel 7 Essentials
19.25
Setting the Run-Time Start-Up Parameters

Use View Options and select the Debug tab to set the runtime start up information
Browse to locate the modified .cfg file
Optionally provide login parameters
25 of 28
19
Siebel 7 Essentials
19.26
Launching the Local Web Client

Test the new configuration by selecting Debug Start
Collects login parameters if not already specified Launches the local Siebel remote Web client
26 of 28
Start
You may use the F5 function key to execute the Debug as well.
Start command
Siebel 7 Essentials
19.27
Summary
This module showed you how to:
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
27 of 28
19
Siebel 7 Essentials
19.28
Lab
In the lab you will:
Practice editing and validating object definitions in Siebel Tools Explore the use of diff and archive options in Siebel Tools Compile a custom .srf file
28 of 28
Siebel 7 Essentials
Understanding Siebel Template Files
20.1
Module 20: Understanding Siebel Template Files
20
Siebel 7 Essentials
20.2
Module Objectives
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

Understanding template structure and how to register, associate, and bind template files is necessary in order to deploy your Siebel eBusiness application
2 of 28
Reference
Siebel 7 Essentials
20.3
Siebel 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:
Graphical and text elements User data
Consist of standard HTML tags and Siebel-specific tags

<table width="100%" class="banner" cellpadding='0' cellspacing='0' border='0'> <tr> <td><img src="images/spacer.gif" height="29" width="10"></td> <td><swe:menu type="Default" width="275" height="29" bgcolor="#ccccff" fgcolor="#000000" /></td> HTML table tag
3 of 28
Sample HTML
The sample HTML tags shown in the slide are excerpted from the CCFrameBanner.swt template file.
20
Siebel 7 Essentials
20.4
Siebel Tags
Are a Siebel-developed library of tags that are processed at run time by the Siebel Web Engine to:
Retrieve object definitions from the repository and convert them to HTML Control layout repetitively through iteration
Serve as placeholders for Siebel-specific content

<swe:for-each-screen> Siebel tag to iterate over all screens <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=""> <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>
Module 20: Understanding Siebel Template Files 4 of 28
Siebel tag to insert the name of the screen
Sample HTML
The sample HTML tags shown in the slide are excerpted from the CCScreenbar_Tabs.swt template file.
Siebel 7 Essentials
20.5
Siebel Template Files

Can include other template files (swe:include tag)
Enables modularization of the template files
Permits efficient reuse of files Minimizes maintenance and development effort
<head> <title><swe:this property="Title"/></title> <swe:include file="CCStyleChoices.swt"/> </head>
Siebel tag to include another Siebel template file

Sample HTML
The sample HTML tags shown in the slide are excerpted from the CCSiteMap.swt template file.
20
Siebel 7 Essentials
20.6
Siebel Template Files Continued

Can include links to style sheets to define global parameters
Font family and size 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
From main.css
body, td,input,select,textarea { font-family: Arial,Helvetica,Sans-Serif; font-size: 8pt; } a { color: #6666cc; text-decoration:none; } a:visited { color: #6666cc; text-decoration:none;} a:active { text-decoration:none; } a:hover { text-decoration:underline; }
Siebel 7 Essentials
20.7
Siebel Template Files Continued

Are stored as separate files outside the Siebel repository
Located in the WEBTEMPL directory in a Siebel installation Have .swt extension
Are edited using a text or HTML editor of your choice
7 of 28
20
Siebel 7 Essentials
20.8
Web Template Explorer

Use the Web Template Explorer in Siebel Tools to:
Identify the template files included in a template file Examine the contents of a template file Invoke an editor to modify the template file
Invoke by selecting View Windows Web Templates Window
8 of 28
Siebel 7 Essentials
20.9
Using Template Files

Requires three types of relationships
Registering, associating, and binding
Object definitions (in the repository) specify these relationships

View
Associating
Applets
(View) Web template

Registering
Binding
(View) Template file

Applet placeholders
9 of 28
20
Siebel 7 Essentials
20.10
Registering
Creates an object definition in the repository that identifies the physical template file
View Applets
(View) Web template

Registering
Applet placeholders
10 of 28
Siebel 7 Essentials
20.11
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 evident that you need to create a new file.
20
Siebel 7 Essentials
20.12
Types of Templates
View templates are used to render Siebel views
Contain placeholders for applets
Applet templates are used to render Siebel applets

Contain placeholders for controls
Web page templates are used to render elements other than Siebel views and applets
Login pages Error pages Container pages
Uses Web page template
12 of 28
Siebel 7 Essentials
20.13
Container Page
Contains tags that render the elements that surround the view in a Siebel application
Menus Screen tabs Logos and graphics
View tabs
13 of 28
20
Siebel 7 Essentials
20.14
Associating
Identifies the Web Template object definition used to render the view, applet, or Web page
View
Associating
Applets
(View) Web template
Applet placeholders
14 of 28
Siebel 7 Essentials
20.15
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
15 of 28
20
Siebel 7 Essentials
20.16
Associating an Applet with Its Template

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 that mode

16 of 28
Siebel 7 Essentials
20.17
Applet Web Templates

Applets can use a different Applet Web Template object definition for different applet modes
Base (display only), edit, query
Required most often for applets in customer applications
Applet in base mode Applet in query mode
17 of 28
Applet
The Contact Service Request List Applet (eService) is shown as it displays in the base and query modes.
20
Siebel 7 Essentials
20.18
Associating a Web Page with Its Template

Creates a Web Page object definition and sets the Web Template property
Web page template used to render Web page
18 of 28
Web Page Template
Web page templates are all templates that are not a view or applet Web template. Examples of common Web page templates are login page, error page, and container page.
Siebel 7 Essentials
20.19
Binding
Maps the components of a view or applet to the placeholders in the corresponding template file
Binding Applets to Views Binding Controls to Applets
View
Applets
Applets
Controls/List
View Web template
Binding
Applet Web template
Binding
View Template File
Applet Placeholders
Applet Template File
Control Placeholders
19 of 28
20
Siebel 7 Essentials
20.20
Binding Information
Is specified in the repository with these object definitions
View Web Template Item Applet Web Template Item Web Page Item
Results in the corresponding element being displayed at run time
20 of 28
Siebel 7 Essentials
20.21
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.
20
Siebel 7 Essentials
20.22
Applet Web Template Items

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.
Siebel 7 Essentials
20.23
Web Page Items

Identify the links and buttons appearing on a Siebel Web page
Item Identifier is the id attribute value in the swe:pagetitem tag
Are used at run time by the Siebel Web Engine to position the links and buttons
23 of 28
swe:pageitem tags
The HTML and SWE tags shown in the slide are excerpted from the dCCFrameBanner.swt template file.
20
Siebel 7 Essentials
20.24
Mapping Placeholders
Not all placeholders in a template file need to be mapped
HTML source is generated only for mapped placeholders
Allows for views with varying number of applets to reference the same view Web template Allows for applets with varying number of controls to reference the same applet Web template
24 of 28
Siebel 7 Essentials
20.25
Template Reuse
A Siebel Web template can be referenced by multiple object definitions
Consequence of a template containing placeholders
Reuse of templates:
Enables standardization of display for views and applets Minimizes the number of templates required and the cost of creation and maintenance Simplifies application-wide modification and upgrade
25 of 28
20
Siebel 7 Essentials
20.26
Summary of Object Definitions

Registering, associating, and binding adds object definitions to the repository
Registering Web Template Web Template Files Associating Applet Web Template View Web Template Web Page Binding Applet Web Template Item View Web Template Files Web Page Item
Identifies the physical template file
Identifies the logical template used to render an applet, view, or container page Specifies how the components of an applet, view, or container page are mapped
26 of 28
Siebel 7 Essentials
20.27
Summary
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
27 of 28
20
Siebel 7 Essentials
20.28
Lab
Determine the template objects associated to view and applet objects Examine the binding in views and applets Edit parameters in a style sheet to modify the UI of a Siebel application
28 of 28
Siebel 7 Essentials
Configuring Applications and Screens
21.1
Module 21: Configuring Applications and Screens
21
Siebel 7 Essentials
21.2
Module Objectives
Customize container page components including page and view tabs and system menus Modify the text in the startup splash screen

Enables you to configure aspects of the interface to meet your companys requirements
2 of 19
Siebel 7 Essentials
21.3
The Container Page

Web page contents with Siebel data and formatting
Renders the elements that surround the view in a Siebel application
Container Page
3 of 19
21
Siebel 7 Essentials
21.4
Specifying the Container Page

The Container page is specified in the Application object definition
Container Web Page: Specifies the Container Page
4 of 19
Siebel 7 Essentials
21.5
The Container Page: Employee Application

Container page sections are composed of frames
Banner frame Screenbar frame Viewbar frame
Content frame
5 of 19
Content Frame
Configuration of the Content frame will be covered in a later module. The Content frame contains the views.
21
Siebel 7 Essentials
21.6
The Banner Frame

Contains the application-level menus and branding area
Application-level menus
Branding area
6 of 19
Banner Frame Template CCFrameBanner.swt
Siebel 7 Essentials
21.7
The Banner Frame: Application Level Menu

Assign the application-level menu items to the Generic WEB menu
Position: Specifies order of appearance
Caption: Specifies displayed text
7 of 19
21
Siebel 7 Essentials
21.8
The Banner Frame: Branding Area

The branding area may contain additional images such as
Company logo Graphic to illustrate primary purpose of page
Modify the CCFrameBanner.swt template file to add an image Modify main.css to change background color
<td align="right background="images/banner_back.gif"><a href="http://www.siebel.com" target="_blank"><img src="images/ebus.gif" border="0"></a> </td>
8 of 19
main.css
This is the cascading style sheet that controls visual attributes.
Siebel 7 Essentials
21.9
Screenbar Frame
Contains screen tabs for major screens
A screen is a collection of views
9 of 19
Screenbar Frame Template
CCFramceScreenbar.swt
21
Siebel 7 Essentials
21.10
Screenbar Frame: Screen Tabs

Create a page tab object definition for each screen you want to appear Select screens that will appear as tabs, mark all others Inactive
Inactive: Select if you do not want the tab to show
Text: Specifies text that appears on page bar
Sequence: Specifies page tab order appearance in screenbar
10 of 19
Siebel 7 Essentials
21.11
The Viewbar Frame

Contains
Siebel Application Toolbar
History menu Customer Dashboard control
Show drop-down list box

Views
Show drop-down list box
History menu
Dashboard
11 of 19
Appears in employee applications only.
21
Siebel 7 Essentials
21.12
The Viewbar Frame: Siebel Application Toolbar

Create Toolbar Object Definitions for each toolbar
Dashboard History
Dashboard toolbar
12 of 19
Siebel 7 Essentials
21.13
Screen View
Edit the Screen View definitions to set the display text and sequence for views
Menu Text: Text that appears in site map
Sequence: Defines order in drop-down lists and view tabs
Viewbar Text: Text that appears in Show dropdown list and view tabs
13 of 19
21
Siebel 7 Essentials
21.14
The Container Page: Customer Application

Has the same frames as the Employee application
Fewer objects are in the frames With a few exceptions, objects are configured similarly
Banner frame Screenbar frame Viewbar frame Content frame
14 of 19
Siebel 7 Essentials
21.15
The Banner Frame: Customer Application

Contains global navigation hyperlinks
15 of 19
21
Siebel 7 Essentials
21.16
The Banner Frame: Customer Application Continued

Change caption in Web Page Item
Caption: Changes displayed text
16 of 19
Siebel 7 Essentials
21.17
Configuring Startup Text

Specify the text that appears in the splash screen by editing the parameter in the .cfg file
Mobile clients only
17 of 19
Reference
Siebel Applications Administration Guide
21
Siebel 7 Essentials
21.18
Summary
Customize container page components including page and view tabs and system menus Modify the text in the startup splash screen
18 of 19
Siebel 7 Essentials
21.19
Lab
Configure startup text Customize page tabs and view tabs Customize system menus Add a graphic to the banner frame Customize the color and banner frame graphic of the customer application
19 of 19
21
Siebel 7 Essentials
21.20
Siebel 7 Essentials
Configuring Views
22.1
Module 22: Configuring Views
22
Siebel 7 Essentials
Configuring Views
22.2
Module Objectives
Explain the role of basic view templates and Siebel tags for views Create and administer a view Associate a view with a template

Enables you to configure views to meet your companys business requirements Enables you to make new views available to users
2 of 24
Siebel 7 Essentials
Configuring Views
22.3
Views
Consist of one or more lists or forms Reference a single business object Are grouped into a screen
3 of 24
Reference
22
Siebel 7 Essentials
Configuring Views
22.4
View Templates
Are used to render Siebel views
Contain placeholders for one or more applets
ID =1
ID =2
4 of 24
Siebel 7 Essentials
Configuring Views
22.5
View Templates Continued

Contain multiple applet tags Typically not all applet tags are mapped
ID =1
ID =2 ID =3-5 ID =6-7 ID =8-9 ID =10-11
5 of 24
22
Siebel 7 Essentials
Configuring Views
22.6
Applets in View Template

Can be related as
Peers Parent-child Parent-child-grandchild
Parent
Parent
Child Peer Peer
Child Grandchild
6 of 24
Siebel 7 Essentials
Configuring Views
22.7
Selecting a View Template

Find an existing view that has desired applet layout Examine the view template object definition to determine the view template to use
7 of 24
22
Siebel 7 Essentials
Configuring Views
22.8
Steps to Create a View

1. Create new view 1. Create new view 2. Associate view template 2. Associate view template with view object definition with view object definition 3. Bind applets to view template 3. Bind applets to view template 4. Configure threadbar 4. Configure threadbar Use View Use View Wizard Wizard
5. Register and assign view 5. Register and assign view

Module 22: Configuring Views 8 of 24
Best Practice
Siebel best practice is to modify an existing template. If the developer will be creating a new template then the extra steps of creating and registering the template are required and substituted for Step 1, Determine View 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 logical name to template file so that it can be referenced by other objects. Registering the template tells the registry that the template file exists.
Siebel 7 Essentials
Configuring Views
22.9
View Wizard
Use the View Wizard to create view and assign applet
Select the project and business object and enter the name and title of the view Select a Web template Assign applets
9 of 24
22
Siebel 7 Essentials
Configuring Views
22.10
1. Create a New View

Create a new View object definition
Assign a view name, project, business object, and view title
View name
Title appears in Show drop-down list or view tab
10 of 24
Siebel 7 Essentials
Configuring Views
22.11
2. Associate View Template and View

Assign the template the view will use
Add a View Web Template object definition to the view
Set the following properties: Name, Web Template
11 of 24
22
Siebel 7 Essentials
Configuring Views
22.12
3. Bind Applets to View Template

Steps
1. Launch the Web View Editor 2. Drag the applets from the list onto the placeholders in the view template This creates the View Web Template Items in the repository 3. Save the template
12 of 24
Siebel 7 Essentials
Configuring Views
22.13
3. Bind Applets to View Template Continued

Launch the Web View Layout Editor
The Web View Layout Editor opens the template file and the applets window
1. Right click View Web Template object 2. Select Edit Web Layout
13 of 24
22
Siebel 7 Essentials
Configuring Views
22.14

Drag the applets from the applet window to the applet placeholders in the Web View Editor
Drop onto applet placeholder Drag applet from Applet window
14 of 24
Siebel 7 Essentials
Configuring Views
22.15

View Web Template Item
Is created during drag-and-drop operation using the Web View Editor Associates an applet in the repository with an applet identifier in the View template Is an object definition containing binding specification for a view
Properties are Name, Item Identifier, and Applet
<swe:applet id=1"/>
Module 22: Configuring Views 15 of 24
22
Siebel 7 Essentials
Configuring Views
22.16

Default Applet Mode for applets in a new view is Base Set the Applet Mode appropriately
Applet Mode
16 of 24
Siebel 7 Essentials
Configuring Views
22.17
4. Configure Thread Bar

The Thread bar tracks user navigation among views
Thread bar
Edit the View definition to set the display text for the Thread bar
Thread Title: Displays text in Thread bar
17 of 24
22
Siebel 7 Essentials
Configuring Views
22.18
5. Assign View to a Screen

Create a new Screen View definition to add the view to the desired screen
Set Menu and Viewbar Text
Menu Text appears in the Site Map

Viewbar Text appears in the Show drop-down list or view tabs

18 of 24
Siebel 7 Essentials
Configuring Views
22.19
6. Register and Assign View

Views must be administered in the client application to make them available to users
Register the view Assign the view to one or more responsibilities
19 of 24
22
Siebel 7 Essentials
Configuring Views
22.20
6. Register and Assign View Continued

Navigate to Application Administration Views in the client application
Copy and paste view name from object definition in Tools to the View record
Copy view name
Paste view name
20 of 24
Siebel 7 Essentials
Configuring Views
22.21
6. Register and Assign View Continued

Navigate to Application Administration Responsibilities in the client application
View will not be available unless the user has this responsibility
Add new view to responsibility
21 of 24
22
Siebel 7 Essentials
Configuring Views
22.22
View Access Location on UI

Views can be accessed through
Show drop-down list View tabs
Show drop-down list
View tab
22 of 24
Siebel 7 Essentials
Configuring Views
22.23
Summary
Explain the role of basic view templates and Siebel tags for views Create and administer a view Associate a view with a template
23 of 24
22
Siebel 7 Essentials
Configuring Views
22.24
Lab
Determine displayed view name Modify display text for an existing view Modify applets in a view
24 of 24
Siebel 7 Essentials
Configuring List Applets
23.1
Module 23: Configuring List Applets
23
Siebel 7 Essentials Siebel Systems, Inc.
23.2
Module Objectives
Describe applet template features Create a list applet using the List Applet Wizard Edit list column definitions

Enables you to configure applets that display your companys data
2 of 28
Reference
Siebel 7 Essentials
23.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 Displays relatively few fields due to width of monitor viewable area
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 Will be covered in the next module
Module 23: Configuring List Applets 3 of 28
Additional Applet Types
The following are some additional applet types (reference Siebel Bookshelf for a complete list): Catalog List Chart Explorer view Hierarchical list Message Multi value group applet Pick applet Rich list Salutation
23
23.4
Applet Class Property

Determines the behavior of the applet
Specifies the C++ class used at run time for the applet
Is set to CSSFrameList for list applets Is set to CCSFrame for form applets Should typically never be changed
Specialized classes are associated with specialized business components and applets
4 of 28
Specialized Applet
Examples of specialized applets include Calendar Applets and Gantt Chart Applets.
Siebel 7 Essentials
23.5
List Applet
Displays one or more records in a list table format
Each row displays fields from one record in the business component
Typically includes two to four action control buttons Supports drilldown to other views through hyperlinked fields
One record
5 of 28
23
23.6
List Applet Action Control Buttons

Use next record and previous record buttons
Allow scrolling one set of records at a time
New button
Creates a new record for the list
May invoke a different applet Web template Use the New button or CTRL-N
Save button
Immediately saves record
In customer application user must explicitly save new or changed records using Save button In employee application you can save by stepping off the record (implicit save)
6 of 28
Siebel 7 Essentials
23.7
List Applet Web Templates

List applets can have multiple Web templates, called modes
Typical modes are Base, Edit, and Edit List
Choose the template based on desired applet functionality

Hint: Look at template definitions of similar applets
7 of 28
23
23.8
Base Mode
Does not permit user to edit, query, or enter new records directly in applet
Depending on business logic and the purpose of the list applet, you can enable these functions through buttons or the applet menu
Fields cannot be edited in list applet
8 of 28
Siebel 7 Essentials
23.9
Edit Mode
Appears as a form applet Is invoked by buttons or applet menu from base mode Allows user to enter new records or edit existing records
9 of 28
Template
The template most commonly used for list applets in base or edit list mode is CCAppletList_B_EL.swt.
Primary list applets allow editing fields in the current record. Usually, there is a form right beneath the list applet in which the record can be edited. This is addressed more fully in the next module.
23
23.10
Edit List Mode

Permits users to edit fields in a list applet
Editing is enabled by default You can disable editing by setting the HTML List Edit property for the column to FALSE
Click New to create a new blank record in the list
Edit fields directly in list applet

Module 23: Configuring List Applets 10 of 28
Siebel 7 Essentials
23.11
Applet Mode Property

Appears in the View Web Template Items object definition Determines which mode the user sees when a view is invoked
11 of 28
23
23.12
Creating a List Applet

You can follow these steps to create a new list applet
1. Create new applet object definition 1. Create new applet object definition
2. Associate applet template 2. Associate applet template with applet object definition with applet object definition
3. Bind controls to applet template 3. Bind controls to applet template
Or you can use the List Applet Wizard

Automates these steps Generally, the preferred method
12 of 28
Siebel 7 Essentials
23.13
List Applet Wizard

Ensures object definitions and properties are created
Ensures steps are not omitted
Increases developer productivity

Speeds project completion
To invoke the List Applet Wizard, select File New Object

In the Applets tab, select List Applet and click OK
13 of 28
23
23.14
Using the List Applet Wizard

Use the List Applet Wizard to create a new list applet Assign a project, business component, applet name, and title
Creates an applet object definition in Tools
Business Component
14 of 28
Tip
Check out or lock project before using the Applet Wizard.
Siebel 7 Essentials
23.15
Using the List Applet Wizard Continued

Select Web templates for Web layout
Associates template and applet
Normally shows only templates for list applets; if checked shows all templates
15 of 28
Review
Associating a template and an applet in Tools lets the program know which template(s) to use for the applet.
23
23.16

Choose the Business Component fields that will appear in the Web layout
Creates the Applet Web Template Items
Necessary to bind the controls to the applet
Select fields to show in the applet Arrange fields in order to show in the applet
16 of 28
Columns
If you add all the columns in the business component, you can delete and add them later as necessary.
Siebel 7 Essentials
23.17

Choose the HTML controls to be added to the applet
Control method invoked when control icon selected
Icons
Tip: Let the Wizard create all default controls so you dont have to add them manually.
17 of 28
Tip
The vertical sequence of the fields in this screen of the wizard determines their sequence from left to right in the resulting list applet. It is easier to set the sequence here than reorder them in the Edit Web Layout editor.
23
23.18

The basic HTML controls for applets come from the Model HTML Controls Applet in Tools
This is a dummy applet not based on any business component Controls added to this applet are automatically added to any new applet you create using the applet wizards
18 of 28
Siebel 7 Essentials
23.19

Review the applet object you have defined
If information is correct, click Finish
19 of 28
23
23.20

Finishing the list applet
Creates required object definitions for
Applet Control List List column
Maps
Applet Web Templates Applet Web Template Items
Sets applet class to CSSFrameList Invokes the Web Layout Editor
20 of 28
Siebel 7 Essentials
23.21
Web Layout Editor

Use Edit Web Layout Editor to add, remove, and reorder the columns displayed
To delete columns select Delete
To add, drag and drop controls and columns
21 of 28
23
23.22
Applet Title
Change the Title property to set the applet display name
22 of 28
Siebel 7 Essentials
23.23
List Column Definitions

Edit the List Column definition to:
Set the column display name Set the column to read only Enable or disable popup editing Enable or disable special processing at run time Change the HTML Type
23 of 28
HTML Type
Attribute of an HTML Input tag which determines what type of HTML control will be used. Some common choices are textbox, checkbox, label, and radio button.
23
23.24
Show in List Property

Determines whether a field appears in the list applet as first displayed
If set to FALSE, the field will be available by selecting Columns Displayed from the applet-level menu
24 of 28
Siebel 7 Essentials
23.25
List Control Definition

List applets require the List control in order to display the collection of list columns
Do not edit this control
25 of 28
23
23.26
List Applet Template

Determines the layout and presentation of the list applet
Each item on the applet has an Item Identifier property Each Item Identifier matches a Control ID in the template The Control ID tells the Siebel Web Engine where and how to render the item
Is reusable
For example: a Contact list applet and an Account list applet may use the same list applet template
<swe:for-each startValue="501" count =20 iteratorName="currentId"> <swe:control id="swe:currentId>
26 of 28
Siebel 7 Essentials
23.27
Summary
Describe applet template features Create a list applet using the List Applet Wizard Edit list column definitions
27 of 28
23
23.28
Lab
Create list applets Modify list applets Create and administer a view
28 of 28
Siebel 7 Essentials
Configuring Form Applets
24.1
24
Module 24: Configuring Form Applets
Siebel 7 Essentials
24.2
Module Objectives
Create a form applet using the Form Applet Wizard Modify an existing form applet Describe the structure of a form applet Web template

Enables you to configure applets that display your companys data Using Applet Wizards reduces the effort to configure applets
2 of 19
Reference
Siebel 7 Essentials
24.3
Form Applet
Displays one record at a time in a data entry form layout
Field controls display fields in the business component
Field Caption property displays caption text
24
Button controls initiate an action when clicked

MiniButton controls Caption Textbox control
3 of 19
Siebel 7 Essentials
24.4
Form Applet Appearance and Function

Fields are usually editable
Can be read-only
Allows scrolling one record at a time
Read-only fields (gray background)
4 of 19
Siebel 7 Essentials
24.5
Expanding and Collapsing Form Applets

Collapsed (Less)
Is the default display Shows limited set of fields Only displayed fields can be edited
24
Expanded (More)
Shows all fields Full edit capabilities (all unprotected fields can be edited)
User can toggle using the show more button
5 of 19
Read Only Fields
Fields are usually editable in form applets but can be configured to be read only.
Siebel 7 Essentials
24.6
Form Applet Modes

Form applets only use Base and Edit modes
Base mode is read-only Edit mode permits editing
The View Web Template Items object definition determines which mode is displayed when a view is invoked
6 of 19
Siebel 7 Essentials
24.7
Create a New Form Applet

Use the Form Applet Wizard to create a form applet Assign the project, business component, applet name, and title
24
Business component
7 of 19
Siebel 7 Essentials
24.8
Create a New Form Applet Continued

Select Web templates for Web layout
Associates template and applet
8 of 19
Siebel 7 Essentials
24.9

Select fields to appear in the form applet
24
Fields come from the business component chosen in the last screen
Because forms are two-dimensional, there are no buttons to arrange fields up and down.
9 of 19
Adding Fields
Some business components have numerous fields. Add those fields you will use or think you may use.
Siebel 7 Essentials
24.10

Choose the HTML controls to be added to the applet
Adds necessary templates for controls
Tip: Let the wizard create all default controls so you dont have to add them manually.
10 of 19
Siebel 7 Essentials
24.11

Finish the form applet
Creates required object definitions for the applet and controls Sets applet class to CSSFrame
24
11 of 19
Siebel 7 Essentials
24.12
Modify a Form Applet

Use Web Layout Editor to modify a form applet
Add, delete, and reposition controls
Drag and drop columns and controls
12 of 19
Siebel 7 Essentials
24.13
Modify a Control
Use Web Layout Editor to edit text and button controls
Edit control properties in Properties window
24
13 of 19
Siebel 7 Essentials
24.14
Setting More/Less Mode on a Field

To have a field display only when applet is expanded, set the More property in Edit Web Layout Editor
Right-click control and set More property
14 of 19
Mode
You can also change the Mode property to More in Tools in the Applet Web Template Items object definition. If you enter More for the Mode property, the field will not display in the collapsed applet. Setting More in the Web Layout Editor sets the Mode property for the Applet Web Template Item to More.
Siebel 7 Essentials
24.15
Setting More/Less Mode on a Field Continued

To enable expanding and collapsing the form applet, create a ToggleLayout control and add it using the Web Layout Editor
24
Set these properties

Module 24: Configuring Form Applets 15 of 19
Siebel 7 Essentials
24.16
Preview the Applet

Right-click and select Preview to see how the applet appears
Edit Web Layout mode
Preview mode
16 of 19
Siebel 7 Essentials
24.17
Form Applet Template

Determines the layout and presentation of the form applet
Siebel Web Engine maps Web Template Item Identifiers to control IDs in the template
24
Many form applets can use the same template

<swe:for-each startValue="1301" count =10 iteratorName="currentId"> <swe:control id="swe:currentId" hintMapType="FormItem">
17 of 19
Siebel 7 Essentials
24.18
Summary
Create a form applet using the Form Applet Wizard Modify an existing form applet Describe the structure of a form applet Web template
18 of 19
Siebel 7 Essentials
24.19
Lab
Modify a form applet
24
19 of 19
Siebel 7 Essentials
24.20
Siebel 7 Essentials
Understanding Business Components and Joins
25.1
25
Module 25: Understanding Business Components and Joins
Siebel 7 Essentials
25.2
Module Objectives
Describe the structure of business components and joins Map fields to columns in base, joined, and extension tables Create joins and join specifications to bring data in from a joined table

Enables you to configure your companys business logic
2 of 20
Siebel 7 Essentials
25.3
Business Component
Represents a fundamental business entity in the users world Is a logical grouping of data from one or more tables Consists of single-value fields that reference a column in a table
Opportunity
Name Description Decision Level Sales Stage Sales Stage Phase
25
S_OPTY
NAME ROW_ID DESC_TEXT CURCY_CD
S_OPTY_X
ROW_ID PAR_ROW_ID ATTRIB_01 ATTRIB_09 ATTRIB_39
S_STG
STG_ORDER ROW_ID NAME PHASE_CD
3 of 20
Reference
Siebel 7 Essentials
25.4
Business Component Properties

Table: Specifies the base table Class: Specifies the C++ class used at run time for the business component
Determines the behavior of the business component Is usually set to CSSBusComp
Certain business components have specialized classes which add extra processing specific to that business component
Base table
C++ class
4 of 20
Siebel 7 Essentials
25.5
Base Table
Has columns that store the main fields for the business component
Fields built on base tables can be edited
Opportunity
Name Description Decision Level Sales Stage Sales Stage Phase
25
S_OPTY
CURCY_CD ROW_ID NAME DESC_TEXT
Base table
5 of 20
Siebel 7 Essentials
25.6
Mapping a Field to a Column in a Base Table

Create a new Single Value Field definition
Leave the Join property blank
Select the column to store the data

Column picklist shows fields from the base table
Set the field type
Columns from S_OPTY

Module 25: Understanding Business Components and Joins 6 of 20
Siebel 7 Essentials
25.7
Type Property for Fields

Specifies the data type for the field Must correspond to the physical type of the associated column Consists of a set of Siebel-defined types Must be set by the configurator
Are defaulted automatically by Siebel Tools to DTYPE_TEXT when fields are created
25
7 of 20
Foreign Key Fields
The Type property for a foreign key field must be set to DTYPE_ID even though the referenced column has a physical type of varchar 15.
Siebel 7 Essentials
25.8
Additional Data for Business Components

Business components can include data from additional related (joined) tables
For display in applets For use in processing by the business component
Fields referencing columns in joined tables are read-only

Opportunity
Name Description Sales Stage Sales Stage Phase
Base table Joined table S_OPTY

NAME ROW_ID DESC_TEXT CURCY_CD
S_STG
PHASE_CD ROW_ID NAME STG_ORDER
8 of 20
Siebel 7 Essentials
25.9
Joined Tables
May provide one related row for each row in the base table
Not all rows in a base table are required to have a related row
25
Have a 1:M or 1:1 relationship with the base table

Foreign key for the relationship is in the base table
Base table S_OPTY
ROW_ID NAME DESC_TEXT CURCY_CD CURR_STG_ID
Joined table S_STG

ROW_ID NAME PHASE_CD STG_ORDER
9 of 20
Joined Tables
Joined tables may be thought of as providing look-up or reference data; data in joined tables is read-only.
Siebel 7 Essentials
25.10
Join Definition
Specifies the joined table from which to retrieve data Defaults the alias property to the name of the joined table
Must assign a different value to the alias for:
A self-join Multiple relationships with the joined table
Specifies the type of SQL join to use
Name of Join
Joined table
10 of 20
Siebel 7 Essentials
25.11
Outer Join Flag

Set the 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 set the flag if there always is a related row in the joined table
25
Use outer join

Module 25: Understanding Business Components and Joins 11 of 20
Setting the Outer Join Flag
It will not be necessary to set the Outer Join Flag property when the foreign key column is required. In addition, there may be business rules and policies that require a related row in the joined table.
Siebel 7 Essentials
25.12
Join Specification Definition

Specifies how to retrieve the related row from the joined table
Based on the foreign and primary keys used to relate the base and joined tables
Opportunity
Name Description Sales Stage Id
Foreign key S_OPTY

DESC_TEXT ROW_ID NAME CURCY_CD CURR_STG_ID
Primary key
S_STG
STG_ORDER ROW_ID NAME PHASE_CD
12 of 20
Siebel 7 Essentials
25.13
Mapping a Field to a Column in a Joined Table

Create the required join if it does not exist Create the single-value field
25
13 of 20
Siebel 7 Essentials
25.14
Create a Join
If the required join does not exist
Verify the relationship is 1:1 or M:1 Verify there is a foreign key column for the relationship in the base table Create a field in the business component to reference the foreign key column Create the Join object definition Create the Join Specification object definition
14 of 20
Siebel 7 Essentials
25.15
Create the Single Value Field

Set the Join property
Select the alias for the desired join Inspect the Join and Join Specification definitions to verify the desired table and foreign keys have been selected
25
Select the desired column in the joined table

The column picklist shows the fields from the joined table
Set the appropriate type
Columns from S_STG
15 of 20
Siebel 7 Essentials
25.16
Extension Table
Provides additional columns to store business component data
Opportunity
Name Budgeted Decision Level Sales Stage Phase
Base table S_OPTY

ROW_ID CURCY_CD NAME DESC_TEXT
Extension table S_OPTY_X

PAR_ROW_ID ROW_ID ATTRIB_01 ATTRIB_09 ATTRIB_39
Joined table S_STG

ROW_ID STG_ORDER NAME PHASE_CD
16 of 20
Siebel 7 Essentials
25.17
Implicit Joins
Fields on extension tables use implicit joins
Are predefined for all extension tables for the base table for the business component
Name of an implicit join is always the name of the extension table
25
Do not appear as Join object definitions Appear in the picklist for the Join property in a single value field
S_OPTY_X does not appear here

S_OPTY_X appears here
17 of 20
Siebel 7 Essentials
25.18
Mapping a Field to a Column in an Extension Table

Set the Join property by selecting the name of the desired extension table
A Join appears automatically for each extension table
Select an unused column that has the desired type

Column picklist shows columns from the selected extension table
Set the appropriate field type Fields on extension tables can be edited
Columns from S_OPTY_X
18 of 20
Extension Tables
Extension tables can be thought of as a continuation of the base table. Hence fields built on an extension table can be edited just like fields built on the base table.
Siebel 7 Essentials
25.19
Summary
Describe the structure of business components and joins Map fields to columns in base, joined, and extension tables Create joins and join specifications to bring data in from a joined table
25
19 of 20
Siebel 7 Essentials
25.20
Lab
Examine how fields in a business component map to columns in a base and joined table Create a join to bring in data from another table
20 of 20
Siebel 7 Essentials
Business Components and Joins: Party Extension Tables
26.1
26
Module 26: Business Components and Joins: Party Extension Tables
Siebel 7 Essentials
26.2
Module Objectives
Map fields in party business components Create and use joins and join specifications to bring in data from party tables

2 of 16
Siebel 7 Essentials
26.3
Joins and Party Business Components

Require additional considerations for:
Mapping fields in party business components Bringing party data into a non-party business component Bringing party data into a party business component
26
Note: Party data refers to data stored in a S_PARTY extension table such as S_CONTACT or S_ORG_EXT
3 of 16
Siebel 7 Essentials
26.4
Mapping Fields in Party Business Components

Party business components:
Have S_PARTY as the base table But store their main data in S_PARTY extension tables
Main fields are mapped using the implicit join for the extension table
Contact
First Name Last Name Birth Date
S_PARTY
ROW_ID NAME PARTY_TYPE_CD PARTY_UID
S_CONTACT
ROW_ID FST_NAME LAFST_NAME BIRTH_DT PAR_ROW_ID
Main columns uses the implicit join to S_CONTACT

4 of 16
S_PARTY Extension Tables
The following tables are some of the extension tables for S_PARTY: S_BU S_CONTACT S_ORG_EXT S_POSTN S_USER In addition, tables such as S_CONTACT_X (which is the 1:1 extension table for the S_CONTACT table) are formally a S_PARTY extension table as well. To determine 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.
Siebel 7 Essentials
26.5
Bringing Party Data into a Non-Party Business Component

Example: Bringing account data into the opportunity business component for display in an opportunity applet
26
Opportunity
Name Description Account Account Location
5 of 16
Siebel 7 Essentials
26.6
Join Definition
References the extension table storing the data of interest
Opportunity
Name Description Account
S_OPTY
ROW_ID DESC_TEXT NAME CURCY_CD
S_ORG_EXT
ROW_ID LOC
6 of 16
S_PARTY extension table

NAME
Siebel 7 Essentials
26.7
Join Specification Definition

Source field (as before) references the relevant foreign key column to the joined table Destination column must reference the PAR_ROW_ID column in the joined table
26
7 of 16
Siebel 7 Essentials
26.8
PAR_ROW_ID
Is referenced in the Join Specification
Identifies the primary key of the related account record
Opportunity
Name Description
Source field
Account Id Account
S_OPTY
ROW_ID DESC_TEXT NAME PR_DEPT_OU_ID
S_ORG_EXT
NAME PAR_ROW_ID ROW_ID LOC
S_PARTY
PARTY_UID ROW_ID NAME PARTY_TYPE_CD
Identifies primary key of the related account record
Destination Column
8 of 16
Siebel 7 Essentials
26.9
Bringing Party Data into a Party Business Component

Example: Bringing account data into the contact business component for display in a contact applet
26
Contact
Last Name Account Id Account Account Location
9 of 16
Siebel 7 Essentials
26.10
Join Definition
Do not use the implicit join for S_ORG_EXT that already exists
Both S_CONTACT and S_ORG_EXT are extension tables of S_PARTY
Use an explicit join to S_ORG_EXT based on the appropriate foreign keys

Will have a different alias
Explicit join, cannot be named S_ORG_EXT
10 of 16
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, S_USER, and so forth. These implicit joins are used in other party business components to map their main data.
Siebel 7 Essentials
26.11
Mapping a Field to a Column in a Party Table

Create the required join if it does not exist Create the single value field
26
11 of 16
Siebel 7 Essentials
26.12
Creating a Join to a Party Table

Verify the relationship is 1:1 or M:1 Identify the foreign key column for the desired relationship to the joined table Create, if necessary, a field in the business component to reference the foreign key column Create the Join
Assign an appropriate alias property
Create the Join Specification

Use PAR_ROW_ID for the destination column
12 of 16
Siebel 7 Essentials
26.13
Mapping a Field to a Column in a Party Table

Select the appropriate explicit join
Do not use the implicit join to the table
Select the desired column in the joined table Set the appropriate type
26
Select the explicit join instead of S_ORG_EXT
13 of 16
Siebel 7 Essentials
26.14
Considerations
Mapping fields in party business components
Use the implicit join for the extension table
Bringing party data into a non-party business component

Create the join specification based on PAR_ROW_ID
Bringing party data into a party business component

Use the appropriate explicit join
14 of 16
Siebel 7 Essentials
26.15
Summary
Map fields in party business components Create and use joins and join specifications to bring in data from party tables
26
15 of 16
Siebel 7 Essentials
26.16
Lab
Examine mappings of fields to party tables Bring data in from a party table
16 of 16
Siebel 7 Essentials
Understanding Business Objects and Links
27.1
Module 27: Understanding Business Objects and Links
27
Siebel 7 Essentials
27.2
Module Objectives
Describe the role of business objects and links Create links and business objects

2 of 14
Siebel 7 Essentials
27.3
Business Objects
Are a collection of related business components that represent a major area of the business
One business component is the parent or master Other business components are the children
Provide the foundation for views

Business Object (BO)
Account
Account Master BC provides focus for BO
27
Business Component (BC)
Action
Product
Contact
3 of 14
Reference
Siebel 7 Essentials
27.4
Business Object Definition

Specifies the business object
Is usually named for the master business component
Account
Account
Action
Product
Contact
4 of 14
Siebel 7 Essentials
27.5
Business Object Component Definition

Specifies that a business component is to be included in the business object Link property specifies the link definition that relates the parent and child business components
27
Parent BC
Child BCs
5 of 14
Siebel 7 Essentials
27.6
Link Definition
Specifies which records to retrieve from the child business component
Supports master-detail views
Specifies the foreign keys to populate when new child records are created Used with both 1:M and M:M relation between parent and child data
Account
Account Links
Action
Product
Contact
6 of 14
Siebel 7 Essentials
27.7
1:M Link
Used for 1:M relationship between parent and child business components
Foreign key (FK) for the relationship is in the child table
FK field in child BC
27
Defaults to parent BC/child BC
PK field in parent BC (defaults to Id)
7 of 14
Siebel 7 Essentials
27.8
Cascade Delete Property

Specifies whether child records of a 1:M relationship are deleted when the parent record is deleted
Delete: If a parent record is deleted, all child records are deleted Clear: Does not delete but clears, the foreign key column None: Does not delete nor clear the foreign key column
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?
8 of 14
Siebel 7 Essentials
27.9
M:M Link
Used for M:M relationship between parent and child business components
Foreign keys for the relationship are in the intersection table
27
Intersection table with FK columns
9 of 14
Siebel 7 Essentials
27.10
Creating Business Objects

Create a Business Object definition for the new business object Add the master business component
Create a Business Object Component definition Leave the Link property blank
Add the child business components

Create the link for the master and child business components Create a new Business Object Component definition for the child Set the Link property
10 of 14
Link Property
When a business object component is created without setting the link property, all records of that business component will be displayed in the view. This is used when creating views with peer-to-peer applets.
Siebel 7 Essentials
27.11
Grandchild Business Components

Business objects may include grandchild business components Used in parent-child-grandchild views
27
Activity Plan BC Activity Plan Action BC Child activities for selected activity plan
Module 27: Understanding Business Objects and Links 11 of 14
Grandchild View
A parent-child-grandchild view uses three applets to display parent, child, and grandchild data in a single view. The records displayed in the grandchild applet are related directly to the selected record in the child applet and not to the selected record in the parent applet.
Siebel 7 Essentials
27.12
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 BC
12 of 14
Siebel 7 Essentials
27.13
Summary
Describe the role of business objects and links Create links and business objects
27
13 of 14
Siebel 7 Essentials
27.14
Lab
Create a new business component and link Add the new business component to an existing business object Create new applets and a view Add the new view to an existing screen
14 of 14
Siebel 7 Essentials
Configuring Business Components and Fields
28.1
Module 28: Configuring Business Components and Fields
28
Siebel 7 Essentials
28.2
Module Objectives
Edit business component properties to capture business logic Edit field properties to capture business logic

Editing the properties of business components and fields helps you to more accurately and fully capture your business logic
2 of 24
Siebel 7 Essentials
28.3
Business Components Properties

Change the properties of business components to capture business logic Commonly used properties include
Editing properties
No Delete No Insert No Merge No Update
Owner Delete Search Specification Sort Specification
28
3 of 24
Reference
Object Types Reference
Siebel 7 Essentials
28.4
Properties for Editing

Set the editing properties at the business component level to prevent deleting, inserting, merging, and updating of records in all applets
Even administrators cannot edit records if these properties are set
Example: To maintain record continuity, users cannot delete or change price lists once they have been created
4 of 24
No Delete
If TRUE, once a record is created and committed, users cannot delete it.
No Insert
If TRUE, users cannot add new records.
No Merge
If TRUE, users cannot merge records.
No Update
If TRUE, users cannot change existing records.
Siebel 7 Essentials
28.5
Properties for Editing Continued

Set these properties to FALSE at the business component level so that you can make exceptions at the applet level
If you want even one applet to have edit privileges, you must set FALSE at the business component level You can also protect individual fields
Example:
Users can generally edit their personal contacts On the Contact Form ReadOnly Applet, they can not edit these
28
5 of 24
Siebel 7 Essentials
28.6
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 effective owner of the record
6 of 24
Siebel 7 Essentials
28.7
Search Specification Property

Specifies records to be retrieved by the business component
Typically used when there are multiple business components on the same main table
Example: The Personal Contact business component is distinguished from Contact by a search specification
Personal Contact is a Boolean flag field
28
7 of 24
Siebel 7 Essentials
28.8
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
Field Name in [ ] Operator
Logical Operator
Function
Must match exactly

Module 28: Configuring Business Components and Fields 8 of 24
Siebel 7 Essentials
28.9
Search Specifications
Are joined with an AND in business components and applets to determine the WHERE clause in the generated SQL statement
Avoid mutually exclusive search specifications Predefined queries also contribute to the WHERE clause
28
9 of 24
Siebel 7 Essentials
28.10
Search Specifications Continued

Example: Home page My Accounts list searches for records where
The organization is not an external organization The record has been updated in last 30 days The current user is the records owner
10 of 24
Siebel 7 Essentials
28.11
Sort Specification Property

Determines the sort order of the retrieved records
Use (DESC) or (DESCENDING) to sort that field in reverse order
Example: Contacts are sorted by name

Field Name or Names, no [ ]
Comma separated
28
Must match exactly
11 of 24
Siebel 7 Essentials
28.12
Sort Specification Performance Considerations

To ensure good performance, check whether an index exists for the business component base table
Use the columns from the index as the sort specification, in the same order
Avoid using a sort specification that references columns in different tables because indexes refer to one table only
12 of 24
Siebel 7 Essentials
28.13
Field Properties
Customize fields by editing property values Setting field properties at the business component level sets them across all applets
28
13 of 24
Siebel 7 Essentials
28.14
Required Property
Set the Required property to TRUE to prevent user from leaving field blank
Example: Contacts require last names
Attempting to save without a last name causes an error message Attempting to save a record without a value in a required field results in a warning message
Required fields in forms are marked with asterisks (*)

Siebel 7 Essentials
28.15
Read Only Property

Set the Read Only property to TRUE to prevent user from editing the value
Read only on all applets
28
15 of 24
Siebel 7 Essentials
28.16
Validation Property
Create a Validation property to ensure that field data is valid
Rule is checked when you save the record
Example: When creating a warranty for an asset, end date must be after start date
Attempting to save with an incorrect start and end date pair causes an error message
16 of 24
Siebel 7 Essentials
28.17
Validation Property Continued

Is expressed as a combination of logical operators, constants, field names, and predefined functions Can refer only to business component fields in the same record
Constant
Field name
28
Operator Logical Operator
17 of 24
Siebel 7 Essentials
28.18
Pre Default Values for Fields

Automatically assigns a value to a field for a new record
User can modify the field if it is displayed and not set to Read Only
Example: Income Currency Code for a new Contact is set to a system default currency code
System value Inherit from parent (in this case, from the Account to which this Contact belongs) Constant
Siebel 7 Essentials
28.19
Post Default Values for Fields

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
28
19 of 24
Siebel 7 Essentials
28.20
Calculated Fields
Derive their value from the values in other fields of the business component Cannot be stored in the database
So there is no associated column
Require setting the Calculated property to TRUE (shown as checkmark)
Blank
20 of 24
Siebel 7 Essentials
28.21
Calculated Value Property

Is an expression built from:
Field names in the same business component Field names from the parent business component
Current business component must the child in a detail view
Standard functions String, numeric, and logical operators
28
System functions
21 of 24
Reference
Siebel 7 Essentials
28.22
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 the functions in the query expression can be incorporated into the SQL statement
22 of 24
Siebel 7 Essentials
28.23
Summary
Edit business component properties to capture business logic Edit field properties to capture business logic
28
23 of 24
Siebel 7 Essentials
28.24
Lab
Incorporate business logic into the application by configuring properties of business components and fields
24 of 24
Siebel 7 Essentials
Creating a New BC Using the Standard 1:M Extension Table
29.1
Module 29: Creating a New BC Using the Standard 1:M Extension Table
29
Siebel 7 Essentials
29.2
Module Objectives
Describe the structure of a 1:M extension table Create a new business component (BC) using the 1:M extension table Add the 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 15
Siebel 7 Essentials
29.3
Business Problem
Siebel business components capture most commonly-used 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,
The contacts favorite restaurants

Name and location, price range, type of cuisine, and so on
To capture this kind of information requires:

Multiple fields to capture the details 1:M relationship to the parent entity
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table 3 of 15
Reference
Siebel Tools Reference Object Types Reference
Siebel 7 Essentials
29.4
Creating New Business Components

To capture this sort of information, create new business components as children of an existing business component
Used to add entities specific to your organization that are not in the Siebel repository Is an exception to the recommendation not to copy or modify existing business components
You base these business components on standard 1:M extension tables supplied by Siebel Systems Example: Create College and Restaurant business components for sales organization
Favorite Restaurants
Colleges Attended
Contact
4 of 15
Siebel 7 Essentials
29.5
Standard 1:M Extension Tables

Predefined in the repository for many business components Has name of main table appended with _XM
Contains many predefined ATTRIB columns of varying type
NAME column stores the name of the child entity
PAR_ROW_ID column stores foreign key to ROW_ID in main table TYPE column identifies the child business component
29
Siebel 7 Essentials
29.6
Multiple Business Components

You can use one _XM table to map multiple user-defined child business components Each business component has a unique TYPE value
Stored in the TYPE column of the _XM table
Each business component retrieves only those rows with its TYPE value
Colleges Attended
Type = College
S_CONTACT_XM
ROW_ID NAME TYPE PAR_ROW_ID
Favorite Restaurants
Type = Restaurant
6 of 15
Siebel 7 Essentials
29.7
User Key for _XM Table

NAME, TYPE, and PAR_ROW_ID serve as a user key for the _XM table
Must provide values for all 3 columns when creating a new record Combination must be unique
For business components with data that cannot be stored in a Varchar 100 column, you must still provide a unique value for NAME
Workaround is to store value of ROW_ID in NAME
29
Siebel 7 Essentials
29.8
Create New Business Component

Create a business component (BC) to represent the 1:M extension table
Set Table property to name of the 1:M extension table Set Class property to CSSBusComp Select the appropriate project
For Name, use a tag such as company initials to distinguish new BCs from Siebel-supplied BCs
Set Search Specification property to match the unique TYPE value for the business component
8 of 15
Siebel 7 Essentials
29.9
Create Fields for Business Component

Add fields that map to
TYPE column
Set Predefault Value property to value used in the BC search specification
PAR_ROW_ID NAME
Create additional fields for any other required data

Choose an ATTRIB column with the right type and length
29
Siebel 7 Essentials
29.10
Relating the Child and Parent BCs

Associate the newly configured child business component with the parent by:
Creating a link definition to relate child and parent records Including the child in the business object defined for the parent
Contact
XYZ Restaurant
10 of 15
Siebel 7 Essentials
29.11
Create the Link

Create a new 1:M link
29
Siebel 7 Essentials
29.12
Add Business Component to Business Object

Create a new Business Object Component definition for the child Set the Link property
12 of 15
Siebel 7 Essentials
29.13
Displaying Data from _XM Table

Build applets and views as required to display data from the child business component
Do not display the TYPE field to prevent users from changing the value
Applet Wizard
29
Siebel 7 Essentials
29.14
Summary
Describe the structure of a 1:M extension table Create a new business component (BC) using the 1:M extension table Add the business component to a business object
14 of 15
Siebel 7 Essentials
29.15
Lab
Create new business components Create the links, applets, and views needed to display the new business components
29
Siebel 7 Essentials
29.16
Siebel 7 Essentials
Configuring Navigation
30.1
Module 30: Configuring Navigation
30
Siebel 7 Essentials
30.2
Module Objectives
Configure drilldown to a related view Enable the thread bar Configure toggle applets

Enables you to add drilldowns and toggles to assist users in navigating Enables you to activate the thread bar to assist users
2 of 23
Siebel 7 Essentials
30.3
Navigation Using Drilldown

You can configure fields in a list for drilldown
When the user clicks the field, 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 23
30
Reference
Siebel 7 Essentials
30.4
Static Drilldown: Same Business Component

Drill down to another view, keeping the business component (BC) context
Contact record in Visible Contacts List View
Same contact record in Contact Detail view
4 of 23
Siebel 7 Essentials
30.5
Configuring Drilldown
Create a new drilldown object
Set the Hyperlink Field and View properties to enable static drilldown
Specifies BC field the drilldown column maps to

Specifies the target view

5 of 23
30
Siebel 7 Essentials
30.6
Static Drilldown: Different Business Component

Drill down to another view, changing the business component context
Account field of contact record in Visible Contacts List View
Related account record in Account Detail - Contacts view

Module 30: Configuring Navigation 6 of 23
Siebel 7 Essentials
30.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
Specifies master BC in target view
Foreign Key field in record pointing to target BC

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

7 of 23
30
Siebel 7 Essentials
30.8
Dynamic Drilldown
Enables drilldown to multiple views from the same hyperlink field, depending on the value of a field in the active record of the list or form
8 of 23
Siebel 7 Essentials
30.9
Matching Conditions
Identify one or matching conditions to trigger drilling down to a specific target view
Type = Hotel ====> Expense Hotel List View Type = Mileage ====> Expense Item Mileage View
Determine the order to check the matching conditions

Conditions can involve different fields Multiple matches could occur for a given record
9 of 23
30
Siebel 7 Essentials
30.10
Configuring Dynamic Drilldown

Create the drilldown objects for each view Create a dynamic drilldown destination definition for each condition
Go to view for this drilldown object
Field to check
Value to check for
Order to check in
10 of 23
Siebel 7 Essentials
30.11
Configuring Dynamic Drilldown Continued

Configure the default drilldown object to navigate to the desired view if there are no matches
If no default is configured, clicking when there is no match does not drill down
Configure a dynamic drilldown destination definition for each condition

Set the Field, Value, and Sequence properties Set the Destination Drilldown Object property for the view to drill down to if a match occurs
Configure additional drilldown objects for each of the special target views
Avoid creating child dynamic drilldown destination definitions this can cause a loop
11 of 23
30
Siebel 7 Essentials
30.12
Thread Bar
Tracks previous business object (view) and active record Updates whenever the user navigates to a different business object or active record Provides hyperlinks to previous views
Allows user to backtrack easily
Hyperlink to prior active record in the thread
12 of 23
Reference
Siebel 7 Essentials
30.13
Thread Properties
Specifies the text that appears in the thread button
Hyperlink to prior active record in the thread Specifies the record to remember in the hyperlink Thread Title property specifies prior business object in hyperlink if not entered, application uses Title property
Module 30: Configuring Navigation 13 of 23
30
Siebel 7 Essentials
30.14
Threadbar Tag To enable the thread bar, the applet template must include a SWE threadbar tag
Usually included by referencing an external SWT file, CCThreadbar.swt For example, to include the thread bar in a view, use
<swe:include file="CCThreadbar.swt"/>
Excerpt from CCViewDetail.swt how to include thread bar in view Web template
14 of 23
Siebel 7 Essentials
30.15
Toggle Applets
You can configure several applets to share the same space in a view
You only add one applet to the view Web template Users can switch this applet with others by an applet toggle that you define on the applet
Select an applet from the toggle list
15 of 23
30
Applet Toggles and Toggle Applets
You define objects called applet toggles to switch between two or more different applets, called toggle applets.
Siebel 7 Essentials
30.16
Configuring Applet Toggles

Create a new applet toggle definition for each applet to be added to the toggle list
Create it on the applet defined in the view Web template Note: This is not limited to a single view the toggle list will appear in all view Web templates that include this applet
Specifies another applet in the toggle list
16 of 23
Reference
Siebel 7 Essentials
30.17
Configuring Applet Toggles Continued

Each applet you add to the apple toggle definition becomes available from the toggle list
The toggle list will appear on the new applet when you toggle to it
17 of 23
30
Siebel 7 Essentials
30.18
Togglebar Tag
The toggle list will appear only if the applet template includes a SWE togglebar tag
Example:
<swe:togglebar type=Select> <table> <tr> <td> <swe:control id=1 property=DisplayName> </td> <td> <swe:this property=FormattedHtml/> </td> </tr> </table> </swe:togglebar>
18 of 23
Siebel 7 Essentials
30.19
Dynamic Toggling
Determines the applet to appear in a view based on the value in a specific field in the displayed record Does not use a toggle list
User does not directly control navigation between applets
The contents of this field determine what applet displays below
19 of 23
30
Siebel 7 Essentials
30.20
Dynamic Toggling Continued

Example: Changing the Type property of a pricing factor determines which one of several pricing factor detail applets appears
20 of 23
Siebel 7 Essentials
30.21
Configuring Dynamic Toggling

Create a child applet toggle for each possible applet
Set the Auto Toggle Field, Auto Toggle Value, and Sequence properties Child applets must be based on same business component as parent
Set the parent applet as the default to display when all conditions fail
Order to check for matches Value to check for Field to check (may be a computed field based on a field used in the applet)
21 of 23
30
Siebel 7 Essentials
30.22
Summary
Configure drilldown to a related view Enable the thread bar Configure toggle applets
22 of 23
Siebel 7 Essentials
30.23
Lab
Create and configure dynamic drilldowns Enable and configure thread support Explore toggle applets
23 of 23
30
Siebel 7 Essentials
30.24
Siebel 7 Essentials
Extending the Database
31.1
Module 31: Extending the Database
31
Siebel 7 Essentials
31.2
Module Objectives
Create extension columns in a table Create custom extension tables
Stand-alone 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 23
Siebel 7 Essentials
31.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 23
31
Siebel 7 Essentials
31.4
Evaluate the Existing Database Tables

Prior to extending the Siebel database, consider using:
Unused columns in an existing table Unused Siebel-supplied business components Existing 1:M extension table
4 of 23
Siebel 7 Essentials
31.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 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
5 of 23
Joins
Adding a field that references a column in a 1:1 extension table may result in some performance degradation associated with the join. However, if that field is displayed on an applet that is not frequently used, then the performance impact is slight. In addition, there may already be fields that reference the extension table (a number of Siebel business components are delivered configured this way). In this case there will not be any additional joins.
31
Siebel 7 Essentials
31.6
Unused Siebel-Supplied Database Tables

Consider using a Siebel-supplied business component that is not required for the application
Verify that it has appropriate fields and relationships to other business components
6 of 23
Siebel 7 Essentials
31.7
Existing 1:M Extension Tables

Consider mapping the new business component to an appropriate 1:M extension table
Verify that business component has correct relationship to the candidate parent business component
7 of 23
31
Siebel 7 Essentials
31.8
Using Siebel Tools to Extend the Database

Supports creating new:
Extension columns on tables Stand-alone tables 1:1 extension tables 1:M extension tables Intersection tables
Creates new object definitions for the database extension

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

Developers do not create, use, or maintain SQL scripts
8 of 23
Reference
Mid-Market Technical Difference
Siebel Tools for Siebel MidMarket supports creating only custom extension columns and 1:1 extension tables.
Siebel 7 Essentials
31.9

Changes database schema and requires propagating changes to:
Other developers during development Mobile users after development if the application has already been deployed
Requires creating additional object definitions to:

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)
9 of 23
31
Siebel 7 Essentials
31.10
Creating a Custom Extension Column

Make logical changes to the data layer
Check out the appropriate project Select table to be extended Create a new column record with the desired properties
Name automatically prefixed with X_
10 of 23
Siebel 7 Essentials
31.11
Applying Changes
Click Apply to make the physical database changes
All database schema changes are made by Siebel Tools No separate SQL scripts need to be created or maintained Changes are preserved across Siebel application upgrades
Compile relevant projects Test changes locally before checking projects into server
Use vendor-supplied utility to query extended tables as part of testing
11 of 23
31
Siebel 7 Essentials
31.12
Propagating Changes
Propagate changes to other developers
Check project into the server Apply database changes to the server Compile and test on the server Have other developers check out project and apply changes locally Alternatively re-extract developers and have them get all projects
Server Machine Developer Workstation Developer Workstation Developer Workstation
Check in
Check out
12 of 23
Siebel 7 Essentials
31.13
Creating a New Table

Use the Table wizard to create a new table
Select File New Object Table
Table name starts with CX_ Select a locked project Select type of table to create
13 of 23
Table Name
A table name must start with CX_ and cannot exceed 15 characters.
31
Siebel 7 Essentials
31.14
Creating a Stand-Alone Table

Table wizard creates a stand-alone table with:
Seven system columns Type of Data(Public)
14 of 23
Siebel 7 Essentials
31.15
Creating a 1:1 Extension Table

Select a base table
Choice restricted to type Data(Public) Multiple extension tables relate directly to base table and not to each other
S_PROD_INT
NAME PART_NUM ROW_ID UOM_CD
CX_PROD_INT_X
ROW_ID
15 of 23
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.
31
Siebel 7 Essentials
31.16
Creating a 1:1 Extension Table Continued

Table wizard creates an extension table with:
Seven system columns PAR_ROW_ID column as foreign key column to base table P1 index on ROW_ID U1 index on PAR_ROW_ID and CONFLICT_ID
16 of 23
Indexes
The P1 index refers to the index on the primary key for the table. The U1 index refers to the index on the U1 user key.
Siebel 7 Essentials
31.17
Creating a 1:M Extension Table

Select a parent table
Choice restricted to type Data(Public)
17 of 23
31
Siebel 7 Essentials
31.18
Creating a 1:M Extension Table Continued

Table wizard creates an 1:M extension table with:
Seven system columns PAR_ROW_ID column as foreign key column to base table TYPE and NAME columns Type of Data(Public) P1 index on ROW_ID U1 index on PAR_ROW_ID, TYPE, NAME, and CONFLICT_ID M1 index on TYPE and NAME
18 of 23
Indexes
The P1 index refers to the index on the primary key for the table. The U1 index refers to the index on the U1 user key. The M1 index refers to a general multi-valued index.
Siebel 7 Essentials
31.19
Creating an Intersection Table

Select both parent tables
Choices restricted to type Data(Public)
Specify the foreign key column name for each parent table
19 of 23
31
Siebel 7 Essentials
31.20
Creating an Intersection Table Continued

Table wizard creates an intersection table with:
Seven system columns Two foreign key columns as specified Type of Data(Intersection) P1 index on ROW_ID U1 index on two foreign key columns, Type, and CONFLICT_ID F1 index on foreign key to second parent table
20 of 23
Indexes
The P1 index refers to the index on the primary key for the table. The U1 index refers to the index on the U1 user key. The F1 index refers to an index on a foreign key column.
Siebel 7 Essentials
31.21
Apply and Propagate Database Changes

Click Apply to make the physical database changes Compile relevant projects Test changes locally before checking projects into server Check project into the server Compile and test on server before propagating to other developers and users
21 of 23
31
Siebel 7 Essentials
31.22
Summary
Create extension columns in a table Create custom extension tables
Stand-alone table 1:1 extension table 1:M extension table Intersection table
22 of 23
Siebel 7 Essentials
31.23
Lab
Create a custom extension column on a table
23 of 23
31
Siebel 7 Essentials
31.24
Siebel 7 Essentials
Configuring Picklists
32.1
Module 32: Configuring Picklists
32
Siebel 7 Essentials
32.2
Module Objectives
Describe the differences between drop-down list and picklists Administer a list of values Configure a drop-down list Configure a picklist

Enables you to add picklists to your Siebel application
2 of 28
Siebel 7 Essentials
32.3
Picklists
Allow users to populate one or more single value fields by selecting a value from a list
Enforces business rules and polices Makes data entry faster Reduces errors
Can be either
Static Dynamic
3 of 28
32
Siebel 7 Essentials
32.4
Picklist Terms
In Siebel applications 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

Module 32: Configuring Picklists 4 of 28
Reference
Siebel 7 Essentials
32.5
Static Picklist
Draws values from picklist data managed by an administrator
Values displayed in static picklists do not change during runtime
Displays values in 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
Drop-down list
5 of 28
32
Siebel 7 Essentials
32.6
The S_LST_OF_VAL Table

Holds picklist values for all static picklists Exists in the application database Has values entered through List of Values Administration view or by batch loading
Access to view limited to Application Administrators
Specifies a value in the MR_MS picklist
6 of 28
Siebel 7 Essentials
32.7
Administering a Picklist
Use Site Map Application Administration List of Values Explorer to administer static picklist data
Select an existing picklist or create a new picklist type in the List of Values - Types applet Expand the type and select the child Values folder Edit the picklist values in the List of Values applet
Ok to set inactive
Dont change names of Siebel-supplied values

Reference
Applications Administration Guide
32
Siebel 7 Essentials
32.8
PickList Generic Business Component

Is a Siebel-supplied business component that references the S_LST_OF_VAL table
Static picklists are based on PickList Generic
8 of 28
Siebel 7 Essentials
32.9
Creating a Static Picklist

Create object definitions to:
1. Define the static picklist 2. Specify the field to be populated by picklist 3. Specify mapping between picklist and the originating business component field 4. Enable the user to invoke the picklist
Can possibly use an existing static picklist
9 of 28
32
Siebel 7 Essentials
32.10
1. Define the Static Picklist

Create a Pick List object definition
Set Business Component property to PickList Generic Set Type Field property to Type Set Type Value property to picklist name in S_LST_OF_VAL Set Bounded property to TRUE for bounded picklists
10 of 28
Siebel 7 Essentials
32.11
2. Specify the Field to be Populated

Select the Single Value Field to be populated Set the PickList property to the name of the static picklist
11 of 28
32
Siebel 7 Essentials
32.12
3. Specify Mapping
Create a SVF Pick Map definition
Set Field property to the field to be populated Set Pick List Field property to field in Picklist Generic to copy
Usually copy the Value field (VAL column)
Field in originating BC
Indicates to pick from the value field in Picklist Generic (maps to VAL in S_LST_OF_VAL)
12 of 28
Siebel 7 Essentials
32.13
4. Enable the User to Invoke the Picklist

Identify the list column/control that that references the field with a picklist
Can involve multiple applets
Set the Runtime property to TRUE

A drop-down arrow will appear as a cue
Runtime set to TRUE
13 of 28
32
Siebel 7 Essentials
32.14
Drop-Down
Is used to display values for a static picklist Is auto-generated at run time
Drop-down
14 of 28
Siebel 7 Essentials
32.15
Pick List Wizard

Use the Pick List Wizard to create a new static picklist
Select the originating business component and field Select an existing picklist or create a new one
Wizard adds the new picklist values to the S_LST_OF_VAL table
Set Runtime property on list columns or controls to TRUE to enable users to invoke the picklist
15 of 28
32
Siebel 7 Essentials
32.16
Dynamic Picklist
Draws values from a business component with records edited by users
Values displayed in picklist change during run time
Is used to update joined fields Copies foreign key reference to the selected value into destination field
Reflects the current data in the database
Displays values queried from the Account BC

Siebel 7 Essentials
32.17
Creating a Dynamic Picklist

1. Define the dynamic picklist 2. Associate the picklist with a field 3. Specify mapping between the pick BC and and originating BC fields 4. Identify an existing pick applet (or create a new one) to display the pick data 5. Enable the user to invoke the picklist
Can possibly use an existing picklist and pick applet
17 of 28
32
Siebel 7 Essentials
32.18
1. Define the Dynamic Picklist

Create a Pick List object definition
Set the Business Component property to the name of the pick business component
Pick business component
Determines whether users can add or delete records through picklist
Leave blank for dynamic picklists
18 of 28
Siebel 7 Essentials
32.19
2. Associate the Picklist with a Field

Select the single value field to associate the picklist
Determined by the list column or control in applet
Set the Picklist property to name of dynamic picklist

Originating BC
19 of 28
32
Siebel 7 Essentials
32.20
3. Specify Mappings
Create SVF Pick Map definitions to:
Map fields in the pick business component to the respective joined fields
Updates the values displayed in the applet
Map the primary key field in the pick business component to the foreign key field
Updates the FK field so new values are retrieved in future
Fields in originating BC
Fields in pick BC
20 of 28
Siebel 7 Essentials
32.21
4. Identify or Create a Pick Applet

Identify an existing pick applet to display records from the pick business component
Search for applets of Type Pick List that reference the pick business component Verify that applet displays enough list columns to allow user to distinguish the desired record
21 of 28
32
Siebel 7 Essentials
32.22
4. Identify or Create a Pick Applet Continued

If a suitable pick applet does not exist, create a new one
Copy an existing pick applet
Copies all controls required for pick applet
Set the Business Component property to reference the pick business component if required Edit list columns as required
Pick applet controls
22 of 28
Siebel 7 Essentials
32.23
5. Enable User to Invoke the Picklist

Identify the list column or control that references the field with the picklist Set the Runtime property to TRUE Set the Pick Applet property to the corresponding pick applet
Runtime set to TRUE
23 of 28
32
Siebel 7 Essentials
32.24
Pick List Wizard

Use the Pick List Wizard to create a new dynamic picklist
Select the originating business component and field Select an existing picklist or create a new one
Indicate the pick business component if a new list
Wizard can build new pick applet if desired
24 of 28
Siebel 7 Essentials
32.25
Constrained Picklist
Filters values dynamically to display only records with one or more fields that match corresponding fields in the originating BC record
Shows only contacts from the account in the parent record

32
Siebel 7 Essentials
32.26
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
Constrain to return only values with matches

Siebel 7 Essentials
32.27
Summary
Describe the differences between drop-down list and picklists Administer a list of values Configure a drop-down list Configure a picklist
27 of 28
32
Siebel 7 Essentials
32.28
Lab
Create a new static picklist Create a new dynamic picklist
28 of 28
Siebel 7 Essentials
Configuring Multi-Value Groups
33.1
Module 33: Configuring Multi-Value Groups
33
Siebel 7 Essentials
33.2
Module Objectives
Describe multi-value groups and their benefits Use Siebel Tools to configure a multi-value field and multi-value link Use Siebel Tools to configure a multi-value group so users may select one or more related child records

Enables you to incorporate child data directly in an applet
More child data can be available within a view More effective use of screen space
Understanding how to configure primaries for multi-value groups improves performance
2 of 27
Siebel 7 Essentials
33.3
Multi-Value Group
A multi-value group (MVG) is set of detail (child) records associated with a parent record
Parent applet displays only one of the child records Multi-value group applet opens on demand to display all child records
Parent applet Select button invokes the MVG applet
MVG Applet
Module 33: Configuring Multi-Value Groups 3 of 27
Reference
33
Siebel 7 Essentials
33.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 for detail records to be available from a single view
Industry MVG Territory MVG Organization MVG
Position MVG Business Address MVG

4 of 27
Multi-Value Group
A set of parent and related child records are normally displayed in a detail view. An MVG is an alternate way to display the same parent and child data.
Siebel 7 Essentials
33.5

Allows users to access child records for multiple parent records using a single view
Business Address MVG
Territory MVG
Industry MVG
5 of 27
33
Siebel 7 Essentials
33.6

Allows for creating queries that include values for fields in both parent and child records
Query on Industry
Query on Team
Query on Organization
Query on Address
6 of 27
MVG Queries
An MVG allows for complex queries that span multiple business components. Such queries are not possible when displaying parent and child records in a detail view.
Siebel 7 Essentials
33.7
Multi-Value Field
Is a field in the parent business component that references a field in the child business component (not a column in a table) Is required for an MVG
Parent business component Account
Name Location City
Singlevalue field S_ORG_EXT

NAME EMP_COUNT ROW_ID LOC
Multi-value field
Business Address
City Street Address
Child business component
7 of 27
33
Siebel 7 Essentials
33.8
Link
Must exist between parent and child business components in the MVG
Specifies how child records are related to parent records
Account
Name Location City
Parent business component Business Address

City Street Address
Child business component
8 of 27
Siebel 7 Essentials
33.9
Creating a Multi-Value Group

1. Specify the multi-value link in the parent business component 2. Add multi-value fields to the the parent business component 3. Identify an existing MVG applet (or create a new one) to display the child records 4. Enable user to invoke the MVG applet 5. Enable primaries to improve performance
9 of 27
33
Siebel 7 Essentials
33.10
1. Specify the Multi-Value Link

Create a Multi-Value Link object definition
Child object definition of business component that specifies how to retrieve the records for a multi-value field Based on an existing link definition that specifies how the parent and child business components are related
Set destination link
Set destination business component
10 of 27
Siebel 7 Essentials
33.11
2. Add Multi-Value Fields

Create a Multi-Value Field object definition for each field in the child business component to be added to parent business component
Uses the multi-value link
Fields in parent BC
Multi-value link
Fields in child BC
11 of 27
33
Siebel 7 Essentials
33.12
3. Identify or Create an MVG Applet

Identify an existing MVG applet to display records from the child business component
Search for applets of Type MVG that reference the child component Verify that applet displays enough list columns to allow user to distinguish the desired record
Can display more columns than are displayed on the parent applet
12 of 27
MVG Applet
There is no requirement that the MVG applet display only those multivalue fields that are displayed on the parent applet. This allows an MVG applet to be used in other MVGs throughout the application.
Siebel 7 Essentials
33.13
3. Identify or Create an MVG Applet Continued

If a suitable MVG applet does not exist, create a new one
Copy an existing MVG applet
Copies all controls required for MVG applet
Set the Business Component property to reference the child business component Edit list columns as required
Pick applet controls
13 of 27
33
Siebel 7 Essentials
33.14
4. Enable User to Invoke the MVG Applet

Identify the list column or control that references the multi-value field Set the MVG Applet property to the corresponding MVG applet Set Runtime property to TRUE
Field control is on
Set MVG Applet
Set Runtime TRUE

14 of 27
Setting Runtime to TRUE
While an MVG may consist of several multi-value fields, it is necessary to set the Runtime property to TRUE only on one of the multi-value fields. A select button appears on that field whenever it is displayed in the applet. There is no need to set Runtime to TRUE on all the multi-value fields in the MVG.
Siebel 7 Essentials
33.15
Multi-Value Groups for M:M Relationships

MVGs can be built on M:M relationships as well
Example: Industry multi-value field in Account based on Account Industry M:M relationship
Parent business component Account
Name Location Industry
Child business component Industry

Name SIC Code
Singlevalue field
Industry MVG Applet
Multi-value field
15 of 27
33
Siebel 7 Essentials
33.16
Configuring MVGs for M:M Relationships

Create object definitions required for 1:M MVGs Specify an associate applet for the MVG applet
Allows users to select other child records to add to the MVG
Invokes associate applet
16 of 27
Siebel 7 Essentials
33.17
MVG Performance Considerations

Each MVG (as discussed so far) requires a separate query to retrieve a child record to display in the parent applet Form applet with 5 MVGs requires 6 queries
1 query to populate parent single-value fields 5 additional queries (1 per MVG) to populate the MVGs
Industry MVG Territory MVG Organization MVG
Position MVG Business Address MVG

17 of 27
33
Siebel 7 Essentials
33.18
MVG Performance Considerations Continued

List applet displaying 7 records and 3 MVGs per record requires 22 queries
Requires 1 query to populate parent fields in list applet Requires 21 queries (3 per parent record) to populate the MVFs
Business Address MVG

Territory MVG
Industry MVG
18 of 27
Siebel 7 Essentials
33.19
Primary for a MVG

A primary refers to a designated child record To improve performance use a foreign key in the parent record that points to the primary child record
Creates a M:1 relationship between the parent and primary child record Allows a single query using a SQL join to retrieve the parent and primary child record for display in the parent applet
Add a foreign key field to track the primary address for account
Primary Address Id
Account
Name Location Street Address
Business Address
Id City Street Address
19 of 27
33
Siebel 7 Essentials
33.20
Performance With Primaries

When primaries are used on MVFs, one query returns the data for all records in the list applet
No additional queries required
Single query populates both parent and child data
20 of 27
Multiple Queries
Multiple queries are required to retrieve all the child records when the user invokes the MVG applet.
Siebel 7 Essentials
33.21
Finding the Primary Foreign Key

The Siebel Data Model includes primary foreign keys for many relationships
Begin with PR_
To find a primary foreign key:

Scan the columns in the main table for parent Select the column with the desired Foreign Key Table (main table for child)
S_ORG_EXT
ROW_ID NAME LOC PR_ADDR_ID
S_ADDR_ORG
ROW_ID CITY ADDR OU_ID
Primary foreign key
Regular foreign key

21 of 27
33
Siebel 7 Essentials
33.22
5. Enable Primaries for Performance

Add a primary key field in the parent business component to reference the primary foreign key column Set the Primary Id Field and Use Primary Join properties in the MVL
22 of 27
Siebel 7 Essentials
33.23
Setting the Primary Record

Set the Auto Primary property in the MVL to Default
Will set the first record as the primary
Add a SSA Primary Field to the MVG applet to display a special field to permit the user to see and change the primary child record
23 of 27
SSA Primary Field
This is not a field in the business component; rather it is a special name that is recognized by the Siebel execution engine and results in the display of a checkmark next to the primary child record.
33
Siebel 7 Essentials
33.24
Creating a New MVG

Verify that a link between the parent and child business components exists Use the MVG wizard to construct the MVL and the MVFs
Select the link to be used in the MVF Set the Primary Id field if desired Select one or more fields in the child BC and create MVFs
24 of 27
MVG Wizard
Siebel Systems recommends that you use the MVG wizard to configure MVGs. It ensures that you completely configure all the required object definitions. In addition it allows you to perform configuration in a faster, more productive manner.
Siebel 7 Essentials
33.25
Displaying MVGs
To display the child records
Use an existing MVG applet for the child business component Copy an existing MVG applet and edit as required Create a new applet using the MVG Applet wizard
Modify the parent applet to display the new MVFs

Set Runtime TRUE for new list columns or controls Set the MVG Applet property
MVF Wizard will invoke automatically
25 of 27
33
Siebel 7 Essentials
33.26
Summary
Describe multi-value groups and their benefits Use Siebel Tools to configure a multi-value field and multi-value link Use Siebel Tools to configure a multi-value group so users may select one or more related child records
26 of 27
Siebel 7 Essentials
33.27
Lab
Create a new MVG Create a MVG applet to display the MVG
27 of 27
33
Siebel 7 Essentials
33.28
Siebel 7 Essentials
Configuring Access Control
34.1
Module 34: Configuring Access Control
34
Siebel 7 Essentials
34.2
Module Objectives
Determine the access control mechanism for a business component Configure views to control access to data based on
Person Position Organization

Ensures that your configured application displays the appropriate set of records to each of your users Enables you to configure views that allow designated users to see additional data required to do their jobs
2 of 20
Siebel 7 Essentials
34.3
Access Control
Determines the records displayed to a user who has access to a view
Records displayed depend upon the user and the selected view
Module 34: Configuring Access Control 3 of 20
Reference
Authentication and Access Control Administration Guide
34
Siebel 7 Essentials
34.4
Access Control Continued

Depends upon the access control mechanisms for the referenced business component
Limit records a user can access based on the users:
Organization Position User ID Membership in access groups for catalogs and categories
4 of 20
User ID
User ID most often refers to the users LOGIN. However it could refer to another field that describes a user.
Access Groups
Access groups can contain organizations, accounts, and positions, but cannot contain users directly. Instead a user should be added to a user list which can then be added to an access group.
Siebel 7 Essentials
34.5
BusComp View Mode Definition

Specifies that business component is subject to access control
Owner Type property identifies the access control mechanism
Access control based on User ID
5 of 20
Reference
Object Types Reference
34
Siebel 7 Essentials
34.6
Visibility Field
Value in Visibility Field
Indicates that a business component record can be associated with one and only one record of the owner type Specifies the field to check when retrieving records
Records associated with individuals based on their User ID
Associated with one individual only identified by Created By field
6 of 20
Siebel 7 Essentials
34.7
Visibility MVField and MVLink

Value in Visibility MVField and MVLink
Indicates that a business component record can be associated with one or more records of the owner type Specifies the multi-value field to check when retrieving records
Records associated with individuals based on their User ID
Associated with one or more individuals identified by Owned By field
7 of 20
34
Siebel 7 Essentials
34.8
Multiple Access Control Mechanisms

Business components may have multiple access mechanisms
Allows records to be associated with different owner types Support multiple view modes
Records associated with single organization
Records associated with an individual
Records associated with team of positions

8 of 20
Siebel 7 Essentials
34.9
View Modes
Provide access to different sets of records for business components with one or more access control mechanisms Are based on the users organization, position, and user ID Permit additional access for
Managers Executives Administrators
9 of 20
34
Siebel 7 Essentials
34.10
View Modes Continued

View mode is configured by
Setting the Visibility Applet property
Identifies the business component
Setting the Visibility Applet Type

Determines the access control mechanism to use when retrieving records
Setting these properties makes the view appear with other access control views
10 of 20
Context Views
The views with a visibility mode set belong to the set of context views for the screen. They are referred to as context views since they determine the set of parent records available to the user. By convention, context views for a screen are displayed using a show drop-down, while the remaining non-context views appear as view tabs below the parent applet.
Siebel 7 Essentials
34.11
My View
Displays all records for which users position is on the team Is configured by
Setting the Visibility Applet property to identify an applet in the view Setting the Visibility Applet Type property to Sales Rep
Defaults to this value if none set
11 of 20
34
Siebel 7 Essentials
34.12
Retrieving My View Records

Visibility Applet determines the business component Visibility Applet Type determines the access mechanism used to restrict records
Looks for a BusComp View Mode with name Sales Rep Owner type must be Position or Personal
12 of 20
Siebel 7 Essentials
34.13
Personal View
Displays all records for which user is the owner Is configured by
Setting the Visibility Applet property to identify an applet in the view Setting the Visibility Applet Type property to Personal
Looks for a BusComp View Mode with name Personal

Owner type must be Position or Personal
13 of 20
Personal View
The personal view for contact views is labeled My Personal Contacts to distinguish it from the My Contacts view. For many other business components (service request, quotes, and so forth) the personal view is labeled My Service Requests, My Quotes, and so forth.
34
Siebel 7 Essentials
34.14
Manager View
Displays all records
For which direct and indirect reports are the primary or owner For which the user is the primary or owner
Is configured by
Setting the Visibility Applet property to identify an applet in the view Setting the Visibility Applet Type property to Manager
Looks for a BusComp View Mode with name Sales Rep

Owner type must be Position or Personal
14 of 20
Manager View
A manager view can be used for records that are personally owned in addition to records that are owned by sales teams. For example there is a manager view for service requests.
Visibility Applet Type
Notice that the name of the BusComp View Mode definition (Sales Rep in this case) is not the same as that of the Visibility Applet Type.
Siebel 7 Essentials
34.15
All View
Displays all records (with a primary set) within a single organization
Any sort specification in the business component is ignored
Is configured by
Setting the Visibility Applet property to identify an applet in the view Setting the Visibility Applet Type property to Organization
Looks for a BusComp View Mode with name Organization

Owner type must be Organization
15 of 20
34
Siebel 7 Essentials
34.16
Across All Organizations View

Displays all records (with a primary set) across all organizations
Does not use a BusComp View Mode definition
Is configured by
Setting the Visibility Applet property to identify an applet in the view Setting the Visibility Applet Type property to All
16 of 20
Siebel 7 Essentials
34.17
Administration View
Displays all the records in the database ignoring any visibility consideration Is configured by setting the Admin Mode Flag
17 of 20
34
Siebel 7 Essentials
34.18
All View Administration

All, Across All Organization, and Administration views should not be made available to mobile users
Unpredictable behavior since mobile users have only a small subset of records in the local database
Set the local access flag to FALSE when administering views on the client
Leave TRUE for testing by the developer
18 of 20
Siebel 7 Essentials
34.19
Summary
Determine the access control mechanism for a business component Configure views to control access to data based on
Person Position Organization
19 of 20
34
Siebel 7 Essentials
34.20
Lab
Explore visibility properties Configure view visibility properties
20 of 20
Siebel 7 Essentials
Localizing an Application
35.1
Module 35: Localizing an Application
35
35.2
Module Objectives
Distinguish between localization and internationalization activities Set the Tools Language Mode Edit locale object definitions to localize an application Enable multilingual List of Values

Localization enables you to configure your application for deployment in a multinational environment
2 of 24
Siebel 7 Essentials
35.3
Global Deployment
Refers to meeting the needs of customers operating in a global environment by:
Supporting users in multiple regions using multiple languages Supporting local business needs and regulations
3 of 24
35
35.4
Locale
Refers to a combination of language, region, and culture with a distinct set of:
Spelling conventions Formats for
Numbers Money Date and time
Can be a:
Single country (for example, Australia) Part of country (for example, French-speaking Canada)
4 of 24
Siebel 7 Essentials
35.5
Internationalization
Refers to the process of building capability into a software product to allow it to be used for any locale
Internationalization is performed by the manufacturer of the software product
Examples of internationalization in Siebel applications

A single set of binary files with locale-specific dependent DLL files Multiple foreign currency support Locale-specific string, number, and date handling Multiple code page support including multibyte languages Bi-directional support
5 of 24
Reference
Global Deployment Guide
35
35.6
Regional Settings
Presentation of the following data is determined by a regional settings parameter
Defaults to OS regional setting Can be set explicitly through an Object Manager component parameter
Date and time Currency and numbers
Telephone numbers
6 of 24
Siebel Web Client
The object manager has a locale-country parameter to specify the country/region code. If not set, the OS regional setting is used.
Siebel Mobile Web Client
The mobile client uses the OS regional setting for the client machine on which it is running.
Siebel 7 Essentials
35.7
Localization
Refers to the process of adapting a program to a specific locale Siebel applications can be localized by translating and resizing elements of the user interface
Dialog boxes Buttons Error messages Reports Online Help
7 of 24
Localizing UI Elements In addition, elements of the UI can be selectively displayed and repositioned in localized versions of an application.
35
35.8
Support for Localization

Tools development environment supports
Tools language mode Localization of applets
Multiple languages in a single repository Locale-specific object definitions for variety of objects
Exporting and importing displayable strings for external translation Configuration of multilingual List of Values
8 of 24
Reference
Tools Reference Guide
Siebel 7 Essentials
35.9
Tools Language Mode

Determines the locale-specific data that are:
Displayed and edited in Tools Compiled into the .srf file Transferred during checkin and checkout
Is set by selecting View Options Language Settings
9 of 24
35
35.10
Locale Object Definitions

Store locale-specific information for the parent object definition
Display names for captions Position coordinates
Used instead of the parent (locale-independent) property values when:

Editing using the visual editors in language-override mode Compiling into the target language
10 of 24
Siebel 7 Essentials
35.11
Localizing Applets
Set the Tools Language Mode Create the locale definitions for the applet to be translated
List Column Locale and Column Locale definitions Control Locale Applet Locale (applet title)
Invoke the Applet Web Editor and preview the applet to verify the translations
11 of 24
35
35.12
Language Specific Compiling

Produces a .srf file with text in following locale-specific UI elements
Strings are translated Controls and columns are resized and repositioned as required
Menu text Thread Bar Applet title Screen Tab
Labels
View Tab Column

Module 35: Localizing an Application 12 of 24
Siebel 7 Essentials
35.13
Locale Management Utility

Assists localization by:
Identifying untranslated strings Exporting strings to an external file for translation Importing a set of translated strings Supporting development by incremental translation of recently modified strings
13 of 24
Locale Management Utility
Select Tools Utilities Locale Management to invoke the utility.
35
35.14
List of Values Table

Stores data used to populate dropdown lists Administered using Application Administration views
From Opportunity Form applet
14 of 24
Siebel 7 Essentials
35.15
Unilingual List of Values

Values in the List Of Values table can be translated into the target language
For display in dropdown lists For storage in the database
Reasonable solution when all users speak the same target language
15 of 24
35
35.16
Multilingual List of Values

Multilingual List of Values enables the display of picklists in different languages to different users on the same database
Values in the List of Values table are translated at run time into the Object Managers language for display in drop-down lists Selected value is stored in the database as a languageindependent code Value retrieved from database is displayed in the Object Managers language
User sees the value in the Object Managers language
16 of 24
Siebel 7 Essentials
35.17
Enabling Multilingual List of Values

1. Determine the columns to enable 1. Determine the columns to enable 2. Configure columns for MLOVs 2. Configure columns for MLOVs 3. Add translated values to LOV table 3. Add translated values to LOV table 4. Update existing data in database 4. Update existing data in database
5. Compile new .srf file and deploy 5. Compile new .srf file and deploy
17 of 24
35
35.18
1. Determine the Columns To Enable

Check candidate MLOV columns to verify that column can be translated
Picklist populating the column must be bounded
Bounded property of Pick List definition must be TRUE LOV Bounded property of Column definition must be TRUE
Column must not store data read by server programs such as Assignment Manager, Siebel Remote, Siebel Anywhere, and Workflow Manager
Check for visibility rules referring to the candidate column

Values in rules need to be changed to Language Independent Code
18 of 24
Siebel 7 Essentials
35.19
2. Configure Columns for MLOVs

Open Siebel Tools and connect to the server database
Editing object definitions on the server is required for enabling MLOVs
Identify all target columns that can be populated by the new MLOV picklist
Select the Column object type in the Flat tab Query for the LOV Type property for the MLOV picklist Verify that LOV Bounded property is TRUE for all target columns
Set the Translation Table Name to S_LST_OF_VAL
19 of 24
35
35.20
3. Add Translated Values to LOV Table

Edit the List of Values table to create the the languageindependent code and the display values for each supported language
Start the client application and connect to the server For each LOV type that is to be made an MLOV type:
Create a new record for each display value for the LOV type Set the language-independent code accordingly
20 of 24
Siebel 7 Essentials
35.21
4. Update the Existing Data in the Database

Run the MLOV upgrade utility (mlovupgd.exe) to:
Change the data in the target columns to the corresponding language-independent codes Set the Multilingual column in the List of Values table to TRUE Verify that all target columns have been enabled
Consult the Siebel Global Deployment Guide for additional details
21 of 24
35
35.22
5. Compile a New .srf File and Deploy

Compile the modified table definitions to produce an updated .srf file Migrate the new .srf file and the modified database to the server Start up Object Managers for the new supported languages Extract a new database for mobile users (if any)
22 of 24
Siebel 7 Essentials
35.23
Summary
Distinguish between localization and internationalization activities Set the Tools Language Mode Edit locale object definitions to localize an application Enable multilingual List of Values
23 of 24
35
35.24
Lab
Explore how to localize an applet for a foreign locale Identify columns that can be configured for MLOVs
24 of 24
Siebel 7 Essentials
Configuration Guidelines
36.1
36
Module 36: Configuration Guidelines
Siebel 7 Essentials
36.2
Module Objectives
Describe guidelines for configuring objects Identify performance issues Describe some recommended reviews

Helps you to successfully implement a Siebel configuration project Identifies configuration decisions that have performance implications
2 of 19
Siebel 7 Essentials
36.3
This module reviews configuration guidelines for:
Business components Business objects Applets Views Screens Applications
36
3 of 19
Reference
Siebel 7 Essentials
36.4
Configuring Business Components

Modify an existing business component
Easier to maintain and manage Provides an upgrade path
Copy an existing business component to:

Include it twice in a business object Create a specialized copy with a different search specification or pre-defaulted field value
Create a new business component to represent a new entity that does not already exist Leave unused business components as originally configured as other definitions may reference them
Do not modify, set inactive, or delete unused business components
4 of 19
Copying a Business Component
You will need to copy the Account business component (and cal it Sub Account) to create an Account Sub Account view.
Siebel 7 Essentials
36.5
Upgrade Ancestor
Set the Upgrade Ancestor property when copying a business component
Property must be set explicitly by developer
36
Ensures that the copied business component is upgraded in the same way as the original business component
Set ancestor manually
5 of 19
Upgrade Ancestor
Applets, Integration Objects, and Reports also have an Upgrade Ancestor property.
Siebel 7 Essentials
36.6
Business Components with Specialized Classes

Copy a business component with a specialized class only to create a new one with essentially identical behavior
For example, the Person Forecast business component uses CSSBCRevenueForecast
Class automatically creates a new forecast record whenever a user submits a forecast
Use caution when modifying existing fields or setting them inactive

Can be referenced explicitly by the underlying code
6 of 19
Specialized Classes
A business component is generally considered to specialized if it is based on a class other than CSSBusComp, CSSBCBase, or their child or grandchild classes. Specialized business components should be copied only when you wish to reproduce all the class behavior. Some highly specialized business components cannot be copied because the business component name is coded directly into the class. The Calendar business component is an example of such a class.
Siebel 7 Essentials
36.7
Configuring Business Objects

Create a new business object for a screen based on a new business component Leave unused business objects as originally configured
Other definitions might reference them
36
7 of 19
Siebel 7 Essentials
36.8
Configuring Applets
Modify an existing applet for minor changes
Title or caption changes Adding or deleting a few fields
Set the Upgrade Ancestor property when copying applets Create a new applet to:
Display data for a new business component Make a large number of changes Create a read-only copy of the applet Add the applet to a toggle cycle
Leave unused applets as originally configured
8 of 19
Siebel 7 Essentials
36.9
Configuring Views
Modify an existing view for minor changes
Title Applet layout
36
Create a new one to show a master-detail relationship that has no current view Associate a view with a single screen only
Threads track prior view but not the screen
Leave unused view definitions as originally configured
9 of 19
Siebel 7 Essentials
36.10
Configuring Screens
Add a new screen whenever you create a new business object Modify existing screens to:
Change text in:
View tabs Show drop-down list Site map
Add or remove views from a screen
Leave unused screen definitions as originally configured Edit responsibilities to hide unnecessary views from screens
10 of 19
Siebel 7 Essentials
36.11
Configuring Applications
Modify the existing application to:
Add, remove, or reorder screen tabs Change the text in the screen tabs and site map
36
Edit responsibilities to hide unnecessary screens
11 of 19
Siebel 7 Essentials
36.12
General Configuration Recommendations

Never delete top-level object definitions
Inactivate child object definitions to hide them when necessary
Validate object definitions prior to compiling them Add comments to newly-created or modified object definitions Follow recommended naming conventions
12 of 19
Siebel 7 Essentials
36.13
Naming Conventions
Give object definitions meaningful names
Avoid meaningless names such as "Account 2"
36
Name all new object definitions with a prefix that is specific to your company
Assists maintenance and development since all new definitions will be grouped together Reduces chance of a name conflict when a new version of the standard application is released
Initial-capitalize object definitions to prevent unexpected sorting in the object list editor
Example: ABC Service Request instead of ABC service requests
13 of 19
Siebel 7 Essentials
36.14
Optimizing Performance
Use primaries for multi-value groups in list applets Ensure that indexes exist to support sort and search specifications
Indexes cannot span multiple tables Avoid sorting on un-indexed columns
Avoid calculated fields that are not supported by the RDBMS Avoid displaying totaled columns in list applets unless number of records will always be small
All records must be retrieved whenever entering a view
14 of 19
Performance Implications
Ignoring these issues during configuration may result in significant performance problems.
Siebel 7 Essentials
36.15
Additional Performance Considerations

Use primaries for multi-value fields in form applets Keep the number of business components used in a view small
Includes those in applet toggle cycles
36
Avoid creating a large number of joins in business components

Includes implicit ones to extension tables and primaries to MVFs
Avoid retrieving a large number of fields Avoid specifying outer joins when the relationship is mandatory Avoid unnecessarily setting Force Active and Link Specification to TRUE
15 of 19
Performance Implications
These situations may cause some performance problems but not as severe as those mentioned in the previous slide.
Siebel 7 Essentials
36.16
Performance Tuning
Test the configured application against realistic and representative volumes of server and local data For slow performing views, spool the SQL and run it using database vendor tools to inspect query plan and index usage Execute typical user sort by and query by processing
16 of 19
Siebel 7 Essentials
36.17
Recommended Reviews
Design reviews during initial phases to verify proposed
Data mappings Database extensions Configuration design
36
Configuration reviews at key phases

Pilot Rollout
Any review should include experts in the client subject matter as well as Siebel implementation technology
17 of 19
Siebel 7 Essentials
36.18
Summary
Describe guidelines for configuring objects Identify performance issues Describe some recommended reviews
18 of 19
Siebel 7 Essentials
36.19
Lab
Complete the configuration by checking in all the modified definitions to the server Verify the modified configuration by running the Siebel Web client on the server database
36
Configuration wrap-up propagates the local configuration work up to the server database. You must do this to successfully continue with the rest of the server-based labs.
19 of 19
Siebel 7 Essentials
36.20
Siebel 7 Essentials

Siebel 7 Essentials Student Guide Vol2-1

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Siebel 7 Essentials Student Guide Vol2-1

Загружено:

Авторское право:

Доступные форматы

Siebel Systems, Inc.

Re: Training Materials Siebel Systems Confidential and Proprietary Information

Copyright 2001 Siebel Systems, Inc.

Siebel Systems, Inc.

ii COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel Systems, Inc.

iv COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel Systems, Inc.

Editing and Compiling Object Definitions

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Why you need to know

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Editing Object Definitions

Edit the property

Module 19: Editing and Compiling Object Definitions

Siebel Tools Reference

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Creating a New Object Definition

Locked projects only

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Validating Object Definitions

Is based on set of Siebel-defined rules

User can enable/disable a Siebel-defined rule

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Validating Object Definitions Continued

Click Start in Validate window

Violations appear in Errors list window

Click to access Validate Options window

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Exporting Object Definitions

To export object definitions

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Editing and Compiling Object Definitions

Module 19: Editing and Compiling Object Definitions

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED