The format of a token is as follows:
<token name=”xxxxxxxxxx”/>
Where,
xxxxxxxxxx defines the name of the token. The following tokens are supported in the file availability template:
| Token
|
Description
|
| fileid
|
This token is typically used in the URL to define the file name that has just been made available.
|
| clientfilename
|
This token defines the name that has been defined for the file on the client side.
|
| serverfilename
|
This token defines the name that has been defined for the file on the server side.
This information is not usually displayed on the users screen. If the notification message is sent to a user, it is good practice to not add this field to the file availability template. If this email is sent to an internal user, you can include this token in the email.
|
| description
|
This token defines the description that was defined for the file in the transfer record.
This is an important field for the client because it can describe the contents of the file to be sent or received.
|
| availabledate
|
This token defines the date that the file will be made available to transfer.
|
| expirationdate
|
This token defines the date that the file will expire and be no longer valid for transfer.
|
| transferdirection
|
This token defines whether the transfer will be an upload (client to
TIBCO MFT Internet Server server) or a download (TIBCO MFT Internet Server server to client).
|
