Workflow triggers: the client invents server state #1951
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1951
Reference in new issue
Block a user
After arming, pausing or resuming a binding or schedule, the UI sets a hard-coded next status instead of the server's response. Call-graph semantics (
workflow.call, handoff, approve) are re-implemented inworkflow-triggers.ts, and a new schedule's defaults are invented client-side.Done when: statuses come from responses, starts-via is served, and defaults come from the server.
Fixed in
ecf4e6b9. Approve, Pause and Resume on event and schedule triggers show the status the server returns (the transition endpoint answers with the binding), not a hard-coded next state. The trigger list reads the playbooks resource itself instead of relying on another page having loaded it, and a failed read keeps the lists already shown beside the error. The new-schedule defaults matched the Schedules page exactly, so both now share blankSchedule() in schedules/schedule.ts. Serving the call graph (startsVia) needs a server change and is filed as #1960 (serve what starts a workflow). Checked the trigger card and Add schedule in the browser. task check passed.