Bug in Build Forge Help or in Build Forge

The main page of Help says "This edition applies to version 7.1.1.4".
....
This appears to be inaccurate. It says that it doesn't interpolate
*the hidden variable*. What appears to happen is that *it doesn't
interpolate ANY variables on that line*.

The main page of Help says "This edition applies to version 7.1.1.4".

Help page "Variable properties" says

Assign Hidden: The system assigns the variable, but hides the
value in the logs, showing it as "*****". Use this option when you
are including a password or other sensitive information in a
variable. Example: you need to include password information in an
_MAP variable in order to map a drive. You want to hide the
password from users who run the project.

The system normally changes the syntax of a variable in a command
line to the appropriate form for your operating system (%VAR% for
Windows(R), $VAR for Linux(R) and UNIX(R) systems). It does not do
this for a hidden variable. The variable is passed directly to the
server and the operating system environment of the server
interprets the variable.

This appears to be inaccurate. It says that it doesn't interpolate
*the hidden variable*. What appears to happen is that *it doesn't
interpolate ANY variables on that line*.

For example, if PASSWORD is the only hidden variable in a Windows
command and has the value 1234, the documentation says that
some_command -w "${WORKSPACE}" -u "${USER}" -p "%PASSWORD%"
will work, when it fact on Windows it will become
some_command -w "${WORKSPACE}" -u "${USER}" -p "1234"
literally.

I request that Build Forge be changed to match the documentation, so
that it actually did interpolate non-hidden variables. Failing that,
the Build Forge documentation should be changed to match the
behavior.

--
Tim McDaniel, tmcd@panix.com