Yes I agree, as developer, having full visibility into where my code is used is crucial for maintaining and refactoring applications safely. Currently, Service Actions, Events, and Screens do not show their usage in ODC Workflow, which creates a blind spot in the development process.

I suggest extending the Usages feature to include references within ODC Workflows. This would ensure developers can confidently track dependencies and make changes without inadvertently breaking functionality. It’s a small change that would greatly enhance developer productivity and code reliability.

To let the developer know where the actions, events and screens are used is quite essential.

This will lead in getting to know the flow better along with its dependencies.

ODC needs to have this feature, maybe in the next updates we might see this coming.

It is a good idea when bugs happen it is quicker to trace what is affected and also helps avoid accidental issues when changing or deleting something. Fetching Workflow usages might slightly slow down ODC Studio in large apps. May be adding the Show or Hide Workflow References filter can make it smooth. 

Idea already implemented. 🚀

It is now possible to have visibility of element usage in workflows within ODC Studio.