Bookshelf Home | Contents | Index | PDF |
Configuring Siebel Business Applications > About Business Components, Fields, Joins, and Links > About Business Components > Guidelines for Creating a Business ComponentThis topic describes guidelines for creating a business component. For more information, see the following topics:
Guidelines for Naming a Business ComponentDo not use the parent entity in the name of a business component that represents child entities. For example, use ABC Subsegment instead of ABC Account Subsegment. Similarly, you can include only the name of the business component in an applet that references these child business components. For example, ABC Subsegment List Applet instead of ABC Account Subsegment List Applet. An exception to this requirement occurs if you must use multiple variations of the same business component or applet. A multiple variation might be necessary if Siebel CRM must display an entity as a top level applet and as a child applet on other views, and if these two applets are not the same applet. In this situation, you can place the name of the parent entity at the beginning of the name of the child applet. For example, the ABC Account Contact List Applet is a contact list that Siebel CRM displays as the child of an account. It uses the word Account to distinguish it from the predefined ABC Contact List Applet. Guidelines for Creating a Business Component That References a Specialized ClassIf you must create a new business component, then you must avoid copying a business component that references a specialized class unless you do the following:
For example, you can create a Locked Service Requests business component that displays only the service requests that are locked. To do this, you use a business component user property:
The underlying behavior of the new business component remains the same as the original business component. You must avoid copying a specialized business component to reproduce an isolated feature that is associated with that business component. If you set the Class property of a business component to CSSBCServiceRequest, then you must add the Abstract field to this business component. If you do not add this field, and if an applet references a business component that is a child of the business component that you add, then Siebel CRM might disable the New button in this applet. For more information, see Caution About Using Specialized Classes. Guidelines for Configuring How a Business Component Sorts RecordsIf you define the Sort Specification property of a business component, then use the following guidelines:
Guidelines for Modifying a Predefined Business Component That Siebel CRM Does Not UseIf you modify a predefined business component that Siebel CRM does not use, then use the following guidelines:
|
Configuring Siebel Business Applications | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |