(this page was created automatically. In case of formatting issues, please visit the official Wiki Page)

Action Placement

Overview

Actions trigger functions, such as saving or deleting a business object. They can also trigger navigation to another dashboard, where the action can be executed, described in detail, or checked further. Actions are displayed in the form of action icons or buttons.

Actions that refer to a content are displayed at the top of the boardlet, next to the title that identifies the object. Actions that relate to the task workflow are located at the bottom right and can be performed after working through the content.

To make actions easier to organise and find, they are usually placed in toolbars. Depending on the content that is affected by the action, different toolbars are available. Within the tool bars, some actions are usually more important than others. Refer to the arrangements in the below examples for better understanding.

Actions are always distinguished from pure navigation. Navigation functions are always on the left, such as Home or Breadcrumbs, while actions in toolbars are aligned on the right.

Anatomy

Actions can be categorized into three groups: Toolbar Actions, Footer Actions, and Content Actions. More information on each can be found in their respective pages.

Toolbar actions

Toolbar actions are an important part of action placement. They control functions of the content as well as the container. Actions are represented by action icons. If more than the allowed number is needed, group them in an overflow “More” menu.

Toolbars appear in different organisms and follow specific rules. Use the following placements and constraints.

• Header toolbar. It contains actions that affect all applications or the entire user environment. Primary and secondary actions are distinguished. The application name appears in the right header toolbar.
• Boardlet toolbar. It is always on the right side of the boardlet. There is a first actionbar for actions that affect the boardlet and a second actionbar for actions that affect the content. Do not place more than three actions per boardlet toolbar. Additional actions go under the “More” action. A boardlet must always include the “More” action. Separate the second actionbar with a divider and never use it without the first. Page-level toolbars can remain constant and are optional.
• Ghost boardlet toolbar. It follows the boardlet rules. The first actionbar has only one “More” icon.
• Card toolbar. Cards do not have a first and second toolbar. Only two actions are allowed. Use “More” and “Expand/Collapse” if the card supports this function. A card must always have a “More” icon.
• Dialog toolbar. It follows the boardlet rules. In a dialog with a sidebar, place the first actionbar on the outer right of the sidebar. This makes the difference between dialog functions and content functions clear.
• Table row toolbars. Toolbars can be used in rows of tables. They always control functions of the entire row.

Footerbar actions

The footerbar controls the workflow of the organism it is placed in. Actions related to the workflow are always at the bottom right of the boardlet.

The footerbar has a fixed height and must never be multiline. Use only the allowed combinations.

• Tabs only. Tabs are arranged side by side. There is no default number of tabs.
• Tabs with buttons. Use this when the boardlet has multilayer content and a content action. If an action exists only in one tab, show it disabled in all other tabs to avoid visual jumping. The number of possible actions is limited to a maximum of two buttons.
• Buttons only. Use this when an action is required in the boardlet. The number of possible actions is limited to a maximum of two buttons.
• Tabs with actionbar. Use this as a secondary display option. It can be used in kiosk mode to control tab rotation and timing.

Footerbars appear in different organisms and follow further rules.

• Boardlet footerbar. All four combinations are allowed. The kiosk mode variant can control the tabs, rotation, and time control.
• Dialog footerbar. Only the combinations Tabs only, Tabs with buttons, and Buttons only are allowed. If the dialog has a sidebar, the footerbar goes over the whole width. Buttons must not be wider than the footerbar.
• Modal footerbar. Only buttons are allowed. The designer chooses the button set. Primary buttons are always on the right.
• Tooltip footerbar. To be announced.
• Dashboard footerbar. Not further specified here.

Content actions

Content actions are placed directly in freely selectable content. They can appear in the content area of a boardlet, dialog, modal, or free-standing content.

We distinguish three categories.

• Inline actions. The action molecule or organism is not enclosed by a body. The action is always on the left inside the molecule or organism.
• Actions. These actions also have no enclosing body. The action is always on the left inside the molecule or organism.
• Table actions. Rules are to be added.

Best practices

Place and align

Place actions as close as possible to the content they affect. Prefer a toolbar or place actions directly in a form or table row when needed. Right-align actions inside toolbars. Keep navigation on the left and actions on the right.

Choose the right pattern

Use a Toolbar action when the function controls the content or its container. This includes boardlets, cards, dialogs, or a whole table row. Use a Footerbar action when the function advances or finalizes the workflow of the organism. Keep to the allowed combinations and the fixed single-line height. Use a Content action when the function belongs inline to a specific field, record, or piece of content.

Action order and emphasis

Follow this order in the Header toolbar. Place business actions first and then content management actions. Place layout management actions next and then generic actions. It is recommended to place the action most important for your business context on the very left within its group. Follow this order in the Footer toolbar. Place the primary workflow or finalizing action on the leftmost position. Place secondary actions next and then the negative path.

Use only one primary action per page. Show a primary action or a semantic danger action, but never both.

Hierarchy and alignment

Buttons follow a hierarchical order that moves from right to left. Primary actions come first and then danger actions. Secondary actions follow and then negative path actions. Secondary actions can be collapsed into menus to preserve clarity. Use the overflow menu when space is limited.

Toolbar capacity and grouping

Do not place more than three actions per boardlet toolbar. Group additional actions under the More action. List grouped actions in an overflow menu. A boardlet must always include the More action. The second actionbar must not exist without the first.