siebel 7 essentials student guide vol2

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.

Copyright 2001 Siebel Systems, Inc. Siebel Systems, Inc.

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.

Siebel 7 Essentials

Siebel Systems, Inc. i

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Table of Contents

Volume 1 Foundations Module i: Siebel 7 Essentials Training Module 1: Introducing Siebel eBusiness Applications Module 2: Using the Siebel Client Module 3: Organizing Data Behind the User Interface Architecture and Installation Module 4: Exploring the Siebel Architecture Module 5: How Clients Access Siebel Data Module 6: Installing Siebel Software Module 7: Server Administration Access Control and Organization Setup Module 8: Access Control and Views Module 9: Access Control and Data Module 10: Access Control and View Types Module 11: Creating an Organization Module 12: Authenticating Users Exploring Siebel Applications Module 13: Understanding Object Definitions Behind a Siebel Application Module 14: Using Siebel Tools to Examine Object Definitions Module 15: Understanding the Siebel Data Model Module 16: The Siebel Data Model: Party Business Components Configuration Module 17: The Configuration Process Module 18: Managing Object Definitions

Siebel 7 Essentials

ii Siebel Systems, Inc.


Volume 2 Configuration, Continued

Module 19: Editing and Compiling Object Definitions Module 20: Understanding Siebel Template Files Module 21: Configuring Applications and Screens Module 22: Configuring Views Module 23: Configuring List Applets Module 24: Configuring Form Applets Module 25: Understanding Business Components and Joins Module 26: Business Components and Joins: Party Extension Tables Module 27: Understanding Business Objects and Links Module 28: Configuring Business Components and Fields Module 29: Creating a New BC Using the Standard 1:M Extension Table Module 30: Configuring Navigation Module 31: Extending the Database Module 32: Configuring Picklists Module 33: Configuring Multi-Value Groups Module 34: Configuring Access Control Module 35: Localizing an Application Module 36: Configuration Guidelines

Volume 3 Data Loads Module 37: Introducing Enterprise Integration Manager Module 38: Data Mapping Module 39: Invoking Enterprise Integration Manager Module 40: Setting Enterprise Integration Manager Options Module 41: Access Control and Access Groups

Siebel 7 Essentials

Siebel Systems, Inc. iii


Business Process Automation Module 42: Introducing Siebel Workflow Module 43: Invoking Workflow Processes Module 44: Additional Workflow Topics Module 45: Introducing Assignment Manager Module 46: Creating Sales Assignment Rules Module 47: Creating Service Assignment Rules Module 48: Invoking Assignment Manager Module 49: Personalizing View and Applet Access Module 50: Personalizing Content and Behavior Deployment Module 51: Using Siebel Remote to Support Mobile Clients Module 52: Additional Siebel Remote Topics Module 53: Migrating Data Between Environments Conclusion Module 54: Final Words

Siebel 7 Essentials

iv Siebel Systems, Inc.


Editing and Compiling Object Definitions

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION — DUPLICATION IS PROHIBITED

19.1

Siebel Systems, Inc.Siebel 7 Essentials

Module 19: Editing and Compiling Object Definitions

19



19.2


Module 19: Editing and Compiling Object Definitions 2 of 28

Module Objectives

After completing this module you will be able to:Create new and edit existing object definitionsValidate edited object definitionsArchive object definitions and projectsBack up the local databaseCompile object definitions into a repository file

Why you need to knowThese are all fundamental activities that occur during all configuration efforts



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 lockedEdit the property

Type in a valuePick a value from a picklist (if provided)

Type SelectIndicates project locked

Siebel Tools ReferenceReference

19



19.4



Creating a New Object Definition

Select the desired object type in the Object ExplorerCreate a new record in the Object List Editor

Select a project from picklistCreate a unique name Assign values to remaining fields

Locked projects only



19.5



Changed Flag

Indicates records that have been modified since the Changed DateIs set whenever a record is editedIs cleared by resetting the Changed Date value

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.

Changed Flag

19



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

Warning

Error



19.7



Validating Object Definitions Continued

Select object definition to validateRight-click and select Validate

Click Start in Validate window

Violations appear in Errors list

window

Click to access Validate Options

window

19



19.8



Archive Files

Contain object definitions exported from a repositoryAvailable for importing into other repositories

Have .sif extension by defaultAre used to share object definitions in multiple repository developmentAre used to back up object definitionsCan be version-controlled using source control systems



19.9



Exporting Object Definitions

Top-level object definitions can be exported to an archive fileIncludes all child object definitions for selected parent definition

To export object definitionsSelect the object definition or definitionsSelect Tools Add to ArchiveSelect an existing (or create a new) archive fileClick Save in the Export to Archive File window

19



19.10



Exporting Projects

Projects can also be archived to .sif filesSelect the project (or projects) to be archivedSelect Tools Add to ArchiveSelect an existing (or create a new) archive fileClick Save in the Export to Archive File window



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 repositoryTo import object definitions

Select Objects Import from ArchiveSelect the archive fileIndicate how to resolve conflicting object definitions

19



19.12



Resolve Import Conflicts

Set the default conflict resolution

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



19.13



Compare Objects

Displays differences between selected object definition and another one:

In current local repositoryIn archive fileIn repository on server

Allows developers to reconcile differences while comparing objects

Delete individual child object definitionsCopy individual child object definitions in either direction

19



19.14



Compare Objects Continued

To compare object definition to one in archive or repositorySelect object definition to be comparedSelect Tools Compare ObjectsSelect type of comparisonChoose the archive or repository



19.15




Examine the differences in the Compare Objects window

Definitions with difference highlighted

Differences displayed

19



19.16




To compare two object definitions in the developer repositorySelect two object definitions to be compared (by shift-clicking)Select Tools Compare Objects Selected

Modifying definitions is supportedCopy selected field

Delete selected field

A child object definition in either parent object definition can be deleted or copied to the other definition.

Modifying Definitions



19.17



Creates archive when project checked in

Check archive into code

management system

Source Code Control Integration

Automate integration with source code control for repository data

ODBC to server and local

databases

19



19.18



Backing Up the Development Database

Developers can back up local work by:Using archive files to back up repository dataChecking in projects into the server in order to back up repository dataCopying the local database file (.dbf) in order to back up the entire database

.sif

Repository Data

Server

Add to archive

Check in

Windows copy/paste



19.19



Compiling

Compile to produce an .srf file to test the configurationReads object definitions from repository and creates a flat filerepresentation to be accessed by siebel.exe at runtime

Compile into .srf file located in the objects directory of the client application

RepositoryData

Database

Compiling Configured Application

.srf

ApplicationObject Manager

ToolsApplication

19



19.20



Compile Options

Developers can compileProjectsIndividual object definitions



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 compileTo compile projects

Select Tools Compile ProjectsSelect project or projects

Compile into client directory

Remember to compile any projects that you get to ensure that object definitions edited by your fellow developers are compiled into your .srf file.

Get Projects

19



19.22



Compile Objects

Top-level object definitions can be compiled individuallyCompiles all child object definitions for the selected parent

To compile individual object definitionsSelect the object definition or definitionsRight-click and select Compile



19.23



Configuration File

Copy the default .cfg file for the application being customizedEdit it to refer to the new .srf file

Copy .cfg file

Change Repository File to refer to new .srf file

19



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



19.25



Setting the Run-Time Start-Up Parameters

Use View Options and select the Debug tab to set the run-time start up information

Browse to locate the modified .cfg file

Optionally provide login parameters

19



19.26



Launching the Local Web Client

Test the new configuration by selecting Debug Start Collects login parameters if not already specifiedLaunches the local Siebel remote Web client

You may use the F5 function key to execute the Debug Start command as well.

Start



19.27



Summary

This module showed you how to:Create new and edit existing object definitionsValidate edited object definitionsArchive object definitions and projectsBack up the local databaseCompile object definitions into a repository file

19



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

Understanding Siebel Template Files


20.1


Module 20: Understanding Siebel Template Files

20



20.2


Module 20: Understanding Siebel Template Files 2 of 28

Module Objectives

After completing this module you will be able to:Describe the role of Siebel Web template filesDescribe the role of Siebel tags in template filesList the types of templates Describe how to register, associate, and bind a template file

Why you need to knowUnderstanding template structure and how to register, associate,and bind template files is necessary in order to deploy your Siebel eBusiness application




20.3



Siebel Template Files

Are HTML files that specify how to render the views for a Siebel application in the user’s browserSpecify the formatting and layout of:

Graphical and text elements User data

Consist of standard HTML tags and Siebel-specific tags

HTML table tag

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

The sample HTML tags shown in the slide are excerpted from the CCFrameBanner.swt template file.

Sample HTML

20



20.4



<swe:for-each-screen>

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

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 themto HTMLControl layout repetitively through iteration

Serve as placeholders for Siebel-specific contentSiebel tag to iterate over all screens

Siebel tag to insert the name of the screen

The sample HTML tags shown in the slide are excerpted from the CCScreenbar_Tabs.swt template file.

Sample HTML



20.5



Siebel Template Files

Can include other template files (swe:include tag)Enables modularization of the template files

Permits efficient reuse of filesMinimizes 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

The sample HTML tags shown in the slide are excerpted from the CCSiteMap.swt template file.

Sample HTML

20



20.6



Siebel Template Files Continued

Can include links to style sheets to define global parametersFont family and sizeForeground and background colorsAnd so forth

Style sheets:Are located in PUBLIC\enu\FILES directory in a Siebel installationCan be modified by customers

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; }

From main.css



20.7



Siebel Template Files Continued

Are stored as separate files outside the Siebel repositoryLocated in the WEBTEMPL directory in a Siebel installationHave .swt extension

