How to use filename tokens and placeholders in Titan MFT
Titan MFT supports using tokens in some fields like ‘Destination File’ and ‘Source File’. The pipe character ‘|’ can be used in Destination File to represent the original filename and extension. For example, you could set Destination File to “COPY_|” and if the original file was “titanmft.txt” it would then become “COPY_titanmft.txt” in the destination.
Supported Destination Filename Placeholders
The following placeholders can be used within the Destination File field:
|
Placeholder |
Description |
|
<FILENAME> |
Original filename without extension |
|
<EXT> |
Original file extension without the dot |
|
<DATE> |
Date resolved using destination date settings |
|
<SEQ> |
Sequence number extracted from the source filename |
|
<#> |
Auto-incrementing copy number (no padding) |
|
<###> / <####> |
Auto-incrementing copy number with zero padding |
|
<INDEX> |
Sequential transfer index |
|
<LLL> |
Left 3-digit sequence slice |
|
<RRR> |
Right 3-digit sequence slice |
|
<PARENT> |
Parent folder name |
|
$1, $2, ${name} |
Regex capture group replacements when using Regex pattern matching Destination File= $2_$1_report.<EXT> source = 2024_Sales.txt Destination = Sales_2024_report.txt |
Destination Filename Examples
|
Template |
Source File |
Result |
|
PROD_| |
testfile.txt |
PROD_testfile.txt |
|
<FILENAME>_backup.<EXT> |
testfile.txt |
testfile_backup.txt |
|
<FILENAME>_<DATE>.<EXT> |
report.txt |
report_20260608.txt |
|
file_<###>.txt |
newfile.txt |
file_001.txt, file_002.txt, etc. |
|
product_<INDEX>_<FILENAME>.<EXT> |
file1.txt |
product_1_file1.txt |
|
prod_<LLL>_<RRR>.txt |
titan_seq_00123_report.txt |
prod_001_123.txt |
|
<PARENT>_<FILENAME>.<EXT> |
testfile.txt |
Source_testfile.txt |
Other Fields Supporting Template Tokens
Source Filename
The Source File field is used for file matching rather than file renaming.
Supported tokens:
<DATE> – Date token interpreted using SourceDateFormat
SourceFilename: test_file_<DATE>.txt
SourceDateFormat: <YYYY><MM><DD>
Files that MATCH:
test_file_20240615.txt (June 15, 2024)
test_file_20240101.txt (January 1, 2024)
<SEQ> – Sequence token matching
SourceFilename: test_seq_<SEQ>.txt
Files that MATCH:
test_seq_1.txt (1 digit)
test_seq_007.txt (3 digits)
PostTransferMoveOnSuccess / PostTransferMoveOnError
These fields support date, time, and job-related variables when moving files after transfer.
Supported tokens:
<%JOB_NAME%>
<%NOW:format%>
<DATE>
<DATEUTC>
<YEAR>
<MONTH>
<DAY>
<HOUR>
<MINUTE>
<SECOND>
<TIME>
<TIMESTAMP>
Examples:
processed/<YEAR>/<MONTH>
archive/<DATE>
backup/<%NOW:yyyyMMdd_HHmmss%>