Scenario: Arguments and Variables can have the same name which causes likely unintended behavior.
Steps to reproduce: Create a sequence or workflow with a variable name the same as an argument name
Current Behavior: Allows the creation of both a variable and an argument with the same name. In this instance, the variable is used but not the argument. When trying to get information
Expected Behavior: Disallow the creation of variable or argument names that shadow each other
Studio/Robot/Orchestrator Version: 2018.2.3 (For all)
OS Version: Windows 10
Others if Relevant: (workflow, logs, .net version, service pack, etc): Please see attached workflow:
Test_SameName.xaml (5.4 KB)