Examples: invalid naming patterns

This topic includes examples of naming patterns that don't work and the reasons why.

Example 1: Incorrect file naming syntax

In the following example, the source file is accepted by the smart hot folder, but a job is not created because the back reference is incorrect.

The reason: You cannot include a character delimiter (for example, :6) in the target job naming pattern.

Example 2: Incorrect file naming syntax

In the following example, the source file is accepted and a job is created, but with the wrong name. The job name is named eps_pages because the second [$] wild card (that is not back-referenced) overwrites the first [$] wild card (that is not back referenced).

The reason: You cannot use a wild card more than once without a named back reference. The created job is named whatever is referenced by the last wild card.

Example 3: Insufficient back references

In the following example, a new job is created for every source file.

The reason: The target job naming pattern is too generic; there are insufficient back references. All source files match the [$] target job file naming pattern.
Note: A generic source file naming pattern is valid only when moving or renaming files, as shown in the following example.

Example 4: Excessive back references

In the following example, a new job is created for every source file.

The reason: The target job naming pattern is too specific with the [$] wild card and will match anything in the source file name.
Recommendation: Remove [$].ps in the target job name and change the target job name to [%]_[#Date]_pages.

Example 5: Incorrect wild card

In the following example, the source files are not moved, because some of the characters in the file name do not match the wild card.

The reason: The [%] wild card matches letters only, and there are numbers in the file name extension.