Professional Documents
Culture Documents
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.
Siebel 7 Essentials
Table of Contents
Volume 1
Foundations
Module i:
Module 1:
Module 2:
Module 3:
Module 5:
Module 6:
Module 7:
Server Administration
Module 9:
Module 10:
Module 11:
Creating an Organization
Module 12:
Authenticating Users
Module 14:
Module 15:
Module 16:
Configuration
Module 17:
Module 18:
i
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION
DUPLICATION IS PROHIBITED
Siebel 7 Essentials
Volume 2
Configuration, Continued
Module 19:
Module 20:
Module 21:
Module 22:
Configuring Views
Module 23:
Module 24:
Module 25:
Module 26:
Module 27:
Module 28:
Module 29:
Module 30:
Configuring Navigation
Module 31:
Module 32:
Configuring Picklists
Module 33:
Module 34:
Module 35:
Localizing an Application
Module 36:
Configuration Guidelines
Volume 3
Data Loads
Module 37:
Module 38:
Data Mapping
Module 39:
Module 40:
Module 41:
ii
Siebel 7 Essentials
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
iii
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION
DUPLICATION IS PROHIBITED
Siebel 7 Essentials
iv
19.1
19
Siebel 7 Essentials
19.2
Module Objectives
Siebel 7 Essentials
2 of 28
19.3
Reference
Type
Select
3 of 28
19
Siebel 7 Essentials
19.4
Assign values to
remaining fields
Siebel 7 Essentials
4 of 28
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
Changed Flag
5 of 28
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.
Siebel 7 Essentials
19
19.6
User can
enable/disable a
Siebel-defined rule
Error
Warning
Siebel 7 Essentials
6 of 28
19.7
Violations appear
in Errors list
window
Click to access
Validate Options
window
7 of 28
19
Siebel 7 Essentials
19.8
Archive Files
Siebel 7 Essentials
8 of 28
19.9
9 of 28
19
Siebel 7 Essentials
19.10
Exporting Projects
Siebel 7 Essentials
10 of 28
19.11
11 of 28
19
Siebel 7 Essentials
19.12
Siebel 7 Essentials
12 of 28
19.13
Compare Objects
13 of 28
19
Siebel 7 Essentials
19.14
Siebel 7 Essentials
14 of 28
19.15
Definitions with
difference
highlighted
Differences
displayed
15 of 28
19
Siebel 7 Essentials
19.16
Modifying Definitions
Siebel 7 Essentials
16 of 28
19.17
Check archive
into code
management
system
ODBC to server
and local
databases
17 of 28
19
Siebel 7 Essentials
19.18
Add to archive
.sif
Windows
copy/paste
Server
Check in
Repository Data
Siebel 7 Essentials
18 of 28
19.19
Compiling
Compile into .srf file located in the objects directory of the client
application
Database
Repository
Data
Tools
Application
Application
Object Manager
Compiling
.srf
Configured
Application
19 of 28
19
Siebel 7 Essentials
19.20
Compile Options
Siebel 7 Essentials
20 of 28
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
Get Projects
Siebel 7 Essentials
21 of 28
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
19.22
Compile Objects
Siebel 7 Essentials
22 of 28
19.23
Configuration File
Copy the default .cfg file for the application being customized
Edit it to refer to the new .srf file
23 of 28
19
Siebel 7 Essentials
19.24
Siebel 7 Essentials
24 of 28
19.25
Use ViewOptions and select the Debug tab to set the runtime start up information
Optionally provide
login parameters
25 of 28
19
Siebel 7 Essentials
19.26
Start
26 of 28
You may use the F5 function key to execute the Debug Start command
as well.
Siebel 7 Essentials
19.27
Summary
27 of 28
19
Siebel 7 Essentials
19.28
Lab
Siebel 7 Essentials
28 of 28
20.1
20
Siebel 7 Essentials
20.2
Module Objectives
Reference
Siebel 7 Essentials
2 of 28
20.3
HTML
table tag
<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>
Sample HTML
3 of 28
The sample HTML tags shown in the slide are excerpted from the
CCFrameBanner.swt template file.
20
Siebel 7 Essentials
20.4
Siebel Tags
<swe:for-each-screen>
Siebel tag to
insert the name
of the screen
</swe:for-each-screen>
Module 20: Understanding Siebel Template Files
Sample HTML
Siebel 7 Essentials
4 of 28
The sample HTML tags shown in the slide are excerpted from the
CCScreenbar_Tabs.swt template file.
20.5
<head>
<title><swe:this property="Title"/></title>
<swe:include file="CCStyleChoices.swt"/>
</head>
Sample HTML
5 of 28
The sample HTML tags shown in the slide are excerpted from the
CCSiteMap.swt template file.
20
Siebel 7 Essentials
20.6
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; }
Module 20: Understanding Siebel Template Files
Siebel 7 Essentials
6 of 28
20.7
7 of 28
20
Siebel 7 Essentials
20.8
Siebel 7 Essentials
8 of 28
20.9
Applets
Associating
Binding
(View)
Template
file
Module 20: Understanding Siebel Template Files
Applet
placeholders
9 of 28
20
Siebel 7 Essentials
20.10
Registering
Applets
(View)
Template
file
Siebel 7 Essentials
Applet
placeholders
10 of 28
20.11
Logical name in
repository for template
Type of Web
template
Registering
11 of 28
20
Siebel 7 Essentials
20.12
Types of Templates
Uses Web
page template
Siebel 7 Essentials
12 of 28
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
Applets
Associating
(View)
Template
file
Siebel 7 Essentials
Applet
placeholders
14 of 28
20.15
15 of 28
20
Siebel 7 Essentials
20.16
Mode for
the applet
Siebel 7 Essentials
Applet template
used to render
applet for that mode
16 of 28
20.17
Applet in
base mode
Applet in
query mode
Applet
17 of 28
20
Siebel 7 Essentials
20.18
Siebel 7 Essentials
18 of 28
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.
20.19
Binding
View
Applets
View Web
template
Binding
View
Template
File
Applet
Placeholders
Applets
Controls/List
Binding
Applet Web
template
Applet
Template
File
Control
Placeholders
19 of 28
20
Siebel 7 Essentials
20.20
Binding Information
Siebel 7 Essentials
20 of 28
20.21
Are used at run time by the Siebel Web Engine to identify the
applets that make up a view
swe:applet Tag
21 of 28
20
Siebel 7 Essentials
20.22
Are used at run time by the Siebel Web Engine to identify the
controls that make up an applet
swe:control tag
22 of 28
Siebel 7 Essentials
20.23
Are used at run time by the Siebel Web Engine to position the
links and buttons
swe:pageitem tags
23 of 28
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
Siebel 7 Essentials
24 of 28
20.25
Template Reuse
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
Registering
Web Template
Web Template Files
Associating
Applet Web Template
View Web Template
Web Page
Binding
Siebel 7 Essentials
26 of 28
20.27
Summary
27 of 28
20
Siebel 7 Essentials
20.28
Lab
Siebel 7 Essentials
28 of 28
21.1
21
Siebel 7 Essentials
21.2
Module Objectives
Siebel 7 Essentials
2 of 19
21.3
Container
Page
3 of 19
21
Siebel 7 Essentials
21.4
Siebel 7 Essentials
4 of 19
21.5
Screenbar frame
Viewbar frame
Content frame
Content Frame
5 of 19
21
Siebel 7 Essentials
21.6
Application-level menus
Branding area
6 of 19
Siebel 7 Essentials
21.7
Position: Specifies
order of appearance
Caption: Specifies
displayed text
7 of 19
21
Siebel 7 Essentials
21.8
<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>
main.css
Siebel 7 Essentials
8 of 19
21.9
Screenbar Frame
Screenbar Frame
Template
9 of 19
CCFramceScreenbar.swt
21
Siebel 7 Essentials
21.10
Siebel 7 Essentials
10 of 19
21.11
Contains
` Siebel Application Toolbar
History menu
Customer Dashboard control
Views
History menu
Dashboard
Siebel Application
Toolbar
11 of 19
21
Siebel 7 Essentials
21.12
Siebel 7 Essentials
12 of 19
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
13 of 19
21
Siebel 7 Essentials
21.14
Banner frame
Screenbar frame
Viewbar frame
Content frame
Siebel 7 Essentials
14 of 19
21.15
15 of 19
21
Siebel 7 Essentials
21.16
Caption: Changes
displayed text
Siebel 7 Essentials
16 of 19
21.17
Specify the text that appears in the splash screen by editing the
parameter in the .cfg file
` Mobile clients only
Reference
17 of 19
21
Siebel 7 Essentials
21.18
Summary
Siebel 7 Essentials
18 of 19
21.19
Lab
19 of 19
21
Siebel 7 Essentials
Siebel 7 Essentials
21.20
Configuring Views
22.1
22
Siebel 7 Essentials
Configuring Views
22.2
Module Objectives
Siebel 7 Essentials
2 of 24
Configuring Views
22.3
Views
Consist of one or more lists or forms
Reference a single business object
Are grouped into a screen
Reference
3 of 24
22
Siebel 7 Essentials
Configuring Views
22.4
View Templates
ID =1
ID =2
Siebel 7 Essentials
4 of 24
Configuring Views
22.5
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
Can be related as
` Peers
` Parent-child
` Parent-child-grandchild
Peer
Parent
Parent
Child
Child
Peer
Grandchild
Siebel 7 Essentials
6 of 24
Configuring Views
22.7
7 of 24
22
Siebel 7 Essentials
Configuring Views
22.8
Use
UseView
View
Wizard
Wizard
3.
3.Bind
Bindapplets
appletsto
toview
viewtemplate
template
4.
4.Configure
Configurethreadbar
threadbar
5.
5.Register
Registerand
andassign
assignview
view
8 of 24
Best Practice
Siebel 7 Essentials
Configuring Views
22.9
View Wizard
9 of 24
22
Siebel 7 Essentials
Configuring Views
22.10
View name
Siebel 7 Essentials
10 of 24
Configuring Views
22.11
11 of 24
22
Siebel 7 Essentials
Configuring Views
22.12
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
Siebel 7 Essentials
12 of 24
Configuring Views
22.13
13 of 24
22
Siebel 7 Essentials
Configuring Views
22.14
Siebel 7 Essentials
14 of 24
Configuring Views
22.15
<swe:applet id=1"/>
Module 22: Configuring Views
15 of 24
22
Siebel 7 Essentials
Configuring Views
22.16
Applet Mode
Siebel 7 Essentials
16 of 24
Configuring Views
22.17
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
Siebel 7 Essentials
Configuring Views
22.19
19 of 24
22
Siebel 7 Essentials
Configuring Views
22.20
Siebel 7 Essentials
20 of 24
Configuring Views
22.21
21 of 24
22
Siebel 7 Essentials
Configuring Views
22.22
View tab
Siebel 7 Essentials
22 of 24
Configuring Views
22.23
Summary
23 of 24
22
Siebel 7 Essentials
Configuring Views
22.24
Lab
Siebel 7 Essentials
24 of 24
23.1
23
Siebel 7 Essentials
23.2
Module Objectives
Reference
Siebel 7 Essentials
2 of 28
23.3
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
Additional Applet
Types
3 of 28
23
Siebel 7 Essentials
23.4
Specialized Applet
Siebel 7 Essentials
4 of 28
23.5
List Applet
One record
5 of 28
23
Siebel 7 Essentials
23.6
New button
` Creates a new record for the list
Save button
` Immediately saves record
Siebel 7 Essentials
6 of 28
23.7
7 of 28
23
Siebel 7 Essentials
23.8
Base Mode
Siebel 7 Essentials
8 of 28
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
Template
9 of 28
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
Siebel 7 Essentials
23.10
Siebel 7 Essentials
10 of 28
23.11
11 of 28
23
Siebel 7 Essentials
23.12
2.
2.Associate
Associateapplet
applettemplate
template
with
applet
object
with applet objectdefinition
definition
3.
3.Bind
Bindcontrols
controlsto
toapplet
applettemplate
template
Siebel 7 Essentials
12 of 28
23.13
13 of 28
23
Siebel 7 Essentials
23.14
14 of 28
Tip
Siebel 7 Essentials
23.15
Review
15 of 28
23
Siebel 7 Essentials
23.16
Columns
Siebel 7 Essentials
Arrange fields in
order to show in
the applet
16 of 28
If you add all the columns in the business component, you can delete and
add them later as necessary.
23.17
Icons
Tip
17 of 28
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
Siebel 7 Essentials
23.18
Siebel 7 Essentials
18 of 28
23.19
If information
is correct, click
Finish
19 of 28
23
Siebel 7 Essentials
23.20
Applet
Control
List
List column
` Maps
Siebel 7 Essentials
20 of 28
23.21
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
Siebel 7 Essentials
23.22
Applet Title
Siebel 7 Essentials
22 of 28
23.23
HTML Type
23 of 28
23
Siebel 7 Essentials
23.24
Siebel 7 Essentials
24 of 28
23.25
25 of 28
23
Siebel 7 Essentials
23.26
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>
Siebel 7 Essentials
26 of 28
23.27
Summary
27 of 28
23
Siebel 7 Essentials
23.28
Lab
Siebel 7 Essentials
28 of 28
24.1
24
Siebel 7 Essentials
24.2
Module Objectives
Reference
Siebel 7 Essentials
2 of 19
24.3
24
Form Applet
Siebel 7 Essentials
Caption
Textbox control
3 of 19
24.4
Read-only fields
(gray background)
Siebel 7 Essentials
4 of 19
24.5
24
Collapsed (Less)
` Is the default display
` Shows limited set of fields
` Only displayed fields can be edited
Expanded (More)
` Shows all fields
` Full edit capabilities (all unprotected fields can be edited)
Siebel 7 Essentials
5 of 19
Fields are usually editable in form applets but can be configured to be read
only.
24.6
Siebel 7 Essentials
6 of 19
24.7
24
Business component
Siebel 7 Essentials
7 of 19
24.8
Siebel 7 Essentials
8 of 19
24.9
24
Adding Fields
Siebel 7 Essentials
9 of 19
Some business components have numerous fields. Add those fields you
will use or think you may use.
24.10
Siebel 7 Essentials
10 of 19
24.11
24
Siebel 7 Essentials
11 of 19
24.12
Siebel 7 Essentials
12 of 19
24.13
24
Modify a Control
Siebel 7 Essentials
13 of 19
24.14
Mode
14 of 19
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
24
Siebel 7 Essentials
15 of 19
24.16
Preview mode
Siebel 7 Essentials
16 of 19
24.17
24
Siebel 7 Essentials
17 of 19
24.18
Summary
Siebel 7 Essentials
18 of 19
24.19
24
Lab
Siebel 7 Essentials
19 of 19
Siebel 7 Essentials
24.20
25.1
25
Siebel 7 Essentials
25.2
Module Objectives
Siebel 7 Essentials
2 of 20
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
S_OPTY
Decision Level
STG_ORDER
PHASE_CD
NAME
ROW_ID
ATTRIB_39
ATTRIB_09
ATTRIB_01
PAR_ROW_ID
ROW_ID
CURCY_CD
DESC_TEXT
NAME
ROW_ID
Siebel 7 Essentials
S_STG
S_OPTY_X
Reference
Sales Stage
3 of 20
25
25.4
Base table
Siebel 7 Essentials
C++ class
4 of 20
25.5
Base Table
Has columns that store the main fields for the business
component
25
Description
Decision Level
Base table
S_OPTY
CURCY_CD
DESC_TEXT
NAME
ROW_ID
Siebel 7 Essentials
Sales Stage
5 of 20
25.6
Columns
from
S_OPTY
Module 25: Understanding Business Components and Joins
Siebel 7 Essentials
6 of 20
25.7
Siebel 7 Essentials
7 of 20
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.
25
25.8
Description
Sales Stage
Base table
Joined table
S_OPTY
S_STG
STG_ORDER
Siebel 7 Essentials
PHASE_CD
NAME
ROW_ID
CURCY_CD
DESC_TEXT
NAME
ROW_ID
8 of 20
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
Joined table
S_OPTY
S_STG
Siebel 7 Essentials
STG_ORDER
Joined Tables
PHASE_CD
NAME
ROW_ID
CURR_STG_ID
CURCY_CD
DESC_TEXT
NAME
ROW_ID
9 of 20
25
25.10
Join Definition
Specifies the joined table from which to retrieve data
Defaults the alias property to the name of the joined table
A self-join
Multiple relationships with the joined table
Name of Join
Module 25: Understanding Business Components and Joins
Siebel 7 Essentials
Joined table
10 of 20
25.11
` Do not set the flag if there always is a related row in the joined
table
Use outer
join
Module 25: Understanding Business Components and Joins
Siebel 7 Essentials
11 of 20
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.
25
25.12
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
S_STG
STG_ORDER
PHASE_CD
NAME
ROW_ID
CURR_STG_ID
CURCY_CD
DESC_TEXT
NAME
ROW_ID
Siebel 7 Essentials
Primary
key
12 of 20
25.13
Siebel 7 Essentials
25
13 of 20
25.14
Create a Join
Siebel 7 Essentials
14 of 20
25.15
Columns
from S_STG
Siebel 7 Essentials
15 of 20
25
25.16
Extension Table
Base table
Budgeted
Decision Level
Joined table
Extension table
S_OPTY
S_OPTY_X
S_STG
STG_ORDER
PHASE_CD
NAME
ROW_ID
ATTRIB_39
ATTRIB_09
ATTRIB_01
PAR_ROW_ID
ROW_ID
CURCY_CD
DESC_TEXT
NAME
ROW_ID
Siebel 7 Essentials
16 of 20
25.17
Implicit Joins
S_OPTY_X does
not appear here
Module 25: Understanding Business Components and Joins
Siebel 7 Essentials
S_OPTY_X
appears here
17 of 20
25
25.18
Columns from
S_OPTY_X
Extension Tables
Siebel 7 Essentials
18 of 20
25.19
Summary
Siebel 7 Essentials
19 of 20
25
25.20
Lab
Siebel 7 Essentials
20 of 20
26.1
26
Module 26: Business Components and Joins: Party
Extension Tables
Siebel 7 Essentials
26.2
Module Objectives
Siebel 7 Essentials
2 of 16
26.3
26
Siebel 7 Essentials
3 of 16
26.4
Main fields are mapped using the implicit join for the extension
table
Contact
First Name
Last Name
S_PARTY
Birth Date
S_CONTACT
PAR_ROW_ID
BIRTH_DT
LAFST_NAME
FST_NAME
ROW_ID
PARTY_UID
PARTY_TYPE_CD
NAME
ROW_ID
S_PARTY Extension
Tables
4 of 16
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
26
Opportunity
Name
Description
Account
Account Location
Siebel 7 Essentials
5 of 16
26.6
Join Definition
Opportunity
Name
Description
S_OPTY
Account
S_ORG_EXT
LOC
NAME
ROW_ID
CURCY_CD
DESC_TEXT
NAME
ROW_ID
S_PARTY
extension table
Module 26: Business Components and Joins: Party Extension Tables
Siebel 7 Essentials
6 of 16
26.7
Siebel 7 Essentials
7 of 16
26
26.8
PAR_ROW_ID
Opportunity
Name
S_OPTY
Description
Account Id
Account
S_ORG_EXT
S_PARTY
PARTY_UID
PARTY_TYPE_CD
Destination Column
Siebel 7 Essentials
NAME
ROW_ID
PAR_ROW_ID
LOC
NAME
ROW_ID
PR_DEPT_OU_ID
DESC_TEXT
NAME
ROW_ID
8 of 16
26.9
26
Contact
Last Name
Account Id
Account
Account Location
Siebel 7 Essentials
9 of 16
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
Explicit join,
cannot be named
S_ORG_EXT
Implicit Joins
Siebel 7 Essentials
10 of 16
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.
26.11
26
Siebel 7 Essentials
11 of 16
26.12
Siebel 7 Essentials
12 of 16
26.13
26
Siebel 7 Essentials
13 of 16
26.14
Considerations
Siebel 7 Essentials
14 of 16
26.15
Summary
Siebel 7 Essentials
15 of 16
26
26.16
Lab
Siebel 7 Essentials
16 of 16
27.1
Siebel 7 Essentials
27
27.2
Module Objectives
Siebel 7 Essentials
2 of 14
27.3
Business Objects
Business
Component
(BC)
Account
Account
Action
Product
Reference
Siebel 7 Essentials
27
Master BC provides
focus for BO
Contact
3 of 14
27.4
Account
Account
Action
Product
Siebel 7 Essentials
Contact
4 of 14
27.5
27
Parent BC
Child BCs
Siebel 7 Essentials
5 of 14
27.6
Link Definition
Account
Account
Action
Product
Siebel 7 Essentials
Links
Contact
6 of 14
27.7
1:M Link
27
Defaults to parent
BC/child BC
PK field in
parent BC
(defaults to Id)
Siebel 7 Essentials
7 of 14
27.8
Siebel 7 Essentials
8 of 14
27.9
M:M Link
27
Intersection table
with FK columns
Siebel 7 Essentials
9 of 14
27.10
Link Property
Siebel 7 Essentials
10 of 14
27.11
27
Activity Plan BC
Activity Plan
Action BC
Child activities
for selected
activity plan
Module 27: Understanding Business Objects and Links
Grandchild View
Siebel 7 Essentials
11 of 14
27.12
Parent/child
Child/grandchild BC
Siebel 7 Essentials
12 of 14
27.13
Summary
27
Siebel 7 Essentials
13 of 14
27.14
Lab
Siebel 7 Essentials
14 of 14
28.1
28
Siebel 7 Essentials
28.2
Module Objectives
Siebel 7 Essentials
2 of 24
28.3
` Editing properties
No Delete
No Insert
No Merge
No Update
` Owner Delete
` Search Specification
` Sort Specification
Reference
Siebel 7 Essentials
28
3 of 24
28.4
4 of 24
No Delete
If TRUE, once a record is created and committed, users cannot delete it.
No Insert
No Merge
No Update
Siebel 7 Essentials
28.5
Example:
` Users can generally edit their personal contacts
` On the Contact Form ReadOnly Applet, they can not edit these
28
Siebel 7 Essentials
5 of 24
28.6
Siebel 7 Essentials
6 of 24
28.7
28
Siebel 7 Essentials
7 of 24
28.8
Operator
Logical
Operator
Function
Must match
exactly
Module 28: Configuring Business Components and Fields
Siebel 7 Essentials
8 of 24
28.9
Search Specifications
28
Siebel 7 Essentials
9 of 24
28.10
Siebel 7 Essentials
10 of 24
28.11
Comma
separated
28
Must match
exactly
Siebel 7 Essentials
11 of 24
28.12
Siebel 7 Essentials
12 of 24
28.13
Field Properties
Customize fields by editing property values
Setting field properties at the business component level sets
them across all applets
28
Siebel 7 Essentials
13 of 24
28.14
Required Property
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 (*)
Module 28: Configuring Business Components and Fields
Siebel 7 Essentials
14 of 24
28.15
Read only on
all applets
28
Siebel 7 Essentials
15 of 24
28.16
Validation Property
Example: When
creating a warranty
for an asset, end
date must be after
start date
Siebel 7 Essentials
16 of 24
28.17
Constant
Field name
28
Operator
Logical Operator
Siebel 7 Essentials
17 of 24
28.18
System value
Inherit from parent (in this
case, from the Account to
which this Contact belongs)
Constant
Module 28: Configuring Business Components and Fields
Siebel 7 Essentials
18 of 24
28.19
28
Siebel 7 Essentials
19 of 24
28.20
Calculated Fields
Derive their value from the values in other fields of the
business component
Cannot be stored in the database
Blank
Siebel 7 Essentials
20 of 24
28.21
` Standard functions
` String, numeric, and logical operators
28
System functions
Reference
Siebel 7 Essentials
21 of 24
28.22
Siebel 7 Essentials
22 of 24
28.23
Summary
28
Siebel 7 Essentials
23 of 24
28.24
Lab
Siebel 7 Essentials
24 of 24
29.1
29
Siebel 7 Essentials
29.2
Module Objectives
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
2 of 15
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:
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Reference
3 of 15
Siebel 7 Essentials
29.4
Colleges Attended
Contact
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
Favorite
Restaurants
4 of 15
29.5
PAR_ROW_ID column
stores foreign key to
ROW_ID in main table
29
Siebel 7 Essentials
5 of 15
29.6
Favorite
Restaurants
PAR_ROW_ID
TYPE
NAME
Type = College
S_CONTACT_XM
ROW_ID
Colleges Attended
Type = Restaurant
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
6 of 15
29.7
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
7 of 15
29.8
Select the
appropriate project
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
8 of 15
29.9
` PAR_ROW_ID
` NAME
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
9 of 15
29.10
Contact
XYZ Restaurant
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
10 of 15
29.11
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
11 of 15
29.12
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
12 of 15
29.13
Applet
Wizard
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
13 of 15
29.14
Summary
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
14 of 15
29.15
Lab
29
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Siebel 7 Essentials
15 of 15
Siebel 7 Essentials
29.16
Configuring Navigation
30.1
30
Siebel 7 Essentials
Configuring Navigation
30.2
Module Objectives
Siebel 7 Essentials
2 of 23
Configuring Navigation
30.3
Reference
3 of 23
Siebel 7 Essentials
30
Configuring Navigation
30.4
Same contact
record in Contact
Detail view
Siebel 7 Essentials
4 of 23
Configuring Navigation
30.5
Configuring Drilldown
Siebel 7 Essentials
Specifies the
target view
5 of 23
30
Configuring Navigation
30.6
Related account
record in Account
Detail - Contacts view
Module 30: Configuring Navigation
Siebel 7 Essentials
6 of 23
Configuring Navigation
30.7
Specifies master BC
in target view
Siebel 7 Essentials
30
Configuring Navigation
30.8
Dynamic Drilldown
Siebel 7 Essentials
8 of 23
Configuring Navigation
30.9
Matching Conditions
Siebel 7 Essentials
9 of 23
30
Configuring Navigation
30.10
Go to view
for this
drilldown
object
Field to
check
Module 30: Configuring Navigation
Siebel 7 Essentials
Value to
check for
Order to
check in
10 of 23
Configuring Navigation
30.11
Siebel 7 Essentials
11 of 23
30
Configuring Navigation
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
Reference
12 of 23
Siebel 7 Essentials
Configuring Navigation
30.13
Thread Properties
Siebel 7 Essentials
13 of 23
30
Configuring Navigation
30.14
Threadbar Tag
Excerpt from
CCViewDetail.swt
how to include
thread bar in view
Web template
Siebel 7 Essentials
14 of 23
Configuring Navigation
30.15
Toggle Applets
Siebel 7 Essentials
15 of 23
You define objects called applet toggles to switch between two or more
different applets, called toggle applets.
30
Configuring Navigation
30.16
Reference
16 of 23
Siebel 7 Essentials
Configuring Navigation
30.17
Siebel 7 Essentials
17 of 23
30
Configuring Navigation
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>
Siebel 7 Essentials
18 of 23
Configuring Navigation
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
Siebel 7 Essentials
19 of 23
30
Configuring Navigation
30.20
Siebel 7 Essentials
20 of 23
Configuring Navigation
30.21
Siebel 7 Essentials
Value to
check for
21 of 23
30
Configuring Navigation
30.22
Summary
Siebel 7 Essentials
22 of 23
Configuring Navigation
30.23
Lab
Siebel 7 Essentials
23 of 23
30
Configuring Navigation
Siebel 7 Essentials
30.24
31.1
31
Siebel 7 Essentials
31.2
Module Objectives
Stand-alone table
1:1 extension table
1:M extension table
Intersection table
Siebel 7 Essentials
2 of 23
31.3
3 of 23
31
Siebel 7 Essentials
31.4
Siebel 7 Essentials
4 of 23
31.5
Joins
5 of 23
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.
Siebel 7 Essentials
31
31.6
Siebel 7 Essentials
6 of 23
31.7
7 of 23
31
Siebel 7 Essentials
31.8
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
9 of 23
31
Siebel 7 Essentials
31.10
Siebel 7 Essentials
10 of 23
31.11
Applying Changes
11 of 23
31
Siebel 7 Essentials
31.12
Propagating Changes
Check in
Developer
Workstation
Developer
Workstation
Check out
Siebel 7 Essentials
Developer
Workstation
12 of 23
31.13
Table name
starts with CX_
Select a
locked project
Select type of
table to create
Table Name
13 of 23
A table name must start with CX_ and cannot exceed 15 characters.
31
Siebel 7 Essentials
31.14
Siebel 7 Essentials
14 of 23
31.15
S_PROD_INT
Extension Tables
ROW_ID
UOM_CD
PART_NUM
NAME
ROW_ID
CX_PROD_INT_X
15 of 23
31
Siebel 7 Essentials
31.16
Indexes
16 of 23
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
17 of 23
31
Siebel 7 Essentials
31.18
Indexes
18 of 23
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
Specify the foreign key column name for each parent table
19 of 23
31
Siebel 7 Essentials
31.20
Indexes
20 of 23
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
21 of 23
31
Siebel 7 Essentials
31.22
Summary
Stand-alone table
1:1 extension table
1:M extension table
Intersection table
Siebel 7 Essentials
22 of 23
31.23
Lab
23 of 23
31
Siebel 7 Essentials
Siebel 7 Essentials
31.24
Configuring Picklists
32.1
32
Siebel 7 Essentials
Configuring Picklists
32.2
Module Objectives
Siebel 7 Essentials
2 of 28
Configuring Picklists
32.3
Picklists
Can be either
` Static
` Dynamic
3 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.4
Picklist Terms
Reference
Siebel 7 Essentials
4 of 28
Configuring Picklists
32.5
Static Picklist
Drop-down
list
5 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.6
Specifies a value in
the MR_MS picklist
Siebel 7 Essentials
6 of 28
Configuring Picklists
32.7
Administering a Picklist
Ok to set inactive
Reference
7 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.8
Siebel 7 Essentials
8 of 28
Configuring Picklists
32.9
9 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.10
Siebel 7 Essentials
10 of 28
Configuring Picklists
32.11
11 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.12
3. Specify Mapping
Field in
originating BC
Siebel 7 Essentials
Configuring Picklists
32.13
Identify the list column/control that that references the field with
a picklist
` Can involve multiple applets
13 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.14
Drop-Down
Is used to display values for a static picklist
Is auto-generated at run time
Drop-down
Siebel 7 Essentials
14 of 28
Configuring Picklists
32.15
15 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.16
Dynamic Picklist
Displays
values
queried from
the Account
BC
Module 32: Configuring Picklists
Siebel 7 Essentials
16 of 28
Configuring Picklists
32.17
17 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.18
Pick business
component
Determines whether
users can add or delete
records through picklist
Siebel 7 Essentials
18 of 28
Configuring Picklists
32.19
19 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.20
3. Specify Mappings
` Map the primary key field in the pick business component to the
foreign key field
Fields in originating BC
Module 32: Configuring Picklists
Siebel 7 Essentials
Fields in pick BC
20 of 28
Configuring Picklists
32.21
21 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.22
Pick applet
controls
Siebel 7 Essentials
22 of 28
Configuring Picklists
32.23
Runtime set to
TRUE
23 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.24
Siebel 7 Essentials
24 of 28
Configuring Picklists
32.25
Constrained Picklist
25 of 28
32
Siebel 7 Essentials
Configuring Picklists
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
Siebel 7 Essentials
26 of 28
Configuring Picklists
32.27
Summary
27 of 28
32
Siebel 7 Essentials
Configuring Picklists
32.28
Lab
Siebel 7 Essentials
28 of 28
33.1
33
Siebel 7 Essentials
33.2
Module Objectives
Siebel 7 Essentials
2 of 27
33.3
Multi-Value Group
Select button
invokes the
MVG applet
MVG Applet
Module 33: Configuring Multi-Value Groups
Reference
3 of 27
33
Siebel 7 Essentials
33.4
Position
MVG
Territory
MVG
Organization
MVG
Business
Address
MVG
Module 33: Configuring Multi-Value Groups
Multi-Value Group
Siebel 7 Essentials
4 of 27
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.
33.5
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
MVG Queries
Siebel 7 Essentials
6 of 27
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
City
Location
Singlevalue field
Multi-value
field
S_ORG_EXT
EMP_COUNT
LOC
NAME
ROW_ID
Business Address
City
Street Address
Child business
component
7 of 27
33
Siebel 7 Essentials
33.8
Link
City
Location
Parent business
component
Business Address
City
Street Address
Child business
component
Siebel 7 Essentials
8 of 27
33.9
9 of 27
33
Siebel 7 Essentials
33.10
Set destination
business component
Siebel 7 Essentials
10 of 27
33.11
Fields in
parent BC
Module 33: Configuring Multi-Value Groups
Multi-value
link
Fields in
child BC
11 of 27
33
Siebel 7 Essentials
33.12
Can display more columns than are displayed on the parent applet
MVG Applet
Siebel 7 Essentials
12 of 27
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.
33.13
Pick applet
controls
13 of 27
33
Siebel 7 Essentials
33.14
Field control
is on
Module 33: Configuring Multi-Value Groups
Setting Runtime to
TRUE
Siebel 7 Essentials
Set MVG
Applet
Set Runtime
TRUE
14 of 27
33.15
Singlevalue field
Industry
Location
Industry
MVG Applet
Multi-value
field
Child business
component
Industry
Name
SIC Code
15 of 27
33
Siebel 7 Essentials
33.16
Invokes
associate applet
Siebel 7 Essentials
16 of 27
33.17
Industry
MVG
Position
MVG
Territory
MVG
Organization
MVG
Business
Address
MVG
Module 33: Configuring Multi-Value Groups
17 of 27
33
Siebel 7 Essentials
33.18
Business
Address
MVG
Module 33: Configuring Multi-Value Groups
Siebel 7 Essentials
Territory
MVG
Industry
MVG
18 of 27
33.19
Account
Name
Location
Street Address
Primary Address Id
Business Address
Id
City
Street Address
19 of 27
33
Siebel 7 Essentials
33.20
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
Multiple Queries
Siebel 7 Essentials
20 of 27
Multiple queries are required to retrieve all the child records when the user
invokes the MVG applet.
33.21
The Siebel Data Model includes primary foreign keys for many
relationships
` Begin with PR_
CITY
ADDR
ROW_ID
PR_ADDR_ID
ROW_ID
LOC
S_ADDR_ORG
NAME
S_ORG_EXT
21 of 27
33
Siebel 7 Essentials
33.22
Siebel 7 Essentials
22 of 27
33.23
23 of 27
33
Siebel 7 Essentials
33.24
MVG Wizard
Siebel 7 Essentials
24 of 27
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.
33.25
Displaying MVGs
25 of 27
33
Siebel 7 Essentials
33.26
Summary
Siebel 7 Essentials
26 of 27
33.27
Lab
27 of 27
33
Siebel 7 Essentials
Siebel 7 Essentials
33.28
34.1
34
Siebel 7 Essentials
34.2
Module Objectives
Person
Position
Organization
Siebel 7 Essentials
2 of 20
34.3
Access Control
Reference
34
Siebel 7 Essentials
34.4
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
Siebel 7 Essentials
34.5
Access control
based on User ID
Reference
5 of 20
34
Siebel 7 Essentials
34.6
Visibility Field
Siebel 7 Essentials
6 of 20
34.7
7 of 20
34
Siebel 7 Essentials
34.8
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
Context Views
10 of 20
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
11 of 20
34
Siebel 7 Essentials
34.12
Siebel 7 Essentials
12 of 20
34.13
Personal View
Displays all records for which user is the owner
Is configured by
Personal View
13 of 20
34
Siebel 7 Essentials
34.14
Manager View
Is configured by
` Setting the Visibility Applet property to identify an applet in the
view
` Setting the Visibility Applet Type property to Manager
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.
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
Is configured by
` Setting the Visibility Applet property to identify an applet in the
view
` Setting the Visibility Applet Type property to Organization
15 of 20
34
Siebel 7 Essentials
34.16
Is configured by
` Setting the Visibility Applet property to identify an applet in the
view
` Setting the Visibility Applet Type property to All
Siebel 7 Essentials
16 of 20
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
Siebel 7 Essentials
18 of 20
34.19
Summary
Person
Position
Organization
19 of 20
34
Siebel 7 Essentials
34.20
Lab
Siebel 7 Essentials
20 of 20
Localizing an Application
35.1
35
Siebel 7 Essentials
Localizing an Application
35.2
Module Objectives
Siebel 7 Essentials
2 of 24
Localizing an Application
35.3
Global Deployment
3 of 24
35
Siebel 7 Essentials
Localizing an Application
35.4
Locale
Numbers
Money
Date and time
Can be a:
` Single country (for example, Australia)
` Part of country (for example, French-speaking Canada)
Siebel 7 Essentials
4 of 24
Localizing an Application
35.5
Internationalization
Reference
5 of 24
35
Siebel 7 Essentials
Localizing an Application
35.6
Regional Settings
Telephone numbers
6 of 24
The mobile client uses the OS regional setting for the client machine on
which it is running.
Siebel 7 Essentials
Localizing an Application
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
35
Siebel 7 Essentials
Localizing an Application
35.8
Reference
Siebel 7 Essentials
8 of 24
Localizing an Application
35.9
9 of 24
35
Siebel 7 Essentials
Localizing an Application
35.10
Siebel 7 Essentials
10 of 24
Localizing an Application
35.11
Localizing Applets
Set the Tools Language Mode
Create the locale definitions for the applet to be translated
Invoke the Applet Web Editor and preview the applet to verify
the translations
11 of 24
35
Siebel 7 Essentials
Localizing an Application
35.12
Menu
text
Thread Bar
Applet
title
Labels
View Tab
Column
Module 35: Localizing an Application
Siebel 7 Essentials
12 of 24
Localizing an Application
35.13
Locale Management
Utility
13 of 24
35
Siebel 7 Essentials
Localizing an Application
35.14
From Opportunity
Form applet
Siebel 7 Essentials
14 of 24
Localizing an Application
35.15
15 of 24
35
Siebel 7 Essentials
Localizing an Application
35.16
Siebel 7 Essentials
16 of 24
Localizing an Application
35.17
5.
5.Compile
Compilenew
new.srf
.srffile
fileand
anddeploy
deploy
17 of 24
35
Siebel 7 Essentials
Localizing an Application
35.18
Siebel 7 Essentials
18 of 24
Localizing an Application
35.19
19 of 24
35
Siebel 7 Essentials
Localizing an Application
35.20
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
Siebel 7 Essentials
20 of 24
Localizing an Application
35.21
21 of 24
35
Siebel 7 Essentials
Localizing an Application
35.22
Siebel 7 Essentials
22 of 24
Localizing an Application
35.23
Summary
23 of 24
35
Siebel 7 Essentials
Localizing an Application
35.24
Lab
Siebel 7 Essentials
24 of 24
Configuration Guidelines
36.1
36
Siebel 7 Essentials
Configuration Guidelines
36.2
Module Objectives
Siebel 7 Essentials
2 of 19
Configuration Guidelines
36.3
36
Configuration Guidelines
Business components
Business objects
Applets
Views
Screens
Applications
Reference
Siebel 7 Essentials
3 of 19
Configuration Guidelines
36.4
Copying a Business
Component
Siebel 7 Essentials
4 of 19
You will need to copy the Account business component (and cal it Sub
Account) to create an Account Sub Account view.
Configuration Guidelines
36.5
36
Upgrade Ancestor
Set ancestor
manually
Upgrade Ancestor
Siebel 7 Essentials
5 of 19
Configuration Guidelines
36.6
Specialized Classes
Siebel 7 Essentials
6 of 19
Configuration Guidelines
36.7
36
Siebel 7 Essentials
7 of 19
Configuration Guidelines
36.8
Configuring Applets
`
`
`
`
Siebel 7 Essentials
8 of 19
Configuration Guidelines
36.9
36
Configuring Views
Siebel 7 Essentials
9 of 19
Configuration Guidelines
36.10
Configuring Screens
Add a new screen whenever you create a new business object
Modify existing screens to:
View tabs
Show drop-down list
Site map
Siebel 7 Essentials
10 of 19
Configuration Guidelines
36.11
36
Configuring Applications
Siebel 7 Essentials
11 of 19
Configuration Guidelines
36.12
Siebel 7 Essentials
12 of 19
Configuration Guidelines
36.13
36
Naming Conventions
Siebel 7 Essentials
13 of 19
Configuration Guidelines
36.14
Optimizing Performance
Use primaries for multi-value groups in list applets
Ensure that indexes exist to support sort and search
specifications
Performance
Implications
Siebel 7 Essentials
14 of 19
Configuration Guidelines
36.15
36
Performance
Implications
Siebel 7 Essentials
15 of 19
Configuration Guidelines
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
Siebel 7 Essentials
16 of 19
Configuration Guidelines
36.17
36
Recommended Reviews
Siebel 7 Essentials
17 of 19
Configuration Guidelines
36.18
Summary
Siebel 7 Essentials
18 of 19
Configuration Guidelines
36.19
36
Lab
Siebel 7 Essentials
19 of 19
Configuration Guidelines
Siebel 7 Essentials
36.20