langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

maybe a good idea ! allow multiple front blocks for blocks in workflow editor #2613

New Issue
Closed
opened 2026-02-21 17:47:52 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:47:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @sEANzHAO622 on GitHub (Apr 25, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

It's too cumbersome for me to use the same sub workflow after multiple different preprocessing branches.
I must copy this sub workflow node by node multiple times, and connect and set parameters for them.
There are two solutions.

  1. Allow nodes to have multiple entrances
  2. Allow multiple nodes to be selected simultaneously for replication while maintaining their connections

当我需要将同一个子工作流用在多个不同的预处理分支后的时候太麻烦了。
我必须要将这个子工作流一个节点一个节点的抄写多遍，并且为他们连线和设置参数。

这有两个解决方案。
1 允许节点有多个入口
2 允许同时选中多个节点进行复制，并保持他们之间的连线

2. Describe the feature you'd like to see

  1. Allow nodes to have multiple entrances
  2. Allow multiple nodes to be selected simultaneously for replication while maintaining their connections

这有两个解决方案。
1 允许节点有多个入口
2 允许同时选中多个节点进行复制，并保持他们之间的连线

3. How will this feature improve your workflow or experience?

Significantly reduces workload when configuring complex business processes

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @sEANzHAO622 on GitHub (Apr 25, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? It's too cumbersome for me to use the same sub workflow after multiple different preprocessing branches. I must copy this sub workflow node by node multiple times, and connect and set parameters for them. There are two solutions. 1. Allow nodes to have multiple entrances 2. Allow multiple nodes to be selected simultaneously for replication while maintaining their connections 当我需要将同一个子工作流用在多个不同的预处理分支后的时候太麻烦了。 我必须要将这个子工作流一个节点一个节点的抄写多遍，并且为他们连线和设置参数。 这有两个解决方案。 1 允许节点有多个入口 2 允许同时选中多个节点进行复制，并保持他们之间的连线 ### 2. Describe the feature you'd like to see 1. Allow nodes to have multiple entrances 2. Allow multiple nodes to be selected simultaneously for replication while maintaining their connections 这有两个解决方案。 1 允许节点有多个入口 2 允许同时选中多个节点进行复制，并保持他们之间的连线 ### 3. How will this feature improve your workflow or experience? Significantly reduces workload when configuring complex business processes ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🌊 feat:workflow label 2026-02-21 17:47:52 -05:00
yindo closed this issue 2026-02-21 17:47:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌊 feat:workflow
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#2613
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?