Are edited using a text or HTML editor of your choice

20



20.8



Web Template Explorer

Use the Web Template Explorer in Siebel Tools to:Identify the template files included in a template fileExamine the contents of a template fileInvoke an editor to modify the template file

Invoke by selecting View Windows Web Templates Window



20.9



Using Template Files

Requires three types of relationshipsRegistering, associating, and binding

Object definitions (in the repository) specify these relationships

View Applets

(View) Web template

Applet placeholders

(View)Templatefile

Binding

Associating

Registering

20



20.10



Registering

Creates an object definition in the repository that identifies the physical template file

View Applets

(View) Web template

Applet placeholders

(View)Templatefile

Registering



20.11



Registering a Template File

Creates a Web Template object definition to define the logical name for the templateCreates a Web Template File object definition to reference the actual physical file

Logical name in repository for template

Actual name of the physical template file

Type of Web template

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.

Registering

20



20.12



Types of Templates

View templates are used to render Siebel viewsContain placeholders for applets

Applet templates are used to render Siebel appletsContain placeholders for controls

Web page templates are used to render elements other than Siebel views and applets

Login pagesError pagesContainer pages

Uses Web page template



20.13



Container Page

Contains tags that render the elements that surround the view in a Siebel application

Menus Screen tabs

View tabs

Logos and graphics

20



20.14



Associating

Identifies the Web Template object definition used to render the view, applet, or Web page

View Applets

(View) Web template

Applet placeholders

(View)Templatefile

Associating



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

20



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

Applet template used to render

applet for that mode

Mode for the applet



20.17



Applet Web Templates

Applets can use a different Applet Web Template object definition for different applet modes

Base (display only), edit, queryRequired most often for applets in customer applications

Applet in base mode

Applet in query mode

The Contact Service Request List Applet (eService) is shown as it displays in the base and query modes.

Applet

20



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

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.

Web Page Template



20.19



Binding

Maps the components of a view or applet to the placeholders in the corresponding template file

View Applets

View Webtemplate

AppletPlaceholders

ViewTemplate

File

Applets Controls/List

Applet Webtemplate

ControlPlaceholders

AppletTemplate

File

Binding Applets to Views Binding Controls to Applets

BindingBinding

20



20.20



Binding Information

Is specified in the repository with these object definitions View Web Template ItemApplet Web Template Item Web Page Item

Results in the corresponding element being displayed at run time



20.21



View Web Template Items

Are created by the binding processItem 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"

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.

swe:applet Tag

20



20.22



Applet Web Template Items

Are created by the binding processItem 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">

The swe:control tag shown in the slide is in the dCCForm1Col.swttemplate 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.

swe:control tag



20.23



Web Page Items

Identify the links and buttons appearing on a Siebel Web pageItem 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

The HTML and SWE tags shown in the slide are excerpted from the dCCFrameBanner.swt template file.

swe:pageitem tags

20



20.24



Mapping Placeholders

Not all placeholders in a template file need to be mappedHTML source is generated only for mapped placeholders

Allows for views with varying number of applets to reference the same view Web templateAllows for applets with varying number of controls to reference the same applet Web template



20.25



Template Reuse

A Siebel Web template can be referenced by multiple object definitions

Consequence of a template containing placeholdersReuse of templates:

Enables standardization of display for views and appletsMinimizes the number of templates required and the cost of creation and maintenanceSimplifies application-wide modification and upgrade

20



20.26



Summary of Object Definitions

Registering, associating, and binding adds object definitions tothe repository

RegisteringWeb TemplateWeb Template Files

AssociatingApplet Web TemplateView Web TemplateWeb Page

BindingApplet Web Template ItemView Web Template FilesWeb 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



20.27



Summary

This module showed you how to:Describe the role of Siebel Web template filesDescribe the role of Siebel tags in template filesList the types of templates Describe how to register, associate, and bind a template file

20



20.28



Lab

In the lab you will:Determine the template objects associated to view and applet objectsExamine the binding in views and appletsEdit parameters in a style sheet to modify the UI of a Siebel application

Configuring Applications and Screens


21.1


Module 21: Configuring Applications and Screens

21



21.2


Module 21: Configuring Applications and Screens 2 of 19

Module Objectives

After completing this module you will be able to:Customize container page components including page and view tabs and system menusModify the text in the startup splash screen

Why you need to knowEnables you to configure aspects of the interface to meet your company’s requirements



21.3



The Container Page

Web page contents with Siebel data and formattingRenders the elements that surround the view in aSiebel application

Container Page

21



21.4



Specifying the Container Page

The Container page is specified in the Application object definition

Container Web Page: Specifies the Container

Page



21.5



The Container Page: Employee Application

Container page sections are composed of frames

Screenbar frame

Viewbar frame

Banner frame

Content frame

Configuration of the Content frame will be covered in a later module. The Content frame contains the views.

Content Frame

21



21.6



The Banner Frame

Contains the application-level menus and branding area

Application-level menus Branding area

CCFrameBanner.swtBanner Frame Template



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

21



21.8



The Banner Frame: Branding Area

The branding area may contain additional images such asCompany logoGraphic to illustrate primary purpose of page

Modify the CCFrameBanner.swt template file to add an imageModify 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>

This is the cascading style sheet that controls visual attributes. main.css



21.9



Screenbar Frame

Contains screen tabs for major screensA screen is a collection of views

CCFramceScreenbar.swtScreenbar Frame Template

21



21.10



Screenbar Frame: Screen Tabs

Create a page tab object definition for each screen you want to appearSelect screens that will appear as tabs, mark all others Inactive

Text: Specifies text that appears on page bar

Sequence: Specifies page tab order appearance in screenbar

Inactive: Select if you do not want the tab to show



21.11



The Viewbar Frame

ContainsSiebel Application Toolbar

History menuCustomer Dashboard control

Show drop-down list boxViews

Show drop-down list box

Siebel Application Toolbar

DashboardHistory menu

Appears in employee applications only.Siebel Application Toolbar

21



21.12



The Viewbar Frame: Siebel Application Toolbar

Create Toolbar Object Definitions for each toolbarDashboardHistory

Dashboard toolbar



21.13



Screen View

Edit the Screen View definitions to set the display text and sequence for views

Sequence: Defines order in drop-down lists

and view tabs

Viewbar Text: Text that appears in Show drop-down list and view tabs

Menu Text: Text that

appears in site map

21



21.14



Banner frame

The Container Page: Customer Application

Has the same frames as the Employee applicationFewer objects are in the framesWith a few exceptions, objects are configured similarly

Viewbar frame

Content frame

Screenbar frame



21.15



The Banner Frame: Customer Application

Contains global navigation hyperlinks

21



21.16



The Banner Frame: Customer Application Continued

Change caption in Web Page Item

Caption: Changes displayed text



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

Siebel Applications Administration GuideReference

21



21.18



Summary

This module showed you how to:Customize container page components including page and view tabs and system menusModify the text in the startup splash screen



21.19



Lab

In the lab you will:Configure startup textCustomize page tabs and view tabsCustomize system menusAdd a graphic to the banner frameCustomize the color and banner frame graphic of the customer application

21



21.20


Configuring Views


22.1


Module 22: Configuring Views

22

Configuring Views


22.2


Module 22: Configuring Views 2 of 24

Module Objectives

After completing this module you will be able to:Explain the role of basic view templates and Siebel tags for viewsCreate and administer a viewAssociate a view with a template

Why you need to knowEnables you to configure views to meet your company’s business requirementsEnables you to make new views available to users

Configuring Views


22.3



Views

Consist of one or more lists or formsReference a single business objectAre grouped into a screen


22

Configuring Views


22.4



View Templates

Are used to render Siebel viewsContain placeholders for one or more applets

ID =1

ID =2

Configuring Views


22.5



View Templates Continued

Contain multiple applet tagsTypically not all applet tags are mapped

ID =1

ID =2

ID =3-5

ID =6-7

ID =8-9 ID =10-11

22

Configuring Views


22.6



Applets in View Template

Can be related asPeersParent-childParent-child-grandchild

Peer Peer

Parent

Child

Parent

Child

Grandchild

Configuring Views


22.7



Selecting a View Template

Find an existing view that has desired applet layoutExamine the view template object definition to determine the view template to use

22

Configuring Views


22.8



Steps to Create a View

1. Create new view1. Create new view

2. Associate view templatewith view object definition

2. Associate view templatewith view object definition

3. Bind applets to view template3. Bind applets to view template

5. Register and assign view5. Register and assign view

Use ViewWizard

Use ViewWizard

4. Configure threadbar4. Configure threadbar

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.

Best Practice

Configuring Views


22.9



View Wizard

Use the View Wizard to create view and assign appletSelect the project and business object and enter the name and title of the viewSelect a Web templateAssign applets

22

Configuring Views


22.10



1. Create a New View

Create a new View object definitionAssign a view name, project, business object, and view title

Title appears in Show drop-down list or view tab

View name

Configuring Views


22.11



2. Associate View Template and View

Assign the template the view will useAdd a View Web Template object definition to the view

Set the following properties: Name, Web Template

22

Configuring Views


22.12



3. Bind Applets to View Template

Steps1. Launch the Web View Editor2. Drag the applets from the list onto the placeholders in the view

templateThis creates the View Web Template Items in the repository

3. Save the template

Configuring Views


22.13



3. Bind Applets to View Template Continued

Launch the Web View Layout EditorThe Web View Layout Editor opens the template file and the applets window

1. Right click View Web Template object

2. Select Edit Web Layout

22

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

Configuring Views


22.15




View Web Template ItemIs created during drag-and-drop operation using the Web View Editor Associates an applet in the repository with an applet identifier in the View templateIs an object definition containing binding specification for a view

