Repository navigation
Filter schedules by workflow type in Waterline #226
Description
Current preparation
Draft #245, head 73d90f27130eac1c3b77f4f42155870ccc25ec70, tree 96155fb1dcfd35b570006b22d431e4b7c72e4de4, adds combined translated status/type/query controls, applied-filter persistence, explicit Retry and stale-response rejection. Embedded workflow-type filtering combines with status and namespace. Both controllers reject malformed inputs rather than returning an unfiltered success. Local 135 frontend tests/build and 41 PHP tests/508 assertions pass.
Real embedded browser acceptance passes six filter/refusal/recovery cases across both themes at desktop, tablet and mobile widths, plus existing namespace row actions. The current head adds retained JSON/screenshots; fresh full qualification is pending. Website #404 prepares all eight CLI/API references, supported by normal published CLI/Server evidence.
Full embedded visibility-query parity remains unfinished accepted work under shared #224. Namespace typed-definition lookup and the reusable Core query contract belong to that coordinated work. Until available, this draft explicitly refuses embedded queries with 501 backend_capability_unavailable / schedule_visibility_query and malformed inputs with 422. Full embedded/service query and shipped-theme/locale acceptance remain required. This subset does not complete #226. Draft #245 targets main after #244; the independent corrective 2.13.2 release stays separate.
Problem
Operators can't find the schedules that start a given workflow type in Waterline.
- The Server's schedule list accepts
workflow_typeand a visibilityquery, anddw schedule:listhas--typeand--query. - Waterline's schedules screen has only a status filter and sends only
status. It shows a Workflow Type column but can't filter on it. - In embedded mode, Waterline's schedules API filters by status only. It ignores
workflow_typeandquery, though the service-mode controller passes them through.
The website references don't mention these filters: dw schedule:list lists only global options, and GET /api/schedules lists no parameters.
Acceptance criteria
- The Waterline schedules screen can filter by workflow type and by a schedule visibility query, in both embedded and service mode.
- The embedded schedules API applies
workflow_typeandquerywith the same meaning as the Server, with tests. - The website CLI and Server API references document the schedule list filters.
Activity
rmcdaniel commentedon Oct 21, 2026
Accepted as a Waterline feature with embedded/service parity, rather than a documentation-only fix. After the active P1 work, add workflow-type and visibility-query controls and apply their filters in both backend modes, preserving namespace scope and the existing query grammar.
Acceptance includes actual embedded and service API requests, combined status/type/query filters, invalid-query feedback, and real browser use in the shipped themes and locales. The CLI and Server API references should describe the already-supported filters alongside the qualified UI behavior.