Actions
Bug #22554
openSupport launching workflows with optional inputs
Status:
New
Priority:
Normal
Assigned To:
Category:
Workbench2
Target version:
Story points:
-
Description
source:tools/cluster-activity/cluster-activity.cwl has the following inputs:
inputs:
reporting_days: int?
reporting_start: string?
reporting_end: string?
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:../../lib/cwl/cwl.input.json:1:227: the 'reporting_days' field is not valid because tried int but "''" is not int
- If you specify
reporting_days
=0, our own cluster activity script will complain that this is mutually exclusive withreporting_start
orreporting_end
.
It should be possible to completely omit inputs just like it is in YAML.
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.
Updated by Peter Amstutz about 2 months ago
- Target version set to Development 2025-03-19
Updated by Peter Amstutz about 2 months ago
- Target version changed from Development 2025-03-19 to Development 2025-02-26
Updated by Peter Amstutz about 2 months ago
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.
Updated by Peter Amstutz about 2 months ago
- Target version changed from Development 2025-02-26 to Development 2025-03-19
Updated by Brett Smith 27 days ago
- Target version changed from Development 2025-03-19 to Development 2025-02-26
Updated by Brett Smith 26 days ago
- Target version changed from Development 2025-02-26 to Development 2025-03-19
Updated by Peter Amstutz 19 days ago
- Target version changed from Development 2025-03-19 to Development 2025-04-02
Actions