I’m sure there was a lot of discussion around this topic in several threads.
E.g.:
only global triggers could lead to some other issues.
However the Idea came up several times to just call existing triggers.
In my opinion you would need a trigger library, where triggers can be stored on app level or step level and just get called from wherever you are.
This would solve many issues.
One simple example:
I have a Text Input and want to provide some data get by a connector function.
Ways to input the text and execute the function:
- Barcode Scanner (hardware)
- Barcode Scanner (Optical)
- Text Input Widget + Enter Key
- Text Input Widget + Button Press
To achieve this I have to build the exact same trigger 4 times and can only copy it once…
Now I get the Idea to Map_to_Text_List three of the fields, to provide a dropdown for each.
I then have to update all four triggers manually and add three actions each (12 actions)
I had a similar case, where I had to map tons of object fields to a record placeholder… to do so in more than one trigger is a real pain…
I hope that helps to understand some use cases a bit…