Skip to end of banner
Go to start of banner

Switching from Salesforce Classic to Lightning Experience

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

 now supports Salesforce's Lightning Experience. If you are ready to switch over, this page documents various features that may be of concern to you if you are an administrator.

Working with Salesforce Files

In Lightning, attachments are stored and managed as a Files object, as opposed to an Attachment object in Classic. Alongside Attachment objects, the Connector can sync Files objects from Salesforce to Jira as well.

Note that this feature is currently on BETA.

To turn this on:

  1. Visit a mapping configuration page.

  2. Expand the Settings section.

  3. Enable Synchronize attachments from Remote System.

  4. The page will refresh. Repeat step 2, and then enable Synchronize files from Remote System (BETA).


Working with Visualforce buttons

All buttons or links described under Configuring Salesforce are automatically compatible with Lightning Experience. There is no further action required.

Working with Visualforce pages

All Visualforce pages described under Configuring Salesforce are compatible with Lightning.

To add Visualforce pages to a page layout in Lightning, add a Visualforce component when inside the page layout editor:

To adopt the Lightning Experience look and feel to your Visualforce pages, add the following markup to an <apex:page> tag in your Apex classes:

lightningStylesheets="true"

For example, when applied to Connector Fetch REST API - Showing associated Jira Issues in Salesforce Cases, you will have the following:

<apex:page standardController="Case" extensions="JIRAFetchIssuesController" lightningStylesheets="true">

Result

  • No labels