Actions and interaction

Actions allow users to change data or start a process. They are most effective when the next useful step is visible without turning every available function into a choice on the screen. The standard action mechanism and the selected viewtemplate's documented configuration provide the foundation.

Actions for the current task

An action belongs in the current view when users need it to complete their work. An unrelated action merely provided by the entity can make the choice less clear. Where several actions are possible, the normal order of the business process and the recognisability of the next step are useful decision criteria.

When the same business action appears in comparable contexts, a familiar title, icon, grouping, and position help users find it again and anticipate its result. A different task, role, or device may call for a different placement.

Clear titles and consistent icons

The title, tooltip, and icon conventions in Spelling and wording support a consistent experience.

Using one icon consistently for one distinct action helps users learn its meaning. Reusing the same icon for different business operations can undermine that recognition.

Help users find relevant actions

Frequent, task-critical actions benefit from an easy-to-find position. Grouping Actions by a user-understandable purpose and leaving out actions unrelated to the current task reduces unnecessary searching. Available positions and presentations remain component-specific.

A multi-record action should clearly show which selected records it will affect. The available options depend on how record selection is configured in the client.

Respect documented component behavior

The placement, orientation, and available configuration of actions depend on the selected viewtemplate and surrounding view. The individual reference explains what is supported.

This guideline does not define a universal visual order, color, confirmation, or error-handling pattern for actions. Confirming the available behavior before turning it into a project requirement keeps those decisions valid.

The complete interaction

Reviewing actions in the configured client, not only in the Designer, reveals whether users can find an action, understand its title, complete the resulting flow, and return to the expected information. Looking at the whole workflow is more informative than checking only whether a button can be configured. The review must also cover each project device variant and accessibility-related settings.