Workflow configuration not stored due to decimal values in node arguments

Current Situation

When a job's node argument contains a decimal value, for example  test = 1.1, and is used in an environment variable, for example Test = $test, then the value fails to resolve properly due to a JavaScript condition failure. This results in incorrect behavior of the GUI and the workflow will not be stored.

Workaround

• Users can put decimal values for node argument values in single quotes, for example test = '1.1'
• Alternatively, users can use the "Edit JSON" action menu, apply values and store the workflow.

Desired Behavior

The GUI should correctly handle decimal values in node arguments and should resolve them in environment variables without requiring manual edits or special formatting. The value should be properly validated and should be passed through to the API as expected.