Repository navigation
[EPIC] CD: Workflow Actions Follow Up #37428
Description
Description
Follow up to #33999 ([EPIC] CD: Workflow Actions), which delivered the Workflow Center itself: bulk actions grouped by scheme with counts, the item preview, the quick actions, Push Publish, and the configuration step. An editor can open a selection and fire an action without leaving Content Drive.
What #33999 did not settle is everything around the run. A bulk run today is fire-and-forget over whatever rows are on screen: the selection cannot exceed the current page, the grid gives no sign that an action is in flight, and the result comes back as a total rather than an outcome per item.
This epic closes that. Its children belong together because they are one object seen from three sides: a run needs a scope, a lifecycle, and a per-item outcome. Settled separately they contradict each other, so they are designed as one.
Scope
| Child | Concern |
|---|---|
| #36981 — Select all results across pages, with per-row exclusion | Scope: what a selection is, and how large it can be |
| #37049 — Define in-flight behavior | Lifecycle: what the UI does while a run is in flight, and on navigation |
| #36894 — Per-item execution results | Outcome: what the user learns about each item afterwards |
Unlike #33999, which was frontend work over endpoints that already existed, this epic carries backend scope as well.
Desired Outcome
An editor can run a workflow action over an entire filtered result set, see that it is running, and see what it did to each item.
- Acting on a whole result set works, not just the rows currently on screen
- While an action is in flight the UI says so, and the user cannot start a conflicting one
- Leaving mid-run produces a defined, honest outcome rather than silence
- Per item, the user sees whether it succeeded, failed, or was skipped, and why, and can retry the failures
- Where a capability cannot be honored for a given selection, it is withheld with a visible reason rather than quietly applied to a subset
- Editors stop bouncing to the legacy content-search portlet for bulk workflow operations at real content volumes
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Links
- Predecessor epic: [EPIC] CD: Workflow Actions #33999 · Pillar: [Pillar] Content Drive #33171 · Product Feature with mockup: [FEATURE] Enable select all checkbox for page and for table #33338 · Legacy precedent, closed unimplemented: Content Search "Select All" #26317
Naming: users see Workflow Center; the code and i18n keys keep the action-center prefix.
Activity
[-][EPIC] CD: Workflow Actions Follow Up: run scope, in-flight state, and per-item outcomes[/-][+][EPIC] CD: Workflow Actions Follow Up[/+]name_copy_1) instead of appending_copyagain #37894