yangzhang75 opened a new pull request, #8125:
URL: https://github.com/apache/texera/pull/8125
### What changes were proposed in this PR?
Let the backend remember, per workflow, whether it is offered as a Form
View, and expose turning that on/off. Backend + DB only; no UI or form logic.
- **Schema**: new column `workflow.is_form_view BOOLEAN NOT NULL DEFAULT
false` (`sql/updates/43.sql`, `changelog.xml`, `texera_ddl.sql`).
- **Write**: `PUT /enable-form-view/{wid}` and `/disable-form-view/{wid}`,
guarded by write access. They update only that column — never rewriting content
or bumping the modified time. A plain save preserves the stored value; a
duplicate and a hub-clone both inherit it.
- **Read**: `UnifiedResourceSchema` and `WorkflowSearchQueryBuilder` include
the flag in listing/search; `WorkflowVersionResource` carries it across
versions; `retrieveWorkflow` / `retrievePublicWorkflow` report it.
Naming note vs the issue: the flag is `is_form_view` (not
`is_parameterized`) and the endpoints are `enable`/`disable-form-view`, per the
Form View rename; the migration is `43.sql` because `42.sql` was already taken
on main.
### Any related issues, documentation, discussions?
Closes #8014. Part of the Form View parent issue #8011; builds on the
feature flag from #8013.
### How was this PR tested?
`WorkflowResourceSpec` — 9 new cases covering: enable/disable toggle,
rejection without write access, survival across a plain save, inheritance by
both `duplicateWorkflow` and `cloneWorkflow`, reporting by both retrieve paths,
and `formBinding` preserved on disable. Full suite 78/78 green. Compiled and
run against an ephemeral Postgres so jOOQ regenerated the `is_form_view` column.
### Was this PR authored or co-authored using generative AI tooling?
Co-authored with Claude Code.
--
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]
