Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • Lotus Notes and Domino Application Development wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 6.0
  • 6.5
  • 8.0
  • 8.5
  • 8.5.1
  • 8.5.2
  • 8.5.3
  • action bar
  • Agents
  • Ajax
  • app dev
  • Application
  • beginner
  • C&S
  • calendaring and scheduling
  • client
  • composite applications
  • Controls
  • converters
  • css
  • Custom controls
  • Data Binding
  • db2
  • design elements
  • dialog boxes
  • Documents
  • Dojo
  • Domino
  • Domino Designer
  • Domino Designer 8.5
  • DXL
  • Eclipse
  • error handling
  • errors
  • extensions
  • FAQ
  • Forms
  • formulas
  • getting started
  • globalization
  • Help
  • html
  • Installation
  • interface
  • internationalization
  • iPhone
  • Java
  • JavaScript
  • localization
  • Lotus Domino Designer
  • LotusScript
  • LotusSphere
  • LotusTechInfo
  • menu bar
  • Mobile
  • new user
  • Notes
  • Notes 8
  • notes.ini
  • NSD
  • OpenNTF
  • partial update
  • performance
  • Pickers
  • Portal
  • presentations
  • programming
  • Redbooks
  • Requested Articles
  • roadmap
  • rooms and resources
  • samples
  • Scripting
  • security
  • tabs
  • templates
  • themes
  • Tips
  • toolbar
  • troubleshooting
  • tutorials
  • validation
  • variables
  • video
  • VideoFest
  • View
  • view control
  • ViewPanel
  • Views
  • web
  • Web apps
  • Web services
  • webdev
  • XML
  • Xpage
  • XPages
  • XPages Extensibility API
  • xsp-config
  • データソース
  • 九州地区ノーツパートナー会
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > Developing Form- and View-based Applications > Page 2: Description of C&S entries
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Page 2: Description of C&S entries 

expanded Abstract
collapsed Abstract
cs_schema_descriptions
< Previous Page | Table of Contents| Next Page >

The page describes the static state of the various calendar entry types. Since most of the fields are the same for each entry type, a complete listing of available fields is provided on a separate page. Only the fields that are unique to a particular entry are listed separately.

Simple Appointment
Repeating Appointment
Simple Anniversary
Repeating Anniversary
Simple All-Day Event
Repeating All-Day Event
Simple Reminder
Repeating Reminder


Entry Type: Simple Appointment

Simple Appointment document


Form: _Calendar Entry
Alias: Appointment

Alarm items
BusyTime items
Mail items - Not used for appointments
Database Control items

Unique Appointment Items
_ViewIcon – Value is always 160 for Appointment
AppointmentType = 0 for Appointment
Form = “Appointment”
Repeats – value is “” for non repeating
SequenceNum – Value is always 1 for an Appointment

Usage

Chair creates a new Appointment, chooses the time and date options, the busytime and encryption options, the optional categories, and then saves the document. The CalendarDateTime is set to the starting date and time chosen by the Chair to make it appear in the Calendar view. The alarm options are set based on preferences, unless changed during appointment creation
Back to top



Entry Type: Repeating Appointment

Appointment Parent Repeat document


Form: _Calendar Entry
Alias: Appointment

Mail items - Not used for appointments
Database Control items
Repeat UI fields


Unique Appointment items
$CSFlags - value of ’c’ on repeat parent
_ViewIcon = 160
AppointmentType = 0 for Appointment
Form = “Appointment”
Repeats – value is “1” for repeating
SequenceNum – Value is always 1 for an Appointment


Appointment Child Repeat document


Alarm items
BusyTime items
Mail items - Not used for appointments
Database Control items

Unique Appointment items
$CSFlags - value of ‘i’ on repeat child
$Ref - value of parent document ApptUNID
$RefOptions = “1”
_ViewIcon = 160
AppointmentType = 0 for Appointment
Form = “Appointment”
Repeats – value is “1” for repeating
SequenceNum – Value is always 1 for an Appointment


Usage

Chair creates a new Appointment, chooses the time, date, and repeat options as well as the busytime and encryption options, and the optional categories, and saves the document. A child document is created with its CalendarDateTime set to the starting date and time generated by the repeat rule specified by the Chair, to make them appear in the Calendar view. The alarm options are set based on preferences, unless changed.
Back to top



Entry Type: Simple Anniversary

Anniversary Non-Repeat document


Form: _Calendar Entry
Alias: Appointment

Alarm items
BusyTime items
Mail items - Not used for anniversaries
Database Control items

Unique Anniversary Items _ViewIcon = 63 for Anniversary
AppointmentType = 1 for Anniversary
Form = “Appointment”
Repeats – value is “” for non repeating
SequenceNum – Value is always 1 for an Anniversary

Usage

Chair creates a new Anniversary, chooses date options as well as the busytime and encryption options and optional categories, and saves the document. The CalendarDateTime is set to the starting date chosen by the Chair (with the time component added as explained below); the alarm options are set based on preferences, unless changed at creation time; and the Anniversary appears on the calendar.

NOTE: There is no Time component associated with anniversaries. Start time (and the associated StartDateTime component) is always set to 04:00am local time, and the End time is set to 08:00pm. Alarms that are set for anniversaries will default to this time unless modified by the chair.
Back to top



Entry Type: Repeating Anniversary

Anniversary Parent Repeat document


Form: _Calendar Entry
Alias: Appointment

Mail items - Not used for anniversaries
Database Control items
Repeat UI fields

Unique Appointment Items $CSFlags - value of ‘c’ on repeat parent
_ViewIcon = 63 for Anniversary
AppointmentType = 1 for Anniversary
Form = “Appointment”
Repeats – value is “1” for repeating
SequenceNum – Value is always 1 for an Anniversary


