Filter persistence in collection views

State persistence

Users may need to navigate away from a collection and then return within a flow. These users expect their filters or collection preferences to persist upon returning to the page to prevent data loss.

Easy sharing of collection views

Data persistence in URLs is especially helpful for users who may need to share a specific collection view. When the URL is copied from one user and shared with another, the recipient will be able to see the specific collection view within the page without manually applying filters and/or preferences.

On a page where data should persist in the URL, make sure the URL is updated whenever a user makes changes to a collection view.

Filters

Changes to filters are defined as any action taken on a filter within a collection. For example:

• User adds a new filter to a collection

• User removes a filter from a collection

• User edits a property filter token

Collection preferences - optional

You can persist specific collection preferences in the URL to capture an entire collection view beyond a collection’s filters. For example:

• Page size

• Visible columns

When a user enters a page, check if the URL contains any persisted data like filters or collection preferences, and apply them to the relevant filtering component immediately. Discard any parts of the loaded data that is not valid.

Ensure that components consuming data from the URL remain controlled, and treat the URL as the single source of truth for data. See example implementation in saved filter sets and property filter demos. Note that these examples only include persistence for property filtering.

Security considerations

Ensure that all raw data extracted from the URL is properly validated against your expected data format before it is processed by the rest of your application or passed to a Cloudscape component. If invalid data is detected, default to a valid option to maintain a secure and seamless user experience. Additionally, ensure compliance with relevant security policies and best practices, such as encoding data properly and using secure transmission protocols.

Consider the following cases:

• What goes into the URL:

  Avoid including sensitive information to prevent potential data exposure.

• What is read from the URL:

  Validate the data coming from the URL to mitigate risks from maliciously crafted URLs.

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.

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.