GitHub user mengw15 added a comment to the discussion: Proposal: Workflow Templates — save a workflow as a reusable, parameterized template
1. Before answering the four questions, I think we should first be clear about what a template is. In my understanding, a template is a tool that helps users create workflows. Like printing: a plate exists to produce many copies, so a template should be able to produce multiple workflows — that is the semantically correct model. I think 1-to-1 is acceptable as an MVP product, but on the roadmap 1-to-many is a must. 2. Second, a workflow created from a template is no different from a normal workflow — the only difference is how it was created. Since there is no difference in what it is, the way we treat workflows should not change because of this feature. As for the case where some users don't want to click into a workflow just to run it — that is orthogonal to templates. We can address it later with options like a "run workflow / export result" button directly on the workflow dashboard. (Following the same logic, I'd lean toward letting the owner freely edit a template-generated workflow like any other, rather than keeping it locked to the whitelisted parameters.) 3. Third, template-generated workflows should appear on the main Workflows page. I agree with @chenlica that we can add a special tag to distinguish them. 4. Fourth, once a workflow has been generated from a template, it is a workflow — so it should always remain visible, regardless of whether this feature is turned on or off. To use another example: today a user can create a workflow either by uploading a workflow JSON or by building it manually. Whether or not the JSON-upload feature continues to exist, I believe those workflows should always continue to exist. GitHub link: https://github.com/apache/texera/discussions/6070#discussioncomment-17520036 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