<swe:applet id=“1"/>

Properties are Name, Item Identifier, and Applet

22

Configuring Views


22.16




Default Applet Mode for applets in a new view is BaseSet the Applet Mode appropriately

Applet Mode

Configuring Views


22.17



4. Configure Thread Bar

The Thread bar tracks user navigation among views

Edit the View definition to set the display text for the Thread bar

Thread Title: Displays text in

Thread bar

Thread bar

22

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

Viewbar Text appears in the Show drop-down list

or view tabs

Menu Text appears in the Site Map

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 viewAssign the view to one or more responsibilities

22

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

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

22

Configuring Views


22.22



View Access Location on UI

Views can be accessed throughShow drop-down listView tabs

View tab

Show drop-down list

Configuring Views


22.23



Summary

This module showed you how to:Explain the role of basic view templates and Siebel tags for viewsCreate and administer a viewAssociate a view with a template

22

Configuring Views


22.24



Lab

In the lab you will:Determine displayed view nameModify display text for an existing viewModify applets in a view

Configuring List Applets


23.1


Module 23: Configuring List Applets

2323



23.2


Module 23: Configuring List Applets 2 of 28

Module Objectives

After completing this module you will be able to:Describe applet template featuresCreate a list applet using the List Applet WizardEdit list column definitions

Why you need to knowEnables you to configure applets that display your company’s data




23.3



Primary Applet Types

List AppletDisplays one or more records simultaneously in a listFields for one record are displayed in a single rowDisplays relatively few fields due to width of monitor viewable area

Form AppletDisplays a single recordFields for the record are displayed in a grid or formCan show more fields at once than a list appletWill be covered in the next module

The following are some additional applet types (reference SiebelBookshelf for a complete list):

Catalog ListChartExplorer viewHierarchical listMessageMulti value group appletPick appletRich listSalutation

Additional Applet Types

2323



23.4



Applet Class Property

Determines the behavior of the appletSpecifies the C++ class used at run time for the applet

Is set to CSSFrameList for list appletsIs set to CCSFrame for form appletsShould typically never be changed

Specialized classes are associated with specialized business components and applets

Examples of specialized applets include Calendar Applets and Gantt Chart Applets.

Specialized Applet



23.5



List Applet

Displays one or more records in a list table formatEach row displays fields from one record in the business component

Typically includes two to four action control buttonsSupports drilldown to other views through hyperlinked fields

One record

2323



23.6



List Applet Action Control Buttons

Use next record and previous record buttonsAllow scrolling one set of records at a time

New buttonCreates a new record for the list

May invoke a different applet Web templateUse the New button or CTRL-N

Save buttonImmediately saves record

In customer application user must explicitly save new or changedrecords using Save button In employee application you can save by stepping off the record (“implicit save”)



23.7



List Applet Web Templates

List applets can have multiple Web templates, called modesTypical modes are Base, Edit, and Edit List

Choose the template based on desired applet functionalityHint: Look at template definitions of similar applets

2323



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



23.9



Edit Mode

Appears as a form appletIs invoked by buttons or applet menu from base modeAllows user to enter new records or edit existing records

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.

The template most commonly used for list applets in base or edit list mode is CCAppletList_B_EL.swt.

Template

2323



23.10



Edit List Mode

Permits users to edit fields in a list appletEditing is enabled by defaultYou can disable editing by setting the HTML List Edit property for the column to FALSE

Edit fields directly in list applet

Click New to create a new blank record in the list



23.11



Applet Mode Property

Appears in the View Web Template Items object definitionDetermines which mode the user sees when a view is invoked

2323



23.12



Creating a List Applet

You can follow these steps to create a new list applet…

…Or you can use the List Applet WizardAutomates these stepsGenerally, the preferred method

1. Create new applet object definition1. Create new applet object definition1. Create new applet object definition

2. Associate applet templatewith applet object definition

2. Associate applet template2. Associate applet templatewith applet object definitionwith applet object definition

3. Bind controls to applet template 3. Bind controls to applet template 3. Bind controls to applet template



23.13



List Applet Wizard

Ensures object definitions and properties are createdEnsures steps are not omitted

Increases developer productivity Speeds project completion

To invoke the List Applet Wizard, select File New ObjectIn the Applets tab, select List Applet and click OK

2323



23.14



Using the List Applet Wizard

Use the List Applet Wizard to create a new list appletAssign a project, business component, applet name, and title

Creates an applet object definition in Tools

BusinessComponent

Check out or lock project before using the Applet Wizard.Tip



23.15



Using the List Applet Wizard Continued

Select Web templates for Web layoutAssociates template and applet

Normally shows only templates for list applets;

if checked shows all templates

Associating a template and an applet in Tools lets the program know which template(s) to use for the applet.

Review

2323



23.16




Choose the Business Component fields that will appear in the Web layout

Creates the Applet Web Template ItemsNecessary to bind the controls to the applet

Arrange fields in order to show in

the applet

Select fields to show in the

applet

If you add all the columns in the business component, you can delete and add them later as necessary.

Columns



23.17




Choose the HTML controls to be added to the appletControl method invoked when control icon selected

Tip: Let the Wizard create all default controls so you don’t have

to add them manually.

Icons

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.

Tip

2323



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 componentControls added to this applet are automatically added to any new applet you create using the applet wizards



23.19




Review the applet object you have defined

If information is correct, click

Finish

2323



23.20




Finishing the list appletCreates required object definitions for

Applet Control ListList column

MapsApplet Web TemplatesApplet Web Template Items

Sets applet class to CSSFrameListInvokes the Web Layout Editor



23.21



Web Layout Editor

Use Edit Web Layout Editor to add, remove, and reorder the columns displayed

To add, drag and drop

controls and columns

To delete columns select Delete

2323



23.22



Applet Title

Change the Title property to set the applet display name



23.23



List Column Definitions

Edit the List Column definition to:Set the column display nameSet the column to read onlyEnable or disable popup editingEnable or disable special processing at run timeChange the 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.

HTML Type

2323



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



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

2323



23.26



<swe:for-each startValue="501" count =20

iteratorName="currentId">

<swe:control id="swe:currentId“>

List Applet Template

Determines the layout and presentation of the list appletEach item on the applet has an Item Identifier propertyEach Item Identifier matches a Control ID in the templateThe Control ID tells the Siebel Web Engine where and how to render the item

Is reusableFor example: a Contact list applet and an Account list applet may use the same list applet template



23.27



Summary

This module showed you how to:Describe applet template featuresCreate a list applet using the List Applet WizardEdit list column definitions

2323



23.28



Lab

In the lab you will:Create list appletsModify list applets Create and administer a view

Configuring Form Applets


24.1


Module 24: Configuring Form Applets

24



24.2


Module 24: Configuring Form Applets 2 of 19

Module Objectives

After completing this module you will be able to:Create a form applet using the Form Applet Wizard Modify an existing form appletDescribe the structure of a form applet Web template

Why you need to knowEnables you to configure applets that display your company’s dataUsing Applet Wizards reduces the effort to configure applets




24.3



Form Applet

Displays one record at a time in a data entry form layoutField controls display fields in the business component

Field Caption property displays caption textButton controls initiate an action when clicked

Textbox controlCaptionMiniButton controls

24



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)



24.5



Expanding and Collapsing Form Applets

Collapsed (“Less”)Is the default displayShows limited set of fieldsOnly displayed fields can be edited

Expanded (“More”)Shows all fieldsFull edit capabilities (all unprotected fields can be edited)

User can toggle using the show more button

Fields are usually editable in form applets but can be configured to be read only.

Read Only Fields

24



24.6



Form Applet Modes

Form applets only use Base and Edit modesBase mode is read-onlyEdit mode permits editing

The View Web Template Items object definition determines which mode is displayed when a view is invoked



24.7



Create a New Form Applet

Use the Form Applet Wizard to create a form appletAssign the project, business component, applet name, and title

Business component

24



24.8



Create a New Form Applet Continued

Select Web templates for Web layoutAssociates template and applet



24.9




Select fields to appear in the form applet

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.”

Some business components have numerous fields. Add those fields you will use or think you may use.

Adding Fields

24



24.10




Choose the HTML controls to be added to the appletAdds necessary templates for controls

Tip: Let the wizard create all default controls so you don’t have

to add them manually.



24.11




Finish the form appletCreates required object definitions for the applet and controlsSets applet class to CSSFrame

24



24.12



Modify a Form Applet

Use Web Layout Editor to modify a form appletAdd, delete, and reposition controls

Drag and drop columns and controls



24.13



Modify a Control

Use Web Layout Editor to edit text and button controlsEdit control properties in Properties window

24



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

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.

Mode



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

Set these properties

24



24.16



Preview the Applet

Right-click and select Preview to see how the applet appears

Preview mode

Edit Web Layout mode



24.17



<swe:for-each startValue="1301" count =10

iteratorName="currentId">

<swe:control id="swe:currentId"

hintMapType="FormItem">

Form Applet Template

Determines the layout and presentation of the form appletSiebel Web Engine maps Web Template Item Identifiers to control IDs in the template

Many form applets can use the same template

24



24.18



Summary

This module showed you how to:Create a form applet using the Form Applet Wizard Modify an existing form appletDescribe the structure of a form applet Web template



24.19



Lab

In the lab you will:Modify a form applet

24



24.20


Understanding Business Components and Joins


25.1


Module 25: Understanding Business Components and Joins

25



25.2


Module 25: Understanding Business Components and Joins 2 of 20

Module Objectives

After completing this module you will be able to:Describe the structure of business components and joinsMap fields to columns in base, joined, and extension tablesCreate joins and join specifications to bring data in from a joined table

Why you need to knowEnables you to configure your company’s business logic



25.3



