Joint Calendar is an Odoo tool that combines different Odoo events in one or a few configurable super calendars. Odoo users often need to keep in mind a lot of details that are spread out among numerous interfaces. Switching between those is not comfortable and error-prone for planning. This tool solves the problem. The app allows to configure rules to join and share various document types on a single super calendar view but with easy-reachable source objects.

The tool might merge any Odoo document types on the same view: opportunities, meetings, phone calls, activities, sale or purchase orders, shipments and deliveries, tasks and tickets, and time offs, ...

Configure as many calendars as you need: for various functional areas or different user groups. Each joint calendar has its menu item.

Define on your own what to consider a joint event title, start or stop date, who are target attendees, etc. Have even the same document twice on the same calendar just with a different start.

Joint events and their source documents are interrelated. Update the former and the latter will be changed immediately. A reverse operation will be applied according to the system schedule.

Calendar configuration lets assign popups and email alarms. Thus, it is possible to have notification of any Odoo event or activity.

Regulate joint calendar access right on its form. Make it public or share it only for chosen user groups. Shared calendars are especially suitable for team interactions. Users might switch between document types and participants in a single click.

Joint events are updated regularly by the cron job. It is fast, especially if you apply time frames. Refreshing is also available from the calendar interface.

The tool might merge any Odoo document type on the same view: opportunities, meetings, phone calls, activities, sale or purchase orders, shipments and deliveries, tasks and tickets, and time offs, ...

Configure as many calendars as you need: for various functional areas or different user groups. Each super calendar has its menu item. According to the company's needs, you can combine all required documents into one calendar, or divide them logically into several ones. For example, you can create a calendar 'Various calendars' for all documents or you can create a 'Sales Calendar', which will include everything, that relates to sales, and a 'Tasks and Time offs' calendar, which will include only tasks and employees time offs and leaves.

To create a Calendar:

1. Open the Events app and click Configurations > Calendars in the systray

2. Click 'New'

3. Introduce the title

4. Add Rules (see Joint Calendar Rules)

5. Go to the tab 'Settings'

6. Add/Remove the tick 'Active menu', to add/remove the Calendar from the Event's systray

7. Optionally add the sequence, set the privacy, time limits, and alarms

The button 'Generate Events' above the calendar's form can be used to trigger the scheduled job to add the events to the calendar (see Joint Calendar Scheduled Jobs).

When you add rules to the calendar, you specify which models should be presented in the calendar (see Joint Calendar Rules). This allows to keep rules logically divided into several calendars and conveniently switch between them, so the calendar will not be overloaded (see Joint Calendar Interface). Also, it is especially useful to configure rules in a batch as it is the calendar's settings, that control the privacy, time limits, and alarms.

You can find all the features available for configuration in the tab 'Settings' while editing or creating a calendar.

The first feature is 'the Active menu'. If it is turned on, the entry for this shared calendar will be available under the menu ‘Events’ (see Joint Calendar Interface). Otherwise, the calendar will not be shown and you will not be able to access it. It is useful when you no longer need a calendar but don't want to delete it yet as it is still might be useful later.

If the option is turned off for all of the calendars, the menu 'Events' will be hidden from the main menu.

The field 'Sequence' below the 'Active menu' defines the order in which the calendars are displayed in the systray. The Calendar, which goes the first, has a lower sequence. So, the calendar with sequence 20 will be displayed before the calendar with sequence 50.

To change the sequence, type the number in the field 'Sequence'. The number can be either positive or negative or a zero.

For each calendar, you can set access rights. The calendar may be either public (seen by everyone) or private (seen by particular user groups).

The field 'groups' appear as you choose the option 'private' in the field ' Privacy'. Users may observe only the events to which related objects they have access rights (see Joint Calendar Access Rights).

Shared calendars are especially suitable for team interactions. Users might switch between document types and participants in a single click.

It is also possible to set limitations to make events update faster and consume system resources efficiently. For that, tick the box 'Time limits' and set 'Days before' and 'Days after', so only events within this time range will be shown in the calendar. By default, the events are shown 10 days before the event and 30 days after. For example, you have a Task 'Fix the sink' for the 30th of March. Today is the 15th of March, so the task will not be shown on the calendar. However, in 5 days, it will appear, as it is set to show events 10 days before. And the event will stay on the calendar till the 29th of April.

If you remove the tick from the box 'Time Limits', then the events for all time will be shown (see Refreshing Joint Events & Scheduled Jobs).

Calendar configuration lets assign default popups and email alarms. Thus, it is possible to have notification of any Odoo event or activity. You can choose the type of alarm and the time of warning (see Joint Calendar Alarms).

It is also possible to set an alarm for a particular event (see Joint Calendar Interface).

