Previous Page | Table of Contents
$
__
_ViewIcon | Number | The icon to display in the calendar views for the entry.
Valid values are:
9 = Event
10 = Confirmation or Reminder
33 = Reschedule
38 = Counter decline
39 = Counter
63 = Anniversary
71 = Repaired or obsoleted entry (new for 8.5)
81 = Cancel
82 = Completed
83 = Accept
84 = Decline or Delegator response
133 = Invitation or Delegate Invitation
157 = Uninvited or Removed
158 = Meeting
160 = Appointment
168 = Task |
_ViewIcon2 | Number | The icon to display in the calendar views for the entry.
Valid values are:
11 = Blue informational icon. Indicates that the message contains a personal comment from the sender.
33 = Reschedule |
A
Alarms | Text | User interface field.
Value is “1” when an alarm is enabled and is “” when alarm is disabled or was never enabled. |
AllowBusyAccess | Text / Text List | Calendar profile / R&R room profile item
Value is a list of canonical names of entities allowed to access the busytime of the entity whose profile this list appears on.
The names in the list should not contain any domain names.
A value of “” means anyone. |
AllowBusyDetailAccess | Text / Text List | Calendar profile / R&R room profile item
New for 6.0
Value is a list of caonical names of entities allowed to access the detailed information in busytime of the entity whose profile this list appears on.
A value of “” means anyone. |
AllowControversialFields | Text | Calendar profile / R&R room profile item
New for 6.0
Value indicates if items deemed to be potentially sensitive may be harvested as part of detail harvesting in busytime. The list of what items are deemed to be harvested if this setting is enabled are found in the ControversialFields item.
Value(s):
“” = No (Default)
“0” = No
“1” = Yes |
AltBlindCopyTo | Text List | Mail recipient field
Alternate names for the “Bcc” recipients. Defaults to primary name when the alternate name is unavailable.
This list must be kept in sync with the BlindCopyTo field. |
AltChair | Text | Alternate Name of the owner. |
AltCopyTo | Text List | Mail recipient field.
Alternate names for the “Cc” recipients. Defaults to primary name when the alternate name is unavailable.
This list must be kept in sync with the CopyTo field. |
AltDelegator | Text | Alternate name of the calendar owner of delegator. |
AltDelegeeName | Text | Alternate name of the person being delegated to. |
AltFYINames | Text List | C&S attendee field.
Alternate names for users who are not involved in a meeting, but should be aware of it. Only available for the Chair.
This list must be kept in sync with the FYIAttendees field. |
AltOptionalNames | Text List | C&S attendee field.
Alternate names for users who may participate in a meeting.
This list must be kept in sync with the OptionalAttendees field. |
AltRequiredNames | Text List | C&S attendee field.
The alternate name(s) of required users (To) on the entry.
For R5 and later, this list contains the alternate name(s) of any required attendees to an entry. It is organized similar to mail alternate names.
IMPORTANT: This list must be kept in sync with the RequiredAttendees field. |
AltSendTo | Text List | Mail recipient field.
Alternate names for the “To” recipients. Defaults to primary name when the alternate name is unavailable.
This list must be kept in sync with the SendTo field. |
AppendEndTime | Date/Time | Has same value as EndTime. |
AppendStartTime | Date/Time | “Overrides” the StartTime value for an entry. This value, if found, is used to change the calculated start time of an entry. |
AppointmentLead | Text | The default amount of time before an Appointment starts that the alarm should trigger. The value MUST be in minutes and no other unit. The value is only of use when SetAlarmAppointment = 1. This item is used only on calendar profiles. |
AppointmentType | Text | Indicates what kind of calendar entry this is.
Valid values are:
0 = Appointment
1 = Anniversary or Personal ToDo
2 = Event or Group ToDo
3 = Meeting
4 = Reminder |
ApptUNID | Text | A text version of the entry's original/actual UNID.
Generally this item should be the UNID converted to text, but it could also be the iCalendar UID or some other value. This also makes iCalendar support (introduced in Notes version 6) easier since it maps directly onto iCalendar's UID property. |
ApptUNIDURL | Text | The URL used to attend the online meeting place on the Online meeting server. Calculated during the save process.
Default: value is "" |
AssignedTo | Text | A list of users a task is assigned to. This is the task equivalent of RequiredAttendees and should be treated correspondingly. |
AssignedState | Text | Used by tasks for communicating status. |
AudioAndVideoFlag | Text | R&R room profile item
The audio/video options flag for Sametime meetings.
Valid valuesare:
"0" - None (Default)
"1" - Audio and/or Video settings |
AudioFlag | Text | R&R room profile item
The audio only option flag for Sametime meetings.
Valid values are:
"" - None (Default)
"1" - Audio only |
AudioVideoFlags | Text | The audio/video options for Sametime meetings.
Valid values are:
"0" = None (Default)
"1" = Audio only
“2” = Audio and Video |
AudioVideoSelectionList | Text | R&R room profile item
This R&R setting only applies to "Online" R&R types.
For regular rooms or resources the value must be: "" (Default) |
AutoProcessForwardTo | Text / Text list | R&R room profile item
Stored on the room or resource profile document in the R&R dB. Performs the same function as ResourceOwner on a reservation request. See ResourceOwner. |
AutoProcessType | Text | Calendar profile / R&R room profile item
Indicates what kind of owner restriction, if any, exists for a room or resource. Indicates the autoprocessing settings for a user when on a Calendar profile. Not all values are valid for all profile docs.
Value(s) are:
“0” = None (R&R) / Automatically process meeting invitations from all users (Calendar)
“1” = Only the Owner can book (R&R) / Delegate meeting invitations to the following person, the list is specified in AutoProcessUserList (Calendar)
“2” = Only people on specified list can book. See AutoProcessUserList (R&R) / Automatically process meeting invitations from specified users (Calendar)
“3” = Only people on list can book via autoprocess; others need owner approval (R&R)
“4” = Not used
“5” = Inbox management: Calendar managed by another . New with R6 and may be obsolete now.
“6” = Forward notifications of invites to specified users. New to R6. (Calendar)
“7” = Just like “0” and “2” in that you automatically process meeting requests. Supports using AutoProcessFromType to decide which requests to do (Anyone/Only Some/Anyone but). Only really used for "Anyone but" because we map "Anyone" and "Only Some" to”0” and “2” on-disk respectively to maximize backwards compatibility. New with R6. (Calendar)
“8” = Just like “1” in that you specify a delegate for your meetings requests. Supports using AutoProcessFromType to decide which requests to do (Anyone/Only Some/Anyone but). Used for "Only Some" and "Anyone but" but not "Anyone" because we map "Anyone" to 1 on-disk to maximize backwards compatibility. New with R6. (Calendar)
“D” = Disabled (R&R) / No autoprocessing of invitations (Calendar) |
AutoProcessUserList | Text / Text list | R&R room profile item
List of the names of the only users (or groups) which are allowed to reserve a “Specific People” or “Autoprocess” type of room without requiring owner approval. |
AutoRemoveFromInbox |
| Calendar Profile Item. A user preference to NOT see replies in their Inbox. If a user selects this option, replies are automatically removed from Inbox (but are still visible in the Meetings view). |
AutoReminder | Text | R&R site option
Indicates if the Autoreminder feature is enabled or for the site. If not enabled then all the other autoreminder settings are ignored.
Valid values are:
"On" = Autoreminders are enabled
"Off" = Autoreminders are disabled |
AVSlctLst | Text / Text list | R&R room option
Default for non-Sametime rooms is “”.
Default for Sametime rooms is “1” |
B
BlindCopyTo | Text | Mail recipient field.
Primary names for the “Bcc” recipients. Each recipient is only able to see their own name in this field. |
Body | Rich Text or MIME-PART | The description of the appointment. This can be in Rich Text format or HTML format; however, auxiliary processes such as the IMAP server behave better when it is in RichText format. |
Broadcast | Text | Indicates whether the Chair wants to receive any responses. Valid values are:
1 = Broadcast, do not RSVP
Any other value = RSVP (Default)
|
BookFreeTime | Text | User interface field.
Indicates whether an entry is displayed as “penciled in”. It is used by the template but it is not used by the busytime system which relies on the $BusyPriority item. This should be kept in sync with the $BusyPriority item.
Value is “1” if “Pencil-In” has been checked.
Value is “” otherwise. |
C
CalendarDateTime | Date/Time List | A date & time value as to when the entry should show up in the calendar view. Mainly, the presence of this item indicates that it belongs in the Calendar view and when it should appear. |
CalForwardChairNotificationTo | Text List | C&S preference item
Indicates whom notices should be forwarded to when the Chair receives a response back. This is for managed Calendars where another user or users need to be notified of a response back to the Chair. |
CalForwardInviteeNotificationTo | Text List | C&S preference item
Indicates whom notices should be forwarded to when the user receives a C&S workflow message from a Chair. This is for managed Calendars where another user or users need to be notified of a new C&S notice or update from a meeting Chair. |
CalForwardPrivateMode | Text List | C&S preference item
Indicates what level of information should be included on a forwarded notice.
Values are:
0 = None. Do not forward / notify.
1 = Hide details. Only send a summary.
2 = Full details. Send a complete copy (subject of entry, etc). |
Capacity | Number | R&R room option / C&S workflow item
On an room document the value indcates the capacity of a room can hold. If a reservation request exceedes the capacity of a room it will still be accepted; the Acceptance notice the Chair receives will include a note indicating this since not all invitees may be physically attending.
On a reservation request the value indicates the number of meeting participants. The value is compared against the value of the specified room in order to warn the Chair if they have possibly exceeded the capacity.
Values should be positive integer values. |
Categories | Text | Category picked or entered by the user. |
Chair | Text | Name of the user who is chairing or organizing the entry.
This should be the canonical name of the calendar owner when a meeting is created from Lotus Notes.
It can be an Internet address when meeting is created from outside Notes. |
ChairDomain | Text | Notes domain of the user who is chairing or organizing the entry. If Chair is in Internet format, then this item is empty. |
CommonNameResourceName | Text | R&R room option
The friendly or common name part of the room or resource name. |
ConferenceDatabase | Text | R&R room option
The name of the Sametime conference database where the request will be forwarded to by the Rooms & Resource Manager. It appears on ALL room or resource documents even if they are not a Sametime entry.
Value must be “stconf.nsf” |
ControversialFields | Text / Text List | Calendar profile / R&R room profile item
New for 6.0
Value indicates which ‘controversial’ or potentially sensitive items the user will allow to be harvested into busytime. This typically means meeting subjects which can contain information that not everyone should be able to see (eg: Teleconference information).
The list is only used if AllowControversialFields item is set to “1” and detail harvesting has been enabled on the Default Domain Configuration doc in the NAB.
Default: “” |
CopyTo | Text | Mail recipient field.
Primary names for the “CC” recipients.
Contains the names of the optional invitees to which this workflow message is being sent. |
D
DeclineReason | Text | The reason why a room reservation request was declined by a Room Owner.
Default: “” |
DelegateToList | Text list | Text list of delegees in the order in which they were delegated. The original invitee is not on the list. This can be an Internet address. |
Delegator | Text | Owner of calendar who is delegator. This can be an Internet address. |
Delegee | Text | Person being delegated to. This can be an Internet address. |
DeliveredDate | Date/Time | The date/time stamp when the notice was delivered to the invitee’s inbox or the R&R database.
This value is set by the Domino mail Router. |
DeliveryPriority | Text | The delivery priority chosen by the user (High|H, Low|L, Normal|N) |
DeliveryReport | Text | The Delivery Report options chosen by the user (None|0, Only on Failure|1, Confirm Delivery|2, Trace Entire Path|3) |
E
Encrypt | Text | Security mail option “Encrypt”. Value is “0” when not chosen by the user and “1” when chosen. |
EndDate | Date/Time | The UTC date & time at which the entry ends. It is derived from EndDateTime and is typically the same for non-repeating entries. In the rescheduling case, this will be the new date (& time) to which the base instance is being moved. |
EndDateTime | Date/Time List | The UTC date & time at which the entry ends.
The number of values in this item must match the number of values in the StartDateTime item.
|
EndTime | Date/Time | The UTC date & time the entry ends. It is derived from EndDateTime and is typically the same for non-repeating entries. This is a separate item from EndDate, even though they both share the same information, because a UI change for Notes R5 to split the “combo” Date/Time picker into two separate items requires two separate items. |
EndTimeZone | Text | The Notes timezone string for the EndDateTime.
Time zone strings are in the following format:
Fixed Time Zone:
Z=$DO=0$ZX=0$ZN=
Zone with daylight savings:
Z=$DO=1;$DL= > $ZX=0$ZN= |
EnterBlindCopyTo | Text List | C&S attendee field.
Primary names for potential users who are not involved in a meeting but should be aware of it. Only available for the Chair.
Present only on a draft meeting and mutually exclusive to FYIAttendees field. |
EnterCopyTo | Text List | C&S attendee field.
Primary names for potential users who may participate in a meeting.
Present only on a draft meeting and mutually exclusive to OptionalAttendees field. |
EnterSendTo | Text List | C&S attendee field.
Primary names for potential users who are required to participate in a meeting.
Present only on a draft meeting and mutually exclusive to RequiredAttendees field. |
ExcludeFromAll | Text | C&S preference item.
Indicates that C&S entries should be excluded from the “All Documents” view of the mail file. A “1” indicates C&S entries should be hidden. and will cause a “A” to be added to the ExcludeFromView item on the note.
|
ExcludeFromView | Text List | The view(s) to exclude the note from in the mail file. The values are not actual view names but some shorthand abbreviations of them (or their aliases). Valid values (for C&S at least) are:
A = All Documents (aka $All) view
D = Drafts
S = Sent
|
ExpandedList | Text / Text list | R&R room option
The expanded contents of AutoProcessUserList item. If the AutoProcessUserList only contains users then the two items will be the same. |
ExpandedOwners | Text / Text list | R&R room option
The expanded contents of AutoProcessForwardTo item. If the AutoProcessForwardTo only contains users then the two items will be the same. |
ExternalAddress | Text / Text list | R&R room option
The name of the mail-in database entry where the Rooms & Resource Manager should forward the request for a Sametime meeting. The value should match the name given to the stscnf.nsf entry in the Domino Directory.
Default value for non-Sametime entries is “”. |
F
Form | Text | The name of the form used for display.
The value for a room or resource document should be “Resource”
The value for a site document is “SiteProfile”
The value for a room reservation request should be “Notice”. The Rooms & Resource Manager will change it to “Reservation” |
From | Text | Contains the username of the user who created the document. For example, when an assistant creates an invitation, the From item has their name.
In contrast, the Principal item contains name of the owner of the mail database from which mail was created. Of course, the values may the same.
|
FromDomain | Text | Contains the Notes domain of the user who created the document. This is normally put on by client mailer code. |
FYIAttendees | Text List | C&S attendee field.
Primary names for users who are not involved in a meeting but should be aware of it. Only available for the Chair. |
G
H
HowCreated | Text | R&R Site option
Indicates which kinds of reservations should generate autoreminder notices, if the autoreminder feature is enabled.
Valid values are:
"0" = All reservations
"1" = Direct book reservations only |
I
INetFrom | Text | RFC822 email address corresponding to From item. |
InetBlindCopyTo | Text List | Mail recipient field.
Internet addresses for the “Bcc” or “FYI” recipients. Defaults to “.” when the Internet address is unavailable.
This list must be kept in sync with the BlindCopyTo field. |
InetCopyTo | Text List | Mail recipient field.
Internet addresses for the “Cc” recipients. Defaults to “.” when the Internet address is unavailable.
This list must be kept in sync with the CopyTo field. |
INetFYINames | Text List | C&S attendee field.
Internet addresses for users who are not involved in a meeting but should be aware of it. Only available for the Chair.
This list must be kept in sync with the FYIAttendees field. |
INetOptionalNames | Text List | C&S attendee field.
Internet addresses for users who may participate in a meeting.
This list must be kept in sync with the OptionalAttendees field. |
INetRequiredNames | Text List | C&S attendee field.
Internet addresses for users who are required to participate in a meeting.
This list must be kept in sync with the RequiredAttendees field. |
InetSendTo | Text List | Mail recipient field.
Internet addresses for the “To” recipients. Defaults to “.” when the Internet address is unavailable.
This list must be kept in sync with the SendTo field. |
K
KeepPosted | Text | Determines whether participant wants to be kept notified of updates.
This setting is on reply to Chair for decline and delegation.
0 = Do not want further updates (Default if missing)
1 = Do want further updates
|
L
LimitDate | Date / Time | R&R room option
This setting indicates what the last allowed reservable date is for a room or resource. All reservations beyond that date will be declined by the Rooms & Resource Manager. |
LimitDays | Number | R&R room option
This setting indicates the number of days out that a room or resource is allowed to be reserved. All reservations beyond that number of days will be declined by the Rooms & Resource Manager.
Since this value constitutes a moving value, one that needs to change each day, the Update Blocker Documents Agent must be enabled and configured properly for this kind of limit to work properly.
The value must be a positive integer value. |
LimitDD | Text | R&R room option
Admins can limit how far out R&R reservations can be made. This setting on the room or resource profile doc indicates that some limit setting has been enabled. The actual kind of limit is determined by the LimitHow item.
This setting has no effect or relevance for SameTime type resources. |
LimitHow | Text | R&R room option
This setting indicates what kind of future booking limit has been set on a room or resource.
Values are:
1 = Limit by days. The actual number of days ahead is set in the LimitDays item.
2 = Limit by date. The actual last reservable date is set in the LimitDate item. |
Location | Text | The “location” where the entry will occur. This value may be specified by the user or constructed by the template if the user enters no value but some Room & Resource data exists on the entry.
The value is not fixed or governed by any rules; it may be some arbitrary information or data inserted by the template. Trying to parse the value for some semanticly usable data may or may not be possible. Instead, the desired data should be parsed from the other items on the entry. |
Logo | Text | This is the background design on regular mail. Inherited by C&S note but is not used.
The value specifies the sending users default letterhead value and is of the base format of “stdNotesLtr#” where # is some number. |
M
MailOptions | Text | Value appears to be always “0” in this context. |
MeetingType | Text | One of the Sametime meeting types.
Valid values are:
"1" - Collaboration
"2" - Moderated
"3" – Broadcast
Default: "1" in Notes 6 and 7
Default: “2” in Notes 8 |
MeetingPassword | Text | Online Meeting password if used. |
Moderator | Text | The canonical name of the moderator of the Sametime meeting.
Note: This does not have to be the same person who schedules the meeting. |
N
NDays1 | Text | R&R site option
Used to indiciate how many days prior to a event the first autoreminder should be sent if the autoreminders are configured to be sent Daily.
The value is ignored if the autoreminder is set to Weekly.
See the SendWhen item.
|
NDays2 | Text | R&R site option
Used to indiciate how many days prior to a event the second autoreminder should be sent if the autoreminders are configured to be sent Daily.
The value is ignored if the autoreminder is set to Weekly.
See the SendWhen item.
A value of "0" means no second autoreminder should be sent.
|
NDays3 | Text | R&R site option
Used to indiciate how many days prior to a event the third autoreminder should be sent if the autoreminders are configured to be sent Daily.
The value is ignored if the autoreminder is set to Weekly.
See the SendWhen item.
A value of "0" means no third autoreminder should be sent.
|
NewEndDate | Date/Time | The counter-proposed UTC end date (not time) for a new DueDate or EndDate. |
NewEndDateTime | Date/Time | The counter-proposed UTC end datetime for a new DueDate or EndDate. |
NewEndTime | Date/Time | The counter-proposed UTC end time (not date) for a new EndDate. Since tasks have no EndTime, there is no equivalent for it. |
NewEndTimeZone | Text | The Notes timezone string for the NewEndDateTime.
Time zone strings are in the following format:
Fixed Time Zone:
Z=$DO=0$ZX=0$ZN=
Zone with daylight saving:
Z=$DO=1;$DL= > $ZX=0$ZN= |
NewStartDate | Date/Time | The counter-proposed UTC end date (not time) for a new StartDate. Although this information could be merged into one item with NewStartTime, there are Notes R5 historical reasons for the creation of StartDate and StartTime, so two items are needed to convey the counter proposal to the Chair. |
NewStartDateTime | Date/Time | The counter-proposed UTC start date and time for a new StartTime. Although this information could be merged into one item with NewStartTime, there are R5 historical reasons for the creation of StartDate and StartTime, so two items are needed to convey the counter proposal to the Chair. Since tasks have no StartTime, there is no equivalent for it on tasks. |
NewStartTime | Date/Time | The counter-proposed UTC end time (not date) for a new StartTime. Although this information could be merged into one item with NewStartTime, there are R5 historical reasons for the creation of StartDate and StartTime, so two items are needed to convey the counter proposal to the Chair. Since tasks have no StartTime, there is no equivalent for it on tasks. |
NewStartTimeZone | Text | The Notes time zone string for the NewStartDate
Time zone strings are in the following format:
Fixed Time Zone:
Z=$DO=0$ZX=0$ZN=
Zone with daylight saving:
Z=$DO=1;$DL= > $ZX=0$ZN= |
NoticeType | Text | Type of notice being sent. While the data type is for a string, only the first character of this item is used for determining what kind of notice it is.
For R&R in R7 or later, the only valid values to use are ‘I’ on the initial invitation or ‘U’ on an update / reschedule notice. The Rooms & Resource Manager will handle changing it when the request is processed.
Valid values are:
A = User accepted request
B = Chair has accepted a counter proposal
C = Chair cancelled event
D = User is delegating request; sent to Chair
E = Participant would like fresh copy of event. Notice is refreshed info from Chair or Update info from Chair.
When participant is requesting info, the $CSFlags contains ‘r’. When Chair is responding to request, the $CSFlags contains ‘u’.
If Chair is merely sending an update, $CSFlags will not contain either of these flags.
F = User has completed request
G = User wants to add event to calendar (may not be stored on disk, only in memory use.)
H = User is deleting event
I = Invitation request
J = Chair declines a counter-proposal request
K = Chair is sending updated info to all invitees
L = User is delegating request; Notice is sent to delegee
N = Event is being confirmed by Chair
P = User has tentatively accepted the invitation
R = User declined the invitation
S = Status update from Chair
T = User is counter-proposing request
U = Chair has rescheduled the event
W = Waiting for reply from user
X = Placeholder for "Extended NoticeType"; may not be in actual use.
Y = Chair wants to remove rooms/resources
Z = User has been removed (may not be stored on disk, only in memory use.) |
NoticeTypeRepaired | Text | The original NoticeType item value of a repaired / obsoleted entry.
Valid values are the same as those for NoticeType.
New for 8.5.
|
O
OnlineMeeting | Text | If meeting is an online meeting, value field is “1”. |
OnlinePlace | Text | Name of the online place found in the Domino Directory. Note that this is where the name is stored after processing has occurred.
Valid values are:
Taken from the list of Online meeting places in the Domino Directory (in canonical format). |
OnlinePlaceToReserve | Text | Name of the online place found in the Domino Directory. Note that this is where the name is stored before processing has occurred.Valid values are:
Taken from the list of Online meeting places in the Domino Directory. |
OptionalAttendees | Text list | C&S attendee field.
Primary names for users who may participate in a meeting. |
OrgConfidential | Text | Indicates whether the entry is “private” or not . This was also shared with the Lotus Organizer product.
Value is “” if Mark Private is not checked, and “1” if it is checked. |
OrgRepeat | Text | Indicates whether the entry repeats.
See also Repeats field.
Value is “1” if entry is a repeating one, and “” if it is not. |
OrgState | Text | C&S item for Lotus Organizer
Indicates the type of entity the that this was created for: Users, Rooms, Resources or a Sametime meeting. It was added in R5 to support Lotus Organizer. It is currently only present for backwards compatibility.
Valid values are:
"0" = A person
"5" = A room
"6" = A resource
"7" = A Sametime meeting |
OrgStatus | Text | C&S item for Lotus Organizer – from here: http://www.ibm.com/developerworks/lotus/library/ls-Integrating_C_and_S_into_a_group_application/side2.html
Sent on a Status Update notice to an invitee telling them they are either required to attend or removed from a meeting invitation. is currently only present for backwards compatibility
Valid values are:
“2” = Accepted
”5” = Removed |
OrgTable | Text | Tells Lotus Organizer in which section an entry should be displayed. Since Organizer can have > 1 calendar, Notes defaults to using the first one by always putting a "0" in the second character of this items value. The leading character is used to indicate the type of entry.
Valid first character values:
"C0" = Calendar entry
"T0" = To Do entry
"H0" = Calls entry
"P0" = All Day Event / Planner entry
"D0" = Address entry
"N0" = Notepad entry
"A0" = Anniversary entry |
OriginalDelegator | Text | Owner of calendar who was original invitee for this delegation chain. This can be an Internet address. |
OriginalEndDate | Date/Time | The original UTC end date & time of the repeat instance that is being rescheduled. This is necessary when the user reschedules a single (or run of) repeating entry so that they know which one to use as the base reference point. |
OriginalEndTimeZone | Text | The Notes timezone string for
TimeZones strings are in the following format:
Fixed Time Zone:
Z=$DO=0$ZX=0$ZN=
Zone with daylight saving:
Z=$DO=1;$DL= > $ZX=0$ZN= |
OriginalStartDate | Date/Time | The name of this item is misleading. It is not the original S
Useful in the case of rescheduling.
Do not put on a repeat parent doc. |
OriginalStartTimeZone | Text | The Notes
TimeZones strings are in the following format:
Fixed Time Zone:
Z=$DO=0$ZX=0$ZN=
Zone with daylight savings:
Z=$DO=1;$DL= > $ZX=0$ZN= |
P
ParentRepeatDates | Date/Time List | The “current” set of repeating dates & times, including all reschedules to that point.
See RepeatDates for more details on the usage (although its use on a “parent” document may be slightly different). |
ParentRepeatInstanceDates | Date/Time List | The “original” set of repeating dates & times from when the entry was created.
See RepeatInstanceDates for more details on the usage (although its use on a “parent” document may be slightly different). |
PostedDate | Date/Time | The client stamps this date/time on Note when it is mailed.
This item is used by R&R to distinguish a request sent from a users Calendar from a directly booked request. |
Presenters | Text | User |
PreventCounter | Text | Indicates that the Chair does not want any counter proposals.
Valid values are:
1 = Do not allow the invitees to counter propose
All other values (including missing) = Allow it |
PreventDelegate | Text | Used to indicate the Chair does not want to allow any delegation by invitees.
Valid values are:
1 = Do not allow the invitees to delegate
All other values (including missing) = Allow it |
PreventRepliesFromInbox | Text | C&S preference item
Indicates what kinds of C&S documents the user wants displayed in their Inbox.
Values are:
0 = Display All Notices
1 = Display All Except Responses
2 = Display No C&S docs in Inbox – (they only show in the miniview) |
Principal | Text | The fully distinguished username of the owner of the mail database from which mail is being created.
In contrast, the From item is the name of the person, such as an assistant, creating mail. The items may be the same value. |
Purpose | Text | The purpose of the room or resource reservation.
Same as the Topic field for reservations created from the Calendar. This is the item used in the R&R template for direct-booked reservations |
R
RepeatAdjust | Text | Text list describing the days/dates that the rule should use to calculate the list of repeat dates & times (for example, Monday, 1st of the Month). Currently only repeat types ‘W’ (Weekly) and ‘M’ (Monthly) require this parameter.
In Notes version 4, this item was “0” based, so Sunday (for weekly entries) was 0, and so on. This is legacy now and may not be changed without seriously impacting backward compatibility.
When dealing with ‘D’ (Repeat by Month Date) repeats, the list is “1” based and is the list of dates in the month that the entry should repeat. Negative values must not be used here. If you want to have "The 2nd-to-last day" of the month, then use "2" here and set RepeatFromEnd to 1.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
RepeatCustom | Time | A hard-coded list of dates used mainly for “custom” repeating entries. Used by the UI code to set custom dates. Once repeat is saved, the items are copied to RepeatDates.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
RepeatDates | Date/Time List | The set of repeating dates & (start) times at which the entry repeats. The end date & times are not specified on another item; rather, they are derived by shifting the list of start date & times by the entry’s duration. The presence of this item or of OrgRepeat is what truly signifies an entry is repeating, not any other checks.
Note: This exists only in the Parent Doc.
Important: This serves as the key when a lookup is performed on the ($RepeatLookup) view, in the code.
This is a peer item to ParentRepeatDates and, depending on some scenarios, one item may be used in place of the other. When creating an outgoing message, this item is the “backup” to RepeatInstanceDates. If RepeatInstanceDates is not present, then RepeatDates is sent instead. |
RepeatEndDates | Date/Time List | When a repeating meeting is accepted, the repeat end dates are generated on parent repeat document. They are the corresponding end dates for the dates found in RepeatDates item. |
RepeatFor | Number | The number of RepeatForUnits for which the entry repeats This value is a positive integer. Any zero or negative values are automatically treated as 1. Does not have any significance when repeat to date is chosen.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
RepeatForUnit | Text | The “unit” of time that the repeat rule is for. Further defined by RepeatUnit value.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item.
Valid values are:
“” = Custom
D = Daily
M = Monthly
W = Weekly
Y = Yearly |
RepeatFromEnd | Text | Flag indicating whether the monthly repeat is from the end of the month instead of the start of the month. Valid values are:
1 = Start from the end (that is, values in RepeatAdjust are relative to the end of the month).
All other values (or missing) = Start from the beginning of the month
This exists only in the Repeat Parent Document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
RepeatHow | Text | Indicates “how” the user wanted the repeat set to be terminated, either by count or by explicit date.
Valid values are:
F = "For"; indicates a count was desired
U = "Until"; indicates that an explicit repeat end date/time was desired. The desired date/time is in RepeatUntil.
This exists only in the Repeat Parent Document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item.
|
RepeatIds | Text List | A list of UNID(s) of the response documents. One for each repeat instance.
Note: Exists only in the Repeat Parent document.
In Notes 6, this exists only for Repeating All Day Events. |
RepeatInstanceDates | Date/Time List | The set of dates & times that are affected by the message that they are on.
For repeating entries this may be a single date & time if just a single instance is being, say, rescheduled; or it may be a list of dates & times if a range of entries is affected, such as canceling “this and all future” instances.
This item is copied at creation from RepeatDates so that it can become a snapshot of the “original” set of dates & times. This is a peer item to ParentRepeatInstanceDates and, depending on some scenarios, one item may be used in place of the other.
When an outgoing message is created, this item is the “primary” to RepeatDates. If RepeatInstanceDates is not present, then RepeatDates is sent instead.
The number of items in this list must match the number of entries in the StartDateTime and EndDateTime items of a repeating meeting. |
RepeatInterval | Text | The interval at which the rule applies. Only positive integer values are valid. The value is used in conjunction with RepeatUnit to calculate the next repeat date for an entry.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
Repeats | Text | Indicates whether the entry repeats. Value is “1” if entry is repeating and “” if it is not.
See also OrgRepeat field. |
RepeatStartDate | Date/Time | The starting date of the repeating entries. The starting time is actually pulled from either the StartTime item (or from EndTime / DueDateTime when calculating the proper end time).
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
RepeatUnit | Text | The “unit” of time over which the entry repeats.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item.
Valid values are:
C = Custom set of explicit dates
D = Daily
MD = Monthly by date (that is, the 1st of each month)
MP = Monthly by day (that is, the 1st Monday of each month)
Y = Yearly |
RepeatUntil | Date/Time | The UTC date (& time) up to which the entry set repeats. Since Notes does not currently have the concept of a repeat set that occurs more than once a day (for example, “Repeat @ 9AM and 3PM every day for a week"), the time sub value is not used or necessarily set properly. This item is meaningful only if the RepeatHow is set to repeat how until.
This exists only in the Repeat Parent document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item. |
RepeatWeekends | Text | Indicate what, if anything, should happen to a repeat instance that occurs on a weekend. This item’s value is checked only in some cases of repeating entries.
As of Notes R5, this item is used only if the entry is Daily (‘D”), Monthly (‘D’ only), or Yearly (‘Y’); all other types of repeat sets cause this value not to be useful.
This exists only in the Repeat Parent Document and on Notice sent to original invitees. It is informational only, since the UI of the Chair used this information to generate the original repeat dates item.
Valid values are:
D = Don’t move weekend occurrence
F = Move weekend occurrence to previous workday, presumably Friday
M = Move weekend occurrence to next workday, presumably Monday
N = Move weekend occurrence to closest workday (forward or backward)
X = Remove weekend occurrence from the repeat set |
RequiredAttendees | Text list | C&S attendee field.
Primary names for users who are required to participate in a meeting. |
RequiredResources | Text List | C&S attendee field.
A list of resources the Chair wants/needs to have.
Notes version 4: For repeating entries, this entry is stored on the parent document.
Version 5 and later: For repeating entries, this entry is stored on the individual child document(s).
|
RescheduleEndDateTimes | Date/Time List | C&S workflow message.
The set of EndDateTimes for the repeat set to which this invitee is being invited after notice is applied. For example, if the invitee is being invited to only the last three days of the repeat meeting, then RescheduleEndDateTimes contains the new end datetime values for the last three dates of the repeat set.
For other actions such as Cancel, Remove, and Update, the set of EndDateTimes for the repeat set determines what dates should be used when this action is applied. |
RescheduleInstanceDates | Date/Time List | C&S workflow message.
The initial set of DateTimes values for the repeat set over which this action should be applied.
This set must be in sync with RescheduleEndDateTime and RescheduleStartDateTime.
For example, if the invitee is being invited to only the last three days of the repeat meeting, then RescheduleInstanceDates contains the initial datetime values for the last three dates of the repeat set. |
RescheduleStartDateTimes | Date/Time List | C&S workflow message.
The set of StartDateTimes for the repeat set to which this invitee is being invited after notice is applied. For example, if the invitee is being invited only to the last three days of the repeat meeting, then RescheduleStartDateTimes contains the new start datetime values for the last three dates of the repeat set.
For other actions such as Cancel, Remove, and Update, the set of EndDateTimes for the repeat set determines what dates should be used when this action is applied. |
RescheduleWhich | Text | Indicates which repeat entry or range of entries is being modified/cancelled. This is for backward compatibility.
If the recipient is Notes 6 and later, then the information in RescheduleStartDateTimes, RescheduleEndDateTimes, and RescheduleInstanceDates is used instead.
Valid values are:
0 = Current (single) instance only
1 = All instances
2 = Current and all previous
3 = Current and all future
-1 = User-cancelled modifying repeat |
ResourceOwner | Text / Text List | R&R owner list
Used on R&R documents
Value indicates the name(s) of any room or resource owner(s) whose approval is required for a reservation request. |
Resources | Text | User interface field.
Value is always “” in this context, since no resources can be picked for Appointments. (See Meetings) |
ResourceName | Text | R&R item
Used on R&R related documents to indicate which room or resource the document is for. The item is single valued as a separate document is created if multiple rooms or resources are involved.
Value indicates the canonical room or resource associated with the workflow message. |
ResourceType | Text | R&R type indicator.
Used on R&R documents only.
Value indicates the type of resource specified in ResourceName. Values are:
“1” = Room
“2” = Resource
There is no “3” for Online (Sametime) Meetings because those entries are never stored in the R&R dB. They are forwarded along to the Sametime Server and are not kept in the R&R database. |
RestrictAttendance | Text | Indicates whether the online meeting is restricted to only those people/groups in the restricted list.
Default is “0”. |
RestrictToInviteList | Text | The list of users/groups that are allowed to attend this online meeting.
Valid values are:
The list of names are the people/groups in the From, Moderator, SendTo, CopyTo, BlindcopyTo fields. |
ReturnReceipt | Text | Indicates whether user wants a return receipt.
Value is “1” when user has picked return receipt and “” otherwise. |
RmRsrList | Text / Text List | R&R site option
Value indicates which specific rooms or resources have are configured to be subject to sending of autoreminders when the feature is enabled.
The list is ignored if the RRChoice item is not set to "1". |
Room | Text | C&S Attendee field.
The fully qualified name of the room (Roomname/site) for mailing notices to the Resource Reservation database. |
RoomToReserve | Text | User interface field.
Value is always “” in this context, since no rooms can be picked for Appointments. (See Meetings) |
RQStatus | Text | Rooms & Resource Request Status
New to 7.0
All newly created room reservation requests should have a value of “T”
Valid values are:
“T” = Request is tentative. Awaiting Room Owner or Rooms & Resource Manager approval.
“A” = Request has been approved by Rooms & Resource Manager.
“R” = Request has been rejected by a Room Owner or the Rooms & Resource Manager. If the Room Owner provided a reason it will be saved in the DeclineReason item. |
RRChoice | Text | R&R site option
Value indicates which rooms or resources should be subject to sending of autoreminders when the feature is enabled.
Valid values are:
"0" = All rooms / resources
"1" = Particular rooms / resources. The selected names are stored in the RmRsrList item. |
S
SametimeServer | Text | Name of the Sametime server on which the online meeting takes place.
Values: Taken from the Domino Directory. |
SametimeType | Text | Calendar profile setting.
Type of Sametime server the user wants to default to when scheduling online meetings.
Valid values are:
“0” = Sametime meeting (Default)
“1” = Sametime Unyte meeting |
SendTo | Text | Mail recipient field.
Primary names for the “To” recipients.
Contains the names of the required invitees to which this workflow message is being sent. Or, in the case of a response, the Chair’s address. |
SendWhen | Text | R&R site option
Used to indiciate if autoreminders, when enabled, should be sent weeky or daily.
Valid values are:
"0" = Weekly (Default)
"1" = Daily |
SequenceNum | Number | Sequence number of event notice. It is incremented when a change in start or end time occurs. When SequenceNum is changed, all the recipients must accept/decline again. Changing cosmetic things like the Subject is not grounds for increasing. Replies to a different SequenceNum are not valid and are ignored by the Chair as stale information.
Initial Value: 1 |
SendAttachments | Text | Indicates whether the people who are invited to the meeting receive the attachments that will appear in the online meeting.
Default: "0" |
Sign | Text | Allows the user to Sign the entry for security purposes. |
Site | Text | R&R item
Stored on each reservation request to incidate the Site of the room or resource being requested.
The value matchs the last component value of the room or resource name. So if a room or resource is renamed, this value needs to be updated to match any change. |
StartDate | Date/Time | The UTC date (& time) the entry begins.
It is derived from StartDateTime and is typically the same for non-repeating entries. This is a separate item from StartTime, even though both share the same information, because a UI change for R5 to split the “combo” Date/Time picker into two separate items requires two separate items.
|
StartDateTime | Date/Time List | The UTC date & time the entry begins.
The number of values in this item must match the number of values in the EndDateTime item.
|
StartTime | Date/Time | The UTC (date &) time the entry begins.
It is derived from StartDateTime and is typically the same for non-repeating entries. This is a separate item from StartDate, even though both share the same information, because a UI change for R5 to split the “combo” Date/Time picker into two separate items requires two separate items. |
StartTimeZone | Text | The Notes timezone string for the StartDateTime.
Time zone strings are in the following format:
Fixed Time Zone:
Z=$DO=0$ZX=0$ZN=
Zone with daylight saving:
Z=$DO=1;$DL= > $ZX=0$ZN= |
StartWeek | Text | R&R site option
Used to indicate which day the week starts on and thus when weekly autoreminders should be sent. |
StatusUpdate | RichText / MIME-PART | Contains the comment when doing Accept/Decline with comment or when the Chair is rescheduling with comment. |
StorageFYINames | Text List | C&S attendee field
Mail formatting preferences for users who are not involved in a meeting but should be aware of it. Defaults to “1” or “.” when the preference is unavailable. Only available for the Chair.
Formatting types are:
0 – Prefers Notes Rich Text
1 – Keep in senders’ format (no preference)
2 – Prefers MIME
. (Period) – Keep in sender’s format (no preference)
This list must be kept in sync with the FYIAttendees field. |
StorageOptionalNames | Text List | C&S attendee field
Mail formatting preferences for users who may participate in a meeting. Defaults to “1” or “.” when the preference is unavailable.
Formatting types are:
0 – Prefers Notes Rich Text
1 – Keep in senders’ format (no preference)
2 – Prefers MIME
. (Period) – Keep in sender’s format (no preference)
This list must be kept in sync with the OptionalAttendees field. |
StorageRequiredNames | Text List | C&S attendee field
Mail formatting preferences for users who are required to participate in a meeting. Defaults to “1” or “.” when the preference is unavailable.
Formatting types are:
0 – Prefers Notes Rich Text
1 – Keep in senders’ format (no preference)
2 – Prefers MIME
. (Period) – Keep in sender’s format (no preference)
This list must be kept in sync with the RequiredAttendees field.
This item can be overloaded in version 6 and later, to contain a copy of the RescheduleInstanceDates item, due to backward compatibility with R5. When an R5 user accepts, StorageRequiredNames is sent back on the acceptance, allowing the Chair to know what days the invitee is accepting. |
STPermissions | Text List | Sametime Unyte setting
Setting to control who can attend the Sametime meeting.
Valid values are:
“0” = Limit attendance to only meeting invitees
“1” = Open meeting to all users |
STPermPresent | Text List | Sametime Unyte setting
Setting to indicate who will be allowed to present content during the Sametime Unyte meeting.
Valid values are:
“0” = All participants have permission to present content. |
STRecordMeeting | Text List | Sametime Unyte setting
Setting to indicate if the Sametime meeting should be recorded or not.
Valid values are:
“1” = Record this meeting so others can replay it later |
STRoomName | Text List | Sametime Unyte setting
Textual label that the Chair has given to their Sametime Unyte meeting. This label is used to identify which Sametime settings are to be used on the calendar entry. |
STServiceInfo | Text List | Sametime Unyte setting
Valid values are: |
STUnyteConferenceID | Text / Text List | Sametime Unyte setting
The Sametime Unyte conference password. This setting is stored on both the Calendar Profile (for creating new online meetings easily) and on any workflow documents where the chair has scheduled a Sametime Unyte meeting.
For backwards compatability this value is also stuffed into the MeetingPassword item. |
STUnyteConferenceURL | Text / Text List | Sametime Unyte setting
The Sametime Unyte conference URL. This setting is stored on both the Calendar Profile (for creating new online meetings easily) and on any workflow documents where the chair has scheduled a Sametime Unyte meeting.
For backwards compatability this value is also stuffed into the ApptUNIDURL item. |
Subject | Text | The Subject of the notice (prefix + topic + date/time).
Prefixes can be:
Invitation:
Accepted:
Tentative:
Declined:
Countered:
Delegated:
Invitation (Delegated):
Information Update - when this is an update, the Chair indicates what is being updated, such as “Description has been changed”. |
T
TaskLead | Text | The default amount of time before an Task starts (or ends) that the alarm should trigger. The value MUST be in days, NOT minutes as the value is automatically adjusted internally before use. The value is only of use when SetAlarmTask = 1. This item is used only on calendar profiles. |
TaskType |
| Identifies the kind of task this is. Valid values are:
1 = Personal task and personal todo
2 = Group task and group todo |
Topic | Text | The original Subject as entered by the Chair. This item is only on workflow meeting messages. |
U
UpdateSeq | Text | Indicates sequence of updated items in note.
Tracks non-date/time changes (eg: Subject, Location). Always greater than or equal to the SequenceNum item. This value is tied to the entries in the $CSWISL item. |
W
WhiteBoardContent | Composite | The attachments that are presented in the white board during the online meeting.
Values: Files that the user chooses. (Note: works in conjunction with $FILE field.) |
Feedback
To provide your feedback about this content, send a message to ndinfo@us.ibm.com with "C&S Schema " in the subject line. All feedback sent to that address will automatically be routed to the authors for review.
Previous Page | Table of Contents
|