When to use
- Data in a list, Table or Card must be selected before applying actions such as “Run parsing,” “Add to sequence,” or “Remove from plan”.
- You need to conserve table space; an Action toolbar can be used to house common table actions like Delete, Copy, and Duplicate instead of displaying them in the Table or persistent Page toolbar.
- Item(s) must be selected before continuing on with the workflow and there are many paths a user can take.
When to use something else
- Use a Toolbar (including page-level toolbars) when item(s) do not need to be selected before applying an action.
Dos and don’ts
- Do center align the Action toolbar within the container or page it applies to.
- Do keep it contextual and only include actions relevant to the current view or selection.
- Don’t make the Action toolbar draggable or position it anywhere but the bottom area.
- Don’t clutter the toolbar with too many actions. Use progressive disclosure with menus if needed.
Behavior
- The toolbar does not appear until the user has made a selection (for example in a Data grid or list).
- It transitions in from the bottom of the page or section and stays fixed until the user clears selection, completes the action, or navigates away. It is not draggable.
- If the page does not reload when an action runs, the toolbar transitions downward off screen while the action completes.