workflow-xxxx are data objects stored in a project. Since they are stored in a project, it is easy to share the workflow with other users by adding them to the project. Such "local" workflows are also great for fast iterations for development and testing. It is convenient that we can always delete the workflow and create a new one in its place.dx-toolkit. dx-toolkit version 0.253 or higher installed. If you need to upgrade your version of dx-toolkit, you can do so using dx upgrade dx get command to download a JSON representation (dxworkflow.json) of the local workflow:dxworkflow.json file in it.dxworkflow.json to create a new global workflow. The only additional fields that are required for the global workflow are: name and version.stages and any other fields unchanged.title and summary to make our workflow more user-friendly. It is also good practice to include documentation which can be placed in the Readme.md file in the same directory.Exome Analysis Workflow is the name of the directory storing the dxworkflow.json, it can be changed freely.dx build command should return us the unique ID ('globalworkflow-xxxx') of the created version. We can use it to refer to the global workflow from now on, for example:dx add users. We will prepare the list now but the users will be able to find and access the global workflow only after the workflow is published. The list of users can be updated by developers before or after it is published, and it will apply to all to the versions of the workflows, past and future.dx add users command can be used.dx publish:dx find globalworkflow .dxworkflow.json source code with dx get (as well as the dependencies, e.g. applets), though they cannot build new versions with the same global workflow name.dx publish command will make the published version a default one by adding a "default" alias to this version (and removing it from whichever workflow version was previously marked as "default"). The alias indicates that this version will be invoked whenever the workflow name is used without the version. For example, users can run the workflow:dx publish --help for more options for this command.dxworkflow.json and using dx build --globalworkflow. In order to create the new version, we need to explicitly update the version string, e.g. to "0.0.2".dxworkflow.json we can download it any time with dx get, for example to get version 0.0.2:dx find globalworkflows is useful for browsing global workflows that are available to us.dx find globalworkflows lists one version per each available workflow - the version marked as "default". To print the whole version history for a workflow, add the —all flag, for example:--category parameter can be used to restrict the search to workflows from a specific category. Common categories are available as tab completions. For example: