Three folks have asked me about this just today. They wanted to create file names for FTP, Email or WebDAV that have some dynamic component to them e.g. TIM1212009.pdf where the numeric values relate to the date.
Well I learned something today, its supported on the standalone server. Its not that Leslie had not documented it; its just, its tucked away in the API documentation.
You can use the date expressions for a couple of properties. Those expressions will be translated with the actual values just before the delivery. Available expression are following.
For example, if you specify my_file_%y%m%d.txt for the filename, the actual filename will be 'my_file_20051108.txt'.
During some testing we have found that the following statement is not quite true. If you use unsupported expressions such as %a%b%b.pdf you file will arrive on the destination server as defined ie %a%b%b.pdf.
All undefined expressions will be translated into 0 length string, for example, if you specify my_file_%a%b%c.txt, it will be my_file_.txt. You can escape the '%' letter by passing '%%'.
The properties that support the date expressions are as follows.
This can be set either in the standalone scheduling page or when using the delivery APIs.