You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Form View: a form-based view for running a workflow #8011
Today a workflow can only be used through the operator canvas. That's the right tool for authors, but
too much for someone who just needs to change a couple of inputs, run, and read a result.
Form View is a second, form-based view of an existing workflow. An author marks selected
operator properties as "exposed"; a reader opens the same workflow as a simple form, fills in those
inputs, runs it on a computing unit, and sees the results the author chose to surface. It edits the
same workflow the canvas does, never a copy. Every workflow can be opened in either view when the
feature flag is on; a per-workflow default_view preference (canvas or form) chooses which view it
opens in, and either view can switch to the other at any time. The whole feature is gated behind a
form-view-enabled config flag (default off).
Proposed Solution or Design
A new /user/workflow/:id/form page (WorkflowFormComponent) reusing the existing workflow graph model, the read-only workflow-editor + mini-map preview, and the property editor. The form is a lens over the same shared graph, not a fork.
Authoring: in the property editor, tick which properties are exposed and give each an editable label, backed by a form-binding service that owns the operator-to-field bindings.
Reader: exposed bindings render as ngx-formly fields; edits write back to operator properties; an optional author instruction (markdown) shows above; run/stop reuses the canvas run-button state machine plus a computing-unit selector; chosen results render as cards.
Persistence: a default_view enum column (CANVAS or FORM) on the workflow with a set-default-view endpoint, carried through workflow listing/search, so the dashboard opens each workflow in its default view without parsing content.
Feature flag: form-view-enabled (served via /api/config/gui as formViewEnabled), default off, gating every entry point (the dashboard card opens in the workflow's default view plus a per-card toggle, the route, and the canvas menu view switch).
Feature Summary
Today a workflow can only be used through the operator canvas. That's the right tool for authors, but
too much for someone who just needs to change a couple of inputs, run, and read a result.
Form View is a second, form-based view of an existing workflow. An author marks selected
operator properties as "exposed"; a reader opens the same workflow as a simple form, fills in those
inputs, runs it on a computing unit, and sees the results the author chose to surface. It edits the
same workflow the canvas does, never a copy. Every workflow can be opened in either view when the
feature flag is on; a per-workflow default_view preference (canvas or form) chooses which view it
opens in, and either view can switch to the other at any time. The whole feature is gated behind a
form-view-enabled config flag (default off).
Proposed Solution or Design
A new /user/workflow/:id/form page (WorkflowFormComponent) reusing the existing workflow graph model, the read-only workflow-editor + mini-map preview, and the property editor. The form is a lens over the same shared graph, not a fork.
Delivered as stacked sub-issues, bottom-up:
Follow-ups (post-MVP)
Rollout: the flag stays off through the whole stack; the final entry-points PR flips it on and wires the entry points.
Affected Area
Storage / Metadata, Workflow UI