S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

Business Component

Represents a fundamental business entity in the user’s worldIs a logical grouping of data from one or more tablesConsists of single-value fields that reference a column in a table

S_STG

RO

W_ID

NA

ME

PHA

SE_C

D

STG

_OR

DE

R

Opportunity

Name Sales Stage Sales Stage PhaseDescription

S_OPTY_X

RO

W_ID

PAR

_RO

W_ID

AT

TR

IB_01

AT

TR

IB_09

AT

TR

IB_39

Decision Level


25



25.4



Business Component Properties

Table: Specifies the base tableClass: Specifies the C++ class used at run time for the business component

Determines the behavior of the business componentIs usually set to CSSBusComp

Certain business components have specialized classes which add extra processing specific to that business component

Base table C++ class



25.5



Base Table

Has columns that store the main fields for the business component

Fields built on base tables can be edited

S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

Base table

Opportunity

Name Sales Stage Sales Stage PhaseDescription Decision Level

25



25.6



Mapping a Field to a Column in a Base Table

Create a new Single Value Field definitionLeave the Join property blank

Select the column to store the dataColumn picklist shows fields from the base table

Set the field type

Columns from

S_OPTY



25.7



Type Property for Fields

Specifies the data type for the fieldMust correspond to the physical type of the associated columnConsists 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

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.

Foreign Key Fields

25



25.8



Additional Data for Business Components

Business components can include data from additional related (joined) tables

For display in appletsFor use in processing by the business component

Fields referencing columns in joined tables are read-only

S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

S_STG

RO

W_ID

NA

ME

PHA

SE_C

D

STG

_OR

DE

R

Opportunity

Name Sales Stage Sales Stage PhaseDescription

Base tableJoined table



25.9



Joined Tables

May provide one related row for each row in the base tableNot all rows in a base table are required to have a related row

Have a 1:M or 1:1 relationship with the base tableForeign key for the relationship is in the base table

S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

S_STG

RO

W_ID

NA

ME

PHA

SE_C

D

STG

_OR

DE

R

CU

RR

_STG

_ID

Base table Joined table

Joined tables may be thought of as providing look-up or reference data; data in joined tables is read-only.

Joined Tables

25



25.10



Join Definition

Specifies the joined table from which to retrieve dataDefaults the alias property to the name of the joined table

Must assign a different value to the alias for: A self-joinMultiple relationships with the joined table

Specifies the type of SQL join to use

Joined tableName of Join



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 tableOuter joins will affect performance

Do not set the flag if there always is a related row in the joined table

Use outer join

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.

Setting the Outer Join Flag

25



25.12



S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

S_STG

RO

W_ID

NA

ME

PHA

SE_C

D

STG

_OR

DE

R

CU

RR

_STG

_ID

Join Specification Definition

Specifies how to retrieve the related row from the joined tableBased on the foreign and primary keys used to relate the base and joined tables

Opportunity

Name Sales Stage IdDescription

Primary key

Foreign key



25.13



Mapping a Field to a Column in a Joined Table

Create the required join if it does not existCreate the single-value field

25



25.14



Create a Join

If the required join does not existVerify the relationship is 1:1 or M:1 Verify there is a foreign key column for the relationship in thebase tableCreate a field in the business component to reference the foreign key column Create the Join object definitionCreate the Join Specification object definition



25.15



Create the Single Value Field

Set the Join propertySelect the alias for the desired joinInspect the Join and Join Specification definitions to verify the desired table and foreign keys have been selected

Select the desired column in the joined tableThe column picklist shows the fields from the joined table

Set the appropriate type

Columns from S_STG

25



25.16



S_OPTY_X

RO

W_ID

PAR

_RO

W_ID

AT

TR

IB_01

AT

TR

IB_09

Extension Table

Provides additional columns to store business component data

S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

S_STG

RO

W_ID

NA

ME

PHA

SE_C

D

STG

_OR

DE

R

Opportunity

Name Decision Level Sales Stage PhaseBudgeted

AT

TR

IB_39

Base table Extension table Joined table



25.17



Implicit Joins

Fields on extension tables use implicit joinsAre 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 tableDo not appear as Join object definitionsAppear in the picklist for the Join property in a single value field

S_OPTY_X appears here

S_OPTY_X does not appear here

25



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 tableSelect an unused column that has the desired type

Column picklist shows columns from the selected extension tableSet the appropriate field typeFields on extension tables can be edited

Columns from S_OPTY_X

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.

Extension Tables



25.19



Summary

This module showed you how to:Describe the structure of business components and joinsMap fields to columns in base, joined, and extension tablesCreate joins and join specifications to bring data in from a joined table

25



25.20



Lab

In the lab you will:Examine how fields in a business component map to columns in a base and joined tableCreate a join to bring in data from another table

Business Components and Joins: Party Extension Tables


26.1


Module 26: Business Components and Joins: Party Extension Tables

26



26.2


Module 26: Business Components and Joins: Party Extension Tables 2 of 16

Module Objectives

After completing this module you will be able to:Map fields in party business components Create and use joins and join specifications to bring in data from party tables




26.3



Joins and Party Business Components

Require additional considerations for:Mapping fields in party business componentsBringing party data into a non-party business componentBringing party data into a party business component

Note: Party data refers to data stored in a S_PARTY extension table such as S_CONTACT or S_ORG_EXT

26



26.4



Mapping Fields in Party Business Components

Party business components:Have S_PARTY as the base tableBut store their main data in S_PARTY extension tables

Main fields are mapped using the implicit join for the extensiontable

S_PARTY

RO

W_ID

NA

ME

PAR

TY

_TY

PE_C

D

PAR

TY

_UID

S_CONTACT

RO

W_ID

FST_N

AM

E

LA

FST_N

AM

E

PAR

_RO

W_ID

BIR

TH

_DT

First Name Last Name Birth Date

Contact

Main columns uses the implicit join to S_CONTACT

The following tables are some of the extension tables for S_PARTY: S_BUS_CONTACTS_ORG_EXTS_POSTNS_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.

S_PARTY Extension Tables



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

Opportunity

Name Account Account LocationDescription

26



26.6



Join Definition

References the extension table storing the data of interest

S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

CU

RC

Y_C

D

S_ORG_EXT

RO

W_ID

NA

ME

LO

C

Opportunity

Name AccountDescription

S_PARTY extension table



26.7



Join Specification Definition

Source field (as before) references the relevant foreign key column to the joined tableDestination column must reference the PAR_ROW_ID column in the joined table 26



26.8



PAR_ROW_ID

Is referenced in the Join SpecificationIdentifies the primary key of the related account record

S_OPTY

RO

W_ID

NA

ME

DE

SC_T

EX

T

PR_D

EPT

_OU

_ID

S_ORG_EXT

RO

W_ID

NA

ME

LO

C

S_PARTY

RO

W_ID

NA

ME

PAR

TY

_TY

PE_C

D

PAR

TY

_UID

PAR

_RO

W_ID

Identifies primary key of the related account record

Opportunity

Name AccountDescription Account Id

Source field

Destination Column



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

Contact

Last Name Account Account LocationAccount Id

26



26.10



Join Definition

Do not use the implicit join for S_ORG_EXT that already existsBoth 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

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.

Implicit Joins



26.11



Mapping a Field to a Column in a Party Table

Create the required join if it does not existCreate the single value field

26



26.12



Creating a Join to a Party Table

Verify the relationship is 1:1 or M:1Identify the foreign key column for the desired relationship to the joined tableCreate, if necessary, a field in the business component to reference the foreign key columnCreate the Join

Assign an appropriate alias propertyCreate the Join Specification

Use PAR_ROW_ID for the destination column



26.13



Mapping a Field to a Column in a Party Table

Select the appropriate explicit joinDo not use the implicit join to the table

Select the desired column in the joined tableSet the appropriate type

Select the explicit join instead of

S_ORG_EXT

26



26.14



Considerations

Mapping fields in party business componentsUse the implicit join for the extension table

Bringing party data into a non-party business componentCreate the join specification based on PAR_ROW_ID

Bringing party data into a party business componentUse the appropriate explicit join



26.15



Summary

This module showed you how to:Map fields in party business components Create and use joins and join specifications to bring in data from party tables 26



26.16



Lab

In the lab you will:Examine mappings of fields to party tablesBring data in from a party table

Understanding Business Objects and Links


27.1


Module 27: Understanding Business Objects and Links

27



27.2


Module 27: Understanding Business Objects and Links 2 of 14

Module Objectives

After completing this module you will be able to:Describe the role of business objects and linksCreate links and business objects




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 masterOther business components are the children

Provide the foundation for views

Action

Account

Product Contact

AccountBusiness Object (BO)

Business Component

(BC)

Master BC provides focus for BO


27



27.4



Business Object Definition

Specifies the business objectIs usually named for the master business component

Action

Account

Product Contact

Account



27.5



Business Object Component Definition

Specifies that a business component is to be included in the business objectLink property specifies the link definition that relates the parent and child business components

Parent BC

Child BCs

27



27.6



Link Definition

Specifies which records to retrieve from the child business component

Supports master-detail viewsSpecifies the foreign keys to populate when new child records are createdUsed with both 1:M and M:M relation between parent and child data

Action

Account

Product Contact

Account

Links



27.7



1:M Link

Used for 1:M relationship betweenparent and child business components

Foreign key (FK) for the relationship is in the child table

FK field in child BC

PK field in parent BC

(defaults to Id)

Defaults to parent BC/child BC

27



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 deletedClear: Does not delete but clears, the foreign key columnNone: 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?



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

Intersection table with FK columns

27



27.10



Creating Business Objects

Create a Business Object definition for the new business objectAdd the master business component

Create a Business Object Component definition Leave the Link property blank

