[Custom templates] [Workflow template] Workflow display name and Template display name
- Dominant language
- TypeScript
- Stars
- 111
- Forks
- 109
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 20
Description
### Issue description
This issue is for single workflow templates. Placing the workflow display name under the template profile tab breaks mental models and expectations, especially when users think of workflows and templates as separate constructs. In most applications, users expect to manage workflow-specific settings within the workflow context, not at the broader template level.
### Impact
This inconsistency increases cognitive load and can lead to user confusion. The system blurs the boundary between these entities. This mismatch can lead to the incorrect assumption that the workflow display name is a property of the template, rather than of the workflow itself.
### Recommendation
- Clarify ownership by showing the workflow display name in the workflow tab and the template display name in the template profile tab.
- Make syncing transparent with inline helper text or tooltips.
- Workflow display name field: Inform users with inline helper text that this name will also be used as the template display name.
- Template display name field: Inform users this name has been derived from the workflow display name.
### Capabilities
What capabilities are available for this interaction? Can a user edit the `Template display name` and it automatically update the `Workflow display name`?
Even if we can't do auto syncing and the Template display name is read-only, that's ok, because the mental model is consistent.
### Designs


### Current experience

### Priority
Fast follow after Integrate
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.