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

Request for Folder Management and Batch Export Features #5380

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

Originally created by @zhangeden on GitHub (Sep 4, 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.

While using the Dify Studio, I’ve found it increasingly difficult to manage workflows as their number grows. Each workflow needs to be managed individually, and the interface can become cluttered. I believe adding a folder feature would allow users to organize multiple workflows by theme or project, making the interface more structured and enhancing management efficiency.

Additionally, when it comes to backing up and migrating workflows, the current export functionality is somewhat limited, requiring users to export each workflow or knowledge base one at a time. This process can be very time-consuming when dealing with a large number of workflows. Therefore, I’d like to request a batch export feature that would allow users to export multiple workflow DSL files at once, as well as back up knowledge base contents simultaneously.

2. Additional context or comments

The folder feature would help users better organize and manage workflows, especially for complex projects involving a large number of workflows. This feature would significantly improve work efficiency.
The batch export feature could include the ability to export workflow DSL files, allowing users to easily back up and migrate workflows, and it should also apply to the backup of knowledge base content, enabling users to obtain a complete set of data in a single operation.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @zhangeden on GitHub (Sep 4, 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. While using the Dify Studio, I’ve found it increasingly difficult to manage workflows as their number grows. Each workflow needs to be managed individually, and the interface can become cluttered. I believe adding a folder feature would allow users to organize multiple workflows by theme or project, making the interface more structured and enhancing management efficiency. Additionally, when it comes to backing up and migrating workflows, the current export functionality is somewhat limited, requiring users to export each workflow or knowledge base one at a time. This process can be very time-consuming when dealing with a large number of workflows. Therefore, I’d like to request a batch export feature that would allow users to export multiple workflow DSL files at once, as well as back up knowledge base contents simultaneously. ### 2. Additional context or comments The folder feature would help users better organize and manage workflows, especially for complex projects involving a large number of workflows. This feature would significantly improve work efficiency. The batch export feature could include the ability to export workflow DSL files, allowing users to easily back up and migrate workflows, and it should also apply to the backup of knowledge base content, enabling users to obtain a complete set of data in a single operation. ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 18:10:41 -05:00
yindo closed this issue 2026-02-21 18:10:41 -05:00
yindo commented 2026-02-21 18:10:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 4, 2024):

@zhangeden Hello there! I'm here to help you with any bugs, questions, or if you want to become a contributor. Let's work on solving the issue together.

I found a similar unsolved discussion regarding folder organization: Folder Organization Feature for Projects in Studio Page, which was last updated on 2024-04-18 [1].

Folder Management

Currently, Dify has some features related to document management, such as adding, disabling, and archiving documents within the knowledge base. However, there is no specific folder management feature for organizing workflows. Implementing a folder feature would indeed help in organizing multiple workflows by theme or project, making the interface more structured and enhancing management efficiency [2].

Batch Export

Regarding the batch export functionality, there are some constraints in the Dify codebase that might affect its implementation:

  1. Batch Upload Limit: There is a batch upload limit defined by dify_config.BATCH_UPLOAD_LIMIT. If the number of items to be exported exceeds this limit, it could cause issues or require additional handling.
  2. Permission Checks: Extensive permission checks ensure that only authorized users can access or modify datasets, which could complicate batch export functionality if the export involves datasets with varying permissions.
  3. Embedding Model Configuration: Proper configuration of embedding models is required for certain operations. Any misconfiguration could cause errors.
  4. Document Quota Checks: There are checks to ensure that document upload quotas are not exceeded, and similar checks might be needed for batch export to ensure that the system's limits are not breached [3].

Existing Export Mechanism

There is an existing mechanism for exporting workflows in Dify, implemented in the useDSL hook, specifically in the handleExportDSL function. This function handles the export process by synchronizing the workflow draft, exporting the app configuration, and creating a downloadable YAML file. Additionally, you can export a DSL file from the studio application list or the workflow orchestration page [4][5][6][7].

Implementing a batch export feature would require addressing the mentioned constraints and possibly extending the current export mechanism to handle multiple workflows and knowledge base contents simultaneously.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 4, 2024): <!-- Greeting --> @zhangeden Hello there! I'm here to help you with any bugs, questions, or if you want to become a contributor. Let's work on solving the issue together. <!-- Answer --> I found a similar unsolved discussion regarding folder organization: [Folder Organization Feature for Projects in Studio Page](https://github.com/langgenius/dify/discussions/3619), which was last updated on 2024-04-18 <sup>[[1]](https://github.com/langgenius/dify/discussions/3619)</sup>. ### Folder Management Currently, Dify has some features related to document management, such as adding, disabling, and archiving documents within the knowledge base. However, there is no specific folder management feature for organizing workflows. Implementing a folder feature would indeed help in organizing multiple workflows by theme or project, making the interface more structured and enhancing management efficiency <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/knowledge-base/knowledge-and-documents-maintenance.md)</sup>. ### Batch Export Regarding the batch export functionality, there are some constraints in the Dify codebase that might affect its implementation: 1. **Batch Upload Limit**: There is a batch upload limit defined by `dify_config.BATCH_UPLOAD_LIMIT`. If the number of items to be exported exceeds this limit, it could cause issues or require additional handling. 2. **Permission Checks**: Extensive permission checks ensure that only authorized users can access or modify datasets, which could complicate batch export functionality if the export involves datasets with varying permissions. 3. **Embedding Model Configuration**: Proper configuration of embedding models is required for certain operations. Any misconfiguration could cause errors. 4. **Document Quota Checks**: There are checks to ensure that document upload quotas are not exceeded, and similar checks might be needed for batch export to ensure that the system's limits are not breached <sup>[[3]](https://github.com/langgenius/dify/blob/main/api/services/dataset_service.py)</sup>. ### Existing Export Mechanism There is an existing mechanism for exporting workflows in Dify, implemented in the `useDSL` hook, specifically in the `handleExportDSL` function. This function handles the export process by synchronizing the workflow draft, exporting the app configuration, and creating a downloadable YAML file. Additionally, you can export a DSL file from the studio application list or the workflow orchestration page <sup>[[4]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/hooks/use-workflow-interactions.ts)</sup><sup>[[5]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/export_import.md)</sup><sup>[[6]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/export-import.md)</sup><sup>[[7]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/panel-contextmenu.tsx)</sup>. Implementing a batch export feature would require addressing the mentioned constraints and possibly extending the current export mechanism to handle multiple workflows and knowledge base contents simultaneously. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
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 💪 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#5380
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?