Add the child business componentsCreate the link for the master and child business componentsCreate a new Business Object Component definition for the childSet the 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.

Link Property



27.11



Grandchild Business Components

Business objects may include grandchild business componentsUsed in parent-child-grandchild views

Child activities for selected activity plan

Activity Plan Action BC

Activity Plan BC

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.

Grandchild View

27



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

Child/grandchild BC

Parent/child



27.13



Summary

This module showed you how to:Describe the role of business objects and linksCreate links and business objects

27



27.14



Lab

In the lab you will:Create a new business component and linkAdd the new business component to an existing business objectCreate new applets and a viewAdd the new view to an existing screen

Configuring Business Components and Fields


28.1


Module 28: Configuring Business Components and Fields

28



28.2


Module 28: Configuring Business Components and Fields 2 of 24

Module Objectives

After completing this module you will be able to:Edit business component properties to capture business logicEdit field properties to capture business logic

Why you need to knowEditing the properties of business components and fields helps you to more accurately and fully capture your business logic



28.3



Business Components Properties

Change the properties of business components to capture business logicCommonly used properties include

Editing propertiesNo DeleteNo InsertNo MergeNo Update

Owner DeleteSearch SpecificationSort Specification

Object Types ReferenceReference

28



28.4



Properties for Editing

Set the editing properties at the business component level to prevent deleting, inserting, merging, and updating of records inall 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

If TRUE, users cannot change existing records.No Update

If TRUE, users cannot merge records.No Merge

If TRUE, users cannot add new records.No Insert

If TRUE, once a record is created and committed, users cannot delete it. No Delete



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 levelYou can also protect individual fields

Example: Users can generally edit their personal contactsOn the Contact Form ReadOnly Applet, they can not edit these

28



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



28.7



Search Specification Property

Specifies records to be retrieved by the business componentTypically 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



28.8



Search Specification Expression

Consists of field names, constants, functions, logical operators, and comparison operatorsExample: 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 [ ]

Logical Operator

Operator

Function

Must match exactly



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 specificationsPredefined queries also contribute to the WHERE clause

28



28.10



Search Specifications Continued

Example: Home page “My Accounts” list searches for records where

The organization is not an external organizationThe record has been updated in last 30 daysThe current user is the record’s owner



28.11



Sort Specification Property

Determines the sort order of the retrieved recordsUse (DESC) or (DESCENDING) to sort that field in reverse order

Example: Contacts are sorted by name

Field Name or Names, no [ ]

Must match exactly

Comma separated 28



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 thesame order

Avoid using a sort specification that references columns in different tables because indexes refer to one table only



28.13



Field Properties

Customize fields by editing property valuesSetting field properties at the business component level sets them across all applets

28



28.14



Required Property

Set the Required property to TRUE to prevent user from leaving field blank

Attempting to save a record without a value in a required field results in a warning message

Example: Contacts require last names

Attempting to save without a last name

causes an error message

Required fields in forms are marked with asterisks (*)



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



28.16



Validation Property

Create a Validation property to ensure that field data is validRule 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



28.17



Validation Property Continued

Is expressed as a combination of logical operators, constants, field names, and predefined functionsCan refer only to business component fields in the same record

Constant

Operator

Field name

Logical Operator

28



28.18



Pre Default Values for Fields

Automatically assigns a value to a field for a new recordUser can modify the field if it is displayed and not set to ReadOnly

Example: Income Currency Code for a new Contact is set to a system default currency code

Constant

System value

Inherit from parent (in this case, from the Account to

which this Contact belongs)



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 databaseExample: If the user does not designate a contact as personal, the system assumes it is not

28



28.20



Calculated Fields

Derive their value from the values in other fields of the business componentCannot be stored in the database

So there is no associated columnRequire setting the Calculated property to TRUE (shown as checkmark)

Blank



28.21



Calculated Value Property

Is an expression built from:Field names in the same business componentField names from the parent business component

Current business component must the child in a detail viewStandard functionsString, numeric, and logical operators

System functions


28



28.22



Restrictions on Calculated Fields

Calculated fields are read-onlySystem does not validate values of calculated fieldsSorting on calculated fields is not supportedQuerying on calculated fields is supported

Performance depends upon whether the functions in the query expression can be incorporated into the SQL statement



28.23



Summary

This module showed you how to:Edit business component properties to capture business logicEdit field properties to capture business logic

28



28.24



Lab

In the lab you will:Incorporate business logic into the application by configuring properties of business components and fields

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



29.2


Module 29: Creating a New BC Using the Standard 1:M Extension Table 2 of 15

Module Objectives

After completing this module you will be able to:Describe the structure of a 1:M extension tableCreate a new business component (BC) using the 1:M extension tableAdd the business component to a business object

Why you need to knowEnables you to incorporate additional business entities that do not correspond to business components in a standard Siebel applicationEnables you to tailor your business logic



29.3



Business Problem

Siebel business components capture most commonly-used business entities, but they do not cover every possibilityExample: Sales organizations might record personal data about contacts such as:

What colleges the contact attendedName of college, years attended, major field of study, sports played, honors received, …

The contact’s favorite restaurantsName and location, price range, type of cuisine, and so on

To capture this kind of information requires:Multiple fields to capture the details1:M relationship to the parent entity

Siebel Tools Reference Object Types Reference

Reference

29



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 repositoryIs 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 SystemsExample: Create College and Restaurant business components for sales organization

Colleges AttendedColleges Attended FavoriteFavoriteRestaurantsRestaurantsContact



29.5



Standard 1:M Extension Tables

Predefined in the repository for many business componentsHas 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



29.6



Multiple Business Components

You can use one _XM table to map multiple user-defined child business componentsEach business component has a unique TYPE value

Stored in the TYPE column of the _XM tableEach business component retrieves only those rows with its TYPE value

S_CONTACT_XMR

OW

_ID

NA

ME

TY

PE

PAR

_RO

W_ID

Colleges Attended

FavoriteRestaurants

Type = College

Type = Restaurant



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 recordCombination 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



29.8



Create New Business Component

Create a business component (BC) to represent the 1:M extension table

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

Set Class property to CSSBusComp

Set Table property to name of the 1:M extension table

Select the appropriate project



29.9



Create Fields for Business Component

Add fields that map toTYPE column

Set Predefault Value property to value used in the BC search specification

PAR_ROW_IDNAME

Create additional fields for any other required dataChoose an ATTRIB column with the right type and length

29



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

XYZ Restaurant

Contact



29.11



Create the Link

Create a new 1:M link

29



29.12



Add Business Component to Business Object

Create a new Business Object Component definition for the childSet the Link property



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 thevalue

Applet Wizard

29



29.14



Summary

This module showed you how to:Describe the structure of a 1:M extension tableCreate a new business component (BC) using the 1:M extension tableAdd the business component to a business object



29.15



Lab

In the lab you will:Create new business componentsCreate the links, applets, and views needed to display the new business components

29



29.16


Configuring Navigation


30.1


Module 30: Configuring Navigation

30



30.2


Module 30: Configuring Navigation 2 of 23

Module Objectives

After completing this module you will be able to:Configure drilldown to a related viewEnable the thread barConfigure toggle applets

Why you need to knowEnables you to add drilldowns and toggles to assist users in navigatingEnables you to activate the thread bar to assist users



30.3



Navigation Using Drilldown

You can configure fields in a list for drilldownWhen the user clicks the field, the application navigates to another view

You can configure drilldown as static or dynamicStatic: 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

Siebel Tools ReferenceObject Types Reference

Reference

30



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



30.5



Configuring Drilldown

Create a new drilldown objectSet the Hyperlink Field and View properties to enable static drilldown

Specifies BC field the drilldown column maps to

Specifies the target view

30



30.6



Static Drilldown: Different Business Component

Drill down to another view, changing the business component context

Related account record in Account

Detail - Contacts view

Account field of contact record in Visible Contacts List View



30.7



Configuring Drilldown to Different Business Component

Create a new drilldown object for the appletSet Hyperlink field and View properties as beforeSet 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)

30



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 ofthe list or form



30.9



Matching Conditions

Identify one or matching conditions to trigger drilling down to a specific target view

Type = Hotel ====> Expense Hotel List ViewType = Mileage ====> Expense Item Mileage View

Determine the order to check the matching conditionsConditions can involve different fieldsMultiple matches could occur for a given record

30



30.10



Create the drilldown objects for each viewCreate a dynamic drilldown destination definition for each condition

Configuring Dynamic Drilldown

Go to view for this

drilldown object

Field to check

Value to check for

Order to check in



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 propertiesSet 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

30



30.12



Thread Bar

Tracks previous business object (view) and active recordUpdates whenever the user navigates to a different business object or active recordProvides hyperlinks to previous views

Allows user to backtrack easily

Hyperlink to prior active record in the thread


Reference



30.13



Thread Properties

Specifies the text that appears in the thread button

Thread Title property specifies prior business object in

hyperlink – if not entered, application uses Title property

Specifies the record to “remember” in the

hyperlink

Hyperlink to prior active record in the thread

30



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.swtFor 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



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 templateUsers can switch this applet with others by an applet toggle that you define on the applet

Select an applet from the toggle list

You define objects called applet toggles to switch between two or more different applets, called toggle applets.

Applet Toggles and Toggle Applets

30



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 templateNote: 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


Reference



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

30



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>



30.19



Dynamic Toggling

Determines the applet to appear in a view based on the value in a specific field in the displayed recordDoes not use a toggle list

User does not directly control navigation between applets

The contents of this field determine what applet

displays below

30



30.20



Dynamic Toggling Continued

Example: Changing the Type property of a pricing factor determines which one of several pricing factor detail applets appears



30.21



