...
Additionally, if singleLocation is true, then outputFileName can contain location attribute ids, e.g. "H_ (BASIN)", where tags between "@" signs refer to location attributes that are defined in the locationSets config file. These tags will be replaced with the corresponding attribute values of the location of the report. These values can be different for different locations. See 22 Locations and attributes defined in CSV files, Shape-DBF files or external tables for more information. If required to use a "@" sign in this element without using locationAttributes, then need to add an extra escape character "@" before each "@" sign. In other words "@@" is replaced with a single "@" sign.
%TIMESERIES_POSTFIX(dateFormatId)%
The TIMESERIES_POSTFIX tag will be replaced by the minimum date of the configured timeSeries in the report. If no timeSeries have been configured, the system date will be used. An optional dateFormat id can be specified. For example: %TIMESERIES_POSTFIX(dateFormatId)% where dateFormatId is the id of a dateFormat as specified in the reports declarations. If no dateFormatId is passed, the default date format ddmmyyyym will be used.
%CURRENTTIME(dateFormatId)%
The CURRENTTIME tag will be replaced by the current system time. An optional dateFormat id can be specified (see TIMESERIES_POSTFIX).
%TIMEZERO(reportVariableId;dateFormatId)%
The TIMEZERO tag will be replaced by the minimum T0 of the timeSeries configured by the reportVariableId. If no timeseries are configured, the current system time will be used. The reportVariableId is required. The dateFormatid is optionalAn optional dateFormat id can be specified (see TIMESERIES_POSTFIX).
N.B.: Be careful in specifying date formats that are compatible with the filesystem. For example and : in the dateformat will not be compatible with the windows filesystem.
...