| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 402 |
| Technical Name |
ip_stale_record_reminder |
| License | LGPL-3 |
| Website | https://www.iplexsoft.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 402 |
| Technical Name |
ip_stale_record_reminder |
| License | LGPL-3 |
| Website | https://www.iplexsoft.com |
Universal Stale Record Reminder for Odoo
Automatically find inactive records and create follow-up activities for the right users. Use it for contacts, CRM leads, quotations, tasks, tickets, custom models, and any other activity-enabled Odoo record that should not be forgotten.
Prevent missed follow-ups
Old records often remain open without any user action. This app finds those records and creates clear To-Do activities so teams know what needs attention.
Works across Odoo
Configure rules for standard or custom models. Use the last update date or any stored date/datetime field to decide when a record becomes stale.
Controlled reminders
Choose recipients, activity type, deadline, repeat interval, and max records per run. The repeat interval avoids duplicate reminders for the same record and user.
How It Works
Create a rule
Select the model, inactivity days, optional domain, recipients, and activity details.
Run now or schedule
Run manually from the rule form or let the daily cron process active rules.
Activity is created
The selected users receive planned activities directly on the original record.
Review history
Every reminder is logged with the rule, record, user, company, and reminder date.
Screenshots
Main Features
- Configure reminders for any activity-enabled model.
- Use write date or a selected date/datetime field.
- Add optional Odoo domains for precise filtering.
- Assign activities to a responsible user field and fixed users.
- Configure activity type, summary, note, and deadline.
- Prevent repeated reminders using repeat interval days.
- Include archived records when needed.
- Limit records per run for controlled processing.
- Run manually or use the daily scheduler.
- Open the original record directly from reminder history.
Example Use Cases
- Contacts not updated for 30 days.
- CRM leads with no update for 3 days.
- Draft quotations pending for 5 days.
- Project tasks inactive for 2 days.
- Helpdesk tickets waiting too long.
- Custom approval, operations, or service records requiring follow-up.
Please log in to comment on this module