1. Deploying Siebel Open UI Guide
  2. Implementation Differences Related to Browsers

Implementation Differences Related to Browsers

Siebel Open UI tries to hide specific differences in rendering between browsers within the user interface, but some browser-specific differences exist. Customers are encouraged to identify differences in rendering and to choose browsers based on the best usability offered. Examples are provided in this topic.

This topic is part of Siebel Open UI Server Deployment Characteristics.

Use of Popup Blockers

Siebel Open UI is compatible with popup blocker use. Make sure that Siebel application servers and third-party iFrames are whitelisted or excluded from blocking by popup blockers. For more information about configuring Siebel CRM for popup blocker compatibility, see the Siebel Installation Guide.

Impact of Browser Dynamic Patching of Browsers

Two basic strategies exist for managing your browser version:

  • Lock browsers to specific versions. Although locking your browser version mitigates the risks of introducing regressive interactions into the Siebel CRM environment, this approach introduces the risks of not patching imperfect browser code and does not help in addressing functional and security fixes in browsers.

  • Dynamically update browsers. It is strongly recommended to mitigate browser-related functional and security risks by allowing browsers to update dynamically. If regressive interactions occur, then Oracle and the browser vendors are committed to addressing these in a timely manner.

Validation Services for Standards Compliance

To validate Siebel application pages and the browser you are using against W3C standards, you can use any of several validation services, including the following:

  • W3C markup validation:

    http://validator.w3.org/

  • HTML 5 validation:

    http://html5.validator.nu/

  • CSS validation:

    http://jigsaw.w3.org/css-validator/

  • Lint, JSLint and derivative programs:

    http://www.jslint.com/

Multiple Browser Tabs and Sessions

As of Siebel CRM 19.7 Update, you can enable multiple active Siebel application sessions, each in a browser tab, for each browser instance. Multiple tab browsing can be useful for:

  • Support of cut and paste operations between records for contacts, accounts, service requests, and so on, performed by an employee or partner user.

  • Support for starting a Siebel application in a new browser tab using a bookmarked URL.

  • Improving user experience by limiting error messages seen by users, who may not be aware of any configured limitations to the number of sessions.

  • Support of portal applications that include multiple Siebel portlets.

By default, users can open multiple Siebel application sessions only by launching multiple browser instances. Unless configured otherwise, Siebel CRM supports a single active Siebel application session for each browser instance in its own memory space. For that browser instance, multiple Web pages can be opened in a single browser, but only one tab can have a live connection to a Siebel application at a given time.

In Siebel CRM 19.7 Update and later, you can enable multiple tabs for Siebel applications by setting the EnableMultiTab parameter to True for the Siebel Application Object Manager component. Additionally, you can limit the number of tabs allowed per browser instance by setting Maximum Possible Tabbed Sessions in the Application Interface profile. For example, to support users accessing the Siebel application in two tabs, but no more, set Maximum Possible Tabbed Sessions to a value of 2.

Note: Multiple tab browsing impacts scalability, as each browser session consumes server memory. For example, increasing the available sessions from a single session to two sessions per user (as in the example) can double the amount of Application Object Manager resources required. For portal applications, it is recommended to review the maximum number of Siebel portlets and active sessions used in the portal to establish the number of sessions needed in support of the portal for each user. It is recommended to carefully review resource availability and to configure Siebel CRM to limit the number of tabs and sessions that users can run, using the described settings.

For more information about supporting multiple tabs, see Configuring Siebel Open UI. See also Siebel System Administration Guide and the Siebel Installation Guide.

Language Support

In general, language support for Siebel Open UI is similar to language support provided in previous versions on the traditional clients. For Siebel language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support. See also Siebel Global Deployment Guide and the Siebel Installation Guide.

This topic is part of Siebel Open UI Server Deployment Characteristics.