Reduce the number of objects
Reducing number of applets per view not as critical
Cut down on unnecessary duplication

Controls the read-only nature of BC, BC record, or BC Field based on value of another BC Field BC Read Only Field: current record read only Field Read Only Field: field specified by field name is read only Parent Read Only Field: BC read only

Sales Rep (see when user on Team)
Manager (see when direct/indirect reports are “primary” on team or when “primary”) All List (see all records with a primary position) Personal (see Contacts/Activities not Accounts and Opportunities)

Do:
Add/modify fields
Modify properties of existing BC
Add BC to BO
Add new relationships between BC
Create new BC & BO

Do not:
Rename them
Delete/inactivate BC or any of their fields
Delete/inactivate BO or BC within a BO

No Siebel-supplied definition exists to satisfy business requirement
An existing definition is in use
Need the same BC twice in the same BO
Wish to use a table already used by Siebel-supplied BC definition, but for entirely different purpose

Perform analysis, design and document
Create/modify object definitions in the Siebel Repository
Create SRF file for the application
Test the Siebel Enterprise application, including performance testing
Step through until design is fully implemented

Test custom extensions locally first
Prepare the server database
Apply the changes to the server database
Propagate the server changes to mobile users’ databases

Create BC to represent 1:M extension table
Set Search Spec to equal Pre Default Value “TYPE” field
Add fields to the new BC (ensure “NAME” and “TYPE”)
Create a link from BC to New BC and add the New BC to BO
Create applet to display data from new BC

Add a joined field in the parent BC (based on the “main” table). The join is implied and created automatically at runtime. Add a control or list column to an applet.

Standard extension tables - Predefined tables which support 1:1 or M:1 relationship. Part of the existing physical database. Custom extension tables and custom extension columns - New 1:1 tables, New columns that are added to new and existing tables.

View Details (for BCs and BOs only),
View Hierarchy (applicable to applets, applications, BCs, screens, and views), View Relationships (for BCs and Tables only)

Bookmarks (Adding a bookmark saves your ‘context’ as part of the location of the object definition.), Repository Search, Visualization Tools.

A responsibility is a class of users who require access to the same set of applicationfeatures. Controls what views are available when the employee logs in. Whereas Position, controls what records from the BCs are displayed in the view.

Prefix new object definition names with your company acronym to easily recognize your object definitions versus Siebel-supplied ones, Avoid using a numbering convention, Give new object definitions meaningful names

Assign individual developer or group the bottom-to-top development role for specific functional area, Assign developer or group to a specific architectural layer

The table name will be the main table + sequential number + _X, The PAR_ROW_ID column. stores the foreign key to the “main” table, There are eight predefined system columns. User data columns must be added as custom extension columns.

The table name will end with “_XM”, The PAR_ROW_ID column stores the foreign key to the “main” table, There are 47 predefined data columns of varying types, The “NAME” and “TYPE” columns are required, non-system columns.

The table name will end with “_X”, The PAR_ROW_ID column stores the foreign key to the “main” table, There are 47 predefined data columns of varying types.

Yes. But you must add extension columns to the appropriate interface table and map the extension columns to the base table.

Design the extension, Determine the placement of the data item in the user interface,
Determine how to load data into the new data item

Cannot be used as sort criteria, stored in columns and read only. Validation criteria on calculated fields is ignored. If SQL is used and performs a calculation, the value will be applied after the data is in the BC, but before displaying in the applet.

Double-quotes are used to enclose strings. Square brackets are used to enclose field names.

Add a primary key field on the parent BC. Set the Primary Id Field and Use Primary Join properties on the MVL.

Add a primary key field on the parent BC. Set the Primary Id Field and Use Primary Join properties on the MVL.

A primary is a FK on the parent-side that points to one “primary” record on the child-side of a 1:M link. A primary FK creates a 1:1 link between the parent and the child.