| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Tools Reference > Special-Purpose Applets and Controls >
Tree Applets
A tree applet is used to create a view, called an explorer view, that allows the user to navigate hierarchically through a structured list of records of related business components. An example of a tree applet and explorer view in Siebel Service is the Service Requests applet in the Service Request Explorer view, shown in Figure 217.
This view (SR Explorer View) contains a tree applet (SR Tree Applet) in the left side, and one of various predefined list applets in the right side. The particular list applet that appears on the right depends on which node is selected in the tree on the left. For example, if the user double-clicks on the Change Requests folder in the tree hierarchy, the list applet on the right changes to display change requests records.
A tree applet in an explorer view is similar in operation to the Object Explorer and Object List Editor in Siebel Tools. The user may expand and collapse folders in the tree applet, and view the records in that folder in the list applet. The hierarchy displayed in the tree applet represents master-detail relationships between records of different business components.
For example, when the user expands a service request (document icon) by double-clicking, a set of folders appears hierarchically beneath it including Activities, Attachments, Change Requests, Solutions and so on. When the user expands one of these child folders, a list of records appears of the corresponding business component. If the user expands the folder for a service request, and then expands the Activities folder beneath it, the list of records displayed is the set of Activities for that service request. In the master-detail relationship between service requests and Activities, these Activity records are detail records of the master service request record that was expanded.
The user can also add or associate detail records of various kinds to particular master records. For example, the user could navigate through the hierarchy to the Solutions folder beneath a particular service request, click in the list applet, and select New Record from the applet-level menu to associate a solution record from an association applet. The product solution record would become a detail record of the service request.
A tree applet in an explorer view uses the set of master-detail relationships implemented in the business object assigned to the view. As described in Business Objects, a business object implements a business model or entity-relationship diagram, and specifies the set of master-detail relationships between the business components it includes. This makes it possible to arrange the records of these various business components hierarchically, which can be a very useful feature.
Figure 218 shows the full set of master-detail relationships in the Service Request business object.
The portion of the Service Request business object used in the Service Request Explorer view is shown in Figure 219.
The correspondence between business components in the Service Request business object and folder names in the tree applet is indicated in Table 59.
The tree applet and explorer view for service requests can be reconfigured to include additional business components. For example, Contacts, Customer Surveys, and Service Agreements folders could be added as child folders of Service Requests, and a Line Items folder could be added as a child of RMAs/Service Orders. However, only business components from the business object (Service Request in this case) can be added in an explorer view based on that business object. Furthermore, a business component can only be added as the immediate child folder of the business component that is its master in the business object. For example, you could add Order Entry Line Items as a child of RMAs/Service Orders, but not of Activities.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Tools Reference, Version 7.5, Rev. A Published: 18 April 2003 |
