Joint Calendar v.11

To add a new document type for a joint calendar you should set up a joint calendar rule. This rule defines which Odoo objects should create events, which fields of that object should be shown, and whether any filtering should take place. The app will try to add the most typical values by default, but you should think which data is required in your exact case.

• Model - which objects to scan: opportunities, tasks, orders, meetings, activities, and so on. You can choose your custom document type as well!
• Name – what to use as a joint event name (also used as calendar event title). Usually it is 'name', 'subject' or 'reference'.
• Start date - when an event starts. For example, 'expecting closing' for opportunities or 'order date' for quotations. It may be any date or date with time field of a source Odoo object.
• Attendees – who are participants (responsible persons, event owners). Usually, it is a field 'assigned to', 'a sales person' or 'attendees'. You may use even document 'followers'. It is possible to apply both users and partners as attendees
• Stop date – when an even is shown as finished on a calendar.
• Always Whole Day - means that all generated events would last the whole day disregarding whether start or stop are defined with hours and minutes. Such an event would be shown at a special place on a calendar (above the time line)
• Whole Day - a special boolean field of source object which indicates that a related joint event may lasts 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.
• Description – are there any notes important for joint events? Usually the fields like 'internal notes' or 'comments' are used
• Domain – the special filters' constructor to include only topical documents into a joint calendar. You might search almost by any criteria. For example, show only quotations without sales orders, or show opportunities only of this sales team or of this customer. If you are confident to make Reverse Polish Notations you may also turn on the debug mode to construct advanced filters.
• Action – defines which form view should be shown when you open a source document from a joint event. It is a technical field which in the most cases should not be changed in comparison to a default value.

As soon as you prepare a few joint event rules, you are ready to configure a new joint calendar.

First of all, define a title. It would be used as a menu entry for all joint calendar users.

Second of all, choose document types (rules) which should be merged on this shared calendar.

Then, switch to the advanced settings. Some of those might be useful:

• Sequence – in which order various joint calendars' entries are shown. Should it be before the previous super calendar? Then, make a sequence smaller.
• Privacy – let you make a calendar public or private (for predefined user groups only).
• Time limits – allow you optimizing performance of joint events' interfaces. Often there is no need to show the documents of the last year on a calendar.

Is this joint calendar is not any more of use, but it might be needed in the Future? Fine, just archive this calendar: you can activate it at any moment afterwards.

All you need is to prepare a few reminders and indicate those as default on a shared calendar form. Once joint events are generated, each of those would have the same alarms. Afterwards, you may update the these alarms for certain items if you want.

Thus, you can make reminders for any Odoo document automatically. Remind sales persons about next actions in opportunities and calls. Warn workers about a new manufacturing order. Notify programmers about deadlines. So on and so on.

Use both email notifications or pop-up warnings. Warn attendees and responsible users at the moment you like to: from 5 minutes to hundreds of days before.

Users observes a link for a source document right on an event form. Thus, it is always possible to expand miscellaneous details.

If you changed a joint event, its parent object would be updated correspondingly in real time. For example, you drag a record and drop it to another date, then a source document would be also moved. Be cautious: it does not work for computed and readonly fields (e.g. a create date can not be modified logically).

If you changed a source object, a joint event would be updated with a next super calendar scheduled job.