After upgrading to UiPath Studio 25, the Variables/Data Manager panel now lists all variables in the file regardless of where you are in the workflow. Support confirmed this is intended, but it’s a big usability regression.
To be clear: the runtime scoping/encapsulation still works. The issue is the UI view. When I’m working inside a specific Sequence/Flowchart/Loop/Try scope, I need the panel to show me only the variables that belong to the active scope and its direct ancestors, like it did before.
Why this matters
Scopes exist to make code/workflows readable and maintainable. In essentially every programming environment, when you’re inside a scope, the variable view focuses on what’s available in that scope. Studio used to follow this logic, and it was a major productivity aid.
Problems with the current Variables view
- Hard to reason about “what can I use here?”
The panel no longer answers the basic question of availability at the current point in the workflow. - Visual ambiguity when names repeat across scopes.
If two variables have the same name in different scopes, both appear in the list. When scanning the panel to check a variable’s properties (especially Default value), it’s unclear which one you’re looking at unless you carefully inspect the Scope column every time. This defeats the purpose of quick context checking. - Workflow navigation becomes slower.
I have to manually search/filter every time I want to understand the local context, which used to be automatic. - Scope changes are easier to mess up.
When changing a variable’s scope, the selector shows the entire tree without focusing/highlighting the current scope, so it’s easy to pick the wrong one. - Visual noise hurts maintenance.
Large workflows become difficult to maintain because the Variables panel is no longer context-aware.
Requested change
Please either:
- Restore the previous default behavior: Variables panel filters to active scope + ancestors
- Provide a clear toggle between:
- Scoped view (active scope + ancestors)
- All variables in file
“All variables” can be useful sometimes — but it shouldn’t be forced all the time. The panel needs to be context-aware again to support safe, fast development.
Thanks for considering this; it affects day-to-day productivity and reduces mistakes during refactoring.
