Macros Considerations in Lightning Experience

General Considerations

Important Macros created in Salesforce Classic display in the macro utility in Lightning Experience only when their object and macro instructions are supported in Lightning Experience.

For example, a macro created in Salesforce Classic that attaches a Knowledge article to a case email doesn’t display in the macro utility in Lightning Experience because that action isn’t supported yet. However, a macro created in Salesforce Classic that uses the Log a Call action on a case does display in the macro utility in Lightning Experience. Likewise, you can’t use macros created in Lightning Experience that include instructions that are only available in Lightning Experience in Salesforce Classic.

Macros in Lightning Experience work on all objects that allow quick actions and have a customizable page layout. However, we recommend that you don’t use macros with the following items.

• Read-only fields
• Encrypted fields
• Opportunity products
• Crew Size field on the Service Crew object
• Social quick action in the case feed publisher provided with Social Customer Service

Limitations for Macros in Lightning Experience:

• Email message objects (not to be confused with the Email action, because macros work fine there) aren’t supported
• Knowledge articles can't be inserted into Macros
• Macros don’t run when launched from a record’s Details tab.

Note When you run a macro that sends an email with attachments, the macro fails. A pop-up window asks you to confirm sending the email and attached files. Click the option to avoid showing the pop-up message again. Then rerun the macro to send the email and attachments.

Keep the following things in mind when enabling folders for macros.

• You can enable and disable Share and organize macros in folders, but we recommend that you don’t. After it’s enabled, only switch back if you must.
• After you enable folders, the Share button on macro records in Salesforce Classic is disabled for records that are assigned to a folder.
• To create and manage folders, you can also use the Analytics Folder API.
• Folders for macros aren’t supported in Essentials Edition orgs.
• Verify that your macro page layout includes the Folder field.
• After enabling Share and organize macros in folders, you might not see the updated list view that shows folders. To see the updated view, choose a different navigation item and then go back to macros.
• We recommend that you don’t use split view for macros. After folders are enabled, split view displays the folder list view, which isn’t optimized for split view.
• The macros browser panel supports up to 2000 macros and folder records.

Considerations for Creating and Working with Macros

• Macros are a standard object. If your org has org-wide public sharing, all macros are shared. If org-wide sharing is private, you can share macros with groups, roles, and users manually.
  

  Note You can share only individual macros in Salesforce Classic. In Lightning Experience, you can share macros using a folder.
• Macros only work with self-related records and don't support components that point to other objects
• Administrators manage prebuilt macros. If you want your service reps to use these Macros, give them at least read access and share the following folders:
  • Macros folder - Basic Macros
  • Quick Text folder - Sample Quick Texts 2
• In most text fields, you can insert up to 4,000 characters. Some text fields, like Text Area, have smaller character limits.
• If you use quick text in text fields, keep in mind that quick text channels aren’t observed in macros. For example, let’s say you set up quick text to be used only on one channel, such as email. When the quick text is in a macro, it can also be used on actions like Log A Call.
• You can’t use Salesforce Classic email templates that use Visualforce in macros for Lightning Experience.
• You can apply more than one email template. For example, you can use the Subject of one email template and the Body of another. If an email template is updated, the macro uses the updated template.
• Macros that apply Lightning email templates that use Handlebars Merge Language (HML) syntax can't be used in Salesforce Classic.
• The Mobile Smart Actions quick action can’t be used with macros for Lightning Experience. .
• You can attach files to emails in your macro. Keep in mind that Salesforce has two types of attachments: ones uploaded in Salesforce Classic and ones uploaded in Lightning Experience. If the attachment was uploaded in Salesforce Classic, add it to a Salesforce Classic template and then apply that template to the macro. The same applies to Lightning Experience. Add the attachment to a Lightning email template, or click Insert Attachment.
• Before using macros created with Insert at Cursor actions, remember to initialize the cursor where you want the text added. If not, the macro inserts at the beginning of the field.
• You can create macros with relative times and dates for Time, Date, and DateTime fields only in Lightning Experience.
• You can create macros with conditional instructions only in Lightning Experience. These macros use logical expressions that determine which instructions execute.
• The macros utility doesn’t support pop-out.
• To use the Close Case macro, go to Support Settings and check Show Closed Statuses in Case Status Field in the Setup page to allow closed statuses in the Case Status field.
• Macros have a 10-second timeout error. If the instruction is still in progress, feel free to wait or click Retry.
• Macros support only tab-based actions and aren’t supported in the Dynamic Activity Composer. To use macros, switch to the Tabbed Activity Composer.