Joint Calendar

The tool let you decide by your own which columns construct a related joint event. Use flexible rules to filter documents and create events with required logics. The tool is smart enough to find default values and restrict you in selecting improper field types.

• Model - which object to find: opportunities, tasks, orders, meetings and so on
• Name field - which document field is used as a joint event name (it would be shown on a calendar view as a title). Usually it is 'name', 'subject' or 'reference'. Make sure this field is required to be entered in a parent document or filter documents with empty names. Otherwise, there would be an error, since an event title must be shown on a calendar view
• Start date field - which field should be used as a beginning of an event. For example, 'next action date' for opportunities or 'order date' for quotations. It may be both date or date with time
• Attendees Fields - which field should be used to find participants. Usually, it is some 'responsible', 'sales person' or 'attendees'. But you may use even document 'followers'.Besides, in comparison to other similar modules you may use both users and partners as attendees
• Stop date field - which field to use to define when a joint event is going to be finished
• Always Whole Day means that all generated events would last the whole day disregarding whether start or stop are defined with hours and minutes
• Whole Day Field - a special boolean field, which indicates that a related joint event may lasts the whole day. Such an event would be shown at a special place on a calendar (above the time line)
• Description Field - which field of a related object is used as notes for joint events. Usually the fields like 'internal notes' or 'comments' are used
• Domain – the special filters' constructor to define only topical documents included into this 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
• Action - which action (including views and defaults) to invoke, when you go to a parent object from this joint event

As soon as you prepare joint event rules, you are ready to make and configure a joint calendar. Define a title and merge a few rules to show different document types on the same view.

Apply here also advanced settings:

• Define calendars' menus' sequences. Should it be before the previous super calendar? Then, make a sequence smaller
• Make a calendar public or private. Look also at the section Joint Calendar Rights
• Optimize joint events' generation and modification by making time limits. There is no need to show the events of the last year on a calendar! You do not need to wait for ages until the events are created as it in other similar modules
• Deactivate a joint calendar to hide menus and corresponding events
• The configurations provide useful tips: just point a cursor on a field

The tool let you configure alarms for joint events of 2 types of common calendar alarms: mails and notifications. The schema is the same as it is for Odoo standard calendar events.

You may warn attendees and responsible users at the moment you like to: from 5 minutes to hundreds of days before.

To configure a reminder for all implied events, just indicate 'Default alarms' in a needed joint calendar settings.

The very special feature: use the tool to make customized notifications for any required Odoo objects. Remind sales persons about next actions in opportunities and calls. Warn workers about a new manufacturing order. Notify programmers about deadlines. You may configure it by your own! Both email notifications and sticky popup alarms.

• Only users with administrator rights may configure new joint calendars and related rules to search objects
• Users may see only public calendars or calendars, to which user groups they belong to. Configure it through a related joint calendar: the tab 'Settings' - 'Privacy' and 'Groups'
• Joint calendar users access only joint events, to which parents (leads, tasks, orders, etc.) they have access rights. It is equally true for read, write, create and unlink permission. For example, if a sales person doesn't have a right to observe an opportunity, he/she would not see a related joint event as well
• Manually created joint events may be either public (for all employees) or private (visible for attendees only)

Activities by all objects and responsibles on a single calendar

Activities are a great Odoo invention, which helps you organize daily routine as a set of well-reached and structured tasks. They are quite comfortable for use, but for team collaboration and efficient management, sometimes you want to have a calendar overview of planned and overdue activities.

Joint Calendar let you achieve that goal. Just add an activity rule as joint calendar rule:

• As a model use 'Activity'
• As a name use 'Display Name'
• As a start date field use 'Due Date'
• As attendees fields use 'Assigned to'
• As a domain apply 'Summary is set'
• For the action field create a new one: go to the Settings > Technical > Actions > Window Action. As an object use 'mail.activity', as a view mode – 'form', as a name – any suitable

Opportunities on a super calendar

• As a model use 'Lead / Opportunity'
• As a name use 'Opportunity'
• As a start date field use 'Expecting Closing'
• As attendees fields use 'Salesperson'
• As a domain optionally restrict opportunites by sales teams

Tasks on a joint calendar

• As a model use 'Task'
• As a name use 'Title'
• As a start date field use 'Deadline'
• As attendees fields use 'Responsible User'
• As a domain optionally you can set definite projects