[UI] Allow defining triggers directly from the Flow/Trigger tab instead of editing the YAML flow #3288
Comments
fhussonnois
added
area/backend
|
We could add a button here, something like "Add a trigger"
And this would then navigate to the Code Editor with the form open on the right with the option to select a trigger equivalent to this option
Would it satisfy the user's request? (seems like a good idea to make that empty trigger table more actionable) |
|
@anna-geller,I'm sorry, I just realized that there's already a panel for adding triggers from the Editor/Actions button. But, this one is not very visible. I think your proposal to add a new button to the trigger tab is sufficient. |
tchiotludo
added
good first issue
|
Hey All, I will check this. I would like to proceed as: Would this be fine with new changes to flow ?
These buttons should switch editor to NO_CODE (similar to when we try to Edit from Topology) to add trigger from below
|
|
sounds good
keep in mind this will change fairly soon as we are revamping the Code vs No-Code Editor tabs, but for now we can do it as you described 👍 |
Feature description
Currently, if the users want to add a trigger to a new or existing flow, for example, they need to do so via the YAML editor. We should provide a friendly UI (more basically a form) to do it from the Trigger tab. This will help users to more easily discover the available triggers and their options. Eventually, we could add an
/PATHAPI to be able to add a trigger to an existing flow without the need to push back the entire flow definition. In that way, adding a trigger through the Trigger API will lead to a new flow revision.The text was updated successfully, but these errors were encountered: