Feature Request: Add Filter Options to "Find Usages" Results

Problem:

When using the Find Usages feature in OutSystems, all references to a widget, action, variable, or other element are displayed in a single list.

In large applications, an element can have 100+ usages, making it difficult and time-consuming to locate the specific usage that a developer is looking for.

Proposed Solution

Introduce filter and search options in the Find Usages results panel.

Possible filters could include:

• Module

• Screen

• Block

• Client Action

• Server Action

• Flow

• UI vs. Logic

• Usage Type (Read, Write, Call, Reference, etc., where applicable)

Additionally, add a search box that allows developers to quickly search within the displayed results by screen name, action name, or module.

Benefits:

• Faster navigation in large applications.

• Improved developer productivity.

• Easier debugging and impact analysis.

• Reduced time spent scrolling through long usage lists.

• Better overall development experience in Service Studio.

Example:

If an action has 150 usages, instead of scrolling through the entire list, a developer could:

• Filter by a specific module.

• Search for a screen or action name.

• Narrow the results to only the relevant references.

This enhancement would make the Find Usages feature much more efficient, especially for enterprise applications with large codebases.