Use workflow metadata to allow the dx build command to build a workflow according to your specifications.
Last updated
Was this helpful?
The file dxworkflow.json is a DNAnexus workflow metadata file. If a dxworkflow.json file is detected in the directory provided to , the toolkit will attempt to build a workflow on the Platform according to the workflow specifications in the JSON file.
The format of the file closely resembles that of the corresponding calls to .
The next section shows a detailed example of the fields used in the file.
Annotated Example
The following lists the contents of an example dxworkflow.json that should be provided in a directory for use with the dx build command.
Note that comments as shown below are not written in a valid JSON format but are provided here only for reference.
{
"name": "exome_variant_calling", # (optional for regular, project-based workflows;
# required for global workflows) Workflow name
"title": "Exome Variant Calling", # (optional) Title of a workflow, it is a label used when displaying,
# searching, or listing the workflow in the UI or CLI
"version": "1.0.0", # (optional for regular, project-based workflows; required for global workflows)
# Version of the global workflow
"summary": "A simple exome pipeline",# (optional) A short description of the workflow
"outputFolder": "/output", # (optional) Folder for the workflow's output
"inputs": [ # (optional) Workflow level input specification (see API documentation)
{
"name": "reads", # Name of the workflow-level input
"class": "array:file", # Class of the workflow-level input
"help": "An array of FASTQ gzipped files"
# (optional) help for this workflow-level input
}
],
"outputs": [ # (optional) Workflow level output specification (see API documentation)
{
"name": "variants", # Name of the workflow-level output
"class": "file", # Class of the workflow-level output
"outputSource": { # Link to the output of the stage which
"$dnanexus_link": { # provides the output of the workflow
"stage": "call_variants",
"outputField": "variants_vcfgz"
}
}
}
],
"stages": [ # (optional) A list of stages
{
"id": "align_reads", # Unique ID of the first stage
"name": "BWA MEM", # (optional) Display name of the first stage
"executable": "app-bwa_mem_fastq_read_mapper/2.0.4",
# Name or ID of the app or ID of the applet run in this stage
"folder": "map_reads_output", # The output subfolder into which the outputs of this stage should be cloned
"input": { # (optional) Input of the first stage
"genomeindex_targz": { # Input field name
"$dnanexus_link": { # Link to a reference genome file
"project": "project-BQpp3Y804Y0xbyG4GJPQ01xv",
"id": "file-B6ZY4942J35xX095VZyQBk0v"
}
},
"reads_fastqgzs": { # Input field name
"$dnanexus_link": { # Link to the workflow level input; the input passed to "reads" on the
"workflowInputField": "reads" # workflow level will be consumed by the "reads_fastqgz" input
}
}
},
"systemRequirements": { # (optional) Request different instance types for different entry
# points of this stage
"main": { # "main" is the name of the entry point called when a stage is run
"instanceType": "mem1_ssd1_v2_x16"
}
},
"executionPolicy": { # (optional) Options governing job restart policy
"restartOn": {
"*": 3 # Restart automatically up to 3 times for all errors
}
}
},
{
"id": "call_variants",
# Unique ID of the second stage
"name": "Freebayes",
# (optional) Display name of the second stage
"executable": "app-freebayes/2.0.1",
# Name or ID of the app/globalworkflow or ID of the applet/workflow run in this stage
"folder": "call_variants_output", # The output subfolder into which outputs should be cloned for the stage
"input": { # (optional) Input of the second stage which is linked
"sorted_bams": [{ # to the output of "sorted_bam" of the first stage.
"$dnanexus_link": {
"stage": "align_reads",
"outputField": "sorted_bam"
}
}],
"genome_fastagz": {
"$dnanexus_link":{
"project": "project-BQpp3Y804Y0xbyG4GJPQ01xv",
"id": "file-B6ZY7VG2J35Vfvpkj8y0KZ01"
}
}
}
}
]
}
Specification
name
string. The name of the workflow. If it is not provided, the auto-generated workflow ID will be used. When a global workflow is built (with dx build --globalworkflow) the name is required and more strict formatting rules apply: the name can have lower case letters, numbers, "-" , "." , and "_" but cannot have spaces.
Example:
{
...
"name": "exome_variant_calling",
...
}
title
string. The title of the workflow. It is a label displayed to the users in the Web Interface. If it is not provided, the name of the workflow will be used.
Example:
{
...
"title": "Exome Variant Calling",
...
}
version
string (Global workflows only). The version of the workflow. This version must be unique from all other versions of the global workflow (published or not).
Example:
{
...
"version": "1.0.0",
...
}
summary
string. A short description of the workflow.
Example:
{
...
"summary": "A simple exome pipeline",
...
}
outputFolder
string (optional). The default output folder for the workflow.
Example:
{
...
"outputFolder": "/output",
}
inputs
array of mappings (optional). JSON array containing the specifications for each input to the workflow.
Other options for the /workflow/new call, such as specifying in which project or folder to create a workflow, are populated via command-line flags of .
We recommend following the conventions for numbering the versions of your global workflow. Semantic Versioning also specifies how you should change the version number for various kinds of updates to your global workflow (that is, bug-fix only, backwards compatible, or backwards incompatible). Using the Semantic Versioning guidelines will help users and other developers to understand when it is safe to move between different versions of your global workflow.
array of mappings (optional). JSON array containing the specifications for each output of the workflow. The specification is the same as the of an app(let) with an addition of the "outputSource" field, which allows the workflow developer to link specific stage outputs to workflow outputs.
string (optional). A list of stages to add to the workflow. See the stages input field of the call for a detailed specification.
