Skip to main content

​
Filter bars and filter definitions

Filter execution is based on filter definitions that contain:
  • Display columns
  • User inputs
  • Constraints
  • Sorting
You can create, edit, and delete user-defined filter bars. The filter designer provides dedicated editors for each definition section. Filter definitions are managed through the Search configurator.

​
User input parameterization

User input parameters support:
  • Typed controls based on data type
  • Operator selection
  • Required-field enforcement before search execution

​
Result table capabilities

The Caseflow result table includes:
  • Column sorting
  • Per-column typed filtering with dedicated UI per data type — see Typed column filters
  • Global text search
  • Virtualized rendering for large result sets
  • Sticky/pinned columns
  • Hide/show columns
  • Drag-to-group and hierarchical group expansion
  • Row selection including shift-range selection
  • Bulk edit and bulk delete for selected rows — see Bulk operations
  • Inline cell editing by double-clicking an editable cell — see Inline cell editing
  • Object context menu with permission checks

​
Typed column filters

Each result column exposes a filter button in the column header. Clicking the button opens a control whose UI matches the column’s data type. Active filters are visually marked on the button so you can tell at a glance which columns are constraining the result set. All filter controls have a Clear action to reset that column without touching others. Filters are dispatched by the ColumnFilterControl router, which picks the right filter UI based on the column’s detected data type.
Which attributes appear as filterable columns is controlled by the Filterable in tables flag in Attribute administration. Attributes without the flag set are still queryable through the Search configurator but do not show a column filter button in the result table.

​
Bulk operations

When one or more rows are selected, a Bulk action bar appears at the bottom of the table showing the selection count and the available bulk actions. Selection supports click, shift-click range selection, and a header checkbox for “select all rows currently visible.”

​
Bulk edit

The Bulk edit popover lets you change a single attribute on every selected row at once.
  • Pick the attribute to edit from a dropdown (only attributes flagged as Editable in bulk are listed)
  • Enter a single new value using the same control the inline editor uses for that data type
  • Apply — the platform updates rows in batches of 5 to keep the UI responsive
System attributes (object ID, created date, and so on) are blocked from bulk edit. Attributes that are not flagged editable in administration are not offered.

​
Bulk delete

The Bulk delete action removes every selected row, after a confirmation dialog. Permission is checked per-row — rows the user cannot delete are skipped and reported in the result summary.

​
Inline cell editing

Double-clicking a cell in the result table opens an inline editor for that single value, scoped to that row. The editor matches the column’s data type: Press Escape to cancel without saving. Cells whose data type is not editable inline (relations, documents, computed values) show an indeterminate state when double-clicked. Inline editing respects the same permission and validation rules as EditableField in templates: validation errors block the save, and attribute-level permissions hide editing from users without the right.

​
Command bar

The Command bar is a global quick-access palette opened with Ctrl+K (or ⌘+K on macOS). It lets users jump to anywhere in Caseflow without navigating menus. Recent items are stored locally and persist across sessions. Saved searches show their folder breadcrumbs so palette results stay unambiguous when names overlap across folders.

​
Search operators

These operators are available for ObjectSearch constraints and filter definitions:

​
Action condition operators

For when conditions in action expressions, prefer text-safe comparisons where HTML quoting can be tricky: See Templates and syntax for the full conditional expression reference.

​
Boolean representation

Boolean values in Caseflow often appear as:
  • "1" / "0"
  • "true" / "false"
Template and action logic should normalize expectations accordingly. When comparing booleans in conditions, test for both forms or use isTrue/isFalse operators.