Ensure that Subject Line is selected. Using this selection indicates that you are defining a subject line.

Enter a unique identifier for this subject line. Do NOT include spaces in your entry. For example, enter REMINDER_SUBJECT to define a subject line for a reminder notification.

Enter a description of how the subject line is used. For example, enter "Subject Line for reminder template."

Enter the subject line for the email notification. Use the syntax ${table.field} as a placeholder for specific field values.

For example, enter “Event ${activity_log.action_title} is scheduled to begin on ${activity_log.date_scheduled}”. This entry includes the syntax for entering a placeholder for the Event Title and its Date Schedule. See Configuring Email Messages for information on creating messages.

Use this field to keep track of any standard messages that you have changed from the default message value.

If you are referencing database fields in the message, you must set the Is Rich Text field to Yes.

Messages can be created using the new Rich Message format. The format utilizes Freemarker (http://freemarker.sourceforge.net ) software, and the messages entered are templates that use parameters that the system will fill in at runtime. See the topic Workplace Services / Service Desk / System Integrator / Service Desk Steps / Configuring Email Messages in User Help.

Ensure the Message Body is selected. Using this selection indicates that you are defining the message content.

Enter the body text for the email notification. Use the syntax ${table.field} as a placeholder for specific field values.

You can use either ${afm_metrics_definitions.metric_name} or ${afm_metrics_Trend_values.metric_name}

For notifications that are sent for other granularities then 'all' (all = entire portfolio), for example 'by Building', for greater clarity, you can include the granularity value in the message.

For example:

“"${afm_metric_trend_values.metric_value} EH&S Requirements deadlines are approaching for building ${afm_metric_trend_values.collect_by_value}, on date ${afm_metric_trend_values.date_collected}.

Please be alerted as this is considered a critical number of requirement deadlines.

For more information, please access your Environmental Manager Home Page:

http://localhost:8080/archibus/”

This entry includes the syntax for entering a placeholder for metric details. See Workplace Services / Service Desk / System Integrator / Service Desk Steps / Configuring Email Messages in the User Help for information on creating messages.

Use this field to keep track of any standard messages that you have changed from the default message value.

Describe the purpose of this template, for example, “Notify if the Monthly Energy Consumption is Above Target”

For better identification, it is best to include in the description a reference to the scope of the notification, or the Metric Name- for example:

"Daily Warning: EH&S Requirements Deadlines Approaching

(High Warning Limit Notification)"

Select a predefined subject, or enter a custom one. You defined subject lines in step 2 of this Help topic.

In the messages table, the messages specifically for metrics are associated with the Primary Application (messages.activity_id) = ‘AbSystemAdmin” and Referenced By (messages.referenced_by) = ‘METRICS’.

Select a message body that has been defined for metrics. You defined messages in step 2 of this Help topic.

In the messages table, the messages specifically for metrics are associated with the Primary Application (messages.activity_id) = ‘AbSystemAdmin” and Referenced By (messages.referenced_by) = ‘METRICS’.

Specify the employees or group of recipients who should receive the notification message

This is entered as a comma or semicolon-separated list of email addresses. You can select from the list of employees or manually enter an email address.

You can also have the application dynamically select the recipient by using the following format to specify the role that should receive the notification.

(FreeMarker): ${activity_log.manager.em.email}

See Configuring Dynamic Email Recipients .

This is a read-only field that describes the date on which the Manager receives the notifications, if the notification condition is met.

The email notification is triggered on the metric’s collection date (‘afm_metric_trend_values.metric_date). This date is determined by the recurrence pattern set when defining the metric (afm_metric_definitions.recurring_rule).

From the list, select the status and condition that triggers this notification to be sent. If the metric value for the Collection Date meets the value defined for the condition, then the notification is sent. The values for these conditions are part of the metric definition.

• >= Report Limit High Critical
• <= Report Limit Low Warning
• <= Report Limit Low Critical
• <= Report Limit Low Warning OR >= Report Limit High Warning
• <= Report Limit Low Critical OR >= Report Limit High Critical
• <= Report Limit Target
• >= Report Limit Target

If you want notifications to be sent again after the first notification is sent, enter the number of days between these subsequent notifications. This entry depends on the business priority for the metric, and how often the metric is collected:

• Leave this field blank if you want the notification to be sent only once, the first time the triggering conditions are met.
• When entering this field, you need to consider how often the metric is collected. For example, if the metrics are collected on a daily basis, there would be no need to make an entry here.
• If the metric is especially critical (such as the number of regulations due this week), and the metric is calculated on a less than daily basis, you might want to send the message additional times during the week.

Enter the maximum number of notification to be sent. Notifications are sent until the Event Status changes, or until the maximum number of notifications has been sent, whichever occurs first. If you do not enter a maximum number, notifications are sent until the Event Status changes.