data-protection

History

Jairo Llopis f3324bf41e privacy_consent: Separate automated emails send process Before https://github.com/OCA/data-protection/pull/29 there was a race condition where an email could be sent while the same transaction that created the `privacy.consent` record still wasn't committed, producing a 404 error if the user clicked on "Accept" or "Reject" before all mails were sent. To avoid that, a raw `cr.commit()` was issued, but this produced another situation where the user had to wait until the full email queue is cleared to get his page loaded. It wasn't an error, but a long queue meant several minutes waiting, and it's ulikely that an average human is so patient. So, here's the final fix (I hope!). The main problem was that I was looking in the wrong place to send the email. It turns out that the `self.post_message_with_template()` method is absolutely helpless in the case at hand, where these criteria must be met: * E-mail must be enqueued, no matter if there are less or more than 50 consents to send. * The template must be processed per record. * In an ideal world, a `cr.commit()` must be issued after each sent mail. The metod that was being used: * Didn't allow to use `auto_commit` mode. * Only allowed to render the template per record if called with `composition_mode="mass_mail"`. * Only allowed to enqueue emails if called with `composition_mode="mass_post"`. Obviously, I cannot set 2 different values for `composition_mode`, so a different strategy had to be used. I discovered that the `mail.template` model has a helpful method called `send_mail()` that, by default: * Renders the template per record * Enqueues the email * The email queue is cleared in `auto_commit=True` mode. So, from now on, problems are gone: * The user click, or the cron run, will just generate the missing `privacy.consent` records and enqueue mails for them. * The mail queue manager will send them later, in `auto_commit` mode. * After sending the e-mail, this module will set the `privacy.consent` record as `sent`. * Thanks to not sending the email, the process the user faces when he hits the "generate" button is faster. * Instructions in the README and text in the "generate" button are updated to reflect this new behavior. * Thanks to the `auto_commit` feature, if Odoo is rebooted in the middle of a mail queue clearance, the records that were sent remain properly marked as sent, and the missing mails will be sent after the next boot. * No hardcoded commits. * No locked transactions. * BTW I discovered that 2 different emails were created when creating a new consent. I started using `mail_create_nolog=True` to avoid that problem and only log a single creation message. Note to self: never use again `post_message_with_template()`.		6 years ago
..
controllers	privacy_consent: Privacy explicit consent tracking tools (#11)	4 years ago
data	privacy_consent: Separate automated emails send process	4 years ago
i18n	privacy_consent: Separate automated emails send process	4 years ago
models	privacy_consent: Separate automated emails send process	4 years ago
readme	privacy_consent: Separate automated emails send process	4 years ago
security	privacy_consent: Privacy explicit consent tracking tools (#11)	4 years ago
static/description	privacy_consent: Separate automated emails send process	4 years ago
templates	privacy_consent: Privacy explicit consent tracking tools (#11)	4 years ago
tests	privacy_consent: Separate automated emails send process	4 years ago
views	privacy_consent: Separate automated emails send process	4 years ago
README.rst	privacy_consent: Separate automated emails send process	4 years ago
__init__.py	privacy_consent: Avoid race condition with mail queue cron	4 years ago
__manifest__.py	privacy_consent: Privacy explicit consent tracking tools (#11)	4 years ago

README.rst

=================
Privacy - Consent
=================

.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !! This file is generated by oca-gen-addon-readme !!
   !! changes will be overwritten.                   !!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png
    :target: https://odoo-community.org/page/development-status
    :alt: Production/Stable
.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png
    :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
    :alt: License: AGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fdata--protection-lightgray.png?logo=github
    :target: https://github.com/OCA/data-protection/tree/10.0/privacy_consent
    :alt: OCA/data-protection
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
    :target: https://translation.odoo-community.org/projects/data-protection-10-0/data-protection-10-0-privacy_consent
    :alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runbot-Try%20me-875A7B.png
    :target: https://runbot.odoo-community.org/runbot/263/10.0
    :alt: Try me on Runbot

|badge1| |badge2| |badge3| |badge4| |badge5| 

This module allows the user to define a set of subjects (partners)
affected by any data processing activity, and establish
a process to ask them for consent to include them in that activity.

For those that need explicit consent as a lawfulness base for personal data
processing, as required by GDPR (article 6.1.a), this module provides the
needed tools to automate it.

**Table of contents**

.. contents::
   :local:

Installation
============

You may want to install, along with this module, one of OCA's
``mail_tracking`` module collection, such as ``mail_tracking_mailgun``, so
you can provide more undeniable proof that some consent request was sent, and
to whom.

However, the most important proof to provide is the answer itself (more than
the question), and this addon provides enough tooling for that.

Multi-database instances
~~~~~~~~~~~~~~~~~~~~~~~~

To enable multi-database support, you must load this addon as a server-wide
addon. Example command to boot Odoo::

    odoo-bin --load=web,privacy_consent

Usage
=====

New options for data processing activities:

#. Go to *Privacy > Master Data > Activities* and create one.

#. Give it a name, such as *Sending mass mailings to customers*.

#. Go to tab *Consent* and choose one option in *Ask subjects for consent*:

   * *Manual* tells the activity that you will want to create and send the
     consent requests manually, and only provides some helpers for you to
     be able to batch-generate them.

   * *Automatic* enables this module's full power: send all consent requests
     to selected partners automatically, every day and under your demand.

#. When you do this, all the consent-related options appear. Configure them:

   * A smart button tells you how many consents have been generated, and lets you
     access them.

   * Choose one *Email template* to send to subjects. This email itself is what
     asks for consent, and it gets recorded, to serve as a proof that it was sent.
     The module provides a default template that should be good for most usage
     cases; and if you create one directly from that field, some good defaults
     are provided for your comfortability.

   * *Subjects filter* defines what partners will be elegible for inclusion in
     this data processing activity.

   * You can enable *Accepted by default* if you want to assume subjects
     accepted their data processing. You should possibly consult your
     lawyer to use this.

   * You can choose a *Server action* (developer mode only) that will
     be executed whenever a new non-draft consent request is created,
     or when its acceptance status changes.

     This module supplies a server action by default, called
     *Update partner's opt out*, that syncs the acceptance status with the
     partner's *Elegible for mass mailings* option.

#. Click on *Generate consent requests* link to create new consent requests.

   * If you chose *Manual* mode, all missing consent request are created as
     drafts, and nothing else is done now.

   * If you chose *Automatic* mode, also those request e-mails are enqueued
     and, when the mail queue is cleared, they will be set as *Sent*.

#. You will be presented with the list of just-created consent requests.
   See below.

New options for consent requests:

#. Access the consent requests by either:

   * Generating new consent requests from a data processing activity.

   * Pressing the *Consents* smart button in a data processing activity.

   * Going to *Privacy > Privacy > Consents*.

#. A consent will include the partner, the activity, the acceptance status,
   and the request state.

#. You can manually ask for consent by pressing the button labeled as
   *Ask for consent*.

#. All consent requests and responses are recorded in the mail thread below.

Bug Tracker
===========

Bugs are tracked on `GitHub Issues <https://github.com/OCA/data-protection/issues>`_.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us smashing it by providing a detailed and welcomed
`feedback <https://github.com/OCA/data-protection/issues/new?body=module:%20privacy_consent%0Aversion:%2010.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.

Do not contact contributors directly about support or help with technical issues.

Credits
=======

Authors
~~~~~~~

* Tecnativa

Contributors
~~~~~~~~~~~~

* `Tecnativa <https://www.tecnativa.com>`_:

  * Jairo Llopis

Maintainers
~~~~~~~~~~~

This module is maintained by the OCA.

.. image:: https://odoo-community.org/logo.png
   :alt: Odoo Community Association
   :target: https://odoo-community.org

OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.

This module is part of the `OCA/data-protection <https://github.com/OCA/data-protection/tree/10.0/privacy_consent>`_ project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.