My example was per what I guessed was OP’s filename so the solution varies based on the specifics. That being said, here is what the smart rule looks like…
Give me a few…
- Target the appropriate location. Being specific is better than too general, especially if a rule is running unattended.
- Avoids processing existing documents in subgroups.
- Avoids processing existing documents. They can be processed manually after the fact, as needed.
- Target specific document types. You could use compound criteria to match more than one kind but
Any Documentis likely unwanted. - This matches months by name, accounting for abbreviations and caps. The pipe (|) is used but
ORwould also work. - This looks for 2 thousand-something in the name.
- Once tested and confirmed it’s running properly, the
On Importingevent trigger could be added. - This is specific to the OP’s naming convention and would be different (or unneeded) for others.
- Filing works in the current database. A
Moveaction is required to move the document to a different database. - Filing using placeholders, in this case in
year/monthnested groups.
Note: This is a proof-of-concept and works per my understanding of the requirements I have (and still no full name example). But it’s employs solid filtering and action techniques to be used in all kinds of smart actions (rules and batch process configurations).