To add a new document type for a shared interface you should set up a shared calendar rule. Rules define which Odoo objects should create events, which fields of that object should be used and shown, and whether any filtering should take place.

Define on your own what to consider a joint event title, start or stop date, who are target attendees, etc. Have even the same document twice on the same calendar just with a different start.

To create a rule:

1. Open the Events app and click Configurations > Rules in the systray

2. Click 'New'

3. Type the rule title

4. Choose a model (see Rules Fields)

5. Define a name field (see Rules Fields)

6. Select a start date field (see Rules Fields)

7. Choose an attendees field (see Rules Fields)

8. Optionally add a stop date field (see Rules Fields)

9. Optionally choose a description field (see Rules Fields)

10. Optionally select a contact links field (see Rules Fields)

11. Optionally add filters to specify events, that should be shown in a calendar with this rule (see Filters)

You can add a rule to a calendar while creating or editing it in the tab Rules by clicking 'Add a line'. To delete a rule from the calendar click on the cross by it.

You cannot add the same rule to one calendar twice. However, you can create a slightly different rule, with another title or fields used.

If the same object was found twice by different rules, an event will also be generated twice. It's because essential parameters like attendees, start time, and subjects may differ.

Each field, that a rule has, serves a particular purpose. Below you can find the description of each setting.

Model - a target Odoo document, which defines what objects to scan: opportunities, tasks, orders, meetings, activities, and so on. You can choose your custom document type (including those created in Odoo Studio) as well. The mandatory field.

For example, if you choose the model 'Sales Order', then events will be created based on the existing Odoo quotations.

Name - a field of the target Odoo model, which defines what to use as a joint event name (also used as calendar event title). Usually, it is 'name', 'subject', or 'reference'. The mandatory field.

For example, if you create a rule for the model 'Sale Order' and choose the ‘Order reference’ for the Name Field, then, a joint even related to the quotation ‘S00001’ will be also named ‘S00001’.

Start date - a field of the target Odoo model, which defines when an event starts. For example, 'expecting closing' for opportunities or 'order date' for quotations. It may be any date or date with the time field of a source Odoo object. The mandatory field.

For example, if you create a rule for the model 'Sale Order' and choose the 'Order Date' for the Start date field, then the event will appear in the calendar on the same day for which the quotation is planned.

Stop date - a field of the target Odoo model, which defines when an event is shown as finished on a calendar. The optional field.

For example, if you create a rule for the model 'Sale Order' and choose the 'Delivery Date' for the Stop date field, then the event will be shown in the events menu from the day for which this quotation is planned (Start Date field - Order Date) till the day of the product's delivery.

If you leave the field empty, then in the events menu, the event will be placed only on the day defined by the Start Date field.

Attendees - a field of the target Odoo model, which defines who are participants (responsible people, event owners). For instance, 'assigned to', 'sales person', or 'attendees'. You may use even document 'followers' since it's possible to apply both users and partners. The mandatory field.

For example, If you create a rule for the model 'Sale Order', and add choose the 'Salesperson' for the Attendees field, then joint even participants would include a quotation salesperson. Also, the event will be shown, if you sort events by this salesperson in the section attendees in the 'Events' menu (see Joint Calendar Interface).

Description - a field of the target Odoo model, which shows the notes, that the event has if there are any. Usually, the fields like 'internal notes' or 'comments' are used. The optional field.

For example, if you create a rule for the model 'Sale Order' and choose 'Terms and Conditions' for the Description field, then the related-to-order terms and conditions will be shown on the event's card.

If you leave the field empty, then the event's description field will be also empty.

Always Whole Day - an option, which can be turned on/off. When it is turned on, then all generated events created with the rule will last the whole day disregarding whether start or stop is defined with hours and minutes. Such an event will be shown at a special place on the calendar.

For example, if you create a rule for the model 'Sale Order', and turn on the option 'Always Whole Day', then the event will be placed on the daily and weekly super calendars above the timeline.

If you turn off the option, then, if the start or stop are defined with hours/minutes, the event will be placed at a particular time on the day's timeline and you will see the time before the event's title.

Whole Day - a special boolean field of the source object, which indicates that a related joint event may last the whole day. This setting is usually applied to standard Odoo calendar events which both might have definite time indicated or might be planned for a whole day. This optional field is available only if the setting 'Always Whole Day' is turned off.

For example, if we create a rule for the model 'Calendar Event' and choose 'All Day' as the Whole Day field, then, in case the event lasts all day, an event without the timing will be created. The event will be on the calendar the whole day and it will be placed above the timeline.

If you leave the field empty, then in case the calendar event has a definite time, it will be mentioned.