We would like to build custom launch interfaces for nf-core pipelines in our Seqera Platform instance. By that I mean a restricted, minimal interface that only allows to set a minimal set of parameters while the rest is either frozen to a predefined default, or derived from these parameters.

For instance, for the nf-core/demultiplex pipeline, the only thing we'd like launch users to be able to set is the flowcell ID, the filename of the samplesheet and to which project this flowcell belongs. The input and output path shall be derived from the flowcell and project ID, and other options (e.g. ) shall not be editable by the user. For instance, to derived the outdir from the , we'd envisage something like .

To achieve this, for now, we built a custom Nextflow pipeline that wraps the nf-core pipeline with a custom schema. Example. However, ideally, the same could be achieved directly in Seqera Platform. For that, I believe the following would be necessary:

In the platform, each pipeline is linked to a specific repository version and a predefined set of parameters. This feature will enable associating multiple configurations and/or versions to a single pipeline to boost flexibility and simplify user interaction.

At the moment custom schemas can be set in the pipeline launch form, but they have to be in the same repository as the pipeline code.

When adding community pipelines (like nf-core) that custom schema would need to be available in the same repository.

To make this process easier, it would be helpful to be able to add a schema from another location like a raw github URL or s3 path.

Dear Seqera-Team,

As of Version 23.2.0, the Seqera Platform has poor support for launching multi-revision pipelines and the UI facilitates the misconfiguration of parameters.

Therefore, I wanted to point out a potential UI/UX improvement.A user launching a run via Seqera Platform’s browser interface is first presented with a form for entering pipeline parameters. Similar to nf-core launch, this form is based on the file.

Only if all mandatory parameters were provided, it is possible to proceed to the Launch settings. Here, a different workflow revision, e.g. an older version, may be selected. Unfortunately, it is rather the rule than the exception that parameters and schema change between workflow revisions. Hence, the current UI does not allow configuring launches of older revisions properly.

For example, uses the parameter up to revision and 1.0.1 and for newer releases. Even if a user is aware of this change, it is not possible to provide the correct parameter when launching older revisions, since it will be validated against the most recent schema. When providing instead, it is ignored for older revisions and the pipeline’s default is used. Moreover, it happens silently, so a user can easily fail to notice that the workflow is not executed as planned.

To no longer promote misconfiguration via the UI, I suggest putting the revision choice first and thereafter displaying the parameter form, based on the actual of that particular revision:

If the schema is for technical reasons only read when adding or updating pipelines, and looping through all revisions is not feasible, it should be possible to disable the parameter form in favour of a general text area to enter all parameters at once.

Thanks a lot for consideration.

Ticket attachments: