...

Types

Type	Description	Layout (replace images)	Example
Top navigation layout	Used by default for Verint applications. For more information, see VerinTop Top Navigation.
Left navigation layout	Used for Verint applications with larger navigation menus. For more information, see VerinTop Left Navigation.
Webpage layout	For Verint web pages, such as Verint Connect. Contact the UX team for more information.

...

The header area contains information and controls which relate to the whole page, across all Workspace sectionsthe entire workspace.

...

Structure

The header area can contain multiple components, including:

...

The main workspace should be central within the layout.

Content

The workspace content may consist ofcontains one or multiple Widgets.

Each widget may contain:

• Textual and graphical content

• Data Tables

• Forms

• Data VisualisationsDashboards

Workspace

...

layout

Where there are distinct fields within the content, the main workspace may be separated into multiple sections. Workspace sections are usually directly related to one another.

The layout of workspace sections should also have a clear hierarchy, ordered left-to-right, top-to-bottom.

...

REPLACE IMAGE

Note: For standalone interfaces, use Widgets instead.

Structure

Each workspace section may include:

• a header, to identify its purpose.

• any separate controls which only operate on the individual section, such as expand-collapse.

contain multiple Widgets with their own headers and controls. (Note: controls which operate across all workspace sections widgets should be placed in the Header area).

Placement and positioning

Workspace sections may:

• Each widget may use any proportion of the available area within the main workspace.

• be nested within a larger section, where there is a clear hierarchy.

• The spacing between each

...

• widget should be consistent across the workspace.

Interaction

Workspace sections should be of a fixed proportional width. Their size should not be adjustable by the user.

Where relevant, workspace sections may optionally:

• be collapsible, particularly for sections containing secondary or optional content. Titles should still be visible when a workspace section is collapsed.

• have a maximize option, to show the section’s content in a larger space such as a Popup or separate pageThe layout of widgets within the workspace should also have a clear hierarchy, ordered left-to-right, top-to-bottom.

See /wiki/spaces/UserExp/pages/3204678053 for more information on how content is laid out within each widget.

A Dashboard layout should be used where:

• the user can add, remove, or resize widgets.

• the workspace provides an overview of data on a particular subject.

Single widget layout	Multi-widget layout	Dashboard layout
Image Added	Image Added	Image Added

Interaction

Each widget should have a fixed position and proportional size, which cannot be adjusted by the user (except where expand/collapse is offered). Where the user can adjust the layout, use a Dashboard.

Left Pane

The left pane may be one of the following:

...

• Make sure there’s a natural flow between elements on the page, from top to bottom, left to right.

• Prioritise the most important elements to facilitate user decisions.

• Form associations between related elements by keeping them in close proximity and using similar styling.

Use:

• fluid responsive design, to ensure the layout works at all screen sizes, across devices and browsers.

• headers for each element within the layout, to make sure they are easily identifiable.

• consistent spacing between elements.

• the same layout for pages with similar content.

...

• controls in the header area which don’t affect the entire main workspace.workspace sections for standalone or embedded interfaces → use Widgets.

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).

• Where there is not enough space to display the full layout, the main workspace should be prioritised. Other areas within the layout may be collapsed or minimised, including the left and right panes.

• The content of the main workspace should be fluid, dynamically adapting to the size of the available area, even as it changes during use. This may include changing text, graphics, table, and spacing sizes. The available space may change due to the state of collapsible panes as well as screen size.

• Where sections widgets are used within the main workspace:

  • as the width of the workspace changes, so should the widths of the individual sections widgets within it. The proportion of the width that each section widget uses should remain the same.

  • the layout of the content within each section widget should dynamically respond to its width.

  • breakpoints may be introduced, at which the sections widgets may be rearranged into a more appropriate layout. For example, a minimum-width workspace breakpoint may make all sections widgets full width and vertically stacked.

• Where space is severely limited, it is acceptable to remove secondary information and functionality, but this should be avoided where possible.

• When the screen width is changed, anchored panes and components should remain fixed to the left- or right-hand side.

• The size and spacing of individual components and fixed panes (such as the Filter Pane and Details Pane) should not change as the layout dynamically responds.

See the recommended responsive design for individual patterns and components, where necessary.

Layout responsive design example

...

Example screens

Top navigation layout

Details panel in AV example goes right to the top?

Left navigation layout

More left nav examples?

Left icon tabs in Details panel isn’t a documented use…

Design

...