Hi @Richard-SNN
I feel like I’ve read this suggestion before …
Still a great idea!
One issue with this is, that I would start only building triggers in buttons and then call them from anywhere… and than start hiding all that buttons… so: Why the button?
That’s why we already discussing triggers to be saved separately (like the variables window or the record placeholder tab or so) and then call them from where ever you like.
That way you can build a trigger library, you can call from a button, a step, an input widget…
What do you think? That’s basically exact what you suggested, but without the button if you don’t need it!
Here are some threads around this Idea…
- Global trigger editor - Product Suggestions - Tulip Community
- Quality of Life: Triggers Library - Product Suggestions - Tulip Community
- Point to other trigger function within trigger - Product Suggestions - Tulip Community
So you dont need a new thread, you can add your thougts right there… 