Mergemill Template Tags - System Values

<?YearNum?>	Current year number, such as 2010 if the job run date is March 31, 2010.
<?MonthNum?>	Current month number, such as 3 if the job run date is March 31, 2010.
<?DayNum?>	Current day number, such as 31 if the job run date is March 31, 2010.
<?DateYMD?>	Current date in the yyyy-mm-dd format, such as 2010-03-31.
<?DateLong?>	Current date in Long format. Example (US): Wednesday, 31 March, 2010.
<?DateAbbr?>	Current date in Short format. Example (US): Wed, Mar 31, 2010.
<?TimeHMS?>	Current time in Long format. Example (US): 1:23:32 pm.

<?PrevPage?>	File name of the preceding page in a page set. The value is empty if PageNum is 1.
<?NextPage?>	File name of the next page in a page set. Please note that this page may not exist.
<?PageNum?>	Current page number in a page set.

The system values are automatically maintained by Mergemill. They may be placed in your template in the form of a tag. Without the tag markers <? and ?>, they may also be used as expression operands, and as check values in IF and CASE tags.

Page Values

The page values are only for the current page set, which is generated using the current data streams. The PrevPage value is therefore empty for the first page of a page set, and NextPage will not be outputted if the current page uses up the remaining data values in the current streams.

The name of the file to be outputted is generated using the output file name components you specify in your job settings. PrevPage and the name of the current file to be outputted are both accurate. NextPage, however, may not exist.

If you use field values in building the file name or an output path component, Mergemill always uses the starting data value for the field. The starting data value is the column-one value used for an out-loop field in the page, or the column-one value used for an in-loop field in the first run of its loop in the page. To build the NextPage, Mergemill uses the starting column-two value for the field for the current page.

Please note that unlike page values, the sequence number part in building file names or output path components is assigned the starting number when the job begins, and is incremented once for each page generated till the whole job is completed. Data stream boundaries have no effect.