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. Related TopicsFor more information, see the following topics:
Guidelines for Naming a Business ComponentFor a business component that represents child entities, do not use the parent entity in the name of the child. For example, ABC Subsegment instead of ABC Account Subsegment. Similarly, only include 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. The exception to this requirement occurs if you require multiple variations of the same business component or applet. A multiple variation might be necessary if you display a specific entity as a top level applet and as a child applet on other views, and if the two applets are not the same. In this situation, 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 displays as the child of an account. It requires the word Account to distinguish it from the predefined ABC Contact List Applet, which is a different applet. Guidelines for Creating a Business Component That References a Specialized ClassIf you must create a new business component, avoid copying a business component that references a specialized class, unless you do the following:
For example, create a Locked Service Requests business component that displays only those service requests that are locked. To do this, you use a business component user prop:
The underlying behavior of the new business component remains the same as the original business component. Avoid copying a specialized business component to reproduce an isolated feature that is associated with that business component. NOTE: If you set the Class property of a business component to CSSBCServiceRequest, then you must also 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 you add, then Siebel CRM might disable the New button in this applet. Guidelines for Determining 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 Is Not UsedIf you modify a predefined business component that is not used, then use the following guidelines:
|
Configuring Siebel Business Applications | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |