Perhaps you can use a parallel activity where the first sequence runs a search including entries with the specific tag and the second sequence runs a search excluding entries with the specific tag. Then use a for each entry loop in each sequence to route the documents to their proper locations.

See this example workflow:

Approach # 1

In the search options, if you click "Customize Search" there is an option called "tags" that will be added to the advanced search syntax when it is included in the criteria. Include the tag you want, and the folder you're searching within, and it will only return the entries with that tag set. From there:

For each entry (connect this to the above search)...

then inside of that, route the documents to where they need to go with a routing activity.

Approach # 2 (perhaps more resource intensive)

run a general search on the repository...

for each entry (of the search)...

conditional sequence (change entry : name to entry : tag) and set the tag in reference...

then proceed with the routing inside of the condition.

I like the first one better!

Tony

Awesome responses... in this particular case this is what needs to happen.  the whole point of the workflow is to search for entries and put a shortcut to them in a certain folder.  If the document is certain tags, then I don't want the shortcut to be created.

Could I perhaps write a search query so that it doesn't return documents if they have a certain tag on them? If so, what would that kind of query look like...  This is the search query I have so far...

{[Dallas Dermatology]:[Account Number]="%(PatternMatching_acctNUM)"} & {LF:LOOKIN="Documents\Patient Charts A-Z"}

Hi Lindsey,

It looks like you have a number of good answers to your question. If one provided the answer you needed, please click the “This answered my question" button.

If you still need assistance with this matter, just update this thread. Thanks!