Segmented Group

A Segmented Group combines two or more elements (Segments) into a single component to manage complex data, search, and fine-grained filtering within an object or dataset.

Usage

A Segmented Group is an agnostic container that wraps two or more Segments, making the relevant use cases broad.

When to use

• When filtering complex data, searching within a set of filters, and in creating complex filter patterns.
• When collecting information in a way that benefits from a "connected" visual representation, e.g., a key/value pair.
• When an action performs a generative function rather than a submit function, e.g., generating API credentials.
• As a complex data input within a form.

When not to use

• To submit a form or set of inputs. A Segmented Group can be used within a form to collect complex data, but an action within the group should not submit that data via a form method. Use the guidelines in Form patterns instead.
• To connect multiple fields that each require their own label.
• When adding a prefix or suffix to an input field. This is not currently supported by Helios form components, instead consider using a simple text element preceding or following the form element.

Segment components

A Segmented Group can consist of multiple primitive Segments that vary in their properties and intended input value. We recommend limiting usage in Figma to the defined Segmented Button, Segmented Dropdown and Segmented Input primitives to ensure consistent styling and grouping. If a custom solution is required, the Ember component yields any component that is passed to it.

Segmented Button

A Segmented Button can perform a function or interaction within a Segmented Group, e.g., generating an object, string, or value in a field it is connected to. It is an extension of the Helios Button.

Segmented Dropdown

A Segmented Dropdown can be used to filter or narrow the available parameters when searching within a dataset or group of objects. It is an extension of the Helios Dropdown.

Segmented Input

A Segmented Input is an extension of Helios form components and their variants, including:

• Text Input
  • Text
  • Password
  • Search
  • Date and time
• Select

Different Segmented Input types can be combined within a Segmented Group to collect complex data and support filtering patterns. Use the type that makes the most sense for the intended value or data.

Custom elements

If a custom component within a Segmented Group is necessary, ensure that the visual language and styling match the pre-defined Segment primitives, or contact the Design Systems Team for assistance.

Base component

In Figma, the Base component is a combination of a button (either a default button or dropdown) and a Segmented Input and is intended for less complex use cases. The properties of each nested Segment are exposed in the component to support rapid customization.

Examples

Since a Segmented Group is intended to be agnostic in relation to the inputs and actions it contains, the number of potential use cases and examples are broad. These examples should serve as inspiration for the different scenarios, contexts, and combinations of elements supported by the Segmented Group guidelines.

Within a filter pattern

A Segmented Group can be used in a filter pattern as a means to reduce or limit the items within a dataset. Depending on the complexity of the pattern, multiple Segmented Groups may be used to filter complex datasets.

This example showcases a larger filter pattern that consists of two Segmented Groups; the first supporting the limitation of the parameters included in a search query, the second grouping similar filter parameters relationally.

Within a form

While less common, a Segmented Group can be used within a form to collect relational data or perform generative functions like generating API keys.

Error validation

For error validation recommendations, refer to the Form patterns documentation.

Content

The content within a Segmented Group is dependent on the context:

• If used in a form, the Segmented Group should be used within a Form::Fieldset primitive and requires a single label.
• If used within a filtering pattern, no label is required.

Related

• Button
• Dropdown
• Text Input
• Select

How to use this component

Within a filter pattern

<Hds::SegmentedGroup as |S|>
  <S.TextInput @type="search" placeholder="Search" aria-label="Search" />
  <S.Dropdown as |DD|>
    <DD.ToggleButton @color="secondary" @text="Across" @count="2" />
    <DD.Checkbox checked>Metadata</DD.Checkbox>
    <DD.Checkbox checked>Tags</DD.Checkbox>
    <DD.Checkbox>Service name</DD.Checkbox>
  </S.Dropdown>
</Hds::SegmentedGroup> 

For complex filters we recommend grouping related filter criteria into a Segmented Group.

<Hds::SegmentedGroup as |S|>
  <S.Dropdown as |DD|>
    <DD.ToggleButton @color="secondary" @text="Health status" />
    <DD.Checkbox>Passing</DD.Checkbox>
    <DD.Checkbox>Warning</DD.Checkbox>
    <DD.Checkbox>Failing</DD.Checkbox>
  </S.Dropdown>
  <S.Dropdown as |DD|>
    <DD.ToggleButton @color="secondary" @text="Source" />
    <DD.Checkbox>Consul</DD.Checkbox>
    <DD.Checkbox>Kubernetes</DD.Checkbox>
  </S.Dropdown>
  <S.Dropdown as |DD|>
    <DD.ToggleButton @color="secondary" @text="Type" />
    <DD.Checkbox>Service</DD.Checkbox>
    <DD.Checkbox>Debug service</DD.Checkbox>
  </S.Dropdown>
</Hds::SegmentedGroup>

Within a form

When used within a form we recommend using component composition, passing a SegmentedGroup in a Form::Field. The Form::Field exposes two attributes, id and ariaDescribedBy, that are used to associate the input with the label, helper text, and error.

<Hds::Form::Field @layout="vertical" as |F|>
  <F.Label>New API Key</F.Label>
  <F.HelperText>Your org must have at least one key and at most five keys</F.HelperText>
  <F.Control>
    <Hds::SegmentedGroup as |S|>
      <S.TextInput id={{F.id}} aria-describedby={{F.ariaDescribedBy}} size="32" />
      <S.Button @color="secondary" @text="Generate" />
    </Hds::SegmentedGroup>
  </F.Control>
</Hds::Form::Field>

Generic Segment

Use the Generic block to pass custom Segments to the group". The predefined Segments adjust their styles automatically depending on their placement within the group. You will need to ensure similar styling for your custom Segment.

<Hds::SegmentedGroup as |S|>
  <S.TextInput aria-label="input leading generic segment" size="32" />
  <S.Generic>
    <Doc::Placeholder @text="generic segment" @height="36" @background="#eee" />
  </S.Generic>
</Hds::SegmentedGroup>

Component API

Contextual components

The following predefined Segments can be passed into the Segmented Group as yielded components: Button, Dropdown, Select, TextInput. For bespoke Segments use the Generic block and style it accordingly.

Anatomy

Base component

Segment anatomy

The Segments contained within a Segmented Group are extensions of Helios form components and have the same anatomy as the main components they extend. For more information on the specifications of each Segment, refer to their respective documentation:

• Button
• Dropdown
• Text Input
  • Text
  • Password
  • Search
  • Date and time
• Select

States

The Segmented Group doesn’t have its own state intrinsically; instead, the nested Segments should maintain their own interactive state corresponding with the main component specs.

Conformance rating

You must make sure each TextInput or Select segment has an accessible name, either by associating them with a <label> element, or by setting an aria-label on each input control.

Applicable WCAG Success Criteria

This section is for reference only. This component intends to conform to the following WCAG Success Criteria:

Support

If any accessibility issues have been found within this component, let us know by submitting an issue.