More details are covered in the Repeat Model section of this paper.Įvery user, room or resource that can be involved in C&S workflow needs to have a calendar in some database somewhere. The ApptUNID and RepeatInstanceDates items form a key pair of values that uniquely identify a particular repeat instance. The parent note is identified by its ApptUNID item (which is its note universal ID), and the child note is identified by the same ApptUNID as the parent and the original RepeatInstanceDates. Repeating Events Repeating events are scheduled more than once over time and are represented by at least two notes in a parent-child relationship. The ApptUNID value is used to uniquely identify an event. If the note does not contain the CalendarDateTime item, it will appear only in the All Documents, Meetings, or All Calendar Entries views. Usually this is the same value as for the item StartDateTime. The note contains a CalendarDateTime item set to the date and time where it should appear in the Calendar view. These events are stored as a single note in the Notes calendaring system. They can have invitees or not, but the key is that they occur only once. Simple Events Simple events are events that do not repeat. Use the list-type views to determine if documents are missing from a Calendar view. If Calendar documents are malformed or corrupted, they may not appear correctly in Calendar views. This feature allows incoming unprocessed meeting notices (like invites and reschedules) to appear on the calendar, so they can also have CalendarDateTime and will appear in Calendar views. Notices can display in the Calendar view if ghosting (an optional new feature in Lotus Notes 8) is enabled. These do not show in the Calendar view because they do not have the CalendarDateTime item. Two major types of calendar items not usually showing in the calendar views are Responses, which use the form “Notice”, and parent documents of repeating meetings or appointments. Items that do not contain these fields appear in the list-type views, called All Documents, Meetings, or All Calendar Entries. Some entries like Reminders have a duration of zero and do not have EndDateTime but are still valid in the Calendar view. Calendar events appear in the calendar views if they contain the fields CalendarDateTime (for placement in the view) and usually StartDateTime and EndDateTime, to calculate duration of the entry. The Notes calendar contains a variety of views, each of which can be configured to the user’s preferences. The event announcement workflow is the same as Meeting, with certain response options disabled. It is used when the chair does not want responses, such as when a large group of people are invited to a teleconference. The event announcement is similar to a broadcast meeting in earlier releases, except that it does not expand groups, so it’s now possible to send a single invitation to an extremely large number of people. Used for events that last all day, such as a day away from work, or a seminar. This event is used for holidays and other anniversaries that repeat at regular intervals. An example is a doctor appointment.ĭesigned to be used to mark an anniversary. Meetings are the most complicated of the calendaring events and, because of the dialog between invitees and the chair person, meeting events are workflow events.Īppointments are like meetings, except that there is no participant to send to or receive notices from.
Invitees can only accept, decline, delegate, or counter propose the request. Changes include general information updates, rescheduling, adding users, and other actions. The owner of the meeting, usually the chair of the meeting, is the only person allowed to make changes to a meeting. Meetings involve more than one party, and this is the major difference between this type of event and the next four.
There are five different types of supported calendar events in Lotus Notes up through the Version 7 code stream.