09 cb cand_f

Siebel 2001 Configuration ©Accenture Configuring Business Components and Fields - 1

These training materials are confidential to Siebel. They may not be used to train anyone other than Accenture employees who have attended Siebel training.

If the materials are marked "Restricted Use Allowed" you may use the information to help clients who are evaluating vendors, one of which must be Siebel and you may use the information to help clients which are implementing Siebel.

If they are not so marked, then the information may only be used to help clients who are implementing Siebel.

In either case, you can not;(a) use the materials if you are involved developing or are likely to be involved in developing a product competitive to Siebel(b)use the materials for a client who is a competitor of Siebel; or(c) provide the materials to any third party, whether it is a client or otherwise.

If you are going to be discussing Siebel with a client and using these training materials as the basis of information you provide to the client, you must also make sure Accenture has a nondisclosure agreement in place with the client (as part of a Consulting Services Agreement or otherwise).


Please adjust volume to hear audio.Audio will play automatically for each slide upon advance.You may replay audio by clicking on the speaker icon in the upper right hand corner of each slide.


Configuring Business Components and Fields


Module Objectives

As a result of taking this module, you will be able to:

• Describe the necessary steps in configuring business components and Fields

• Demonstrate creating a New BC Using the Standard 1:M Extension Table


Business Component Properties

• Commonly used properties include:

Editing properties

•No Delete

•No Insert

•No Merge

•No Update

•Even administrators cannot edit records if these properties are set

Owner Delete

Search Specification

Sort Specification

• Change the properties of business components to capture business logic

Return to Knowledge Check


Properties for Editing

• Set these properties to FALSE at the business component level so that you can make exceptions at the applet level

If you want even one applet to have edit privileges, you must set FALSE at the business component level

You can also protect individual fields

• Example

Users can generally edit their personal contacts

On the Contact Form Read Only applet, they can not edit these


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


Search Specification Property

• Specifies records to be retrieved by the business component

Typically used when there are multiple business components on the same main table

• Example: The Personal Contact business component is distinguished from Contact by a search specification “Personal Contact” is a Boolean flag field


Search Specification Expression

• Comparison operators e.g.: [Revenue] > 5000

• String Constants e.g.: [Type] <> “COST LIST”

• Logical Operators e.g.: [Competitor] IS NOT NULL

• Field in a Search Specification must be enclosed in square brackets e.g.: [Conflict Id] = 0

• The LIKE operator, used for text string comparison expressions, can use wildcards e.g.: [Last Name] LIKE “Sm*”

• The Search Specification expression must be 255 characters or less.


Search Specification Expression - Example

• Example: For a given user, Contact(All) retrieves

All contacts where the Personal Contact flag is “N”

All personal contacts belonging to the user


Sort Specification Property

• Determines the sort order of the retrieved records

Use (DESC) or (DESCENDING) to sort that field in reverse order

• E.g.: Start Date (DECENDING)

• Example: Contacts are sorted by name


Sort Specification Performance Considerations

• To ensure good performance, check whether an index exists for the business component base table

Use the columns from the index as the sort specification, in the same order

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


Field Properties

• Customize fields by editing property values

• Setting field properties at the business component level sets them across all applets

Return to Knowledge Check


Required Property

• Set the Required property to True to prevent user from leaving field blank


Read Only Property

• Set the Read Only property to True to prevent user from editing the value


Validation Property

• Create a Validation property to ensure that field data is valid

Rule is checked when you save the record


Validation Expression

• Is expressed as a combination of:

Logical operators e.g.: >=0 AND <=100

Constants e.g.: >=0

Field names e.g.: [Asset Asset Number] <> 100

• Can refer only to business component fields in the same record


Pre Default Values for Fields

• Automatically assigns a value to a field for a new record

User can modify the field if it is displayed and not set to Read Only

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


Post Default Values for Fields

• Assigns a value to a field, if not entered by the user, before the record is inserted into the database

• Example: If the user does not designate a contact as personal, the system assumes it is not


Calculated Fields• Derive their value from the values in other fields of the business

component

• Cannot be stored in the database

So there is no associated column

• Require setting the Calculated property to TRUE (shown as checkmark)


Calculated Value Property

• Is an expression built from:

Field names in the same business component

Field names from the parent business component

• Current business component must be the child in a detail view

Standard functions

String, numeric, and logical operators


Restrictions on Calculated Fields

