Scribd
Upload
21 views

28ESS - Configuring Business Components and Fields

This module discusses how to configure business components and fields in Siebel 7.7 to capture business logic. It covers editing properties of business components and fields to specify behaviors like restricting edits, default values, and validations. Calculated fields are also described, which derive their values from other fields but are not stored in the database. The objectives are to learn how to edit these properties to fully represent business needs.

Uploaded by

AkhamiePatrickOshioke
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
21 views

28ESS - Configuring Business Components and Fields

This module discusses how to configure business components and fields in Siebel 7.7 to capture business logic. It covers editing properties of business components and fields to specify behaviors like restricting edits, default values, and validations. Calculated fields are also described, which derive their values from other fields but are not stored in the database. The objectives are to learn how to edit these properties to fully represent business needs.

Uploaded by

AkhamiePatrickOshioke
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 27

Essentials (Siebel 7.

7)

Module 28: Configuring


Business Components and
Fields
Module Objectives

After completing this module you will be able to:


 Edit business component properties to capture business
logic
 Describe business component view modes
 Edit field properties to capture business logic
 Specify business component and field user properties to
extend their functionality

Why you need to know:


 Editing the properties of business components and fields
helps you to more accurately and fully capture your
business logic

Module 28: Configuring Business Components and Fields 2 of 27


Business Components and Declarative Configuration
 Business components will provide desired functional behavior
through the specification of properties
 Business component properties
 Business component field properties
 User properties
 These properties may be specified by using declarative
configuration
 Declarative configuration
 Creates and modifies object definitions (metadata) that define
Siebel applications
 Siebel Tools is a declarative configuration tool
 No need to modify source code or write SQL
 Usually provides better performance than scripting

Module 28: Configuring Business Components and Fields 3 of 27


Business Components Properties
 Capture business logic
 Include:
 Editing properties
 No Delete
 No Insert
 No Merge
 No Update
 Owner Delete
 Search Specification
 Sort Specification

Module 28: Configuring Business Components and Fields 4 of 27


Properties for Editing
 Set the editing properties at the business component level to
prevent deleting, inserting, merging, and updating of records in
all applets
 Example: To maintain record continuity, users cannot delete or
change price lists once they have been created

Module 28: Configuring Business Components and Fields 5 of 27


Properties for Editing Continued
 These properties also appear on applets
 Most restrictive settings are always used
 Set these properties to FALSE at the business component level so
that you can make exceptions at the applet level

Module 28: Configuring Business Components and Fields 6 of 27


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

Module 28: Configuring Business Components and Fields 7 of 27


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

Module 28: Configuring Business Components and Fields 8 of 27


Search Specification Expression
 May consist of field names, constants, functions, logical
operators, and comparison operators
 Example: For a given user, Contact(All) retrieves:
 All contacts where the Personal Contact flag is “N”
 All personal contacts belonging to the user

Field Name
in [ ] Operator

Logical Function
Operator

Must match
exactly

Module 28: Configuring Business Components and Fields 9 of 27


Search Specification Considerations
 These business component properties also appear on applets
 Search specifications are joined with an AND in business
components and applets in the generated SQL statement
 Predefined queries may also contribute to the WHERE clause
 Avoid mutually-exclusive search specifications

UI List Column
Layer Applet View Screen Application
or Control

Business Business Business


Layer Field
Component Object

Module 28: Configuring Business Components and Fields 10 of 27


Sort Specification Property
 Determines the sort order of the retrieved records
 Use (DESC) or (DESCENDING) to sort that field in reverse order
 Cannot be set at the applet level

Field Name or
Names, no [ ]

Comma-
separated

Must match
exactly

Module 28: Configuring Business Components and Fields 11 of 27


BusComp View Mode
 Is a child object type of business component that specifies the
business component is subject to Access Control
 Owner Type property identifies the Access Control mechanism
that limits records a user can access
 Business components may have multiple access mechanisms
 Allows records to be associated with different owner types
 Supports multiple view modes
 Example: Opportunities may be owned by Positions and
Organizations

Module 28: Configuring Business Components and Fields 12 of 27


Field Properties
 Customize fields by editing property values
 Setting field properties at the business component level sets
them across all applets

Module 28: Configuring Business Components and Fields 13 of 27


Business Component Field Properties

Required

Read Only

Validation

Pre Default Value

Post Default Value

Force Case

Module 28: Configuring Business Components and Fields 14 of 27


Structuring Slide for Concepts or Components

Calculated

Calculated Value

Module 28: Configuring Business Components and Fields 15 of 27


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

Example: Contacts
require last names

Attempting to save
without a last name
causes an error message

Required fields in
forms are marked
with asterisks (*)

Module 28: Configuring Business Components and Fields 16 of 27


Read Only Property
 Set the Read Only property to TRUE to prevent the user from
editing the value

Read-only on
all applets

Module 28: Configuring Business Components and Fields 17 of 27


Validation Property
 Create a Validation property to ensure that field data is valid
 Rule is checked when you save the record

Birth date must be


prior to the current date

Module 28: Configuring Business Components and Fields 18 of 27


Validation Property Continued
 Is expressed as a combination of logical operators, constants,
field names, and predefined functions
 Can refer only to business component fields in the same record

Constant Field name

Logical operator
Operator

Module 28: Configuring Business Components and Fields 19 of 27


Default Values for Fields
 Pre Default Value
 Automatically assigns a value to a field for a new record
 Post Default Value
 Assigns a value to a field, if not entered by the user, before the
record is inserted into the database
 Example: If the user does not designate a contact as personal,
the system assumes it is not

Module 28: Configuring Business Components and Fields 20 of 27


Force Case Property
 Defines the case for a field value
 Valid values are:
 UPPER
 LOWER
 FIRSTUPPER

Module 28: Configuring Business Components and Fields 21 of 27


Calculated Fields
 Derive their value from the values in other fields of the business
component
 Cannot be stored in the database; therefore, there is no
associated column
 Require setting the Calculated property to TRUE (shown as
check mark)

Column property
is empty because
calculated fields are not
stored in the database

Module 28: Configuring Business Components and Fields 22 of 27


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

Module 28: Configuring Business Components and Fields 23 of 27


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 have the child in a detail view
 Standard functions
 String, numeric, and logical operators

System functions

Module 28: Configuring Business Components and Fields 24 of 27


User Properties
 Are object definitions added as children to an applet, business
component, control, field, or list column
 Use to configure specialized behavior
 Beyond what is configured in the parent object definition's
properties
 Add conditional logic to User Property record, instead of
scripting
 Examples include Business Component:
 BC Read Only Field
 On Field Update Set

Module 28: Configuring Business Components and Fields 25 of 27


Summary

This module showed you how to:


 Edit business component properties to capture business
logic
 Describe business component view modes
 Edit field properties to capture business logic
 Specify business component and field user properties to
extend their functionality

Module 28: Configuring Business Components and Fields 26 of 27


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

Module 28: Configuring Business Components and Fields 27 of 27

You might also like