Cloudscape Design System
  • Get started
  • Foundation
  • Components
  • Patterns
  • Demos
  • GitHub 
Cloudscape Design System
  • Get started
  • Foundation
  • Components
  • Patterns
  • Demos
  • GitHub 
  • About

Patterns


  • General

    • Actions
      • Global actions
      • In-context actions
    • Announcing new features
    • Announcing beta and preview features
    • Communicating unsaved changes
    • Data visualization
      • Chart metric drill down
    • Density settings
    • Disabled and read-only states
    • Drag-and-drop
    • Errors
      • Error messages
      • Validation
    • Empty states
    • Feedback mechanisms
    • Filtering patterns
      • Saved filter sets
      • Filter persistence in collection views
    • Hero header
    • Help system
    • Image magnifier
    • Loading and refreshing
    • Onboarding
      • Hands-on tutorials
    • Selection in forms
    • Service navigation
      • Side navigation
      • Top navigation
    • Service Dashboard
      • Static dashboard
      • Configurable dashboard
      • Dashboard items
    • Secondary panels
    • Timestamps
    • User feedback

  • Generative AI patterns

    • Pattern abstraction
    • Generative AI chat
    • Ingress
    • Generative AI output label
    • Generative AI loading states
    • Progressive steps

  • Resource management

    • Create resource
      • Multipage create
      • Single page create
      • Sub resource create
    • Delete patterns
      • One-click delete
      • Delete with simple confirmation
      • Delete with additional confirmation
    • Edit resource
      • Page edit
      • Inline edit
      • Attribute editing
    • View resources
      • Table view
      • Card view
      • Split view
      • Table with expandable rows
    • Resource details
      • Details page
      • Details page with tabs
      • Details page as a hub
  1. Cloudscape Design System
    • Patterns
    • General: Filtering patterns
    • Saved filter sets
    1. Cloudscape Design System
    2. Patterns
    3. General: Filtering patterns
    4. Saved filter sets

    Saved filter sets

    Enable users to save filter configurations as filter sets and quickly apply them in a collection of resources.

    Published: September 28, 2023
    View demo

    On this page

    1. Key UX concepts
    2. General guidelines
    3. Common flows
    4. Features
    5. Writing guidelines
    6. Accessibility guidelines
    7. Related patterns and components

    Did this page help you?

    Tell us more - optional

    1000 character(s) available. Do not disclose any personal, commercially sensitive, or confidential information.

    Key UX concepts

    Streamline filtering process

    Setting customized filter configurations on every visit in the table or cards view is a repetitive task for users. By saving the configuration as filter sets, users can reuse the saved filter sets, and quickly apply them in the collection view. This increases work agility, enhances work efficiency, and reduces cognitive memory load when users revisit the collection view.

    Filter sets configuration

    Users can create, update, and delete filter sets to customize the filtered collection view. Filter sets can be user generated, or provided by default by your service. When users navigate away and return to the page, retrieve the latest filter set applied to the collection view.

    Return to the previous state

    Users should be able to quickly revert temporary changes, or to correct mistakes to the saved filter set. Allowing users to easily transition out of the temporary changes, and go back to the previous state, will increase user control and satisfaction. 

    General guidelines

    Do

    • Use groups to categorize the saved filter sets created by users, and the saved filter sets provided by your service.
    • Limit the amount of filter controls provided in the collection view when using saved filter sets feature. Use property filter to filter for additional properties such as date or properties in custom form.
    • Include auto filtering in the saved filter sets dropdown for large number of filter sets.
    • Always use a confirmation modal to delete a filter set, or update an existing one.
    • Expose only the most needed metadata associated to a filter set to avoid visual clutter.

    Common flows

    Save a new filter set

    After users apply filters to the collection view, they can save the configuration via the save button in the actions dropdown. Display a modal with form fields for users to:

    • Provide a name for the filter set.

    • Add a description to the filter set - optional.

    • Set the filter set as default view - optional.

    • Add other additional metadata relevant for your service, for example permissions.

    Use client-side validation when creating a new saved filter set:

    • Display an error message when the name is a duplicate.

      • For example: The name already exists in the system, choose another one.

    • Display an error message when the name doesn’t match the constraint requirements.

      • For example: The name has too many characters.

      • Follow the guidelines for form field and validation.

    Display a success or error flashbar to communicate the outcome of the operation.

    Use the saved filter sets

    Users can apply a saved filter set by choosing it among the list of filter sets.

    Saved filter sets will be displayed with the related name, and any additional metadata relevant for the user to distinguish the filter sets quickly (for example, creation date).

    Update current filter set

    After users have drafted changes to the current saved filter set, an “unsaved” label should be displayed next to the saved filter name, to communicate the temporary change. 

    Users can decide to overwrite the previous filter set configuration with the new configuration via the update button in the actions dropdown. 

    Display a modal with the previous and updated filtering tokens to support comparison, and ask users to confirm the change via simple confirmation. 

    There are multiple ways for users to revert the temporary changes, including:

    • Selecting the original filter set in the filter sets dropdown.

    • Removing or adding filtering tokens to match the original configuration.

    • Using the “clear filters” action to remove the filter set applied to the collection.

    Display a flashbar to communicate the outcome of the operation. 

    Delete current filter set

    Users can delete the saved filter set when it is no longer relevant for their task completion. A delete action is provided in the action dropdown, and users can confirm the deletion with a simple confirmation modal.

    Display a flashbar to communicate the outcome of the operation. 

    Features

    A.
    Filter sets select

    Include a select to host the filter sets via customControl in property filter.

    B.
    Filter set actions

    Use a normal button dropdown with main action to display clear, save, update, and delete actions via customFilterActions in property filter.

    C.
    Property filter

    Users can apply saved filter set to a collection view in property filter.

    Writing guidelines

    General writing guidelines

    • Use sentence case, but continue to capitalize proper nouns and brand names correctly in context.

    • Use end punctuation, except in headers and buttons. Don’t use exclamation points.

    • Use present-tense verbs and active voice.

    • Don't use please, thank you, ellipsis (...), ampersand (&), e.g., i.e., or etc. in writing.

    • Avoid directional language.

      • For example: use previous not above, use following not below.

    • Use device-independent language.

      • For example: use choose or select not click.

    Component-specific guidelines

    Actions

    • For the action to save new filter set, use this text: Save as new filter set

    • For the action to update current filter set with new changes, use this text: Update current filter set

    • For the action to delete current filter set, use this text: Delete current filter set

    • Follow the writing guidelines for button dropdown.

    Alert

    • For the default message use this text:

      • In update filter set modal: Proceeding with this action will change the saved filter set with the updated configuration.

      • In delete filter set modal: Proceeding with this action will delete the saved filter set and corresponding configuration.

    • Follow the writing guidelines for alert.

    Constraint text

    • Follow the writing guidelines for form field.

    Filter sets select

    • For the filters set select label, use this text: Saved filter sets

    Modal

    • For the modal header to save a new filter set, use this text: Save filter set

    • For the primary action button of the modal to save a new filter set, use this text: Save

    • For the modal header to update current filter set, use this text: Update filter set

    • For the primary action button of the modal to update current filter set, use this text: Update

    • For the modal header to delete current filter set, use this text: Delete filter set

    • For the primary action button of the modal to delete the current filter set, use this text: Delete

    • Follow the writing guidelines for modal.

    Placeholder text

    • When there are no saved filter set selected, use this placeholder text: Choose a filter set

    • Don’t use terminal punctuation.

    Unsaved label

    • When there are temporary changes to current filter set, for the placeholder use the format: [the filter set name] [unsaved]

    Accessibility guidelines

    General accessibility guidelines

    • Follow the guidelines on alternative text and Accessible Rich Internet Applications (ARIA) regions for each component.

    • Make sure to define ARIA labels aligned with the language context of your application.

    • Don't add unnecessary markup for roles and landmarks. Follow the guidelines for each component.

    • Provide keyboard functionality to all available content in a logical and predictable order. The flow of information should make sense.

    Component-specific guidelines

    • Follow the accessibility guidelines for property filter and button dropdown.

    Related patterns and components

    Property filter

    With the property filter, users can find specific items in a collection of resources by using properties, property values, typing free text, and combining these with operators.

    Collection select filter

    A select filter helps users find specific items in a collection of resources by choosing one or two properties.

    Filtering patterns

    Filtering patterns let users find specific items in a collection of resources. Users can filter by exact values or by finite sets of properties.

    Did this page help you?

    Tell us more - optional

    1000 character(s) available. Do not disclose any personal, commercially sensitive, or confidential information.
    • About
    • Connect
    • Privacy 
    • Site terms 
    • © 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.
    Made with love atAWS