8.4. CalDAV¶
- 8.4.1. CalDAV(Common)
- 8.4.1.1. There are limitations on the request in CalDAV communication.
- 8.4.1.2. User password is required to perform CalDAV linkage.
- 8.4.1.3. Participants cannot be selected when the schedule is registered.
- 8.4.1.4. Facility reservation cannot be made when schedule is registered.
- 8.4.1.5. Schedule of time zone that is not supported in intra-mart Accel Collaboration cannot be registered.
- 8.4.1.6. Client reminder (alarm) setting is not supported.
- 8.4.1.7. Participants and facilities cannot be accessed at schedule reference time.
- 8.4.1.8. Participants and facilities cannot be changed at schedule update time.
- 8.4.1.9. When the schedule synchronization is to be made, E tags of all schedule data for the target term should always be obtained.
- 8.4.1.10. If start/end date and time of the schedule is out of CalDAV obtaining subject period,it will not be displayed even if it is right after the registration and update.
- 8.4.1.11. Iteration conditions for schedule registration and update are limited only to the ones that can be specified by the schedule function of intra-mart Accel Collaboration.
- 8.4.1.12. Iteration interval that can be specified when registering or updating weekly schedule for each iteration type is [1] only.
- 8.4.1.13. Schedule with more than [2] iteration interval for each week is not displayed correctly on CalDAV client.
- 8.4.1.14. In case [No iteration limit] is specified when iteration schedule is registered or updated, schedule and event of maximum term in the setting file are registered.
- 8.4.1.15. Only daily, weekly, or monthly can be specified to iteration type at iteration schedule registration or update time.
- 8.4.1.16. Interval cannot be specified when registering or updating daily schedule for each iteration type.
- 8.4.1.17. Number of times of iterations cannot be specified for iteration schedule registration or update.
- 8.4.1.18. Only one date can be specified for the monthly iteration when registering and updating monthly schedule for each iteration type.
- 8.4.1.19. Data which is outside the obtaining period of CalDAV schedule setting file will also be displayed.
- 8.4.1.20. Regular schedule that you declined in the schedule of intra-mart Accel Collaboration will be displayed on CalDAV client.
- 8.4.1.21. Schedule registration by inputting number of characters that exceed maximum number limit in the description field of intra-mart Accel Collaboration can be made.
- 8.4.2. CalDAV（Thunderbird Lightning）
- 8.4.2.1. Only one CalDAV account may be registered for one server in Thunderbird Lightning.
- 8.4.2.2. For the schedule of time zone that is not supported in Thunderbird Lightning, warning would be displayed at reference time.
- 8.4.2.3. In case iteration schedule is registered in Thunderbird Lightning, end date may not match with the date you have specified.
- 8.4.2.4. In case daily schedule for each iteration type is registered in Thunderbird Lightning, weekdays cannot be specified.
- 8.4.2.5. If you change only the start date without changing the end date of regular schedule, end date will also be changed.
- 8.4.3. CalDAV(iPhone)
- 8.4.3.1. Synchronization setting on iPhone device is invalid.
- 8.4.3.2. Display name and color of calendar are fixed throughout the system.
- 8.4.3.3. The color edited on the device will revert to the system setting by deleting the account and re-registering it.
- 8.4.3.4. Calendar name that was edited on iPhone device will be reverted to the system setting by synchronization.
- 8.4.3.5. On iPhone device, schedule cannot be registered by specifying the last date of each month as the iteration condition.
- 8.4.3.6. If you failed to register the schedule on iPhone device, the failed schedule will remain displayed on the screen.