When you create an action, Salesforce populates its layout with a default set of fields. You can add, remove, or reorder fields on the action layout to present only the essential items your users need when they use the action.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Group, Professional, Enterprise, Performance, Unlimited, Contact Manager, Database.com, and Developer Editions |
- There’s no hard limit to the number of fields you can add to an action layout. However, for optimum usability, we recommend a maximum of 8 fields. Adding more than 20 fields can severely impact user efficiency. To reduce the number of fields in your layout, you can create predefined values for the required fields, and then remove those fields from your layout. You can set predefined field values from the action detail page.
- By default, the Call productivity action in the Salesforce mobile app action bar uses the global Log A Call action layout. If you create one Log a Call action on an object, users see that custom Log a Call action’s layout when they tap Call from the action bar for that object. If you create more than one Log a Call action for the same object, the Call action on that object doesn’t know which layout to use, so it uses the global Log a Call action layout.
- Mobile smart actions are populated with all your org’s required fields on the relevant object, regardless of how many fields there are. For example, the New Case action in the mobile smart action bundle includes all required case fields. You can’t edit the fields on mobile smart actions. The fields that appear change only if you change which fields on an object are required.
- You can remove a required field from the action layout, but make sure that the field has a predefined value. Otherwise, users can’t create records.
- Rich text area fields are supported only when you add them to one-column layouts, or as fields that span both columns in two-column layouts. If you add a rich text area field to only one column in a two-column layout, it appears as a plain text area, because there’s not enough space to display the full rich text editor.
- When you create a custom action and the action type is Update a Record, you can't add the Owner field to the action layout for most objects. The exception is Case records. You can add the Case Owner field to your action layout when you create a custom action to update a Case record.
- When an Activities component is placed in a sidebar region on a Lightning page, global action fields always appear in a single column, even if the global action has a two-column layout.