GitHub user yangzhang75 added a comment to the discussion: Proposal: Workflow Templates — save a workflow as a reusable, parameterized template
That framing makes sense to me. A few follow-up thoughts: 1. Preview vs linked workflow: with the lock gone, my current split is that the preview under the Templates page stays read-only (users can run but not edit; any modification means generating a linked workflow first), and the linked workflow on the Workflows page is fully editable like any other workflow. Does that match how you'd expect it to work? 2. Template page UX: since the linked workflows live on the Workflows page, would it help to add a button on the Templates page that jumps directly to the user's linked workflow (already editable), so users don't have to switch pages to find it? 3. Parameter versioning: after a user edits parameters in their linked workflow, should the template's default parameters update to the latest submitted version (so future users start from the most recent state), or stay locked to the values the template author originally set? Updating feels easier to keep in sync, but keeping the original feels safer against accidental drift. GitHub link: https://github.com/apache/texera/discussions/6070#discussioncomment-17533773 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
