Scenario:
Renaming a variable changes the name in all instances in the xaml, even if it’s actually a different variable.
Steps to reproduce:
-
Open attached workflow.
RenamingScopeError.xaml (6.5 KB) -
Select FirstScope or SecondScope.
-
Go to Variables pane.
-
Rename
myVariable
to something else. -
myVariable
in both FirstScope and SecondScope gets changed, leading to validation errors in the other scope.
Current Behavior:
All instances of myVariable
gets changed.
Expected Behavior:
Only instances in myVariable
s scope should be changed.
Studio/Robot/Orchestrator Version:
Encountered in: 2016.2.6274, 2017.1.6435
Last stable behavior: N/A
Last stable version: N/A
OS Version: Server 2016, Win7
Others if Relevant: (workflow, logs, .net version, service pack, etc):