RIFE is able to pre-filter names of value tags when a template is compiled and thus offers an easy way for a template parser to automatically attach behaviour to specific value ids. That is how the engine-specific HTML template parser is able to replace the following value names automatically without any needs for additional scanning and parsing:
EXIT:QUERY:name
is replaced by the url to activate the corresponding exit, all data will be passed through an automatically constructed query string.
EXIT:FORM:name
is replaced by the url to activate the corresponding exit, no query string will be present and it's thus intended to be used as the action of a form.
This value id has to be always accompanied by the EXIT:PARAMS:name value id.
EXIT:PARAMS:name
is replaced by the data that will be passed to the corresponding exit, the data will be formatted as hidden HTML form parameters.
This value id has to be always accompanied by the EXIT:FORM:name value id.
SUBMISSION:QUERY:name
is replaced by the url to activate the corresponding submission, all data will be passed through an automatically constructed query string.
SUBMISSION:FORM:name
is replaced by the url to activate the corresponding submission, no query string will be present and it's thus intended to be used as the action of a form.
This value id has to be always accompanied by the SUBMISSION:PARAMS:name value id.
SUBMISSION:PARAMS:name
is replaced by the data that will be passed to the submission, the data will be formatted as hidden HTML form parameters.
This value id has to be always accompanied by the SUBMISSION:FORM:name value id.
PARAM:name
is replaced by the value of the corresponding submission parameter in the context.
INPUT:name
is replaced by the value of the corresponding input var in the context.
OUTPUT:name
is replaced by the value of the corresponding output var in the context.
ELEMENT:id
allows for element embedding, you provide it with the id of an element in the site structure. You can either use absolute ids (by starting with a dot) or use relative ids. For the latter you use circumflex (^) to go up one level and the dot (.) to seperate the levels (very similar to directories). For example:
or from another an element in .MYSITE.THEIRSITE
The element will be processed as if it was accessed directly and receives the same request context as the embedding element. The embedded element is unable to modify the context of the embedding element, except for globalvars and cookies. If an embedded element is bound to an url in the site structure, submissions will be sent to its own personal url. If it has no url, submissions will be sent to the first embedding element that is found that is mapped an url.
CONFIG:param
is replaced by the value of the corresponding parameter in the default configuration participant that has been initialized by the repository.
L10N:key
is replaced by the value of a resource bundle key, more information here.
