GitHub user mengw15 added a comment to the discussion: Proposal: Unify Macro & Template
**On "To generate a workflow": where should Run live?** Currently the macro page has a "Run workflow" button, but clicking it actually creates a workflow first under the hood. This becomes confusing once the user leaves the page and comes back: - If the macro is a general building block (not itself a workflow), the executions launched from this page arguably should not be listed on this page at all. - Either way, UX-wise the user may no longer be able to find the execution they started — it belongs to a workflow they never explicitly saw. Two possible designs: **Design 1 — a macro *is* a workflow.** A cloned macro is a workflow; clicking Run runs it right here and never creates a new workflow. To reuse the same macro with different parameters, you clone it again. **Design 2 — a macro is where workflows get created.** One macro can create multiple workflows with different parameters. In this design I do not think the macro page should run anything directly: the button should be "Create workflow", which jumps to the generated workflow's canvas, and the user clicks Run there. I lean toward Design 2. With Design 1, macros and workflows sit in separate tabs yet both are effectively "workflows" — that is confusing and not a good design language. Design 2 adds a small learning curve, but all the user needs to learn is to click the Run button on the canvas; the macro author can also put a tutorial in the macro description (which can be markdown). It also resolves the "a run keeps running in the background and stays findable" feedback above for free — the execution lives with the created workflow, not with the macro page. And it stays consistent with what was agreed in #6070: each generation produces a new, normal workflow the user owns. GitHub link: https://github.com/apache/texera/discussions/7368#discussioncomment-17937913 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
