"Process Files" needs option to process folders
 

It seems as though "Process Files" will always ignore folders in the specified directory unless you use the "Recursively search subfolders" option. Perhaps I’m doing something wrong, but I haven’t found a way of getting this action to recognize folder even at the specified directory level without the recursive flag. And then you end up getting all of the files in those directories as well.

In the system I am trying to build, I have a parent folder which contains a number of direct sub-folders. I would like to simply iterate over just these sub-folders (with a few exclusions), ignore all files, and then do some processing on the current sub-folder (as described by %PROCFILES_FULLPATH%).

How might I do this?

The 'once per folder' option does not currently work with non-recursive processing. This will be supported in the next release.

I'm not seeing this new behavior in the 6.2 Beta. Is it there? If so, how would I test this behavior?

It works in our tests. Attached is a sample.

Yes -- following your example this does seem to be working. The only "surprise" was that I had to check "Process empty folders" to get this to work. I'm not sure why I had to check that (my folders are not empty), but it will not work without that.

Could someone explain why I need to have "Process empty folders" selected? Why is this necessary in order for things to work?

That's just the way it works. Adding that option doesn't have any harmful effects, and it's fairly unusual to use the dir-only non-recursive combination, so we didn't think it mattered much.

Fair enough -- just be sure to document this behavior

This is now handled properly in the latest beta build.

Correct -- according to my tests with the latest Beta, you no longer need to check the "Process empty folders" option to get things to work as expected.

Thanks for fixing this.