No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
How Actions Are Ordered in the Salesforce1 Action Bar and List Item Actions
The actions in the action bar, list item actions, and associated action menus are divided up into groups. The arrangement of these groups is fixed, but the order of actions within the groups can vary based on the object and the actions that are present on the global publisher layout or on an object’s page layout.
Not every object or page displays every group. Action groups 3, 4, and 5 respect the ordering of the actions as defined by the global or object page layouts, with a few exceptions, as you’ll see in the next table.
Productivity actions don’t display if a record doesn’t include the information that the actions are keyed to—for example, the Send Email action is dependent on the record including an email address and the View Website action requires the record to include a website URL.
Here’s the breakdown of which actions are contained in each group for each object or page.
As we mentioned, some actions are in fixed positions. In places where you see a numbered list in the table, this is the fixed order that those actions appear in on the action bar, list item actions, and in the respective action menus.
For example, for the Account object, the standard Chatter Post action is in the fourth position. This is fixed. Regardless of where you put the Post action in the Publisher Actions section of the account page layout, Post always displays in the fourth position.
However, deletion of actions is always respected. So in our example, if you delete the Post action from the account page layout, the remaining actions move up and you see Edit in the fourth position.
* Custom buttons that are added to the Button section of a page layout and that use a Visualforce page as the content source are supported in Salesforce1. Remember that the Visualforce page must be enabled for use in Salesforce1. Custom links, custom buttons that are added to list views, and custom buttons that define the content source as URL or OnClick JavaScript aren’t available in Salesforce1.