SSH Job does not resolve environment variable correctly when set in command parameter

Current Situation

When using SSH Job with a remote SSH Server on a Windows Operating System the command

echo MYPARAM=myTestParam >> %SCHEDULER_RETURN_VALUES%

as described in the documentation doesn´t work when set as the value for the command parameter of the Job. Instead a file is generated on the remote system with the name %SCHEDULER_RETURN_VALUES%.
If you use the command above in a script file and refer the script file in the parameter command_script_file everything works as expected

Desired Behavior

The command should be processed correctly in the same manner as if the command was called through a script file.

Workaround

Put the command in a script file and refer the script file in the parameter command_script_file.

Maintainer Note

For SSH servers that provide a Windows shell (such as CopSSH and Bitvise SSH Server), make sure that setting environment variables is allowed.
Setting environment variables is allowed per default for CopSSH and Bitvise SSH Server