You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Simone Orsi
45ddba30a9
|
7 years ago | |
---|---|---|
.. | ||
controllers | 7 years ago | |
data | 7 years ago | |
demo | 7 years ago | |
i18n | 7 years ago | |
images | 7 years ago | |
models | 7 years ago | |
security | 7 years ago | |
static/description | 7 years ago | |
templates | 7 years ago | |
tests | 7 years ago | |
views | 7 years ago | |
README.rst | 7 years ago | |
__init__.py | 7 years ago | |
__manifest__.py | 7 years ago |
README.rst
.. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
=========================
Mail digest notifications
=========================
Features
--------
This module allows users/partners to:
* select "digest" mode in their notification settings
* with digest mode on select a frequency: "daily" or "weekly"
* configure specific rules per message subtype (enabled/disabled)
to receive or to not receive any email notification for a given subtype.
The preference tab on user's form will look like:
.. image:: ./images/preview.png
Behavior
--------
When a partner with digest mode on is notified with a message or an email
all the messages are collected inside a `mail.digest` container.
A daily cron and a weekly cron will take care of creating a single email per each digest,
which will be sent as a standard email.
If the message has a specific subtype, all of this will work only
if personal settings allow to receive notification for that specific subtype.
Specifically:
* no record for type: message passes
* record disabled for type: message don't pass
* record enabled for type: message pass
NOTE: under the hood the digest notification logic excludes followers to be notified,
since you really want to notify only mail.digest's partner.
NOTE 2: Odoo's mail machinery has an option `force_send`
to send the email immediately without waiting for the mail queue to be processed.
When this option is used the email is sent right away
and the message record is deleted right after.
A typical use case is the reset password mail.
We assume that if you use that option you really want the email to go out "now"
so when `force_send` is used, digest machinery is completely bypassed.
Global settings
---------------
By default digest functionality is enabled for every message type ('email', 'comment', 'notification').
You change this with the config param `mail_digest.enabled_message_types`
whereas you can specify message types separated by comma.
Digest rendering preview
------------------------
You can check how messages are formatted per each mail subtype by going to `/digest/layout-preview` in your browser.
.. image:: ./images/digest_layout_preview.png
Known issues / Roadmap
======================
* take full control of message and email template.
Right now the notification message and the digest mail itself is wrapped inside Odoo mail template.
We should be able to customize this easily.
Bug Tracker
===========
Bugs are tracked on `GitHub Issues
<https://github.com/OCA/social/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.
Credits
=======
Contributors
------------
* Simone Orsi <simone.orsi@camptocamp.com>
Funders
-------
The development of this module has been financially supported by: `Fluxdock.io <https://fluxdock.io>`_
Maintainer
----------
.. image:: https://odoo-community.org/logo.png
:alt: Odoo Community Association
:target: https://odoo-community.org
This module is maintained by the OCA.
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.
To contribute to this module, please visit https://odoo-community.org.