Meeting Messages

This message type creates messages based on meetings that the citizen is invited to, provided that they are created via the curam.meetings.sl.impl.Meeting API. This API raises events that the meeting messages functionality consumes. There are other ways of creating Activity records without this API, but meetings created in these ways will not have related messages created as the events will not be raised. These messages are persisted to the database. They replace each other, for example, if a meeting is scheduled and then the location is changed, the initial invitation message will be replaced with one informing the citizen of the location change. The properties file EJBServer\components\CitizenWorkspace\data\initial\blob\prop\CitizenMessageMeetingMessages.properties contains the properties for the meeting messages text, message parameters, links and images. This properties file is stored in the resource store. This resource is registered under the resource name CitizenMessageMeetingMessages. To change the message text of meeting messages, or to remove placeholders or change links, a new version of this file must be uploaded into the resource store. The table below describes the messages created when various events related to meetings occur in the system, and the properties in CitizenMessageMeetingMessages.properties that relates to each message created. Different versions of the message text are displayed depending on whether the meeting is an all day meeting, whether a location has been specified, and whether the meeting organizer has contact details registered in the system. Accordingly, the property values in this table are approximations that relate to a range of properties within the properties file. Please refer to the properties file for a full list of the message properties.

Table 1. Meeting messages
Meeting event	Message Properties
Meeting invitation	Non.Allday.Meeting.Invitation., Allday.Meeting.Invitation.
Meeting update	Non.Allday.Meeting.Update., Allday.Meeting.Update.
Meeting canceled	Allday.Meeting.Update., Allday.Meeting.Cancellation.

Customization of the Meeting Messages Display Date

The number of days before the meeting start date that the message should be displayed to the citizen can be configured using a system property. By default the property value is set to 10 days, however, this can overridden from property administration.

The meeting message expires (i.e. it is no longer displayed to the citizen) at the end of the meeting, i.e. the date time at which the meeting is scheduled to end.

Table 2. Meeting message display date property
Name	Description
curam.citizenaccount.meeting.message.effective.days	The number of days before the meeting start date that the message should be displayed to the citizen.

Customization of Activity types for which to create Meeting Messages

Meetings are stored on the Activity entity. There are different types of Activity, which are stored in the CT_ActivityType codetable. The list of activity types for which to create messages can be customized using the following property. The default code is 'AT2' which represents Meeting.

Table 3. Activity types for which to generate meeting messages
Name	Description
curam.citizenaccount.meeting.activity.types.to.generate.messages	A configuration setting to dictate the types of activities for which messages will be generated.