How to show only variables that belong to the scope i have selected and it's direct ancestor, like it was before?

Help Studio
1

After updating to UiPath Studio 25, variable scope selection has become much harder to work with.

Previously, the Variables panel only showed variables from the currently selected scope and its direct ancestors. Now, regardless of where I am in the workflow, the panel lists all variables in the file.

Also, when I open the Scope dropdown for a variable, it shows the entire scope tree without auto-selecting or focusing the current scope. That makes it almost impossible to quickly understand where a variable belongs or to change its scope efficiently.

Please bring back the ability to filter variables by active scope (current scope + ancestors), and make the scope selector default to the current scope in the tree.

2

Since updating to Studio 25, managing variable scopes has become harder. The Variables panel now shows all variables in the workflow, not just the current scope and its ancestors. Also, the Scope dropdown doesn’t auto-select or highlight the current scope, making it harder to navigate.

It would be great to:

  1. Filter variables by the current scope and its ancestors.
  2. Auto-select the current scope in the Scope dropdown.
3

Hi @m_landos
This is the intended behavior in the new version, and the official recommendation is to share usability feedback through the UiPath Forum or Feedback Portal.

Or
Ref. post:

4

Thanks for clarifying. If this is intended behavior, I think it’s a step backward in usability and safety.

Showing all variables in the file regardless of the active scope breaks a basic encapsulation principle: when I’m working inside a specific scope, I need to immediately see only the variables available in that scope (and its ancestors). Listing everything makes it much harder to reason about what I can actually use right here.

This change introduces real risk:

  • Name collisions become dangerous. If two variables share the same name in different scopes, I can’t reliably tell which one I’m using.
  • Refactoring scope is error-prone. When I want to move a variable to the parent scope, the scope selector shows the entire tree without focusing the current scope. It’s easy to pick the wrong one by mistake.

In short: the new behavior makes workflows harder to maintain and increases the likelihood of subtle bugs.

Please consider restoring the previous scoped view, or at least providing a toggle to switch between:

  1. Scoped view (current scope + ancestors)
  2. All variables
5

The variables filter in the exact same way as I am used to on the latest STS release.

Are you sure you guys are looking in the right place? Perhaps share some screenshots or gifs?