|
General functionality and
customization
|
| Split view placement |
Yes |
Yes |
In Salesforce Classic, this feature is called pinned lists, and you
configure it with the Choose List Placement setting.
In Lightning Experience, split view is enabled by default, and users
can open or minimize split view. The Salesforce Classic Pinned to
Top setting isn’t available in Lightning Experience.
|
| Resizeable split view |
Yes |
No |
In Salesforce Classic, you can adjust the width of a pinned list.
In Lightning Experience, you can’t adjust the width of split
view.
|
| Custom keyboard shortcuts |
Yes |
Partial |
In Lightning Experience, background utility items can be used to
customize keyboard shortcuts. |
| Keyboard shortcut overrides |
Yes |
No |
|
| Interaction logs |
Yes |
No |
|
| Dynamic list updates (push notifications) |
Yes |
No |
|
| Dynamic record updates (push notifications) |
Yes |
No |
|
| Forget open tabs |
Yes |
No |
As a workaround, use a background utility item to control your
tabs. |
| Tab limits |
Yes |
Partial |
In Lightning Experience, you can limit tabs using background utility
items. |
| Close all tabs |
Yes |
Partial |
In Salesforce Classic, Close all primary tabs
is an option when selecting  on the tab
bar.
In Lightning Experience, you can close all tabs with the Shift+w
keyboard shortcut.
|
| Save user sessions |
Yes |
Different |
In Salesforce Classic, you can disable saving user sessions. In
Lightning Experience, console apps always open the tabs you last
opened. |
| Tab preview on hover |
Yes |
No |
|
| Third-party domain workspace tabs and subtabs (allowed
domains) |
Yes |
Different |
Use the openTab or openSubtab JavaScript API methods to open web tabs
inside Lightning console apps. Third-party domains must be allowlisted
in the Trusted URLs list to be used with openTab and openSubtab in
Lightning Experience. |
| Console API (JavaScript APIs for navigation and utilities) |
Yes
|
Different
|
Two APIs interact with Salesforce console apps: the Salesforce
Console Integration Toolkit (used in Salesforce Classic) and the
Lightning Console JavaScript API (used in Lightning Experience).
For
more information about both APIs, see the Salesforce Console Developer
Guide.
|
| Internet Explorer 11 support |
Yes
|
Yes
|
You can access Lightning console apps in IE11, but expect significant
performance issues. We recommend using a different browser.
Keep in mind that support for IE11 ends on December 16, 2017, unless you
opt in to extend support. If you opt in to Extended
Support for IE11, you can continue to use IE11 to access
Lightning Experience until December 31, 2020. |
|
Utility
functionality
|
| Notes utility |
No |
Yes |
In Lightning Experience, use the Notes utility to create, view, and
associate notes with records. |
| Background utility items |
No |
Yes |
Background utility items run without a visible button in the utility
bar. They add functionality to a Lightning console app without
cluttering the user experience. |
| Support for multiple lines of text |
Yes |
No |
|
|
Component
functionality
|
| Region presentation—size |
Yes |
No |
In Salesforce Classic, you can adjust the size of a component. In
Lightning Experience, the page template for your record page
determines the size of the component region. For example, the three
column page template provides a main column width of 50%, and the
side columns widths are each 25%. You can’t collapse or adjust
region size. To view the available page templates, create a page in
Lightning App Builder.
|
| Pinned region in custom templates |
Yes |
No |
|
| Multi-monitor—pop-out workspaces |
Yes |
No |
In Salesforce Classic, this feature is called multi-monitor
components.
|
| Visualforce overrides |
Yes |
Partial |
The delete action isn’t supported.
|
| Lightning component overrides |
No |
Yes |
Action overrides that use Lightning components for View, New, Edit,
and Tab are supported in Lightning console apps. When a user performs an
action that’s overridden with a Lightning component, the content from
the custom action appears in a tab or subtab. When the split view is
open, tab action overrides load the Lightning component in a split-view
container that is 400-pixels wide. |
| Collapsible regions |
Yes |
No |
|
|
Service Console
functionality
|
| Service-specific Setup flows |
No |
Yes
|
In Lightning Experience, the Service Console app comes with
Service-specific setup flows to get you up and running quickly. The
flows walk you through setting up Email-to-Case, integrating with
Twitter and Facebook, creating an Experience Builder site, and enabling
Lightning Knowledge, Chat, and Omni-Channel. |
| Knowledge component |
Yes
|
Yes
|
In Salesforce Classic, this feature is called the Knowledge One
sidebar component. In Lightning Experience, use Lightning App Builder to
add the Knowledge component to the case page.
Lightning Knowledge is
different from Knowledge in Salesforce Classic. Learn
more.
|
| Omni-Channel utility |
Yes |
Yes |
In Salesforce Classic, this feature is called the Omni-Channel footer
component. |
| Chat |
Yes
|
Yes |
In Lightning Experience, Chat works a bit differently. Learn
more.
Chat is available only in the Lightning Service
Console app.
|
|
Sales Console
functionality
|
| Person accounts |
Yes |
Different |
Lightning console apps support person accounts with some
differences.
Person accounts don’t have the same three-column
layout as business accounts. Use the Lightning App Builder to create
the desired layout, and then assign it to appropriate console app
and the person account record type.Person account records that
display in a contact’s Related Record components are
read-only.
https://help.salesforce.com/articleView?id=console_lex_limitations.htm&language=en_US.
|
| Forecasts |
No |
Yes |
In Lightning Experience, add forecasts to your console app from the
App Manager in Setup. |