Quality of life: Comments in triggers

It would be nice to have a Comment action in triggers that would function similar to Step Groups with a visual difference (bg color).

Why:
Triggers can get huge and difficult to read. Its easy to miss something, so having a way to group actions and write comments for the section would be great.

i.e.

Call Connector Function
Comment → Update Work Order Table
Data manipulation → store → …


Comment → Update inventory number for X in Material table
Data manipulation → store → …

This would be huge. Right now I keep notes on the triggers for each step in the step notes, but having comments on the trigger would be awesome!

1 Like

Totally agree. This isnt being addressed with existing engineering work right now, but let me put a request in for it.

Pete

1 Like

Any update on this?

My current workaround which I picked up from somewhere in the community is populating a dummy variable…

Not so pretty…

1 Like

This would be great.

Hey Folks, there are a few different threads about commenting in triggers, and I want to make sure I chime in here and say that we hear you. Across the different threads, this is likely the most requested feature we have. Here are some for reference:

For perspective, this is a gap our product teams are aware of, and it’s definitely something that’s on our radar. Given how far back these requests go, some context is in order: we’ve known for awhile that we wanted to improve the basic trigger writing experience in Tulip. As a result, we’ve decided to bucket QOL improvements to the trigger editor to that cluster of work rather than implementing many of them in the interim.

If this is something that’s valuable, please continue to let us know. We want to make sure we’re taking your feedback and using it to create the best possible app building experience.

@kimberly, if you have more insight to share here, or more questions to ask, please do.

2 Likes

Hi folks,

I wanted to post a quick update here to let the Community know Trigger usability and legibility is on our radar, and that we’re actively designing a quick improvement while taking time for bigger rework.

Longer term - Over the next year, we’re planning a couple of big projects that could help with Trigger legibility - Functions, and a revamp of the App Trigger editing experience to make it more visual and also handle Loops (similar to Automations).

Short term - In the meantime we’re planning a smaller “quick win” improvement to the current triggers experience to let App Builders add Descriptions to triggers – similar to Comments. App Builders would then be able to quickly read these Descriptions in the context pane without having to open each trigger - likely on hover. Details are still TBD and timing is probably Q4, but thought I’d drop a quick update since this topic came up again recently.

Send me a note if you’re interested in learning more about either!

  • Olga
6 Likes

Exciting news folks! The short term “quick win” Olga mentioned above for this feature request has been implemented in Release 298 - December 2024 !! :tada:

Comment and describe your triggers to your hearts content!

Thanks all for the great feedback here and let @OlgaStroilova or I know if you have any questions or further suggestions.

2 Likes

This is amazing @Beth @MaxN-C !!!

Now if all of us Tulip app builders start writing really good descriptions, Tulip will be able to train an AI model to generate triggers! Let’s get to work community :rofl:

3 Likes