System Node Tags

System node tags embed data that is not derived from the message or the channel: the current date and time, a generated identifier, or the QIE-assigned source and message IDs. Unlike the tags described in Node Tags, a system node tag takes no source indicator and no node path: the tag name is the whole tag.

The following system node tags are defined:

System Node Tag	Syntax	Description
ENDPOINT_URL	%%ENDPOINT_URL%%	The Endpoint URL node tag applies to SOAP based web service calls only and is replaced with the associated web service endpoint URL.
SYSTEM_DATE	{SYSTEM_DATE[yyyy-MM-dd]}	The system date node tag is replaced with the current system date/time in the specified format. The format is required. Without a format indicator the tag is not recognized and renders as an empty string. See the format indicators described in Node Tags. The system date/time can be adjusted by adding a modifier after SYSTEM_DATE in the format of [+/-][number][y/M/W/d/H/m/s/S]. Short codes are y = year, M = month, W (or w) = week, d = day, H = hour, m = minute, s = second, S = millisecond. The legacy aliases Y, D, and h are also accepted for backward compatibility. Long-form unit names (YEAR, MONTH, WEEK, etc.) are not accepted inside a node tag; use them with the qie.getSystemDate(offset, dateUnit) and qie.isDateWithin() functions instead. For example, to adjust the date ahead 2 hours: {SYSTEM_DATE+2H[yyyy-MM-dd]}; to adjust it back one week: {SYSTEM_DATE-1W[yyyy-MM-dd]}.
UTC_DATE	{UTC_DATE[yyyy-MM-dd]}	The UTC date node tag is replaced with the current UTC date/time in the specified format. The format is required. Without a format indicator the tag is not recognized and renders as an empty string. See the format indicators described in Node Tags. The UTC date/time can be adjusted by adding a modifier after UTC_DATE using the same [+/-][number][y/M/W/d/H/m/s/S] grammar described for SYSTEM_DATE above (including the legacy Y/D/h aliases). For example, to adjust it ahead 5 minutes: {UTC_DATE+5m[yyyy-MM-dd]}.
UUID	{UUID}	The UUID node tag is replaced by a randomly generated Universally Unique Identifier (UUID) with dashes.
UUID-NO-DASHES	{UUID-NO-DASHES}	The UUID-NO-DASHES node tag is replaced by a randomly generated UUID without dashes.
QIE Source ID	{SOURCE_ID}	Returns the unique QIE source ID that gets generated for each message that passes through QIE. Available in QIE 26.1.1 and later. The deprecated tags {SRCID} and {MSGID} also return the source ID and are retained for backward compatibility only.
QIE Message ID	{MESSAGE_ID}	Returns the unique QIE message ID that gets generated for each destination message. Available in QIE 26.1.1 and later.
No Extension	{no-extension}	A placeholder that survives template evaluation and is interpreted by the File and FTP destinations and by the qie.writeFTPFile* and qie.writeSFTPFile script functions to write a file with no extension. See FTP Destination.