Scenario: Using the Type into activity into a command prompt send the incorrect keys. Typing the same command manually using the keyboard works as expected so it doesn’t appear to be a keyboard mapping issue.
Steps to reproduce: Using Type into on a command window (cmd.exe)
Current Behavior: I use the following command:
"net user robot1 /domain|find /I "“Password exp”
This is entered as:
net user robot1 'domain§find 'I ØPassword expØ
Expected Behavior: Correct keys are typed
Studio/Robot/Orchestrator Version: Studio Enterprise 2018.1.1
Last stable behavior: n/a
Last stable version: n/a
OS Version: Windows 10 Pro and Windows Server 2012 R2
This image demonstrated my manually typed command immediately followed by the robot command