Expand App resources overview to Custom Widgets

On the Custom Widgets page, you can see the where‑used information at the app level.
The link provided takes you directly to the corresponding app.

However, when you want to switch to a newer version of a custom widget, you currently need to manually search through all steps in the app to identify every occurrence of that widget.

To improve usability, please add a third tab called “Custom Widgets” to the Resources Overview on the App Versions tab.
This tab should list all custom widgets used in the app and provide information about the steps in which they appear—similar to how the Functions and Connector Functions tabs work.

Hi @thorsten.langner ,

Thank you for the feedback, extending the where used capability for other assets in Tulip is something we are actively thinking about. We definitely see the value in better visibility and locating your assets so that you can iterate faster.

Where does the lack of visibility cause the most friction in your workflow? Are you more concerned with managing the impact of changing a custom widget , or is the primary bottleneck the manual effort required to find assets used within triggers? i.e. users, user groups

Best,
Cana

Hi @canaalpaslan
Thank you for reaching out.
I don’t understand the second part of your question fully.

I sometimes have custom widgets, that get changed or replaced.
I then need to check the result in an app oder (more complex) need to replace all current appearences of the previous widget.

It is almost impossible to find all appearences, when I can only find the app, but not the step.

This is what I don’t get. The widget can contain triggers, but can not be in another trigger (as the functions and connector functions).

I only need a gapless navigation to all the steps.

Also before copying an app to another workspace or instance it would be helpful, to see all the custom widgets, that are used in it.

@canaalpaslan Did my explanation help?

I’m not sure, if I overcomplicated it a bit. :slight_smile:

It was definitely helpful :slight_smile: To show the demand of the feature and help us prioritize please share/upvote community this post.