Module Auto Reminder: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Tag: 2017 source edit
No edit summary
Tag: 2017 source edit
Line 13: Line 13:
|status=stable
|status=stable
|prerequisites=Dolibarr 19 or higher
|prerequisites=Dolibarr 19 or higher
|note=Tested on Dolibarr 23. Free module, GPLv3.
|note=Tested on Dolibarr 24. Free module, GPLv3.
}}
}}


Line 75: Line 75:


The module works with the Multicompany module. Each entity sends and reminds '''its own documents only''', with its own settings, its own reminder levels and its own email templates. Sharing in Multicompany grants read visibility on the documents of another entity, it does not change their owner: a shared invoice is still reminded by the entity it belongs to. Nothing to configure. Before 1.3.3, an entity picked up the invoices and proposals of the entities it was allowed to see and processed them with its own settings.
The module works with the Multicompany module. Each entity sends and reminds '''its own documents only''', with its own settings, its own reminder levels and its own email templates. Sharing in Multicompany grants read visibility on the documents of another entity, it does not change their owner: a shared invoice is still reminded by the entity it belongs to. Nothing to configure. Before 1.3.3, an entity picked up the invoices and proposals of the entities it was allowed to see and processed them with its own settings.
== Triggers for developers (since 1.3.5) ==
After each successful email, the module fires a trigger on the invoice or proposal, so that another module can react to it: <code>AUTOREMINDER_SEND</code> after the automatic sending of a validated document, <code>AUTOREMINDER_REMIND</code> after a reminder. The listener receives the document as <code>$object</code> and the details in <code>$object->context['autoreminder']</code>: <code>doctype</code>, <code>actioncomm_id</code> (the agenda event of this email), <code>level_id</code> and <code>level_days</code> (the reminder level, 0 and empty for the initial sending), <code>email_to</code>, <code>email_from</code>, <code>email_subject</code>. The module does not fire the core <code>BILL_SENTBYMAIL</code> and <code>PROPAL_SENTBYMAIL</code> triggers, which mean that a user sent the document from its card.


= Installation =
= Installation =
Line 98: Line 102:
= Version history =
= Version history =


* '''1.3.4''' (2026-09-24, beta): emails to customers whose language has no translation of the template no longer fail, the template selected in the settings is used. Clearer error messages. Version 1.3.1 remains the release version.
* '''1.3.5''' (2026-09-25, beta): triggers <code>AUTOREMINDER_SEND</code> and <code>AUTOREMINDER_REMIND</code> for developers, fired after each successful email. Version 1.3.1 remains the release version.
* '''1.3.3''' (2026-08-05, beta): compatibility with the Multicompany module. Each entity now sends and reminds its own invoices and proposals only, with its own settings and templates, even when sharing is enabled.
* '''1.3.4''' (2026-09-24, beta): emails to customers whose language has no translation of the template no longer fail, the template selected in the settings is used. Clearer error messages.


Full changelog, every version since the first one: [https://framagit.org/doli/modules/autoreminder/-/blob/main/ChangeLog.md ChangeLog.md]
Full changelog, every version since the first one: [https://framagit.org/doli/modules/autoreminder/-/blob/main/ChangeLog.md ChangeLog.md]
48

edits

Navigation menu