Submit Hierarchy ignoring rules

[bdieckman]

Hello,

I have a folder hierarchy that looks like this:

\\server\share\product

In the product folder, there is a subfolder that can never be submitted to the flow, called "DONE". (\\server\share\product\DONE) Also deposited into the product folder (by an outside system) are job folders that always have the folder pattern "12345A". (\\server\share\product\12345A)

I want the Submit Hierarchy element to pick up folders in the product folder and submit them as job folders. (Not the DONE folder) The problem is that any change to the DONE folder causes that folder to be submitted to the flow, even when I set an "Adjusted by (rule 1)" rule that I think should be excluding it.

The flow element is configured:

Path: \\server\share\product
Leave originals in place: Yes
Ignore Updates: No
Subfolder levels: 0 <-- I think this means "only monitor the root folder" is that right?
Process these folders: All folders
Adjusted by (rule 1): Including folders named
Folder Name: Regular expression defined: [0-9]{5}[A-Z]
On levels: 0
Restriction: None
Nesting: Don't include nested subfolders

My assumption is that "Including folders named" means "excluding all others" but maybe that's not right? I've also tried to set the rule up like this:

Adjusted by (rule 1): Excluding folders named
Folder Name: *DONE*
On levels: 0
Restriction: None
Nesting: Don't include nested subfolders

This doesn't work either. Any change to the "DONE" folder will cause it to be submitted to the flow.

If I set the element up with "Subfolder levels" to 1, the element ignores the DONE folder, but then any job folders that land in the product folder are also ignored and not submitted to the flow.

[bdieckman]

I misunderstood what Switch considers the "hot folder" and I think I understand now...

So I currently have the element set this way:

Path: \\server\share
Subfolder levels: 1 <-- This should treat my "product" folder as the "hot folder" yeah?
Adjusted by (rule1): Excluding folders not named
--Folder name: prod* <-- I have multiple products, so I want to only pay attention to this one.
--On levels: 1
--Restriction: None
--Nesting: Don't exclude nested subfolders
Adjusted by (rule2): Excluding folders named
--Folder name: *DONE*
--On levels: 2 <-- Can the element see past level 1 or will it always treat every folder past level 1 as a job folder?
--Restriction: None
--Nesting: Exclude nested subfolders as well

It's picking up new jobs in the product folder now, but it's still picking up the DONE folder in this configuration.

[jan_suhr]

Levels are the folder structure.

Root folder/Level1/Level2/Level3/Level4/Level5

You can also combine a Level with variables so that you on Level2 for example create a subfolder structure from variables like Root folder/Level1/Level2/Folder name from Job.PrivateData, in the property for Level2 it looks like this "OrderNumber/[Job.PrivateData]" where order number also come from a Metadata variable. And the PrivateData is picked up somewhere in the flow, could be Error Preflight, Warning Preflight an dso on.

You can also have Set hierarchy in meny places in the flow.