Skip to content

Add customizable run name field to workflow launch node#8

Merged
ewels merged 1 commit into
mainfrom
feat/customise-run-nmae
Oct 27, 2025
Merged

Add customizable run name field to workflow launch node#8
ewels merged 1 commit into
mainfrom
feat/customise-run-nmae

Conversation

@adamrtalbot

Copy link
Copy Markdown
Contributor

Summary

This PR adds a customizable run name field to the workflow launch node, allowing users to specify custom names for their workflow runs.

Changes

  • UI: Added new "Run name" input field in workflow-launch.html
  • Runtime: Added logic to set runName in the launch request body when provided
  • Documentation: Updated README.md with the new field
  • Help text: Updated inline node documentation
  • CHANGELOG: Documented the new feature

Features

The run name field:

  • Optional: Can be left blank for auto-generated names from Seqera Platform
  • Flexible: Supports dynamic values from message properties, flow/global context, environment variables, and JSONata expressions
  • Clean: Automatically trims whitespace
  • Integrated: Uses the existing TypedInput system for consistency

Testing

The implementation follows existing patterns in the codebase and integrates seamlessly with the workflow launch node's architecture.

Related

Resolves user request to customize run names when launching pipelines.


🤖 Generated with Claude Code

Added optional runName field to workflow launch node that allows users to
specify a custom name for workflow runs. If left blank, Seqera Platform
will auto-generate a default name. Field supports dynamic values from
message properties, context, environment variables, and JSONata expressions.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@adamrtalbot adamrtalbot requested a review from ewels October 23, 2025 16:01
@ewels ewels merged commit 456660c into main Oct 27, 2025
1 check passed
@ewels ewels deleted the feat/customise-run-nmae branch October 27, 2025 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants