Every member of staff gets one EMS message a day at most, at the moment they chose in their profile, with everything EMS has for them that isn’t urgent:
mail.activity) assigned to them that is due today or
overdue (see Postponing a task). Most EMS tasks
(convalidation requests, supporting documents to validate, attendance corrections, absence
approvals…) are scheduled with mail_activity_quick_update, which suppresses Odoo’s “X has
assigned you an activity” email on purpose (see Task assignment), so this
is how someone who hasn’t opened EMS learns that work is waiting.ems.info_notice), grouped
by the record they are about (usually a student; a Quality agreement for its responsible people, see
Quality: telling the people concerned).It replaced two separate emails (issue #644): the morning pending-tasks digest and the tutor’s
attendance issues report, each with its own schedule. Rule for new code (also in CLAUDE.md):
a notice to staff that asks for no action and isn’t urgent is never sent on the spot; it is
queued with ems.info_notice._ems_queue() and travels in this summary. Something the person must
act on is an activity. Only a genuinely urgent case (e.g. a guard duty for today) is sent
immediately, with a comment in the code saying why. Families and students are not affected: their
emails are a different channel.
Module files: models/shared/daily_summary.py (res.users), models/shared/info_notice.py
(ems.info_notice), models/employees/workday.py (hr.employee/res.company working days),
mails/shared/daily_summary.xml (QWeb body), data/main/ir.cron-daily_summary.csv,
views/community/employee/user_profile_form.xml.
res.users (inherited)| Field | Type | Description |
|---|---|---|
ems_digest_moment |
Selection, required, default teacher_start |
When the summary is sent: teacher_start (start of their working day), teacher_end (end of it), students_end (end of their students’ last class, group tutors only; anyone else gets teacher_end), fixed_time. Self-readable and self-writable, in My Profile > Preferences > Daily summary. |
ems_digest_time |
Float |
The fixed_time hour (local). Default: the company’s attendance_issue_tutor_default. Must be a time of day (constraint). |
ems_digest_next |
Datetime, readonly |
When the next summary is due (naive UTC). Set as soon as something is waiting, moved on after each summary, cleared when nothing is left. Never shown to the user. |
ems_digest_last_sent |
Datetime, readonly |
When the last summary went out. |
ems_is_tutor |
Boolean, computed |
Whether the user tutors a group (ems.group.tutor_id); not the ems.group_tutor role, which Department/Seminar Chiefs, JE/JEA and the Director also hold. |
The native notification_type (“Handle by Emails” / “Handle in Odoo”) is moved into the same
“Daily summary” block of the profile (it lives in the native preferences block, which EMS hides
from ordinary users): it decides whether the summary arrives by email or in their EMS inbox.
ems.info_noticeA notice waiting for its recipient’s summary. Only the system reads or writes it (sudo()); the
administrator (base.group_system) may read it.
| Field | Type | Description |
|---|---|---|
user_id |
Many2one res.users, required, cascade |
Recipient. |
res_model / res_id |
Char / Many2oneReference |
The record the notice is about, linked from the summary. |
body |
Html |
The notice, already written in the recipient’s language when queued. |
sent_date |
Datetime |
When it went out in a summary; notices sent more than 30 days ago are deleted by the cron. |
_ems_queue(users, record, compose) creates one notice per user, compose(user) writing it in
that user’s language; archived users, portal users and OdooBot are skipped.
All in the company’s timezone. res.users._ems_digest_moment_on(day) gives the moment on one day,
or None when there is none:
| Moment | On a given day |
|---|---|
teacher_start (default) |
Start of the person’s working day: their employee’s schedule with approved absences and public holidays subtracted (hr.employee._ems_workday_intervals), or the company’s default schedule framework without an employee or schedule. None on a day they don’t work. |
teacher_end |
End of that same working day. |
students_end |
End of the last class that day of any student they tutor, from each student’s own schedule (hr.employee._ems_students_day_end, built from their enrollments: a 2nd-year student taking a 1st-year subject counts with that group’s class). |
fixed_time |
ems_digest_time, on every school day of the centre (a day the default framework has periods, public holidays subtracted). |
_ems_digest_eta(issue_date, fallback) gives the next due moment, always after now:
teacher_end, students_end): that moment on issue_date (the day the
reported data belongs to) if it hasn’t passed yet.attendance_issue_tutor_default. Pending tasks and notices never use it: nobody
gets a summary on a day off or during an absence just for those.flowchart TD
A[Something waits for the summary:<br/>activity, unreported issue, queued notice] --> B{ems_digest_next set?}
B -- no --> C[Cron sets it:<br/>_ems_digest_eta, fallback only if issues]
B -- yes --> D
I[Tutor's issue of day D<br/>_schedule_tutor_report] --> J[ems_digest_next = min of current,<br/>_ems_digest_eta of D]
J --> D
C --> D{Cron, every 15 min:<br/>ems_digest_next ≤ now?}
D -- no --> Z[Next run]
D -- yes --> E{Anything in it?}
E -- yes --> F[message_notify the summary;<br/>mark issues tutor_notified, notices sent]
E -- no --> G[Nothing sent]
F --> H[_ems_digest_reschedule:<br/>next moment if something is still pending, else cleared]
G --> H
res.users.write) moves a summary already due to the new moment.fields.Datetime.now(), so a test can freeze them together.The summary only lists tasks due today or overdue (date_deadline <= the company’s today,
res.users._ems_digest_task_domain(), shared by the candidate search, _ems_digest_has_content()
and _ems_digest_task_groups()). Postponing a task is moving its due date (issue #727): it leaves
the summary, and the subject’s count, until that day and comes back on its own: the cron, every
few minutes, finds its owner among the candidates again once it is due and schedules their next
moment. Someone whose tasks are all due later has no summary scheduled at all.
How people postpone one, in My Activities (to-do tray 🕒 → “View all activities”; it opens on what
is due today or overdue). Each row is one line of icons (the text is the tooltip): Done, Cancel and
a bell, the ems_activity_snooze view widget (static/src/js/backend/activity_snooze.js), in place
of Odoo’s “Snooze 7d”. The bell opens a popover with three choices, 1, 3 and 7 days, each showing
the date the task would move to. The web client repeats neither the days nor the rule: it asks the server (mail.activity.ems_snooze_choices(), which returns the days and, for a single task, the resulting date). The
list’s header has one “Snooze” (action_ems_snooze_dialog) that opens the same choices for the
selected tasks, as a client action with target: 'new' (Odoo shows it in a dialog and reloads the
list once it closes; the header only takes buttons, not widgets). Views:
views/shared/mail_activity/list.xml.
Both call mail.activity.action_ems_snooze(days) (models/shared/mail_activity.py), which only
accepts 1, 3 or 7 and moves the due date to the later of (today, due date) + days. Odoo’s own
action_snooze is overridden the same way (7 days), in case anything else calls it. Today is the
company’s, read from the same clock as the summary’s task domain (ems.datetime_utils.utc_to_local_date(fields.Datetime.now())): Odoo’s own action_snooze uses the server’s UTC
date, a day behind just after local midnight. Permissions are Odoo’s: only whoever can write the
activity (its owner, or someone with write access to its record) can snooze it. Editing the due
date in the record’s chatter works the same way.
Tasks EMS creates are due today, so they reach the first summary after they appear and their
owner decides whether to postpone them: the attendance correction request for its approver, the
admins’ “Automatic check-in/check-out failed”, and Odoo’s own absence approval (hr.leave’s
activity_update dates it 15 days before the absence; EMS moves new ones to today). The one
deliberate exception is the employee’s “upload the supporting document” step of an absence, due
the day after the absence ends, when it can be uploaded. A task someone assigns by hand keeps the
due date they chose (Odoo’s to-do type suggests 5 days).
res.users._ems_daily_summary_content() builds the subject and body in the recipient’s language
(also used by the user manual’s screenshot); _ems_send_daily_summary() sends it with
message_notify() on the user’s own partner, authored by OdooBot, with the light layout
(mail.mail_notification_light). Being a notification, it honours the user’s
notification_type: an email, or a message in their EMS inbox. It belongs to no record’s
chatter and does not make anybody a follower.
ems.daily_summary_body (translated through the .po files, like
any view), with only the sections that have something:
/mail/view (Odoo’s own access-checked redirect), its summary and due date, an
overdue mark, at most 20 per type then “and N more”./mail/view.tutor_notified = True and their day’s
ems.attendance_issue_tutor.summary_message_id points at the message (the “Daily issues”
screen shows Pending/Sent/Failed from it); the notices get sent_date.migrations/18.0.0.44.0/pre-migrate.py:
ems_digest_moment/ems_digest_time from the tutor report’s old preference
(ems_attendance_report_moment/_time). The old default, teacher_end, can’t be told apart from
a deliberate choice, so it becomes the new default (teacher_start); any other value is kept.The old ems_task_digest switch is gone: the summary always arrives when it has something, and
the user decides the channel with notification_type.
| Who | What |
|---|---|
| Every internal user | Receives their own summary; reads and changes their own ems_digest_moment, ems_digest_time and notification_type from My Profile. |
Administrators (base.group_system) |
Change anyone’s from the user form; read ems.info_notice. |
| Portal users, OdooBot, archived users | Never get a summary; no notice is queued for them. |
The summary reads tasks, issues and notices with sudo(), but every link goes through
/mail/view (or the student’s form), which applies the recipient’s own access rights when opened.