8.4.1. CalDAV(Common)¶

Followings are the request types that are supported in CalDAV communication.

In order to perform CalDAV linkage, user password is required.

Users who do not have the password cannot use CalDAV linkage.

When schedule is registered by using CalDAV client, participants are only registrants.

In case schedule is registered by using CalDAV client, facility reservation cannot be made at registration time.

In CalDAV client, the schedule cannot be registered by specifying the time zone that is not supported by intra-mart Accel Collaboration.

If the time zone that is not supported is specified, input parameter error occurs at schedule registration time.

Reminder (alarm) setting of CalDAV client is not supported.

In case schedule is referred to by using CalDAV client, information about participants and facilities of the registered schedule cannot be accessed.

In case you update the schedule by using CalDAV client, information about participants and facilities cannot be changed when it is updated.

When the schedule synchronization is to be made, E tags of all schedule data for the target term should always be obtained.

When you register or update the schedule with CalDAV client,

it will not be displayed in CalDAV client even if it is right after the registration or update if planned start/end date and time is out of CalDAV obtaining subject period.

Contents of the registration and update are reflected as the schedule function data of intra-mart Accel Collaboration at this point.

If you register and update the schedule that has iteration conditions by using CalDAV client,

only a condition that can be specified by schedule function of intra-mart Accel Collaboration can be specified for the iteration condition.

Please refer to the intra-mart Accel Collaboration / Schedule Users Operations Guide for the details of iteration conditions.

Iteration interval that can be specified when registering or updating weekly schedule for each iteration type by CalDAV client is [1] only.

If you specify more than [2] as an iteration interval, input parameter error will occur.

Schedule that has more than [2] iteration interval for each week is not displayed correctly on CalDAV client.

Operations for the corresponding data also would be out of scope of operation warranty.

If you specify [No iteration limit] to iteration condition when you register the iteration schedule using CalDAV client,

schedule of the term up to the [Registerable Term] [Registerable number of items] in the setting file is registered.

Iteration type that can be used when you register and update the iteration schedule using CalDAV client are daily, weekly, and monthly only.

Input parameter error will occur if you specify other types.

You cannot specify the interval of iteration period when you register or update daily schedule for each iteration type by using CalDAV client.

Input parameter error will occur if you specify the interval.

When you register and update the iteration schedule using CalDAV client, you cannot specify number of times of iterations.

Number of times of iterations would be ignored even if it is specified and it will be registered as it is.

Only one date can be specified for the monthly iteration when you register or update monthly schedule for each iteration type by using CalDAV client.

Input parameter error will occur when you specify multiple dates for monthly iteration.

Data which is outside the obtaining period of CalDAV schedule setting file will also be displayed,

if end date and start date of schedule were registered within the obtaining period.

If you decline only one day from the regular schedule in the schedule function of intra-mart Accel Collaboration,

schedule of the date declination was made for is displayed in the schedule of CalDAV client.

This phenomenon occurs because of iCalendar specifications.

If you register and update schedule using CalDAV client,

you can input number of characters that exceed maximum number limit in the description field of intra-mart Accel Collaboration.

Schedule that was registered or updated exceeding the maximum number limit in the description field

cannot be updated by the schedule function of intra-mart Accel Collaboration if it remains exceeding the limit number of 1000 characters.