Calendar Item: Difference between revisions
m (Bradley Smith moved page Calendar item to Calendar Item without leaving a redirect) |
No edit summary |
||
| Line 1: | Line 1: | ||
[[ContactsLaw]] supports several different types of '''items''' (or '''events''') that may appear on a '''calendar''': | [[ContactsLaw]] supports several different types of '''items''' (or '''events''') that may appear on a '''calendar''': | ||
* '''Appointments''' (with instructions) | * '''Appointments''' (with instructions) | ||
* '''Availability''' entries | * '''Availability''' entries | ||
* [[Calendar:Resource|Resource]] '''reservations''' | * [[Calendar:Resource|Resource]] '''reservations''' | ||
* '''Holidays''' | |||
== Properties == | == Properties == | ||
| Line 9: | Line 10: | ||
* '''Description''' of the event | * '''Description''' of the event | ||
* '''Start''' and '''end''' times ( | * '''Start''' and '''end''' times, including time zones (or all-day events) | ||
* '''Organiser''' [[member]] | * '''Organiser''' [[member]] | ||
* '''Notes''' (in [[Markdown]] format) | * '''Notes''' (in [[Markdown]] format) | ||
| Line 24: | Line 25: | ||
=== Reservations === | === Reservations === | ||
Members can reserve non-venue [[Calendar:Resource|resources]] (such as parking bays, shared computers, etc), helping to avoid collisions and overbookings. | Members can reserve non-venue [[Calendar:Resource|resources]] (such as parking bays, shared computers, etc), helping to avoid collisions and overbookings. | ||
=== Holidays === | |||
Holidays appear on every member's calendar and block out time as busy. Depending on the location of the primary [[business]], public holidays may be periodically updated via an external data source. | |||
== Attendees == | == Attendees == | ||
The organiser of an appointment or availability entry can invite attendees in the form of other [[Member|members]] or external [[Contact|contacts]]. | The organiser of an appointment or availability entry can invite '''attendees''' in the form of other [[Member|members]] or external [[Contact|contacts]]. | ||
Attendees may be required or optional, and responses are recorded when an attendee accepts or declines their invitation. | Attendees may be required or optional, and responses are recorded when an attendee accepts or declines their invitation. | ||
== Venues == | == Venues == | ||
Appointments can be assigned to a particular venue. Venues may be either: | Appointments can be assigned to a particular '''venue'''. Venues may be either: | ||
* A [[Calendar:Resource|resource]] whose occupancy (capacity) can be taken into account when scheduling; or | * A [[Calendar:Resource|resource]] whose occupancy (capacity) can be taken into account when scheduling; or | ||
| Line 37: | Line 41: | ||
== Scheduling == | == Scheduling == | ||
Various features are included to schedule calendar items, all based around detecting and resolving scheduling conflicts. | Various features are included to '''schedule''' calendar items, all based around detecting and resolving scheduling conflicts. | ||
A scheduling conflict occurs when the proposed calendar item overlaps with another item on a calendar belonging to one of the attendees (or the resource consumed by the item). If an attendee has not responded to the invitation, or if their response is ''Accepted'' or ''Tentative<sup>1</sup>'', then a scheduling conflict occurs. If their response is ''Declined'', a scheduling conflict does NOT occur. Scheduling conflicts occur for both ''Required'' and ''Optional<sup>1</sup>'' attendees. | A scheduling conflict occurs when the proposed calendar item overlaps with another item on a calendar belonging to one of the attendees (or the resource consumed by the item). If an attendee has not responded to the invitation, or if their response is ''Accepted'' or ''Tentative<sup>1</sup>'', then a scheduling conflict occurs. If their response is ''Declined'', a scheduling conflict does NOT occur. Scheduling conflicts occur for both ''Required'' and ''Optional<sup>1</sup>'' attendees. | ||
| Line 44: | Line 48: | ||
<sup>1</sup> This is the default behaviour. You can choose to ignore ''Tentative'' responses and/or ''Optional'' attendees on an individual basis. | <sup>1</sup> This is the default behaviour. You can choose to ignore ''Tentative'' responses and/or ''Optional'' attendees on an individual basis. | ||
== Recurrence == | |||
All types of calendar items can be configured to '''recur''' according to a specific pattern, which includes: | |||
* '''Unit''' (from days to years) and '''frequency''' of recurrence | |||
* '''Start''' and '''end''' of the series (can be open-ended) | |||
* Whether occurrences must fall within '''business hours''' | |||
* Any '''exceptions''' to the pattern (dates to skip) | |||
=== Occurrences === | |||
Recurring calendar items behave differently depending on whether a specific '''occurrence''' has been created or not. Normally, there is only one active occurrence in a series, which is created when the previous occurrence is completed; all other occurrences are "virtual" and cannot be manipulated individually. You can, however, create any occurrence on-demand. | |||
== Synchronisation == | == Synchronisation == | ||
ContactsLaw supports 2-way synchronisation for calendar items, via integration with [[Microsoft 365 integration|Microsoft 365]]. You can configure settings for this feature in your [[Member|member profile]]. | ContactsLaw supports 2-way '''synchronisation''' for calendar items, via integration with [[Microsoft 365 integration|Microsoft 365]]. You can configure settings for this feature in your [[Member|member profile]]. | ||
[[Category:Calendar]] | [[Category:Calendar]] | ||
Revision as of 16:51, 11 December 2024
ContactsLaw supports several different types of items (or events) that may appear on a calendar:
- Appointments (with instructions)
- Availability entries
- Resource reservations
- Holidays
Properties
Regardless of type, all calendar items have the following properties:
- Description of the event
- Start and end times, including time zones (or all-day events)
- Organiser member
- Notes (in Markdown format)
- Optional matter
Appointments
Appointments schedule work and include instructions to perform particular activities in ContactsLaw, such as recording time or creating a matter.
Starting an appointment commences the associated activity.
Availability
Availability entries have no associated instruction and are simply used to block out time as free or busy.
Reservations
Members can reserve non-venue resources (such as parking bays, shared computers, etc), helping to avoid collisions and overbookings.
Holidays
Holidays appear on every member's calendar and block out time as busy. Depending on the location of the primary business, public holidays may be periodically updated via an external data source.
Attendees
The organiser of an appointment or availability entry can invite attendees in the form of other members or external contacts.
Attendees may be required or optional, and responses are recorded when an attendee accepts or declines their invitation.
Venues
Appointments can be assigned to a particular venue. Venues may be either:
- A resource whose occupancy (capacity) can be taken into account when scheduling; or
- Free-form text describing an address or other location (for which collision checking is not performed).
Scheduling
Various features are included to schedule calendar items, all based around detecting and resolving scheduling conflicts.
A scheduling conflict occurs when the proposed calendar item overlaps with another item on a calendar belonging to one of the attendees (or the resource consumed by the item). If an attendee has not responded to the invitation, or if their response is Accepted or Tentative1, then a scheduling conflict occurs. If their response is Declined, a scheduling conflict does NOT occur. Scheduling conflicts occur for both Required and Optional1 attendees.
Settings determine whether ContactsLaw assumes members are free or busy during empty periods on their calendar. By default, members are assumed to be free.
1 This is the default behaviour. You can choose to ignore Tentative responses and/or Optional attendees on an individual basis.
Recurrence
All types of calendar items can be configured to recur according to a specific pattern, which includes:
- Unit (from days to years) and frequency of recurrence
- Start and end of the series (can be open-ended)
- Whether occurrences must fall within business hours
- Any exceptions to the pattern (dates to skip)
Occurrences
Recurring calendar items behave differently depending on whether a specific occurrence has been created or not. Normally, there is only one active occurrence in a series, which is created when the previous occurrence is completed; all other occurrences are "virtual" and cannot be manipulated individually. You can, however, create any occurrence on-demand.
Synchronisation
ContactsLaw supports 2-way synchronisation for calendar items, via integration with Microsoft 365. You can configure settings for this feature in your member profile.