GitHub user mengw15 added a comment to the discussion: Proposal: Workflow Templates — save a workflow as a reusable, parameterized template
Agreed on the motivation — the goal is to give users who find the canvas too complicated a simple, form-based way to create a workflow. On "a template is NOT designed to create multiple workflows": understood, but I think purpose and cardinality are orthogonal — "mass production is not the goal" doesn't mean the design should assume exactly one workflow per template. In fact, I think your preference on the key question settles the cardinality question. The rationale for 1-to-1 was that "any template change naturally flows to that workflow" — i.e., 1-to-1 exists to make propagation easy. If we prefer no propagation (which I agree with: easier maintenance, and no surprises for the workflow owner), then that rationale goes away, and nothing else in the design requires 1-to-1. Meanwhile sharing already produces multiple instances naturally: a template shared with N users gives each of them their own workflow, and even a single user may run the same pipeline on two datasets and keep both. So the clean model is exactly what you suggested earlier: the generated workflow just stores the template ID, workflows evolve independently after creation, and no structural assumption of 1-to-1 anywhere. GitHub link: https://github.com/apache/texera/discussions/6070#discussioncomment-17536516 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