• Calculated fields are read-only

• System does not validate values of calculated fields

• Sorting on calculated fields is not supported

• Cannot sort calculated fields in columns

• Validation criteria is ignored

• Querying on calculated fields is supported

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


Modifying a Field - Example

Scenario:

We were asked to modify the Owned By Id field on the Service Request business component. They asked us to add the Creator Id field as a default value.



1. In Siebel Tools/Object Explorer, select Projects definition.

2. Make a query by the Service project and lock it.



3. In the Object Explorer, select Business Components definition.

4. In the Business Components applet, make a query by Service Request.

5. In the Object Explorer, expand the Business Components definition and select Single Value Field.



6. In the Single Value Field Applet, make a query by Owned By Id field.

7. Set Post Default Value = System: CreatorId (Do not include the equal sign, “=“).

8. Add the following Comment: “Your initials” added post default value “Today’s Date”


Testing your changes - Example

9. Compile your changes.

- Go to Tools/Compile Projects

- Add the Siebel Repository File: C:\Siebel7\Client\OBJECTS\ENU\siebel.srf

- Click Compile


Testing your changes - Example

9. Start the Siebel 7 Application from as SADMIN, sample database.

10. Select Service screen, My Service Requests view.

11. Add a new service request record. Leave the Owner Column in blank.

12. From the Applet Menu button select New Query then Run Query. A value for the Owner field will be added.


Lab Activity

• Now is your chance to practice some of the concepts we've just covered.

• Proceed to Lab 1 for this module.

• Once you have completed this section, resume viewing the presentation where you left off.


Activity Recap

Question Answer

Where can you find information about functions to be used as default values?

How do you disallow updates to a Business Component?

What do you have to do to see your changes in your application?

Now that you have completed Lab 1, you should be able to answer the questions below. Try to answer each question; the answer will pop up as you advance the slide.

Setting the No Delete, No Merge, and No Update properties to TRUE.

In Siebel Bookshelf, Tools Guide.

Compile the project making sure you are compiling to the Siebel repository file: appDrive/clients/OBJECTS/ENU/siebel.srf


Creating a New Business Component

• Siebel business components capture most commonly-used business entities, but they do not cover every possibility

• In order to capture a large amount of information, you can create new business components as children of an existing business component

Used to add entities specific to your organization that are not in the Siebel repository

Is an exception to the recommendation not to copy or modify existing business components

• You base these business components on standard 1:M extension tables supplied by Siebel Systems

• Example: Create College and Restaurant business components for sales organization


Standard 1:M Extension Tables

• Predefined in the repository for many business components

• Has name of main table appended with _XM


Multiple Business Components

• You can use one _XM table to map multiple user-defined child business components

• Each business component has a unique TYPE value

Stored in the TYPE column of the _XM table

• Each business component retrieves only those rows with its type value


User Key for _XM table• NAME, TYPE, and PAR_ROW_ID serve as a user key for the

_XM table

Must provide values for all 3 columns when creating a new record

Combination must be unique

• For business components with data that cannot be stored in a Varchar 100 column, you must still provide a unique value for NAME

Workaround is to store value of ROW_ID in NAME


Create New Business Component

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


Create fields for the Business Component

• Add fields that map to:

TYPE column

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

PAR_ROW_ID

NAME

• Create additional fields for any other required data

Choose an ATTRIB column with the right type and length


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


Create the Link

• Create a new 1:M link


Add Business Component to Business Object

• Create a new Business Object Component definition for the child

• Set the Link property


Displaying Data from the _XM Table

• Build applets and views as required to display data from the child business component

• Do not display the TYPE field to prevent users from changing the value


Summary

Now that you have completed this module, you shouldbe able to:

• Describe the necessary steps in configuring business components and Fields

• Demonstrate creating a New BC Using the Standard 1:M Extension Table


Knowledge Check

Question Answer

Describe the steps in configuring businesscomponents.

Describe the steps in configuring fields.

Change the properties of business components to capture business logic.

• Customize fields by editing property values.

• Setting field properties at the business component level sets them across all applets

Take this opportunity to check your knowledge of the concepts presented in this module. Try to answer the questions on the slide. The answer for each question will pop up as you advance the slide. Each answer may link back to the area within the presentation where that concept is presented. At the end of the section referenced you will find a ‘Return to Knowledge Check’ hyperlink, which will take you back to this slide.

09 cb cand_f

Technology