We have created many workflows and chatflows for different clients and business needs. The application’s tag management and categorization are relatively convenient, with tags for applications, tools, different clients, production versions, local debugging versions, and various classification criteria. However, the current tag filtering uses an “OR” logic rather than an “AND” logic. For example, if Client A and Client B each have production and local testing versions (four tags total), selecting both Client A and the production version will also display Client B’s production version, causing inconvenience. In reality, “AND” logic is used more frequently. Could you improve this by adding a logic selection option, allowing users to choose between “AND” or “OR” logic for filtering applications via tags? Thank you!
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| 列表过滤操作可不可以更灵活一点 | 0 | 26 | January 23, 2026 | |
| 关于自定义工具在使用时会被自动移除的问题 | 0 | 19 | February 11, 2026 | |
| Dify Agent 登录与知识库权限 | 3 | 66 | January 22, 2026 | |
| 多路召回时影响到了每一路的召回。这不合理 | 0 | 25 | January 23, 2026 | |
| 公开的ifram-chatflow链接如何绑定自定义用户 | 0 | 30 | December 29, 2025 | |
| 创建的工作流应用,问答时有时会带上工作流节点调试信息和用户的深度思考信息,且找不到可以关闭的地方 | 2 | 55 | December 30, 2025 | |
| 是否可以增加一个api接口关于对话日志追踪的 | 0 | 34 | January 4, 2026 | |
| Dify-chatflow控制是否展示引用及归属 | 0 | 35 | January 6, 2026 | |
| Agent提示词效果求助,为什么官方默认的提示词效果远好于自定义的agnet提示词效果 | 0 | 57 | January 11, 2026 | |
| Allow email addresses to be variables in Human-in-the-Loop nodes | 0 | 46 | February 13, 2026 |