Table 3. Significant Customization Differences Between High Interactivity and Siebel Open UI
|
|
Renders the user interface as a collection of HTML frames. |
Renders the user interface as a collection of HTML div elements. |
Uses hard coding to determine styling, sizing, and positioning. Limits the customizations you make to this style. |
Uses CSS files to determine styling, sizing, and positioning. Allows you to fully modify the user interface. For example, you can create a custom user interface for a small, nondesktop environment. |
Siebel Web Engine can only render an entire view. |
Siebel Web Engine can render an entire view or only an individual applet. |
Uses ActiveX. Limits the customizations that you can make in the user interface. |
Uses JavaScript that allows you to fully customize how Siebel Open UI renders the user interface. Allows any modern, compliant Web browser to use Siebel Open UI. |
An applet can only reference a business component or a virtual business component. |
An applet can reference a business service, business component, or virtual business component. |
High interactivity and Siebel Open UI share the following customization capabilities:
- Metadata configuration for all user interface objects resides in the Siebel Repository.
- Layout configuration of user interface objects resides in SWE templates.
- Negligible server scripting capabilities exist to render custom configurations.
- Browser scripting for proxy objects resides in the client. For more information, see Browser Scripting Compatibility.
|