[ 
https://issues.apache.org/jira/browse/NIFI-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hunter Goller resolved NIFI-14000.
----------------------------------
    Resolution: Won't Fix

> Download Flow Definition File Option Creates the Same Saved Filename
> --------------------------------------------------------------------
>
>                 Key: NIFI-14000
>                 URL: https://issues.apache.org/jira/browse/NIFI-14000
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Hunter Goller
>            Assignee: Hunter Goller
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When downloading flow definitions in Apache NiFi using the "With external 
> services" and "Without external services" options, both options create files 
> with the same default filename (e.g., {{{}flow_definition.json{}}}) when 
> saving the same process group’s flow graph. This forces the user to manually 
> rename files to distinguish between the two types of flow definitions, which 
> can lead to confusion or potential overwriting of files.
> {*}Steps to Reproduce{*}:
>  # Open Apache NiFi and navigate to a Process Group.
>  # Use the *Download Flow Definition* option for the Process Group.
>  # Choose the *With external services* option and save the file.
>  # Repeat the process with the *Without external services* option.
>  # Observe that both downloads create a file with the same name (e.g., 
> {{{}flow_definition.json{}}}).
> {*}Expected Behavior{*}:
> Each download option should result in a distinct filename, such as:
>  * {{flow_definition_with_services.json}}
>  * {{flow_definition.json}}
> This would prevent users from having to manually rename files and reduce the 
> risk of overwriting important flow definitions.
> {*}Actual Behavior{*}:
> Both download options create the same filename (e.g., 
> {{{}flow_definition.json{}}}), requiring users to manually rename the files 
> to avoid confusion.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to