The Calendar category enables you to control Oracle Beehive's Time Management Services. These services support all aspects of time and task management, as well as user, team, and resource scheduling for Oracle Beehive.

For more information about Time Management Services, refer to the section "Time Management Services" in the module "Oracle Beehive Services" in Oracle Beehive Concepts.

A bookable resource is an entity that users can search for, reserve, and use for a specified period of time, such as a conference room or a projector.

A calendar is a container of time management artifacts. It exists as an entity of a team or personal workspace. Refer to the section "Workspace Templates" in the module "Oracle Beehive XML File Reference" in Oracle Beehive Administrator's Reference Guide to see the structure of a calendar in the context of a workspace.

An invitation is an object that is created for every calendar event. It is located in the participant's default calendar. These invitation objects are owned by the participant. The participant can update the status or act on the invitation.

Invitations and occurrences are both represented by the Meeting resource in the BDK. The invitee's meetings do not include a reference to the organizer's meeting.

Meetings reside in calendar objects. When the organizer creates a meeting that includes other participants, a copy of the meeting is created in each participant's default calendar. If the participant is a team workspace, then by default meetings are delivered to the default calendar of the enrollees (who are typically the workspace members). External participants are informed of the meeting with an e-mail notification that includes an iCalendar attachment that can be imported in their calendar application.

A reminder is an entity that is used to trigger a reminder action at some timed event. It associates a timed or relative trigger on the entity, which can set off an event. A timed trigger can be defined relative to the time of an operation, such as create, update, check-in, or checkout or to a scheduled event (usually a future event), such as the start time of an calendar occurrence, due date of a task, or end time of a conference. A timed trigger can also be defined by absolute time, independent of any operation. The relative triggers that the BDK supports are the start of a meeting, start of a atask, and the due time of a task.

An alert is a time-sensitive message to one or more users that typically requires the immediate attention of its recipients, sometimes in the form of actionable responses.

Creating Bookable Resource Accounts

Refer to "Creating Oracle Beehive Bookable Resource Accounts" for more information.

Working with Calendar

The Calendar resource supports common calendar operations:

• Listing, reading, creating, modifying, and deleting meetings
• Time-based search of meeting and tasks
• Free/busy lookup

Use the Calendar resource in conjunction with the Meeting and MeetingSeries resources.

Working with Meeting

The Meeting resource represents both invitations and occurrences. If the member InvitationOnly is true, then the Meeting is an invitation.

Every user that is a participant of a scheduled meeting has a meeting artifact. The meeting organizer is responsible for creating the main meeting artifact. The invitees' copies of the meeting are automatically created by the system.

The organizer of the meeting may update all the common attributes in the main meeting artifact. For example, the organizer may change the title, reschedule the meeting, and add participants. These modifications are automatically propagated to each participant's copy of the meeting. The other participants cannot modify these attributes in their copy of the meeting. Only the attribute with the prefix Invitee may be updated by an invitee. The attribute InvitationOnly may be used to determine if the meeting artifact is the main copy of the meeting.

Working with Task

The Task resource represents both TODOs and assignments. If the member AssignmentOnly is true, then the Task is an invitation.

The task artifact represents a personal task, or a task being assigned to a participant.

The BDK does not allow you to assign a task to another participant; however, the BDK exposes task assignments created from calendar clients. If the attribute AssignmentOnly is true, then only the attribute with the prefix Assignee may be updated. If AssgnmentOnly is false, then this artifact represents the main artifact of the TODO and modifications to the common attributes are propagated to each of the assignees' copy of the task.

Working with Tasklist

To be documented later

Working with Dates and Times

Dates and times are represented with the dateTime data type as defined by XML Schema: Datatypes. You may use local times when working with Calendar.

Working with Reminders

Both Meeting and Task contain a member named InviteePrimaryClientReminderTrigger of type TimedTrigger. The TimedTrigger is used to indicate at what time an reminder should be triggered.

The member InviteePrimaryClientReminderTrigger of the Meeting and Task resources indicates the trigger time of the reminder exposed in the calendar client such as Oracle Behive Extensions for Outlook and Mozilla Lightning.

Entities might have other secondary reminders such as default reminders that trigger a notification 10 minutes before every meeting. There reminder are accessible through the Reminder resource.

Other Notes about Calendar

This section describes various notes and features of the Calendar category:

1. Tasks:
   • You may only create personal tasks or unassigned team workspace tasks.
   • You may only list and read task assigned to yourself (Tasks that represent assignments) or team workspace tasks.
   • Task participants are not listed. Consequently, you cannot assign or reassign a task.
2. Attachments:
   • Calendar can read an attachment if has been created by an Oracle Beehive client
   • Attachments cannot be created or added in Calendar
3. List filters and predicates: General list filters based on predicates are not available for this version. You may instead perform time-based searches and free/busy lookup based on a time range.
4. Group invitation: Groups may be invited, but indirect participants are not exposed.
5. Team workspace scheduling: A Meeting may invite a team workspace. A Meeting may be created in a team workspace calendar. All meetings created in a team workspace calendar invite the enrolment list. Indirect participants are not exposed.
6. Recurring meetings: Recurring meetings are represented by the MeetingSeries resource and its recurrenceRule member. Initially, all the meetings associated with a MeetingSeries are initialized from the attributes of the series and are considered non-exceptions (the value for each of the the meetings' exception member is false). When a particular meeting of a series is explicitly modified it becomes an exception to the series (the value of its exception member is set to true). Modifications to the MeetingSeries are be propagated to all associated meetings, including the exceptions, but will not change their exception status.
   • Recurring meetings may be created from an iCalendar rule (no exception).
   • For /read and /list operations, recurring meetings are always expended and the rule is not returned
   • A Meeting contains an attribute isFromRecurring
   • Updating a specific Meeting that is a from a recurrent meeting changes the value of its exception member to true.
   • You may accept or decline (by setting the Participation Status) all invitations of a recurring meeting or all non-exceptions of a recurring meeting to avoid causing an exception when a user accepts all occurrences of a recurring meeting.
7. Journal: Journals are not supported
8. Bonds and labels: Bonds and labels are not supported
9. Time zones:
   • No time zone IDs are available in Meeting and Task.
   • All times in meetings and tasks are returned in the current logged in user's time zone.