Renaming variable does not respect scope limitation

studio
variable
p_known

#1

Scenario:

Renaming a variable changes the name in all instances in the xaml, even if it’s actually a different variable.

Steps to reproduce:

  1. Open attached workflow.
    RenamingScopeError.xaml (6.5 KB)

  2. Select FirstScope or SecondScope.

  3. Go to Variables pane.

  4. Rename myVariable to something else.

  5. 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 myVariables 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):


#2

Confirmed with 2017.1.6522

@Gabriel_Tatu please check this out


#3

Hello, this is a known issue. Thank you!