When adding arguments with empty values using the wizard for Job Templates (including JITL jobs and user defined jobs) to a job then such arguments can be selected but are not added to the job.
Users can add empty arguments to jobs for
job node arguments
job arguments
job environment variables
Desired Behavior
Use of arguments with empty values is denied.
When adding arguments from the wizard for Job Templates it should not be possible to select arguments with empty values. The respective checkboxes for arguments holding empty values should be disabled.
When adding arguments to job nodes, arguments to jobs and values to environment variables for a job then users can omit the values (behavior unchanged). However, such workflows are considered invalid (behavior changed). As usual invalid workflows are stored but cannot be deployed.
The GUI should provide a hint with the "invalid" status icon that points the user to the argument holding a missing value.
The REST API should deny the workflow on validation.