YADE configuration - full support for variables using ${VAR} syntax

Current Situation

• YADE allows using ${VAR} syntax for elements that hold strings (e.g., Host, Password, FileSpec, Directory, etc.)
• YADE does NOT allow using ${VAR} syntax for elements that hold:
  • Boolean values (e.g., Recursive, etc.)
  • Integer values (e.g., Port, etc.)
  • Enumeration values (e.g., FTPSFragment / SecurityMode: explicit/implicit, etc.)

Desired Behavior

• Schema validation must be preserved to ensure correctness of boolean, integer, enumeration, and other typed values before transfer.
• Additionally, the ${VAR} syntax should be supported for all configuration elements.

Test Instructions

• See YADE-646-affected_elements.txt
• GUI Test
  • Boolean
    • Should be displayed in a combobox (true|false) and additionally user input is allowed
  • Enumeration
    • Should be displayed in a combobox (corresponding values) and user input is allowed
  • Validation
    • All affected elements should be checked to accept only the corresponding type (integer, boolean, enumeration values) and ${VAR} syntax
      • Example: User input in an integer element (e.g., Port) should not accept: abc,  {_} {abc}

        x, but accept _numeric or ${VAR} syntax values

        • "Not accept" means not during input, but when the "Validation" action is performed

• YADE Functions Test
  • Configure all affected elements using the ${VAR} syntax
  • Test with YADE as Shell Job
    • Configure the corresponding environment variables in the workflow and run the test
  • Test with YADE as JITL Job
    • Configure the corresponding workflow variables and run the test