The DisableErrorOnNoFilesFound=true does not work when used with the FilePathSelection/FileListSelection parameters

Current Situation

• If a source file specified by the Profiles->Profile->Operation->...->SourceFileOptions->Selection->FilePathSelection|FileListSelection does not exist in the Source, the Thansfer is aborted with an error even if the ...->SourceFileOptions->Directives->DisableErrorOnNoFilesFound setting is set to true.

Desired Behaviour

• No error should be thrown in the situation described above.

Maintainer Note

• DisableErrorOnNoFilesFound takes effect when 0 files were found in the Source.
• If FilePathSelection|FileListSelection contains multiple files and, for example, one of those files was not found, no exceptions are thrown.
  • If all files are expected to be found, functionality provided with YADE-622 can be used.

Test Instructions

• For example, configure an SFTP Transfer.
• Use FilePathSelection with a file path that does not exist.
• Test the configured Profile with DisableErrorOnNoFilesFound=true and DisableErrorOnNoFilesFound=false.
  • Expected result:
    • DisableErrorOnNoFilesFound=true - no error should be thrown if a file does not exist.
    • DisableErrorOnNoFilesFound=false - an error should be thrown if no files are found.
• Repeat the tests with the FileListSelection setting.
• Use the file path of an existing file and repeat the tests.