Related Pages: System Errors

Description

Empty states are special messages shown in workspaces or containers to indicate that content is unavailable.

Types

Illustration	Icon
Use for a single empty state with sufficient space for displaying the illustration. All illustrations are animated.	Use an icon when multiple empty states are needed in different content areas in the same workspace, or where space is limited.

Usage & Behaviour

General guidelines

Structure

Placement and Positioning

Empty states can be applied to various components (data tables, lists, dashboards, etc.).

Empty states should:

• Replace the content that would ordinarily be shown.

• At the top 1/3 of the content area, centered horizontally.

Full page positioning:

Specific elements positioning:

Content

The selection of the image depends on the specific context:

Context	Illustration	Icon
No results found Use when a search returns no results.
No <item type> defined Use when no items have been defined, such as an empty user list.
No <item type> selected Use when a user has selected no items.
Multiple/too many <item type> selected Use when a user has selected too many items
Specific use cases:
Empty in-tray Use when a user has no new items to review.

Interaction

• Empty state illustrations and icons are non-interactive.

• The message may contain an additional Dialog Button or a Text Link.

• When an empty state is embedded within a container, the rest of the application should remain active.

Transitions

• Appears:

  • After a component or section finishes loading, and there is no data to show.

  • When a specific user action has yet to be taken, for example, no items added/selected.

• Disappears:

  • Either because of a user action (populates the state with content) or a process that changes the state (e.g. server is responsive again).

Best Practices

Use:

• Clear, concise written explanations.

• Messages should be brief and informative.

• Prompts to guide the user to perform actions relevant to their workflow.

• A message may contain information about the system status or direct to relevant features.

Don’t:

• Leave a completely blank content area for an empty state. This creates confusion for users.

• Use links to irrelevant actions.

Accessibility Compliance

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.

Responsive design

Verint products should dynamically respond to the user’s screen size, platform, and orientation, supporting all devices down to the common tablet size (960px width).

Design

Zeplin link	Screen thumbnail
https://zpl.io/9Nqo6DW

Code