|Bookshelf Home | Contents | Index | PDF|
A tree applet is a type of applet that you can use to create an explorer view that allows the user to navigate hierarchically through a structured list of records of related business components. The tree applet presents hierarchically structured information in an expandable tree control. Siebel CRM displays the tree control in a frame on the left side of the applet. Siebel CRM displays detailed information for a chosen tree node in the details applet in a frame to the right. Separate vertical frames allow the user to scroll through the contents of the tree applet independently from the detail applet. This is important because the tree structure can grow very large in length and width.
A tree node is a repository tree node. The swe:node tag specifies the placeholder for a tree item. For more information, see About Siebel Tags.
A tree applet in an explorer view operates in a way that is similar to how the Object Explorer and Object List Editor operates in Siebel Tools. The user can expand and collapse folders in the tree applet and view the records in the folder in the list applet. The hierarchy in the tree applet represents a parent-child relationship between records of different business components.
For example, if the user expands a document tree in the Service Requests tree, such as the 1-49119-Claim-New Claim document, then Siebel CRM displays a set of folders that it positions hierarchically beneath the service request. Note the following:
A tree applet in an explorer view uses the set of parent-child relationships defined in the business object that are assigned to the view. A business object defines a business model or entity-relationship diagram and specifies the set of parent-child relationships with the business components that the business object references. This structure makes it possible to arrange the records of these business components hierarchically. For more information, see About Business Objects.
Figure 62 illustrates the relationships and objects in the Service Request business object.
Figure 63 illustrates relationships and objects in the Service Request business object that Siebel CRM uses in the Service Request Explorer View.
Table 46 describes the relationship between business components in the Service Request business object and folder names in the tree applet.
You can configure the tree applet and explorer view for service requests to include more business components. For example, you can add the Contacts, Customer Surveys, and Service Agreements folders as child folders of Service Requests. You can add a Line Items folder as a child of RMAs and Service Orders. However, you can only add business components from the business object in an explorer view that references the business object. In this example, that business object is Service Request. Also, you can only add a business component as the immediate child folder of the business component that is the parent of this business component in the business object. For example, you can add Order Entry Line Items as a child of RMAs and Service Orders. You cannot add Order Entry Line Items as a child of Activities.
Table 47 describes properties of an applet that implement a tree applet.
Siebel CRM does not support a search specification on a tree applet. For more information, see Options to Filter Data Displayed in an Applet.
A tree applet references an explorer view as a view web template item. A list applet does not reference an explorer view. If the user chooses a folder, then Siebel CRM determines the list applet dynamically. The folder in a tree applet represents a tree node. The Business Object property of the view determines which business component data Siebel CRM displays.
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|