Force.com Platform Fundamentals

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Introducing Action Layouts

Just like we can customize object record pages with page layouts, we can customize publisher actions using action layouts. Using the action layout editor, we can select the fields that will show up when a user clicks on an action.

The action layout editor has a palette on the upper section of the screen and the action layout below it. The palette contains fields from the action’s target object that you can add to the action layout. However, the following field types aren’t supported, and won’t show up in the palette:
  • Record type fields
  • Read-only field types such as roll-up summary, formula, and auto-number fields
  • Read-only system fields such as Created By or Last Modified By

If you convert a field’s type from one that is supported for actions to a type that isn’t supported, the field is removed from the action layout. If you convert the field back to a supported type without changing the action layout, the field is automatically added back onto the layout. If you’ve edited the layout and then convert the field back to a supported type, you must add the field back onto the layout manually.

Note

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, as there’s not enough space to display the full rich text editor.