Use Trigger Link Name Instead of ID
M
Marphie Graboso
Currently, TRIGGER LINKS are represented by their IDs, such as :{{trigger_link.WTSfl5xH9wNSJz79jO2t}}, which can be confusing and hard to manage. It would be more user-friendly if the trigger link's NAME was used instead.
Example
Current: {{trigger_link.WTSfl5xH9wNSJz79jO2t}}
Proposed: "Product Demo" {{trigger_link.ProductDemo}}
Benefits
Easier Management: Names are easier to recognize and manage than IDs.
Improved Clarity: Workflows and templates will be more readable.
Faster Workflow Setup: Simplifies identifying and using the correct trigger link.
Log In
R
Rob Calhoun
Yes, and it should default to the ID when the connection is broken, as the tags and fields do when they have been changed.
A
Albert Abrantes
Yes, everything else uses unique names, such as merge values and fields. Trigger links should maintain the same concept.