Skip to main content

Contexts

A context combines one business object with the views used to work with it. A well-defined context gives users a recognisable place for a task and the information associated with it. A context created solely to expose a technical relation or an extra view usually offers little value to users.

Read this page alongside Information, navigation, and labels and the viewtemplates and layouts reference.

Identify the business object​

Naming the context after the business object or task makes its purpose easier to recognise. Reusing the same term in the menu, context, views, actions, and tabs builds familiarity; Spelling and wording provides the conventions.

Links to another context or view are helpful when users need that information to continue their task. They can save navigation steps, whereas links to every technically related record can make a context harder to scan. The documented link and action mechanisms of the selected viewtemplate provide a dependable implementation basis.

Views by user task​

More than one selectable view is valuable when each view supports a different task or perspective. Names based on content or purpose help users choose a view without trial and error.

Visual design and data presentation supports display-type selection, and the viewtemplates and layouts reference explains which representations and properties are supported.