Configuring Siebel eBusiness Applications > Configuring Business Components >

Defining Business Component Properties

Following are descriptions for key properties for the Business Component object type. For a complete list and more detailed descriptions, see Object Types Reference.

• Class. The C++ class that implements the functionality of the business component. New stand-alone business components should have a class property of CSSBusComp or CSSBCBase. A drop-down list of values appears for setting this property.

  Siebel applications have a hierarchy of business component classes. CSSBusComp is at the top of the hierarchy. All other specialized business component classes (CSSBCOppty is an example) are derived from CSSBusComp.

  The functionality that is common between business components includes navigation (moving through a result set returned from the database), get or set field values in records, create and delete records, commit changes, undo/redo, bookmark, search, and sort.

  NOTE:  Do not change the Class property of preconfigured business components. When creating a business component by copying an existing one, do not change the class property.

  For more information about classes, see Siebel Developer's Reference.

• Name. (Required.) Must be unique among all business components in the repository. All references to the business component are done through its name.
• No Delete, No Insert, No Update properties. (Default is FALSE.) If set to TRUE, then you cannot do data manipulation operations.
• Search Specification. A conditional expression used to restrict the records retrieved.
• Sort Specification. A sort expression used to order the records returned.
• Table. (Required.) The name of the SQL table from which records are retrieved to populate the majority of fields in the business component. A list of tables appears in a picklist.

NOTE:  You can configure queries to be case sensitive or case insensitive by setting the Use Default Sensitivity property in the configuration (.cfg) file. Set the property to TRUE for case-sensitive queries. Set the property to FALSE for case-insensitive queries. However, you cannot configure fields of the type DTYPE_ID in this way because these fields always conduct case sensitive searches.