Page History

...

• All special entries, of the form node.XYZ or event.XYZ are replaced by the node or event property XYZ.
  If the property is structured, with sub-elements (e.g. event.script), then these are shown on separate lines and indented with a tab character.
• The entry link.eventcontext is replaced by a hyperlink to the event context page.
• The entry link.nodecontext creates a hyperlink to the node context page.
• Entries of the form node.* are translated into a list of all "standard summary" node properties, which are defined in opCommon.nmis, key opevents_gui_event_node_summary_list.
  For this summary, the property name is shown first, followed by a colon and a space, the property value, and a newline; repeated for each property. There is a trailing newline.
• The form event.* works similarly, but for event properties and is not restricted to a default set. It also creates a trailing newline.

Associating an email contact with a template

The configuration file Contacts.nmis contains the list of (email) contacts, and needs to be adjusted if you want templates other than default  to be used. The example file as shipped shows where the email template is set:

'contact1' => {
	'Contact' => 'Contact1',
...
	'Email' => 'nobody@localhost',
	'EmailTemplate' => 'default',

Simply change the value after EmailTemplate to the name of your desired template. If opEvents cannot find the named template, or if no EmailTemplate setting is present, then the default template will be used. If that template doesn't exist or work, then you will receive your emails formatted with a hardcoded fallback template that includes a warning notice at the top.