langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Enhancement/Refactor] Variable Assigner Node visibility conditions #12842

New Issue
Open
opened 2026-02-21 19:09:19 -05:00 by yindo · 12 comments
yindo commented 2026-02-21 19:09:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Apr 12, 2025).

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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

In workflows (NOT chat-flows), it's possible to add the variable assigner node in the root flow.
This node can currently be used only inside Loop Node.
For this reason it would be better to make the node visible only inside the Loop Node for WORKFLOWS only

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DavideDelbianco on GitHub (Apr 12, 2025). ### 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. In workflows (NOT chat-flows), it's possible to add the variable assigner node in the root flow. This node can currently be used only inside Loop Node. For this reason it would be better to make the node visible **only** inside the Loop Node for WORKFLOWS only ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancementstale labels 2026-02-21 19:09:19 -05:00
yindo commented 2026-02-21 19:09:19 -05:00
Author
Owner
Copy Link
Copy Source

@GeorgeCaoJ commented on GitHub (Apr 14, 2025):

Agree with you, the workflow is restricted by lacking the conversation like variable getting and setting feature.

@GeorgeCaoJ commented on GitHub (Apr 14, 2025): Agree with you, the workflow is restricted by lacking the conversation like variable getting and setting feature.
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@Yevanchen commented on GitHub (Apr 15, 2025):

@GeorgeCaoJ @DavideDelbianco Have you checked the latest loop variable?

@Yevanchen commented on GitHub (Apr 15, 2025): @GeorgeCaoJ @DavideDelbianco Have you checked the latest loop variable?
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Apr 15, 2025):

I've seen commits about it, but the only new thing I've found is the loop end node, where is it supposed to be the loop variable?

@DavideDelbianco commented on GitHub (Apr 15, 2025): I've seen commits about it, but the only new thing I've found is the loop end node, where is it supposed to be the loop variable?
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@Yevanchen commented on GitHub (Apr 15, 2025):

I've seen commits about it, but the only new thing I've found is the loop end node, where is it supposed to be the loop variable?

In the panel setting of the loop node

@Yevanchen commented on GitHub (Apr 15, 2025): > I've seen commits about it, but the only new thing I've found is the loop end node, where is it supposed to be the loop variable? In the panel setting of the loop node
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Apr 17, 2025):

Modified the subject of this request.
Didn't notice the loop variables, super cool feature.

@DavideDelbianco commented on GitHub (Apr 17, 2025): Modified the subject of this request. Didn't notice the loop variables, super cool feature.
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

Hi, @DavideDelbianco. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested an enhancement to restrict the variable assigner node's visibility exclusively inside the Loop Node for better workflow clarity.
  • The current behavior allows the variable assigner node to be usable only within the Loop Node, but its visibility is not restricted.
  • Other contributors acknowledged the need for improved variable handling and noted recent additions like loop variables accessible in the loop node's panel settings.
  • You appreciated the recent improvements but still seek clearer visibility restrictions for the node.
  • The issue remains unresolved with no recent updates.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 5, 2025): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested an enhancement to restrict the variable assigner node's visibility exclusively inside the Loop Node for better workflow clarity. - The current behavior allows the variable assigner node to be usable only within the Loop Node, but its visibility is not restricted. - Other contributors acknowledged the need for improved variable handling and noted recent additions like loop variables accessible in the loop node's panel settings. - You appreciated the recent improvements but still seek clearer visibility restrictions for the node. - The issue remains unresolved with no recent updates. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Sep 5, 2025):

Variable assigner node should not be visible outside of loop node when in workflow.

@DavideDelbianco commented on GitHub (Sep 5, 2025): Variable assigner node should not be visible outside of loop node when in workflow.
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

@crazywoola The user confirms that the variable assigner node should not be visible outside the loop node in the workflow, as originally requested. Could you please assist with this issue?

@dosubot[bot] commented on GitHub (Sep 5, 2025): @crazywoola The user confirms that the variable assigner node should not be visible outside the loop node in the workflow, as originally requested. Could you please assist with this issue?
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Sep 7, 2025):

to fix this
pr : https://github.com/langgenius/dify/pull/25331

pls review @crazywoola

@jubinsoni commented on GitHub (Sep 7, 2025): to fix this pr : https://github.com/langgenius/dify/pull/25331 pls review @crazywoola
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 7, 2026):

Hi, @DavideDelbianco. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested that the variable assigner node be visible only within the Loop Node to improve clarity.
  • Contributors agreed on the need for better variable handling in workflows.
  • Recent loop variable features have been added to the loop node's panel, which you acknowledged.
  • You still maintain the request for restricting visibility of the variable assigner node.
  • A PR addressing this has been submitted by jubinsoni and is currently awaiting review.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here.
  • If I don’t hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 7, 2026): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested that the variable assigner node be visible only within the Loop Node to improve clarity. - Contributors agreed on the need for better variable handling in workflows. - Recent loop variable features have been added to the loop node's panel, which you acknowledged. - You still maintain the request for restricting visibility of the variable assigner node. - A PR addressing this has been submitted by jubinsoni and is currently awaiting review. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here. - If I don’t hear back within 15 days, this issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@jubinsoni commented on GitHub (Jan 13, 2026):

we can close this as variable assigner is now available inside loop node in main branch

@jubinsoni commented on GitHub (Jan 13, 2026): we can close this as variable assigner is now available inside loop node in main branch
yindo commented 2026-02-21 19:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 13, 2026):

Hi, @DavideDelbianco. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested that the variable assigner node be visible only inside the Loop Node to improve clarity.
  • Contributors acknowledged the need and added loop variable features to the loop node's panel.
  • A PR by jubinsoni restricted the variable assigner visibility as requested.
  • The issue was marked stale twice but later confirmed resolved by jubinsoni on the main branch.

Next Steps:

  • Please confirm if this visibility restriction is working as expected in the latest version of Dify.
  • If no further updates are needed, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 13, 2026): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested that the variable assigner node be visible only inside the Loop Node to improve clarity. - Contributors acknowledged the need and added loop variable features to the loop node's panel. - A PR by jubinsoni restricted the variable assigner visibility as requested. - The issue was marked stale twice but later confirmed resolved by jubinsoni on the main branch. **Next Steps:** - Please confirm if this visibility restriction is working as expected in the latest version of Dify. - If no further updates are needed, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
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 stale 💪 enhancement
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#12842
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?