Lucas Lefèvre
ae3d37c201
This commit refactors calendar synchronization between Odoo and Google after the main calendar application refactoring. This refactoring takes advantage of two new features from the Google API: - New way of synchronizing resources efficiently[1] Incremental sync is performed repeatedly and updates Odoo with all the changes that happened ever since the previous sync. Each time, Odoo provides the previous sync token it obtained from Google and stores the new sync token from the response. - Event metadata[2] Ability to set hidden key-value pairs with an event, called extended properties. These extended properties are used to store the related odoo event id and the Odoo owner id (see known limitations) Known limitations ================= - Let A and B be two new users (no tokens available). A creates an event in Odoo and invites B. A is the owner of the event (user_id). Now B authenticates to his Google Calendar account and synchronizes his calendar. We cannot send the event to A's calendar since we don't have any access to his Google Calendar. Hence the event his sent to B's calendar. This leads to data de-synchronisation: The owner is A in Odoo but B in Google. The "real" owner (user A) is stored in the Google event's metadata to be able to reconcile the owner for following synchronizations. - Let A and B be two users of Odoo and Google Calendar. And let the Google Calendar of B be private (e.g. if A creates an event in Google Calendar and invites B, B won't see the event in his calendar). If A creates an event in Odoo and invites B. The event is synced to Google Calendar of A. Now B can see the event in Odoo but he can't see it in his Google Calendar. Task 2126717 PR #42031 PR Enterprise odoo/enterprise#8006 [1] https://developers.google.com/calendar/v3/sync [2] https://developers.google.com/calendar/extended-properties
24 lines
1.1 KiB
XML
24 lines
1.1 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<odoo>
|
|
<data>
|
|
<record forcecreate="True" id="ir_cron_sync_all_cals" model="ir.cron">
|
|
<field name="name">Google Calendar: synchronization</field>
|
|
<field name="model_id" ref="model_res_users"/>
|
|
<field name="state">code</field>
|
|
<field name="code">
|
|
# LUL TODO check this comment
|
|
# The context key 'last_sync_hours' allows specifying the minimum delay between consecutive syncs.
|
|
# Indeed, in case there are many users / events to sync, the cron might time out. In this case, the
|
|
# solution is to force the last_sync_hours to the expected synchronization interval expected. This
|
|
# will avoid the synchronization of users that succeeded in the previous failing cron.
|
|
model._sync_all_google_calendar()
|
|
</field>
|
|
<field name="user_id" ref="base.user_root" />
|
|
<field name="interval_number">12</field>
|
|
<field name="interval_type">hours</field>
|
|
<field name="numbercall">-1</field>
|
|
<field eval="False" name="doall" />
|
|
</record>
|
|
</data>
|
|
</odoo>
|