[PR #28163] feat: add draft trigger detection to app model and UI #31969

Closed
opened 2026-02-21 20:50:30 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langgenius/dify/pull/28163

State: closed
Merged: Yes


The “Open in Explore” button should only be shown in the web app, and it must be hidden if the app has no user input node.

  • Introduced has_draft_trigger field in the app model to indicate if there are unpublished draft workflows associated with the app.
  • Updated the API to populate has_draft_trigger based on the presence of draft workflows.
  • Modified the app card component to conditionally render UI elements based on the has_draft_trigger status.
  • Enhanced app type definition to include the new has_draft_trigger property.

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before After
... ...

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/28163 **State:** closed **Merged:** Yes --- The “Open in Explore” button should only be shown in the web app, and it must be hidden if the app has no user input node. - Introduced `has_draft_trigger` field in the app model to indicate if there are unpublished draft workflows associated with the app. - Updated the API to populate `has_draft_trigger` based on the presence of draft workflows. - Modified the app card component to conditionally render UI elements based on the `has_draft_trigger` status. - Enhanced app type definition to include the new `has_draft_trigger` property. > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> ## Screenshots | Before | After | |--------|-------| | ... | ... | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:50:30 -05:00
yindo closed this issue 2026-02-21 20:50:30 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#31969