Chapter 4 Customizing Meeting Notifications

How to Customize a Notification Template

Identifying Notification Templates

The notification templates that Cisco Unified MeetingPlace uses are as follows:

NotifySchedule.tpl—Used to generate notifications for newly scheduled meetings.

NotifyReSchedule.tpl—Used to generate update notices for meetings that have been rescheduled.

NotifyCancel.tpl—Used to generate cancellation notices for meetings that have been cancelled.

NotifyNoShowRecur.tpl—Used to generate a notification reminder for a recurring meeting chain that should be cancelled according to the number of no-show meetings that have passed.

NotifyRenewRecur.tpl—Used to generate a notification reminder for a recurring meeting chain that is within a preset number of meetings before its expiration.

NotifyScheduleVideo.tpl—Used to generate notifications for a newly scheduled meeting that include video endpoints.

NotifyReScheduleVideo.tpl—Used to generate update notices for a meeting that includes video endpoints that have been rescheduled.

Modifying the Content of a Notification Template

Notification templates provide the content that appears in the body of outbound e-mail messages. These templates use permanent text and tags to provide content. To modify the content of a template, you can change the permanent text and add or delete tags.

About Tags

Tags are predefined variables that serve as placeholders for specific Cisco Unified MeetingPlace information that you can include in the body of a notification template. When the Cisco Unified MeetingPlace SMTP E-Mail Gateway uses the template to generate an e-mail message, the embedded tags are replaced with specific information about the meeting. This information is extracted from the schedule request and Cisco Unified MeetingPlace registry.

Tags have the following format:

<!--#Cisco...>

Note The syntax <!--#LATD...>, used in releases prior to 5.4, can also be used with Cisco Unified MeetingPlace Release 5.4 and later.

Each tag is associated with a specific Cisco Unified MeetingPlace parameter and serves as a link to that parameter in notification templates. For example, the tag <!--#Cisco Month --> is associated with the parameter that specifies the month in which the meeting is scheduled to take place. If a meeting date is 10/14/2006, then the word October appears in the e-mail message wherever this tag is placed in the notification template.

To view a list and definitions of the tags that you can use in notification templates, see Appendix A, “Tags You Can Use in Notification Templates.” The appendix also suggest labels you can use with the tag in the body text to identify the tag information for message recipients.

To use a tag, enter the complete content of the tag including the brackets, <>, in the body of the template where you want the tag to appear. The information that replaces the tag can vary in length.

Administration Guide for Cisco Unified MeetingPlace SMTP E-Mail Gateway Release 5.4

 

OL-11018-01

4-3

 

 

 

Page 31
Image 31
Cisco Systems SMTP manual Identifying Notification Templates, Modifying the Content of a Notification Template, About Tags