If the source file is moved to more than one hot folder in a job, its
file name in each of the hot folders must be different.
Note: Naming patterns are not available for target group name.
Building valid naming patterns
Each naming pattern must be constructed with valid syntax, or a smart
hot folder will not behave as expected.
The following diagram shows the components of a valid naming
pattern. These apply to all three naming patterns in a smart hot folder
(source, target job, and target file).
●
Wild cards must be enclosed in square brackets.
●
The following wild cards are accepted:
○
[%] to match letters (A-Z, a-z)
○
[#] to match numbers (0-9)
○
[$] to match letters or numbers (A-Z, a-z, 0-9)
●
Adding a descriptor after the wild card (with no space) creates a
back reference. Choose a descriptor that clearly identifies the
information that is being referenced.
Important: You must add a descriptor to use the same wild card more than
once within a naming pattern. For example, the naming pattern [%].[%] is not
valid because it repeats the same wild card more than once. To make it valid,
add a descriptor after each wild card, such as [%Name].[%Ext].
●
Adding a character delimiter (a colon and number after the
descriptor) to a wild card in the file naming patterns limits the
number of characters that are matched. For example, [$Name:6]
matches the first six letters or numbers of the source file name.
Important: Do not use a character delimiter in the target job naming pattern. A
job will not be found or created.
●
Non-variable words and characters in the naming pattern must
exactly match the source file name. For example, to match the
source file naming pattern Job[#ID].[%Ext], all source files must
start with Job.
920
Chapter 18—Automation
