Configuring Siebel Business Applications > Configuring Special-Purpose Applets > Configuring a Tree Applet >

Overview of Configuring a Tree Applet

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. It displays hierarchically structured information in an expandable tree control. Siebel CRM displays the tree control in a frame on the left side of the applet. It 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 item includes any of the following objects. Siebel CRM displays these objects in a tree:

• Root
• Branch
• Leaf

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 control can include repository tree nodes and field values as elements in the tree. Siebel CRM displays the following:

• Name for a tree node
• Field values for tree items

Example of a Tree Applet

To view an example of a tree applet, do the following:

1. Open Siebel Call Center.
2. Click the Service screen tab, and then the Explorer link.

   Siebel CRM displays the SR Tree Applet in a frame on the left side of the interface and the Service Request List Applet in a frame on the right side of the interface.

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:

• These folders include Activities, Attachments, Change Requests, Solutions, and so on.
• If the user expands one of these child folders, then Siebel CRM displays a list of records that represent the corresponding business component.
• If the user expands the folder for a service request, and then expands the Activities folder beneath it, then Siebel CRM displays a list of records that constitute the set of activities for that service request. In the parent-child relationship between service requests and activities, these activity records are child records of the parent service request record that is expanded.
• The user can add or associate child records of various kinds to a parent record. For example, to associate a solution record from an association applet, the user can navigate down through the hierarchy to the Solutions folder, click the list applet, and then choose New Record from the applet menu. The product solution record becomes a detail record of the service request.

Relationships Between Business Components, Business Objects, and Tree Applets

A tree applet in an explorer view uses the set of parent-child relationships defined in the business object that Siebel CRM assigns to the view. A business object represents 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 configuration makes it possible to arrange the records of these business components hierarchically. For more information, see About Business Objects.

Figure 62 describes the relationships and objects that the Service Request business object contains.

Figure 62. Relationships and Objects in the Service Request Business Object

Figure 63 describes relationships and objects in the Service Request business object that Siebel CRM uses in the Service Request Explorer View.

Figure 63. Relationships and Objects in the Service Request Business Object That Siebel CRM Uses in the Service Request Explorer View

Table 49 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. 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. 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.

Objects of a Tree Applet

A tree is a child of an applet. It includes the child tree node. Each tree node defines one folder symbol. The tree object includes the following:

• Only provides a named reference point. A tree is similar to the List object type that Siebel CRM uses in a list applet because the tree works only as a reference for child objects.
• Always includes the text Tree in the Name property.

Table 50 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 That Siebel CRM Displays 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 the business component data that Siebel CRM displays.