Views

You can preserve the current state of the table you're viewing by saving its filters, groupBy, sorting, and column visibility settings. Access the options through the top-right dropdown menu, where you can save the current configuration as a new view, update an existing view, or load predefined view configurations.

By default, these views are stored at the application level and are editable by users with access to the application. However, the creation, saving, or deletion of new views requires users to have a specific role.

Users have the flexibility to modify the view by adjusting its configuration, such as changing filters. Unsaved changes are reflected in the URL as query parameters, identified as "overrides," facilitating users in sharing the table's state by copying the URL. It's essential to note that unsaved changes are lost upon leaving the page, while the selected view is tracked and loaded when the user returns to the page.

Overrides

Overrides are stored in the URL as query parameters, indicating unsaved changes. The URL specifies the selected view number, tracking and storing it for loading the view configuration when the page reloads. Overrides can be saved to an existing or new view, incorporating the view configuration along with the overrides. Notably, overrides are both additive and subtractive, leveraging attribute=* override to remove existing filters, sorts, groupBy, or column visibility settings. After saving or updating a view, overrides are no longer present in the URL as they become part of the view's configuration.

Redirects

Internal redirects include the redirected=true flag, signaling the use of the URL-specified configuration instead of loading the full view configuration. This process overwrites and discards unsaved views, utilizing the last selected view's column visibility settings for redirects.

Global default views

ASTA features system default views for each page, universally applicable across workspaces, applications, and variants. Exclusively modifiable by system administrators, these default views come into play when an application's view is removed or lacks available views.

Special filters

When a filter is required but unspecified, the system defaults to a predefined setting. For instance, not specifying a runId for the log results in the system using the latest runId.

Permissions

Only users with member+ permissions can create or edit views, while owners retain the exclusive capability to remove views.