Bug #22554
Updated by Peter Amstutz about 2 months ago
source:tools/cluster-activity/cluster-activity.cwl has the following inputs:
<pre><code class="yaml">inputs:
reporting_days: int?
reporting_start: string?
reporting_end: string?
</code></pre>
These are optional because you can provide some subset of them, but it's an error to specify all of them.
You cannot launch this workflow from Workbench with a specified date range:
* If you leave @reporting_days@ empty, the workflow will fail to start with the error:<pre>../../lib/cwl/cwl.input.json:1:227: the 'reporting_days' field is not valid because
tried int but
"''" is not int</pre>
* If you specify @reporting_days@=0, our own cluster activity script will complain that this is mutually exclusive with @reporting_start@ or @reporting_end@.
It should be possible to completely omit inputs just like it is in YAML.
h2. Solution
If a field is marked as optional (this looks like "type": ["null", "string"]) then an empty text input field in the interface should be emitted as "null" and not empty string.