Siebel Open UI Features

For specific features, Siebel Open UI deviates from the way Siebel CRM has worked in past releases. The following product differences must be considered when you implement Siebel Open UI.

• Escape key and undo. Pressing the Escape key once performs a single undo operation. Pressing the Escape key multiple times might generate multiple results, depending on the user's previous activity, including which user interface elements the user has interacted with.

• Double-clicking. Double-clicking has been eliminated from the Siebel Open UI client, to improve usability. Double-clicking causes difficulties for novice users and presents drawbacks to accessibility. It also conflicts with the single-click interaction style of the Web and of many mobile devices, and it is not common to all operating systems.

• Right-clicking. Right-clicking has been eliminated from the Siebel Open UI client to improve usability. Right-clicking lacks good usability characteristics. It is not discoverable, it does not meet accessibility requirements, and it is difficult to implement on mobile devices.

• Logout on exit. Automatic logout upon closing the browser cannot be supported in a standards-based implementation, due to Web browser and W3C limitations. This action cannot directly communicate to the server that the user has disconnected. For this reason, the behavior of Siebel Open UI applications has been updated. It is recommended to set session time-out intervals as short as possible while maintaining usability. Also train users to log out of the application explicitly.

• Implicit commit on the browser Back button. An implicit commit of data record changes when a user clicks the browser Back button cannot be supported in a standards-based implementation, due to Web browser and World Wide Web Consortium (W3C) limitations. Users must commit changes through supported methods. Sometimes, a highlight indicates data that has not yet been committed.

• Scrollbars. Horizontal scrollbars are not used in the Siebel Open UI client, because they tend to deteriorate usability. However, to emulate specific behaviors, you can add horizontal scrollbars by using CSS changes. For long lists, use the forward and backward buttons in place of vertical scrollbars. Using refined queries displays a smaller result set and enhances usability.

• Pick lists and LOVs. Pick lists and LOVs do not select a new value until a unique match is made. Where you use auto-fill but an exact match is not made, the value reverts to the original. Selecting from an LOV does not include double-quotes.

• Shuttle applets and MVGs. Shuttle applets and MVGs have been redesigned for improved usability and to make them more consistent with pick lists.

• Images and screens. The look and feel of the following features has changed:

  • Login and logout pages have an updated look.

  • Task bar icons are more modern, with higher resolution and color depth.

  • Buttons have been updated, with higher resolution and color depth.

  • The Oracle logo font and color have changed.

  • The tab bar has no images, for consistency.

  • Check boxes have an updated look.

  • New columns-displayed icons have been added.

• Attachments. Attachment files stored in the Siebel File System cannot be edited on the fly in Siebel Open UI. That is, attachment documents cannot be opened, edited, and saved directly back to the Siebel application. Users must download an attachment document into a secure location specified by the browser, edit and save the document, and then upload the document. This behavior is standard for true Web-based applications.

  Where Desktop Integration Siebel Agent is deployed on the user computer, however, attachment files can be saved directly to the Siebel application. For more information, see Desktop Integration Siebel Agent Guide. See also the Siebel Installation Guide for the operating system you are using.

  For more information about issues in using the Siebel File System in Siebel Open UI applications, see "Migration Options for Siebel File System Features in Siebel Open UI".

• Auditing for the print feature. Siebel Open UI uses the browser's native print features, rather than using proprietary printing features. Use external audit capabilities to audit printing by users of Siebel Business Applications. Siebel Open UI does not support print audit features.

• Signature captures. Store signature captures as images for Siebel Open UI applications, to avoid integration issues for external components trying to display signatures. The previous encryption algorithm for signature captures is not supported. For more information about configuring an integration for signature capturing, see Configuring Siebel Open UI.

This topic is part of "Siebel Open UI Client User Experience".