Learn about display, access, and customization limitations for a console.
Available in: Salesforce Classic
Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions
A Salesforce console is available only in Supported Browsers for Salesforce Classic. If you use an unsupported browser, you get a degraded experience.
For best performance, we recommend that console users adopt the Google Chrome™ browser and machines with 8 GB of RAM. Keep in mind that 32-bit systems are subject to memory limitations. To take full advantage of the added RAM, use 64-bit versions of both the OS and the browser.
A console offers limited support for right-to-left languages, such as Arabic or Hebrew. Since right-to-left languages aren’t fully supported, some features don’t appear as expected in a console, such as Case Feed, Live Agent, and Salesforce Knowledge.
All Salesforce CRM Content items display as primary tabs in a console.
When using Social Accounts, Contacts, and Leads, the Social Viewer window doesn’t align properly within a console.
Record home pages, including their standard Tools sections, don’t display in a console.
Behavior and Access Limitations
Back buttons on browsers are not supported for a console and don’t work as expected.
A Salesforce console doesn’t meet accessibility requirements.
Visualforce pages don’t refresh when you click and select Refresh all primary tabs or Refresh all subtabs. In addition, if you override a detail page with a Visualforce page that uses related lists, any new records created using that related list aren't displayed until the page is reopened in a new tab.
If you edit a page layout in the console, such as adding a primary tab component like an interaction log, the updated layout isn’t displayed until the page is closed and then reopened in a new primary tab.
You can't directly edit the fields on the highlights panel; however, when you change those fields on a record, the highlights panel is automatically updated.
Some objects haven’t been fully adapted to a console, such as reports, dashboards, and Chatter. These and other objects are marked with an asterisk (*) in the console setup area and might cause unexpected behaviors. For example: (1) When viewing opportunity splits, clicking Cancel doesn’t close the subtab; instead, the page detail information is opened in a subtab; (2) opportunity line items and quote line items don’t automatically refresh when changed—you might need to refresh the page to see the latest changes.
If you leave a console and return to it, any subtabs that were displayed might not automatically reload. Also, if you leave a console by selecting an app from the Force.com app menu, your browser's Back and Forward buttons might not work as expected.
If you save changes in a lookup component, and you have unsaved changes in another lookup component, the unsaved changes are lost without a warning message.
If you click a custom link or a link in a text field, such as http://www.salesforce.com/ in a case Description, the link appears in a popup window instead of a tab.
If you refresh the Change Case Status page in a console, an Unable to Access Page error appears.
If Chatter is disabled, you can’t use pinning in search results.
The console doesn’t support Chatter Messenger or the App Launcher.
Some Visualforce pages don’t display correctly in a console unless they're updated to show in it.
If you enable clickjack protection for Visualforce pages in your Salesforce org’s security settings, Visualforce pages won’t work correctly.
The console doesn’t support Visualforce pages that use the Require CSRF protection on GET requests preference. If you use Visualforce pages with CSRF protection, your agents can receive errors when trying to access the page.
Call center users can only use a softphone in a Salesforce console if they're using a CTI adapter built with version 3.0 or 4.0 of the CTI Toolkit; or if they’re using a call center built with Open CTI.
Live Agent is only available for a console with the Service Cloud.
The highlights panel for Live Agent Transcripts is editable, but you can’t turn it on for users.