The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

Human-readable display name for the saved view shown in user interface view selectors, dropdowns, and view management screens. Typically 2-50 characters describing the view purpose such as High Priority Tasks, Q4 Marketing Programs, or My Open Requests. User-defined and can be updated after creation. Should be unique within the space for clarity but uniqueness is not enforced. Use descriptive names that clearly convey the filtering, sorting, or grouping applied in the view to help users quickly identify and select the appropriate view configuration.

Display mode type indicating whether this saved view uses grid/list layout for tabular data display or timeline/gantt chart visualization for chronological project views. Must be either list for table-based views with rows and columns, or timeline for date-based gantt-style displays. Determines which UI components are rendered and which state properties (gridState vs timelineState) are relevant when loading the view. Use list for filtering, sorting, and analyzing data in table format. Use timeline for visualizing task schedules, program phases, and date-based dependencies.

Resource type that this saved view applies to, indicating whether the view filters and displays programs, requests, or tasks. Must be one of programs for program management views, requests for request form submission views, or tasks for task tracking views. Determines the entity type shown when the view is loaded, which API endpoint is called to fetch data, and which properties are available for filtering, sorting, and column display. Each saved view is scoped to exactly one route. Use to organize views by resource type and ensure correct data fetching and UI rendering when the view is activated.

ag-Grid filter model object defining active column filters for the saved view. This complex object structure uses column field names as keys, with each value being a filter configuration object specific to that column type. Text filters include filterType and filter value properties, number filters use type (equals, lessThan, greaterThan) with filter value, date filters contain dateFrom and dateTo for range filtering. The structure follows ag-Grid filter model conventions where each key represents a column ID and its value describes the filter criteria applied to that column. Use this to persist user filter preferences such as showing only high priority items, filtering by specific assignees, or limiting results to date ranges. Set to null or omit to create a saved view with no filters applied. Example shows priority column filtered to high value.