Configuring Dynamic Toggling

Create a child applet toggle for each possible appletSet the Auto Toggle Field, Auto Toggle Value, and Sequence propertiesChild applets must be based on same business component as parent

Set the parent applet as the default to display when all conditions fail

Value to check for

Order to check for matches

Field to check (may be a computed field

based on a field used in the applet)

30



30.22



Summary

This module showed you how to:Configure drilldown to a related viewEnable the thread barConfigure toggle applets



30.23



Lab

In the lab you will:Create and configure dynamic drilldownsEnable and configure thread supportExplore toggle applets

30



30.24


Extending the Database


31.1


Module 31: Extending the Database

31



31.2


Module 31: Extending the Database 2 of 23

Module Objectives

After completing this module you will be able to:Create extension columns in a tableCreate custom extension tables

Stand-alone table1:1 extension table1:M extension tableIntersection table

Why you need to knowEnables you to incorporate additional attributes and business entities into a Siebel application



31.3



Incorporating Additional Data

Your business requirements may includeAdding new fields to capture additional dataCreating new business components to capture additional business entities

Extending the Siebel database can satisfy these requirementsAdding one or more columns to an existing tableCreating new database tables to support new business components

31



31.4



Evaluate the Existing Database Tables

Prior to extending the Siebel database, consider using:Unused columns in an existing tableUnused Siebel-supplied business componentsExisting 1:M extension table



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 typeConsider possible upgrade conflicts in future releasesConsider performance impact of a join to the 1:1 extension table

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.

Joins

31



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 otherbusiness components



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

31



31.8



Using Siebel Tools to Extend the Database

Supports creating new:Extension columns on tablesStand-alone tables1:1 extension tables1:M extension tablesIntersection tables

Creates new object definitions for the database extensionInvokes wizard to build new tables

Makes the corresponding physical database changesDevelopers do not create, use, or maintain SQL scripts

Siebel Tools for Siebel MidMarket supports creating only custom extension columns and 1:1 extension tables.

Mid-Market Technical Difference




31.9




Changes database schema and requires propagating changes to:

Other developers during developmentMobile 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 tablesSpecify how data for these extension columns and tables are to be routed to remote users (Dock Objects)

31



31.10



Creating a Custom Extension Column

Make logical changes to the data layerCheck out the appropriate projectSelect table to be extendedCreate a new column record with the desired properties

Name automatically prefixed with X_



31.11



Applying Changes

Click Apply to make the physical database changesAll database schema changes are made by Siebel ToolsNo separate SQL scripts need to be created or maintainedChanges 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

31



31.12



Propagating Changes

Propagate changes to other developersCheck project into the serverApply database changes to the serverCompile and test on the serverHave other developers check out project and apply changes locallyAlternatively re-extract developers and have them get all projects

Server Machine DeveloperWorkstation

DeveloperWorkstation

DeveloperWorkstation

Check in Check out



31.13



Creating a New Table

Use the Table wizard to create a new tableSelect File New Object Table

Table name starts with CX_

Select type of table to create

Select a locked project

A table name must start with CX_ and cannot exceed 15 characters.Table Name

31



31.14



Creating a Stand-Alone Table

Table wizard creates a stand-alone table with:Seven system columnsType of Data(Public)



31.15



Creating a 1:1 Extension Table

Select a base tableChoice restricted to type Data(Public)Multiple extension tables relate directly to base table and not to each other

S_PROD_INT

RO

W_ID

NA

ME

PAR

T_N

UM

UO

M_C

D

CX_PROD_INT_X

RO

W_ID

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.

Extension Tables

31



31.16



Creating a 1:1 Extension Table Continued

Table wizard creates an extension table with:Seven system columnsPAR_ROW_ID column as foreign key column to base tableP1 index on ROW_IDU1 index on PAR_ROW_ID and CONFLICT_ID

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.

Indexes



31.17



Creating a 1:M Extension Table

Select a parent tableChoice restricted to type Data(Public)

31



31.18



Creating a 1:M Extension Table Continued

Table wizard creates an 1:M extension table with:Seven system columnsPAR_ROW_ID column as foreign key column to base tableTYPE and NAME columnsType of Data(Public)P1 index on ROW_IDU1 index on PAR_ROW_ID, TYPE, NAME, and CONFLICT_IDM1 index on TYPE and NAME

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.

Indexes



31.19



Creating an Intersection Table

Select both parent tablesChoices restricted to type Data(Public)

Specify the foreign key column name for each parent table

31



31.20



Creating an Intersection Table Continued

Table wizard creates an intersection table with:Seven system columnsTwo foreign key columns as specifiedType of Data(Intersection)P1 index on ROW_IDU1 index on two foreign key columns, Type, and CONFLICT_IDF1 index on foreign key to second parent table

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.

Indexes



31.21



Apply and Propagate Database Changes

Click Apply to make the physical database changesCompile relevant projects Test changes locally before checking projects into serverCheck project into the serverCompile and test on server before propagating to other developers and users

31



31.22



Summary

This module showed you how to:Create extension columns in a tableCreate custom extension tables

Stand-alone table1:1 extension table1:M extension tableIntersection table



31.23



Lab

In the lab you will:Create a custom extension column on a table

31



31.24


Configuring Picklists


32.1


Module 32: Configuring Picklists

32



32.2


Module 32: Configuring Picklists 2 of 28

Module Objectives

After completing this module you will be able to:Describe the differences between drop-down list and picklistsAdminister a list of valuesConfigure a drop-down listConfigure a picklist

Why you need to knowEnables you to add picklists to your Siebel application



32.3



Picklists

Allow users to populate one or more single value fields by selecting a value from a list

Enforces business rules and policesMakes data entry fasterReduces errors

Can be eitherStaticDynamic

32



32.4



Picklist Terms

In Siebel applications picklists:Are associated with a field in the originating business componentDraw values from a pick business component

Account: Pick Business Component

Opportunity: Originating Business Component




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 selectionCopies the selected value into destination field

No link to the original picklist dataCan be bounded or unbounded

Bounded picklist forces users to enter only a value in the picklistUnbounded picklist permits users to enter any value into the field

Drop-down list

32



32.6



The S_LST_OF_VAL Table

Holds picklist values for all static picklistsExists in the application databaseHas 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



32.7



Administering a Picklist

Use Site Map Application Administration List of Values Explorerto administer static picklist data

Select an existing picklist or create a new picklist type in the List of Values - Types appletExpand the type and select the child Values folderEdit the picklist values in the List of Values applet

Don’t change names of Siebel-supplied values

Ok to set inactive

Applications Administration GuideReference

32



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



32.9



Creating a Static Picklist

Create object definitions to:1. Define the static picklist2. Specify the field to be populated by picklist3. Specify mapping between picklist and the originating business

component field4. Enable the user to invoke the picklist

Can possibly use an existing static picklist

32



32.10



1. Define the Static Picklist

Create a Pick List object definitionSet Business Component property to PickList Generic Set Type Field property to TypeSet Type Value property to picklist name in S_LST_OF_VALSet Bounded property to TRUE for bounded picklists



32.11



2. Specify the Field to be Populated

Select the Single Value Field to be populatedSet the PickList property to the name of the static picklist

32



32.12



3. Specify Mapping

Create a SVF Pick Map definitionSet Field property to the field to be populatedSet 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)



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 appletsSet the Runtime property to TRUE

A drop-down arrow will appear as a cue

Runtime set to TRUE

32



32.14



Drop-Down

Is used to display values for a static picklistIs auto-generated at run time

Drop-down



32.15



Pick List Wizard

Use the Pick List Wizard to create a new static picklistSelect the originating business component and fieldSelect an existing picklist or create a new one

Wizard adds the new picklist values to the S_LST_OF_VAL tableSet Runtime property on list columns or controls to TRUE to enable users to invoke the picklist

32



32.16



Dynamic Picklist

Draws values from a business component with records edited by users

Values displayed in picklist change during run timeIs used to update joined fieldsCopies foreign key reference to the selected value into destination field

Reflects the current data in the database

Displays values

queried from the Account

BC



32.17



Creating a Dynamic Picklist

Create object definitions to:1. Define the dynamic picklist2. Associate the picklist with a field3. Specify mapping between the pick BC and and originating BC

fields4. Identify an existing pick applet (or create a new one) to display

the pick data5. Enable the user to invoke the picklistCan possibly use an existing picklist and pick applet

32



32.18



1. Define the Dynamic Picklist

Create a Pick List object definitionSet the Business Component property to the name of the pick business component

Determines whether users can add or delete records through picklist

Pick business component

Leave blank for dynamic picklists



32.19



2. Associate the Picklist with a Field

Select the single value field to associate the picklistDetermined by the list column or control in applet

Set the Picklist property to name of dynamic picklist

Originating BC

32



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 appletMap 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



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 componentVerify that applet displays enough list columns to allow user todistinguish the desired record

32



32.22



4. Identify or Create a Pick Applet Continued

If a suitable pick applet does not exist, create a new oneCopy an existing pick applet

Copies all controls required for pick appletSet the Business Component property to reference the pick business component if requiredEdit list columns as required

Pick applet controls



32.23



5. Enable User to Invoke the Picklist

Identify the list column or control that references the field with the picklistSet the Runtime property to TRUESet the Pick Applet property to the corresponding pick applet

Runtime set to TRUE

32



32.24



Pick List Wizard

Use the Pick List Wizard to create a new dynamic picklistSelect the originating business component and fieldSelect an existing picklist or create a new one

Indicate the pick business component if a new listWizard can build new pick applet if desired



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



32.26



Constraining a Picklist

Create a pick map definition for each field that must matchSet the Constrain property to TRUE for each of the matching fields