Anniversary Children Repeat documents


Alarm items
BusyTime items
Mail items - Not used for anniversaries
Database Control items


Unique Appointment Items $CSFlags - value of ‘i’ on repeat child
_ViewIcon = 63 for Anniversary
AppointmentType = 1 for Anniversary
Form = “Appointment”
Repeats – value is “1” for repeating
SequenceNum – Value is always 1 for an Anniversary

Usage

Chair creates a New Anniversary, chooses date options, repeat options, busytime and encryption options, optional categories, and saves the document. Repeat child document is created and saved with its CalendarDateTime field set to the starting date generated by the repeat rule specified by the Chair (with the time component added as explained below), to make them appear in the calendar view. The alarm options are set based on preferences, unless changed.

NOTE: There is no Time component associated with anniversaries. Start time (and the associated StartDateTime component) is always set to 04:00am local time, and the End time is set to 08:00pm. Alarms that are set for anniversaries will default to this time unless modified by the owner.
Back to top



Entry Type: Simple All-Day Event

All-Day-Event Non-Repeat document


Form: _Calendar Entry
Alias: Appointment

Alarm items
BusyTime items
Mail items - Not used
Database Control items

Event items _ViewIcon = 9 for Event
AppointmentType = 2 for Event
Form = “Appointment”
Repeats – value is “” for non repeating
SequenceNum – Value is always 1 for an All-Day Event


Usage

Chair creates a new All-Day Event, chooses the time, date, and encryption options, and saves the document. The CalendarDateTime is set to the starting date and time chosen by the Chair to make it appear in the Calendar view; the alarm options are set based on preferences, unless changed.
Back to top



Entry Type: Repeating All-Day Event

All-Day-Event Repeat Document


Form: _Calendar Entry
Alias: Appointment

Alarm items
BusyTime items
Mail items - Not used.
Database Control items
Repeat UI fields


Event items $CSFlags – exists only on repeat parent with value of ‘c’
$Ref – ApptUNID of the parent document
$RefOptions = “1”
_ViewIcon = 9 for Event
AppointmentType = 2 for Event
Form = “Appointment”
Repeats – value is “1” for repeating
SequenceNum – Value is always 1 for an All-Day Event


Usage

In the case of Repeating All-Day Events, one parent document and multiple child documents (one for each repeating instance) are created. All the documents use the Appointment form. The children have the CalendarDateTime item and therefore appear in the Calendar view. The parent document has no CalendarDateTime item and can be seen only in the All Documents view.

NOTE: There is no Time component associated with All-Day Events. Start time (and the associated StartDateTime component) is always set to 04:00AM local time; the End time is set to 08:00 PM. Alarms that are set for All-Day Events will default to this time unless modified by the owner.
Back to top



Entry Type: Simple Reminder

Reminder Non-Repeat Document


Form: _Calendar Entry
Alias: Appointment

Alarm items
BusyTime items – Not used in Reminders
Mail items - Not used.
Database Control items


Reminder Items _ViewIcon = 10 for Reminder
AppointmentType = 4 for Reminder
Form = “Appointment”
Repeats – value is “” for non repeating
SequenceNum – Value is always 1 for a Reminder


Usage

Chair creates a new Reminder, chooses the time, date, and encryption options, and saves the document. The CalendarDateTime is set to the starting date and time chosen by the Chair to make it appear in the Calendar view; the alarm options are set based on preferences, unless changed.
Back to top



Entry Type: Repeating Reminder

Reminder Parent Repeat Document


Form: _Calendar Entry
Alias: Appointment

Mail items - Not used in Reminders
Database Control items
Repeat UI fields

Reminder Items $CSFlags - value of ‘c’ on repeat parent
_ViewIcon = 10 for Reminder
AppointmentType = 4 for Reminder
Form = “Appointment”
Repeats – value is “1” for Reminder
SequenceNum – Value is always 1 for a Reminder


Reminder Children Repeat Documents


Alarm items
BusyTime items - Not used in Reminders
Mail items - Not used in Reminders
Database Control items


Reminder Items $CSFlags - value of ‘i’ on repeat child
_ViewIcon = 10 for Reminder
AppointmentType = 4 for Reminder
Form = “Appointment”
Repeats – value is “1” for repeating
SequenceNum – Value is always 1 for a Reminder

Usage

Chair creates a new Reminder, chooses the time, date, repeat, and encryption options, and saves the document. Child documents are created and saved with their CalendarDateTime field set to the starting date and time generated by the repeat rule specified by the Chair, to make them appear in the Calendar view. The alarm options are set based on preferences, unless changed.
Back to top


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| Next Page >

expanded Article information
collapsed Article information
Category:
Developing Form- and View-based Applications
Tags:
6.0, 6.5, 8.0, 8.5, calendaring and scheduling, C&S, Domino, Notes, rooms and resources, 7.0

This Version: Version 7 October 1, 2010 6:05:38 PM by Joy Freeman  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (7)
collapsed Versions (7)
Version Comparison     
Version Date Changed by               Summary of changes
This version (7) Oct 1, 2010 6:05:38 PM Joy Freeman  
6 Sep 30, 2010 3:43:55 PM Joy Freeman  
5 Sep 30, 2010 9:56:55 AM Joy Freeman  
4 Sep 30, 2010 9:45:01 AM Joy Freeman  
3 Sep 24, 2010 12:22:48 PM Joy Freeman  
2 Sep 24, 2010 11:52:29 AM Joy Freeman  
1 Sep 24, 2010 4:31:32 AM Joy Freeman  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use