About file patterns

Administrators can specify the type of file that can invoke a service. Multiple file patterns can be established for each watched folder. A file pattern can be one of the following file properties:

Files with specific file name extensions; for example, *.dat, *.xml, .pdf, *.*
Files with specific names; for example, data.*
Files with composite expressions in the name and extension, as in these examples:
- Data[0-9][0-9][0-9].[dD][aA][tT]
- *.[dD][Aa][Tt]
- *.[Xx][Mm][Ll]

The administrator can define the file pattern of the output folder in which to store the results. For the output folders (result, preserve, and failure), the administrator can specify any of these file patterns:

%Y = year (full)
%y = year (last two digits)
%M = month,
%D = day of month,
%d = day of year,
%h = hour,
%m = minute,
%s = second,
%R = random number between 0-9
%J = Job name

For example, the path to the result folder may be C:\Adobe\Adobe LiveCycle ES3\BarcodedForms\%y\%m\%d.

Output parameter mappings can also specify additional patterns, such as these:

%F = Source Filename
%E = Source Filename Extension

If the output parameter mapping pattern ends with “File.separator”, (which is the path separator), a folder is created and the content is copied into that folder. If the pattern does not end with “File.separator”, the content (result file or folder) is created with that name. For more information about output parameter mappings, see Tips and tricks for watched folders.