Filters the pick business component records for matchesDoes not copy values for the field

Constrain to return only values with matches



32.27



Summary

This module showed you how to:Describe the differences between drop-down list and picklistsAdminister a list of valuesConfigure a drop-down listConfigure a picklist

32



32.28



Lab

In the lab you will:Create a new static picklistCreate a new dynamic picklist

Configuring Multi-Value Groups


33.1


Module 33: Configuring Multi-Value Groups

33



33.2


Module 33: Configuring Multi-Value Groups 2 of 27

Module Objectives

After completing this module you will be able to:Describe multi-value groups and their benefitsUse Siebel Tools to configure a multi-value field and multi-value linkUse Siebel Tools to configure a multi-value group so users may select one or more related child records

Why you need to knowEnables you to incorporate child data directly in an applet

More child data can be available within a viewMore effective use of screen space

Understanding how to configure primaries for multi-value groups improves performance



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 recordsMulti-value group applet opens on demand to display all child records

Parent applet

MVG Applet

Select button invokes the MVG applet


33



33.4



Multi-Value Group Continued

Is an alternative to a detail view for managing parent and related child records

Makes effective use of spaceDoes not require dedicated space on a view

Allows for multiple sets for detail records to be available from a single view

Business Address

MVG

Organization MVG

Industry MVG

Territory MVGPosition

MVG

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.

Multi-Value Group



33.5




Allows users to access child records for multiple parent recordsusing a single view

Business Address

MVG

Industry MVG

Territory MVG

33



33.6




Allows for creating queries that include values for fields in both parent and child records

Query on Organization

Query on Industry

Query on Address

Query on Team

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.

MVG Queries



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

S_ORG_EXTRO

W_ID

NA

ME

LO

C

EM

P_CO

UN

T

Business Address

Child business component

AccountName Location City

City Street Address

Parent business component

Single-value field

Multi-value field

33



33.8



Link

Must exist between parent and child business components in the MVG

Specifies how child records are related to parent records

Business Address

AccountName Location City

City Street Address





33.9



Creating a Multi-Value Group

Create object definitions to:1. Specify the multi-value link in the parent business component2. Add multi-value fields to the the parent business component3. Identify an existing MVG applet (or create a new one) to display

the child records4. Enable user to invoke the MVG applet5. Enable primaries to improve performance

33



33.10



1. Specify the Multi-Value Link

Create a Multi-Value Link object definitionChild object definition of business component that specifies howto retrieve the records for a multi-value fieldBased on an existing link definition that specifies how the parent and child business components are related

Set destination business component

Set destination link



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

Fields in child BC

Multi-value link

33



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 componentVerify that applet displays enough list columns to allow user todistinguish the desired record

Can display more columns than are displayed on the parent applet

There is no requirement that the MVG applet display only those multi-value fields that are displayed on the parent applet. This allows an MVG applet to be used in other MVGs throughout the application.

MVG Applet



33.13



3. Identify or Create an MVG Applet Continued

If a suitable MVG applet does not exist, create a new oneCopy an existing MVG applet

Copies all controls required for MVG appletSet the Business Component property to reference the child business componentEdit list columns as required

Pick applet controls

33



33.14



4. Enable User to Invoke the MVG Applet

Identify the list column or control that references the multi-value fieldSet the MVG Applet property to the corresponding MVG appletSet Runtime property to TRUE

Set MVG Applet

Set Runtime TRUE

Field control is on

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.

Setting Runtime to TRUE



33.15



Multi-Value Groups for M:M Relationships

MVGs can be built on M:M relationships as wellExample: Industry multi-value field in Account based on Account Industry M:M relationship

Industry


AccountName Location Industry

Name SIC Code


Single-value field

Multi-value fieldIndustry

MVG Applet

33



33.16



Configuring MVGs for M:M Relationships

Create object definitions required for 1:M MVGsSpecify an associate applet for the MVG applet

Allows users to select other child records to add to the MVG

Invokes associate applet



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 appletForm applet with 5 MVGs requires 6 queries

1 query to populate parent single-value fields5 additional queries (1 per MVG) to populate the MVGs

Business Address

MVG

Organization MVG

Industry MVG

Territory MVGPosition

MVG

33



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 appletRequires 21 queries (3 per parent record) to populate the MVFs

Business Address

MVG

Industry MVG

Territory MVG



33.19



Primary for a MVG

A primary refers to a designated child recordTo 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 recordAllows a single query using a SQL join to retrieve the parent and primary child record for display in the parent applet

Business Address

AccountName Location Street Address

Id City

Primary Address Id

Add a foreign key field to track the primary address for account

Street Address

33



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

Multiple queries are required to retrieve all the child records when the user invokes the MVG applet.

Multiple Queries



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 parentSelect the column with the desired Foreign Key Table (main tablefor child)

S_ORG_EXTRO

W_ID

NA

ME

LO

C

PR_A

DD

R_ID

S_ADDR_ORGRO

W_ID

AD

DR

CIT

Y

OU

_ID

Regular foreign keyPrimary foreign key

33



33.22



5. Enable Primaries for Performance

Add a primary key field in the parent business component to reference the primary foreign key columnSet the Primary Id Field and Use Primary Join properties in the MVL



33.23



Setting the Primary Record

Set the Auto Primary property in the MVL to DefaultWill 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

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.

SSA Primary Field

33



33.24



Creating a New MVG

Verify that a link between the parent and child business components existsUse the MVG wizard to construct the MVL and the MVFs

Select the link to be used in the MVFSet the Primary Id field if desiredSelect one or more fields in the child BC and create MVFs

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.

MVG Wizard



33.25



Displaying MVGs

To display the child recordsUse an existing MVG applet for the child business componentCopy an existing MVG applet and edit as requiredCreate a new applet using the MVG Applet wizard

Modify the parent applet to display the new MVFsSet Runtime TRUE for new list columns or controlsSet the MVG Applet property

MVF Wizard will invoke automatically

33



33.26



Summary

This module showed you how to:Describe multi-value groups and their benefitsUse Siebel Tools to configure a multi-value field and multi-value linkUse Siebel Tools to configure a multi-value group so users may select one or more related child records



33.27



Lab

In the lab you will:Create a new MVGCreate a MVG applet to display the MVG

33



33.28


Configuring Access Control


34.1


Module 34: Configuring Access Control

34



34.2


Module 34: Configuring Access Control 2 of 20

Module Objectives

After completing this module you will be able to:Determine the access control mechanism for a business componentConfigure views to control access to data based on

PersonPositionOrganization

Why you need to knowEnsures that your configured application displays the appropriate set of records to each of your usersEnables you to configure views that allow designated users to see additional data required to do their jobs



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

Authentication and Access Control Administration GuideReference

34



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 user’s:OrganizationPositionUser IDMembership in access groups for catalogs and categories

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.

Access Groups

User ID most often refers to the user’s LOGIN. However it could refer to another field that describes a user.

User ID



34.5



BusComp View Mode Definition

Specifies that business component is subject to access controlOwner Type property identifies the access control mechanism

Access control based on User ID

Object Types ReferenceReference

34



34.6



Visibility Field

Value in Visibility FieldIndicates that a business component record can be associated with one and only one record of the owner typeSpecifies 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



34.7



Visibility MVField and MVLink

Value in Visibility MVField and MVLinkIndicates that a business component record can be associated with one or more records of the owner typeSpecifies 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

34



34.8



Multiple Access Control Mechanisms

Business components may have multiple access mechanismsAllows records to be associated with different owner typesSupport multiple view modes

Records associated with single organization

Records associated with team of positions

Records associated with an individual



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 user’s organization, position, and user IDPermit additional access for

ManagersExecutivesAdministrators

34



34.10



View Modes Continued

View mode is configured by Setting the Visibility Applet property

Identifies the business componentSetting 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

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.

Context Views



34.11



My View

Displays all records for which user’s position is on the teamIs configured by

Setting the Visibility Applet property to identify an applet in the viewSetting the Visibility Applet Type property to Sales Rep

Defaults to this value if none set

34



34.12



Retrieving My View Records

Visibility Applet determines the business componentVisibility Applet Type determines the access mechanism used to restrict records

Looks for a BusComp View Mode with name Sales RepOwner type must be Position or Personal



34.13



Personal View

Displays all records for which user is the ownerIs configured by

Setting the Visibility Applet property to identify an applet in the viewSetting the Visibility Applet Type property to Personal

Looks for a BusComp View Mode with name PersonalOwner type must be Position or Personal

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.

Personal View

34



34.14



Manager View

Displays all records For which direct and indirect reports are the primary or ownerFor which the user is the primary or owner

Is configured bySetting the Visibility Applet property to identify an applet in the viewSetting the Visibility Applet Type property to Manager

Looks for a BusComp View Mode with name Sales RepOwner type must be Position or Personal

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.

Visibility Applet Type

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.

Manager View



34.15



All View

Displays all records (with a primary set) within a single organization

Any sort specification in the business component is ignoredIs configured by

Setting the Visibility Applet property to identify an applet in the viewSetting the Visibility Applet Type property to Organization

Looks for a BusComp View Mode with name OrganizationOwner type must be Organization

34



34.16



Across All Organizations View

Displays all records (with a primary set) across all organizations

Does not use a BusComp View Mode definitionIs configured by

Setting the Visibility Applet property to identify an applet in the viewSetting the Visibility Applet Type property to All



34.17



Administration View

Displays all the records in the database ignoring any visibilityconsiderationIs configured by setting the Admin Mode Flag

34



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



34.19



Summary

This module showed you how to:Determine the access control mechanism for a business componentConfigure views to control access to data based on

PersonPositionOrganization

34



34.20



Lab

In the lab you will:Explore visibility propertiesConfigure view visibility properties

