Hi Tulip Team,
It would be a nice-to-have feature to have the trigger name exposed as an option in App Info. See below screenshot. We are already using App name, Station Name, Step Name, Username, etc from App Info, it would be nice also to use Trigger Name here instead of us having to hardcode this (especially if this trigger name changes, we have to remember to change the static value in the actions also.)
Thanks,
Wout
hi @iamwout , could you share a bit more about the use case here - reading the screenshot - are you trying to pass the Trigger Name to a Connector Function to write to an error table?
Yes, this specific use case is for needing to know trigger name in case of troubleshooting a production line problem.
There is often misinformation or poorly escalated errors that occur on the manufacturing floor. As a result, at each point where our Tulip apps show the user an error (due to some incorrect input or failed validation), we are logging this to an error table, so we have a record of key pieces of information about the inputs, app info, and the Tulip screen (in the form of an app screenshot) at the time the error occurred so that we don’t have to rely on a poorly communicated escalation.
Trigger name is one of the items we’d like to record, as it points us right to the trigger which is failing their validation, and we can point to exactly where to start troubleshooting.
Hope this helps. Note, I believe you’re after the bigger picture here so there are certainly other use cases for exposing the trigger name in the app info properties. Another usecase for us would be ‘if’ statements within the trigger itself that could dynamically determine if that trigger will fire through conditions (i.e.: If App Info.Trigger Name = X, then do these actions, elseif do these other actions, else do nothing). This could allow you to dynamically toggle triggers on or off.
