Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Siebel Architecture (Basic Concepts) > Application Architecture Overview >

Logical User Interface Objects Layer

---

The Logical User Interface Objects layer consists of user interface object definitions that determine the visual interface that the user sees and interacts with in a Web browser. Data from business object definitions is represented to the user for viewing and modification by means of user interface object definitions. The Applet user interface object type (along with its child object types, particularly Applet Web Template) implements application units consisting of data controls, editable scrolling list tables, business graphics, and so on. Other user interface object types control toolbar and menu implementation, and the visual grouping of applets on screen.

The user interface defines the visual elements with which users interact—for example:

Layout of applets and views
Navigation
User interface controls (for example, buttons and check boxes)

The User Interface Objects Layer is insulated from the Data Objects Layer and the underlying database by the Business Objects Layer.

Various interface elements in a Siebel eBusiness Application are shown in Figure 8.

Figure 8. User Interface Objects in a Siebel eBusiness Application

Applets

An applet allows access to the data of a single business component for viewing, editing, and modifying fields in the business component.

An applet can be configured to allow data entry for a single record, to provide a scrolling table displaying multiple records, or to display business graphics or a navigation tree.

As shown in Figure 9, an applet consists of controls that map to fields in the underlying business component or simply support user interactions with the application, as is the case with buttons, for example:

A list column for a list applet (the top applet in Figure 9)
A text box for form applets (the bottom applet in Figure 9)

Figure 9. Fields in a Contact Applet Mapped to the Contact Business Component

All data in a given applet must be part of the business component that calls it.

Data in a given business component can be from a single table or multiple tables.

Business components can be reused in multiple applets. Several applets can reference the same business component definition. This is a benefit of having a single definition in the business component of the logical-to-physical relationship. Since the user interface (applet) layer is abstracted from the physical layer using the business component, there is no need to revisit the details of multiple tables in the physical layer for each of the applets that will display data for the same business function.

NOTE:  Do not confuse the applet construct in Siebel applications with Java applets. They are somewhat similar, but there are significant differences.

Views

A view presents one or more applets together at one time in a predefined visual arrangement and logical data relationship. Views are named, and a specific view is selected by name from a combination of menus or tab symbols.

A given view is mapped to a single business object, which determines the relationship between data displayed in two or more applets in the view. For example, the Opportunity Contacts Detail view is based on the Opportunity business object. Opportunity data is always displayed as the master or parent, and other types of data (for example, Contacts) are displayed as child records of a particular Opportunity. This allows users to see all the contacts associated with a single Opportunity.

Each applet in a view must map to a business component in that business object.

The business components that are required to be included in each view are:

For a view based on the business object, all business components to which applets in that view are mapped
Any business component whose data is exported in a report from a view based on the business object

NOTE:  The business component you include can be a child of another business object.

Screens

A screen is a collection of related views.

Screens are associated with major functional areas of the enterprise.

In general, all views in a screen map to the same business object—an exception is administration screens.

Applications

An application (for example, Siebel Sales) is a collection of screens.

NOTE:  Do not confuse Siebel applications with mobile Siebel application executables (that is, .exe files).

You can access Siebel applications through the Siebel Web client, dedicated Web client, mobile Web client, handheld, or wireless Web client.

Your organization may have licensed more than one Siebel application (for example, Siebel Sales and Siebel Call Center), to be used by different groups (for example, the sales team and the customer support team) within your organization.

In that situation you can install the Siebel Sales and Siebel Call Center as separate applications, or as a single application in which you establish different views for the relevant responsibilities of the two groups using them.

Logical UI Object Types

The object types for the logical UI object layer are described briefly below. For more detailed descriptions, see Data Objects Layer or Siebel Object Types Reference.

Application. An application is a collection of screens. The application is opened in a Web browser on the user's desktop by attaching to a specified URL. The screens are accessed from the tab bar and the Site Map, as defined in the application. Siebel eService is an example of an application. Each combination of screens that is appropriate to a specific class of users can be provided as an application.
Page Tab. A page tab object definition associates a screen to the page tab's parent application object definition and includes it as a tab in the tab bar.
Screen Menu Item. A screen menu item object definition associates a screen to the application and includes the screen as a menu item in the Site Map.
Screen. A screen is a logical collection of views. It is not a visual construct in itself; rather, it is a collection of views that the menu bar and view bar can display. The active screen is selected from the Site Map or the tab bar.
Screen View. A screen view object definition associates a view with the screen view's parent screen object definition. This is how views are included in screens.
View. A view is a collection of applets which appear on screen at the same time. A view can be thought of as a single window's worth of related data forms (applets). The Siebel application window displays one view at any one time. The user can select the current (active) view from the second-level navigation tab or from the Site Map. A view is associated with the data and relationships in a single business object.
Applet. An applet is a form, composed of controls, that occupies a portion of the Siebel application window. An applet can be configured to allow data entry, provide a scrolling table of business component records, or display business graphics, a navigation tree, or a similar user interface unit. It provides viewing, entry, modification, and navigation capabilities for data in one business component. Pop-up windows for multi-value groups and record selection are also implemented as applets.
Control. One control object definition corresponds to one data control in a form applet, such as a text box, check box or command button. A control is something in the applet with which the user can interact. A control usually either exposes data from one field in the business component, or invokes programming logic (in the case of a PushButton control).
List. List is a child object type of Applet. A list object definition specifies property values that pertain to the entire scrolling list table and provides a parent object definition for a set of list columns.
List Column. A list column object definition corresponds to one column in the scrolling list table in a list applet, and to one field in the business component.
Web Template, Applet Web Template, View Web Template. Identify external HTML (or other markup language) files that define the layout and Siebel Web Engine interactions for an applet or view.
Applet Web Template Item. Defines a control, list item, or special Web control in the Web implementation of an applet.
View Web Template Item. Defines the inclusion of an applet in the Web implementation of a view.

Bookshelf Home | Contents | Index | Search | PDF