Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Issue summary
A customer is interested in the ability to exclude certain flows from the agent export [1].
For example, they would like to be able to set a no-export setting for specific flows in a relevant Environment (Manage->Environments->Edit an environment) so that these specific flows will intentionally be excluded from the export.
Feature Request:
Add the option to select which flows will not be exported, and set this via the specific environment settings (Manage->Environments).
In addition - Other objects that are not referenced in any of the “active” flows are excluded from the exported file in both the JSON and BLOB format.
Proposed Solution:
One possible solution is to choose the relevant flows and be able to select 'Do Not Export' for example via Manage->Environments->Edit an environment.
Important Note: It is most likely best to add a new option rather than change the 'Not published' to behave differently as other customers may rely on the current way it works.
Thanks in advance.
[1]https://cloud.google.com/dialogflow/cx/docs/concept/agent#export
How to reproduce the issue in the Dialogflow CX console
Expected behavior
Flows marked as “Do Not Export” will be excluded from the exported file in both the JSON and BLOB format. Other objects that are not referenced in any of the “active” flows are excluded from the exported file in both the JSON and BLOB format
Actual behavior
All the flows (even those marked with 'Not Published' version) are exported. Initially, the customer expected the flows set to 'Not Published' to be excluded, but the fact all flows are exported actually seems to be working as intended according to our public docs.
Current customer workaround
N/A
Documentation consulted
Other information
More context on the customer's initial expectation (check the important note above on another suggested solution):
Flows marked as “Not Published” not to be included in the exported file in both the JSON and BLOB format. Other objects that are not referenced in any of the “active” flows to be excluded in the exported file in both the JSON and BLOB format.