A new minor version of my workflow management system Steep is now available. The most notable changes in version 5.3.0 are the deprecation of the argument type
argument in the process chain model and service metadata as well as the deprecation of
parameters of execute actions in the workflow model. Both properties were mostly unnecessary. The argument type
argument should be changed to
parameters of execute actions should be merged into their
This change is completely backwards compatible. Steep will automatically modify posted workflows and the configured service metadata. It will issue a warning in the log file if it encounters deprecated properties. You should migrate to the new ones as soon as possible as the deprecated ones will be removed in Steep 6.0.0 or with the workflow API 5.0.0.
Existing workflows and process chains in your database will automatically be migrated to the new model if necessary.
Steep 5.3.0 also comes with a few other improvements and fixes (see complete list below). The version has been thoroughly tested in practice over the last couple of months.
Steep is a scientific workflow management system that can execute data-driven workflows in the Cloud. It is very well suited to harness the possibilities of distributed computing in order to parallelise work and to speed up your data processing workflows no matter how complex they are and regardless of how much data you need to process. Steep is an open-source software developed at Fraunhofer IGD. You can download the binaries and the source code of Steep from its GitHub repository.
argument. They are unnecessary because they can be easily mapped to inputs. I’ve deprecated the type
argumentand will remove it in Steep 6.0.0. For the time being,
argumentwill automatically be replaced by
services.yamlfile. A warning will be logged.
argumentin process chains to
parametersof execute actions into their
NotifyingSubmissionRegistryif VM does not exist