You are here:
Lightning Experience Console Limitations
Learn about the limitations of the console in Lightning Experience, and which features don’t yet have parity with Salesforce Classic console apps.
You can’t upgrade a Salesforce Classic console app to Lightning Experience. You can choose to display or hide the app in the Lightning Experience App Launcher, but you can’t edit the app from the App Manager page in Lightning Experience Setup. To get started in Lightning Experience, customize these Salesforce-provided Lightning console apps: Service Console and Sales Console. You can also recreate your Salesforce Classic console app in Lightning Experience, but using the Salesforce out-of-the-box app is faster and easier.
Lightning console apps don’t yet have full parity with Salesforce Classic console apps. For example, some features in Salesforce Classic console apps, such as push notifications and custom keyboard shortcuts, aren’t available in Lightning console apps. Learn more.
- Internet Explorer 11
- 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.
- Lightning Console JavaScript API
-
This API provides methods for Lightning console apps similar to methods provided by the Salesforce Console Integration Toolkit. Not all the methods available in the Salesforce Console Integration Toolkit are available in the Lightning Console JavaScript API. This table lists the Salesforce Console Integration Toolkit methods that you can use in Lightning Console JavaScript API starting with API version 42.0.
- Visualforce
-
Visualforce is available in Lightning console apps as beta, which means it’s a high-quality feature with known limitations. Lightning console apps’ Visualforce support includes:
- Lightning pages containing Visualforce Lightning components
- Visualforce mass actions
- Custom tabs that display a Visualforce page
- Opening Visualforce pages as new workspace tabs or subtabs using the openTab() and openSubtab() JS APIs
- Visualforce overrides for new, edit, view, tab, list, and
clone actionsNote Overrides aren’t supported on the Case object when using the default service console app. To use overrides on cases, create a custom console app.
- Visualforce components in the utility bar
Lightning console apps don’t currently support:
- Visualforce overrides for delete and custom actions
- Visualforce buttons and links
- Person Accounts
- 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.
- Salesforce Knowledge
- Some Knowledge component actions don’t work in Lightning console apps, including attaching PDF files, adding article contents to case emails, and adding article Experience Cloud site URLs. The Knowledge footer is not supported in Lightning Experience.
- Chatter
- If you click an internal link from a Chatter post in Lightning Console, the link doesn't open in the same browser tab. Instead, the link opens in a new console tab in an entirely new browser tab. The workaround is to install Lightning Extension for Chrome and turn on the Link Grabber feature. Then the Salesforce link opens in a new tab in the current console. The Lightning Extension is available only for Chrome.
