The Edit CaseFacts batch action lets you set or delete CaseFacts in several files at once — directly from the case list or a filter view. Until you explicitly Apply, every input is a purely visual preview; nothing is persisted before confirmation.
Prerequisites
Permission "Batch Action CaseFacts" in the File > Bulk processing group. Without it, the "Edit CaseFacts" chip is hidden in the FloatingAppBar.
No CaseFact schema migration running in the current client.
Behaviour during a schema migration
While a CaseFact schema migration is in progress in the client:
the cursor on the chip is
not-allowed,a tooltip says "CaseFacts are being migrated",
if a migration starts while the sidebar is already open, the confirmation modal shows an error on apply and stays open so the user can retry.
Entry, scope and client control
Entry point
Tick one or more files in the case list or a filter view. In the FloatingAppBar that appears, click the "Edit CaseFacts" chip — the CaseFacts side panel opens on the right.
Scope indicator
The primary action button in the side-panel footer states the scope explicitly: "Change in N files", e.g. "Change in 12 files". N matches the number of files ticked in the list.
Client control
Which topics the panel offers depends on the clients of the selected files:
Files from a single client: global and client-specific topics are shown.
Files from multiple clients: only global topics are shown.
Only topics that actually exist in the selected clients are listed — topics that do not occur in the selected files are hidden.
Side-panel layout, editing and deleting values
Layout
The side panel reuses the layout of the existing "Check CaseFacts" action inside a single file: topics as grouped sections, fields with label and value. The action buttons (Apply, Cancel) are pinned to the panel's footer and stay visible while scrolling.
Aggregate values across multiple files
All files share the same value for a fact: the actual value is shown in the input.
Files have different values for a fact: the input shows the placeholder "Different values across files". Entering a new value replaces the existing value in each file on apply.
Inline editing
As soon as you enter or pick a new value for a fact, the field gets the chip "edited" and a reset button (↺) appears.
Inline deletion
Clicking the trash icon marks a field for deletion: the value turns red, the chip "deleted" appears next to the field, and the trash button gets a red background. Clicking the trash button again clears the deletion.
Reset an edit
The reset button (↺) reverts a pending edit or deletion before apply. Effect: the original value is restored, the "edited"/"deleted" chip vanishes, the reset button disappears.
Filter, search and empty states
The side panel provides two cumulative filters:
Label search
Typing filters visible facts to those with a matching label.
Topics without matches are hidden entirely.
No matches: empty state is shown.
"Changed only" toggle
Active with no changes present: empty state.
Active with at least one fact edited or deleted: only those facts are shown.
Combining search and "Changed only"
Both filters apply cumulatively — only facts matching both conditions remain visible.
Field groups and table facts
Field groups are tabular facts with multiple columns per row. The batch action supports adding, editing and deleting rows — the controls match the existing single-file UI.
Single file selected: full preview
With exactly one selected file, all field-group values render as usual. Available row actions:
"+" — add a new editable row; the "+" button is disabled while this row is unsaved.
"✓" — save the populated row; it becomes read-only and the edit button ("✎") appears.
"✎" — re-enter edit mode for a saved row.
Row trash — delete a single row.
Multiple files selected: no per-file preview
With multiple files selected, no cross-file preview is possible. The panel shows the hint "Preview across files not possible". Permitted operations:
fully clear the field group via the group trash,
add new rows.
Editing individual existing rows across files is not supported — use the single-file workflow for that.
Group trash
Clicking the group trash marks the entire field group for deletion, provided no new rows are unsaved. Effect: a "deleted" chip appears in the footer bar and the field group is flagged as marked for deletion.
Apply and confirmation modal
Action button state
No changes present: the action button is disabled.
At least one fact edited or deleted: the action button is active and labelled "Change in N files".
Confirmation modal
Clicking the action button opens the confirmation modal with:
the prompt "Do you want to change X facts in Y files?",
a summary of the changed fields before apply,
"Yes": apply starts and the side panel closes,
"No": only the modal closes; the side panel remains open with all pending changes intact.
Apply logic
Only facts that were edited or deleted are written — untouched fields are left alone. If a schema migration starts while applying, the modal surfaces an error and stays open.
Notifications and errors
Notifications
Start: notification with progress bar as soon as the apply starts.
End: notification on completion; auto-dismisses after a few seconds and shows the actual number of changed files.
Both notifications carry a link to the batch processing history.
Per-file security
Client permissions are validated in the backend per file at apply time. If the user lacks access to a file, that file fails — the remaining files are still processed.
Partial failures and CSV email
If individual files fail, the triggering user receives an email with a CSV attachment (columns: case ID, file number, label, value, error message) and a link to the batch processing history.