Localizing an Application


35.1


Module 35: Localizing an Application

35



35.2


Module 35: Localizing an Application 2 of 24

Module Objectives

After completing this module you will be able to:Distinguish between localization and internationalization activitiesSet the Tools Language ModeEdit locale object definitions to localize an applicationEnable multilingual List of Values

Why you need to knowLocalization enables you to configure your application for deployment in a multinational environment



35.3



Global Deployment

Refers to meeting the needs of customers operating in a global environment by:

Supporting users in multiple regions using multiple languagesSupporting local business needs and regulations

35



35.4



Locale

Refers to a combination of language, region, and culture with a distinct set of:

Spelling conventionsFormats for

NumbersMoneyDate and time

Can be a: Single country (for example, Australia)Part of country (for example, French-speaking Canada)



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 applicationsA single set of binary files with locale-specific dependent DLL filesMultiple foreign currency supportLocale-specific string, number, and date handlingMultiple code page support including multibyte languagesBi-directional support

Global Deployment GuideReference

35



35.6



Presentation of the following data is determined by a regional settings parameter

Defaults to OS regional settingCan be set explicitly through an Object Manager component parameter

Regional Settings

Telephone numbers

Currency and numbersDate and time

The mobile client uses the OS regional setting for the client machine on which it is running.

Siebel Mobile 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 Web Client



35.7



Localization

Refers to the process of adapting a program to a specific localeSiebel applications can be localized by translating and resizingelements of the user interface

Dialog boxesButtonsError messagesReportsOnline Help

In addition, elements of the UI can be selectively displayed andrepositioned in localized versions of an application.

Localizing UI Elements

35



35.8



Support for Localization

Tools development environment supportsTools language modeLocalization of applets

Multiple languages in a single repositoryLocale-specific object definitions for variety of objects

Exporting and importing displayable strings for external translationConfiguration of multilingual List of Values

Tools Reference GuideReference



35.9



Tools Language Mode

Determines the locale-specific data that are: Displayed and edited in ToolsCompiled into the .srf fileTransferred during checkin and checkout

Is set by selecting View Options Language Settings

35



35.10



Locale Object Definitions

Store locale-specific information for the parent object definitionDisplay names for captionsPosition coordinates

Used instead of the parent (locale-independent) property values when:

Editing using the visual editors in language-override modeCompiling into the target language



35.11



Localizing Applets

Set the Tools Language ModeCreate the locale definitions for the applet to be translated

List Column Locale and Column Locale definitionsControl LocaleApplet Locale (applet title)

Invoke the Applet Web Editor and preview the applet to verify the translations

35



35.12



Language Specific Compiling

Produces a .srf file with text in following locale-specific UI elements

Strings are translatedControls and columns are resized and repositioned as required

View Tab

Menu text

Applet title

Column

Thread Bar

Screen Tab

Labels



35.13



Locale Management Utility

Assists localization by:Identifying untranslated stringsExporting strings to an external file for translationImporting a set of translated stringsSupporting development by incremental translation of recently modified strings

Select Tools Utilities Locale Management to invoke the utility.Locale Management Utility

35



35.14



List of Values Table

Stores data used to populate dropdown listsAdministered using Application Administration views

From OpportunityForm applet



35.15



Unilingual List of Values

Values in the List Of Values table can be translated into the target language

For display in dropdown listsFor storage in the database

Reasonable solution when all users speak the same target language

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 Manager’s language for display in drop-down listsSelected value is stored in the database as a language-independent codeValue retrieved from database is displayed in the Object Manager’s language

User sees the value in the Object Manager’s language



35.17



Enabling Multilingual List of Values

2. Configure columns for MLOVs2. Configure columns for MLOVs

3. Add translated values to LOV table3. Add translated values to LOV table

1. Determine the columns to enable1. Determine the columns to enable

4. Update existing data in database4. Update existing data in database

5. Compile new .srf file and deploy5. Compile new .srf file and deploy

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 boundedBounded property of Pick List definition must be TRUELOV 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 columnValues in rules need to be changed to Language Independent Code



35.19



2. Configure Columns for MLOVs

Open Siebel Tools and connect to the server databaseEditing 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 tabQuery for the LOV Type property for the MLOV picklistVerify that LOV Bounded property is TRUE for all target columns

Set the Translation Table Name to S_LST_OF_VAL

35



35.20



3. Add Translated Values to LOV Table

Edit the List of Values table to create the the language-independent code and the display values for each supported language

Start the client application and connect to the serverFor each LOV type that is to be made an MLOV type:

Create a new record for each display value for the LOV typeSet the language-independent code accordingly



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 codesSet the Multilingual column in the List of Values table to TRUEVerify that all target columns have been enabled

Consult the Siebel Global Deployment Guide for additional details

35



35.22



5. Compile a New .srf File and Deploy

Compile the modified table definitions to produce an updated .srf fileMigrate the new .srf file and the modified database to the serverStart up Object Managers for the new supported languagesExtract a new database for mobile users (if any)



35.23



Summary

This module showed you how to:Distinguish between localization and internationalization activitiesSet the Tools Language ModeEdit locale object definitions to localize an applicationEnable multilingual List of Values

35



35.24



Lab

In the lab you will:Explore how to localize an applet for a foreign localeIdentify columns that can be configured for MLOVs

Configuration Guidelines


36.1


Module 36: Configuration Guidelines

36



36.2


Module 36: Configuration Guidelines 2 of 19

Module Objectives

After completing this module you will be able to:Describe guidelines for configuring objectsIdentify performance issuesDescribe some recommended reviews

Why you need to knowHelps you to successfully implement a Siebel configuration projectIdentifies configuration decisions that have performance implications



36.3




This module reviews configuration guidelines for:Business componentsBusiness objectsAppletsViewsScreensApplications


36



36.4



Configuring Business Components

Modify an existing business component Easier to maintain and manageProvides an upgrade path

Copy an existing business component to:Include it twice in a business objectCreate 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

You will need to copy the Account business component (and cal it Sub Account) to create an Account – Sub Account view.

Copying a Business Component



36.5



Upgrade Ancestor

Set the Upgrade Ancestor property when copying a business component

Property must be set explicitly by developerEnsures that the copied business component is upgraded in the same way as the original business component

Set ancestor manually

Applets, Integration Objects, and Reports also have an Upgrade Ancestor property.

Upgrade Ancestor

36



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

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.

Specialized Classes



36.7



Configuring Business Objects

Create a new business object for a screen based on a new business componentLeave unused business objects as originally configured

Other definitions might reference them

36



36.8



Configuring Applets

Modify an existing applet for minor changesTitle or caption changesAdding or deleting a few fields

Set the Upgrade Ancestor property when copying appletsCreate a new applet to:

Display data for a new business componentMake a large number of changesCreate a read-only copy of the appletAdd the applet to a toggle cycle

Leave unused applets as originally configured



36.9



Configuring Views

Modify an existing view for minor changesTitle Applet layout

Create a new one to show a master-detail relationship that has no current viewAssociate a view with a single screen only

Threads track prior view but not the screenLeave unused view definitions as originally configured

36



36.10



Configuring Screens

Add a new screen whenever you create a new business objectModify existing screens to:

Change text in:View tabsShow drop-down listSite map

Add or remove views from a screenLeave unused screen definitions as originally configuredEdit responsibilities to hide unnecessary views from screens



36.11



Configuring Applications

Modify the existing application to:Add, remove, or reorder screen tabsChange the text in the screen tabs and site map

Edit responsibilities to hide unnecessary screens

36



36.12



General Configuration Recommendations

Never delete top-level object definitionsInactivate child object definitions to hide them when necessary

Validate object definitions prior to compiling themAdd comments to newly-created or modified object definitionsFollow recommended naming conventions



36.13



Naming Conventions

Give object definitions meaningful namesAvoid meaningless names such as "Account 2"

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 togetherReduces 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

36



36.14



Optimizing Performance

Use primaries for multi-value groups in list appletsEnsure that indexes exist to support sort and search specifications

Indexes cannot span multiple tablesAvoid sorting on un-indexed columns

Avoid calculated fields that are not supported by the RDBMSAvoid displaying totaled columns in list applets unless number of records will always be small

All records must be retrieved whenever entering a view

Ignoring these issues during configuration may result in significant performance problems.

Performance Implications



36.15



Additional Performance Considerations

Use primaries for multi-value fields in form appletsKeep the number of business components used in a view small

Includes those in applet toggle cyclesAvoid creating a large number of joins in business components

Includes implicit ones to extension tables and primaries to MVFsAvoid retrieving a large number of fields Avoid specifying outer joins when the relationship is mandatoryAvoid unnecessarily setting Force Active and Link Specification to TRUE

These situations may cause some performance problems but not as severe as those mentioned in the previous slide.

Performance Implications

36



36.16



Performance Tuning

Test the configured application against realistic and representative volumes of server and local dataFor slow performing views, spool the SQL and run it using database vendor tools to inspect query plan and index usageExecute typical user sort by and query by processing



36.17



Recommended Reviews

Design reviews during initial phases to verify proposedData mappingsDatabase extensionsConfiguration design

Configuration reviews at key phasesPilotRollout

Any review should include experts in the client subject matter as well as Siebel implementation technology

36



36.18



Summary

This module showed you how to:Describe guidelines for configuring objectsIdentify performance issuesDescribe some recommended reviews



36.19



Lab

In the lab you will:Complete the configuration by checking in all the modified definitions to the serverVerify the modified configuration by running the Siebel Web client on the server database

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.

36



36.20


siebel 7 essentials student guide vol2

Documents

siebel applications

siebel architecture

siebel software module

siebel application module

siebel client module

siebel tools

essentials siebel systems

siebel data model module