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

Enhance the experience of batch operation return formats. #6793

New Issue
Closed
opened 2026-02-21 18:17:20 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:17:20 -05:00
Owner
Copy Link
Copy Source

Originally created by @BrightXiaoHan on GitHub (Nov 15, 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).
  • [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.

Currently, the results returned by batch operations in the workflow have all fields placed in a single column, which can cause inconvenience in viewing and parsing the results. Would it be possible to expand them into different columns? If feasible, I can submit a PR to improve this experience.

2. Additional context or comments

Current behavior: all output fields placed in a single column with json format
image
Expected behavior: each output fields placed in different column like input fields
image

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @BrightXiaoHan on GitHub (Nov 15, 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] [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. Currently, the results returned by batch operations in the workflow have all fields placed in a single column, which can cause inconvenience in viewing and parsing the results. Would it be possible to expand them into different columns? If feasible, I can submit a PR to improve this experience. ### 2. Additional context or comments Current behavior: all output fields placed in a single column with json format ![image](https://github.com/user-attachments/assets/7b1ebe99-a0fa-4793-91e6-423e4811db5b) Expected behavior: each output fields placed in different column like input fields ![image](https://github.com/user-attachments/assets/921906e6-44f4-468a-ac73-fab27eaeb40c) ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:17:20 -05:00
yindo closed this issue 2026-02-21 18:17:20 -05:00
yindo commented 2026-02-21 18:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 16, 2024):

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

Issue Summary

  • Enhancement proposed to expand batch operation results into separate columns.
  • Intended to improve readability and parsing of results.
  • You expressed willingness to contribute a pull request.
  • No further comments or activities have occurred.

Next Steps

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 16, 2024): Hi, @BrightXiaoHan. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - Enhancement proposed to expand batch operation results into separate columns. - Intended to improve readability and parsing of results. - You expressed willingness to contribute a pull request. - No further comments or activities have occurred. **Next Steps** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed 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 💪 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#6793
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?