yangzhang75 opened a new issue, #8011: URL: https://github.com/apache/texera/issues/8011
### 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. It is offered only for workflows marked isParameterized, and the whole feature is gated behind a form-view-enabled config flag (default off). ### Proposed Solution or Design A new /user/workflow/:id/parameters 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 parameterization service that owns the operator↔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: an is_parameterized column on the workflow (migration 42) with endpoints to read/set it, carried through workflow listing/search. - Feature flag: form-view-enabled (served via /api/config/gui as formViewEnabled), default off, gating every entry point (dashboard toggle, route, canvas menu switch). Delivered as 16 stacked sub-issues, bottom-up: - [ ] formview-pr1-flag — feat(config): add form-view-enabled feature flag, default off - [ ] formview-pr2-backend — feat(workflow): persist is_parameterized and add Form View toggle endpoints - [ ] formview-pr3-types — feat(workflow): shared types and collab-model support for Form View - [ ] formview-pr4-parameterization — feat(workflow): parameterization service for Form View bindings - [ ] formview-pr56-property-editor — feat(property-editor): choose which properties the Form View exposes - [ ] formview-pr8-harness — test(workflow-form): add the shared Form View spec harness - [ ] formview-pr8a-shell — feat(workflow-form): Form View page frame — load, title bar, save - [ ] formview-pr8a2-preview — feat(workflow-form): embed the read-only workflow preview - [ ] formview-pr8b-inputs — feat(workflow-form): render the exposed inputs and write values back - [ ] formview-pr8b2-instruction — feat(workflow-form): show the author's instruction - [ ] formview-pr8c-run — feat(workflow-form): run the workflow from the form - [ ] formview-pr8d-results — feat(workflow-form): show the chosen results - [ ] formview-pr8d2-inspect — feat(workflow-form): open a step to inspect its settings read-only - [ ] formview-pr9-author — feat(workflow-form): authoring mode for building the Form View - [ ] formview-pr10-computing-unit — feat(computing-unit): remember the selected unit per workflow - [ ] formview-pr11-entrypoints — feat(workflow-form): add the Form View entry points and turn it on Rollout: the flag stays off through the whole stack; the final PR (formview-pr11-entrypoints) flips it on and wires the entry points. ### Affected Area Storage / Metadata, Workflow UI -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
