Field Service Recurring Agreement
Adds the ability to link recurring field service tasks to agreements. This allows associating agreements with recurring tasks and automatically sets the agreement on generated sales orders.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Link recurring field service tasks to an agreement so that sales orders generated from those recurring tasks automatically carry the same agreement.
This module connects recurring field service work with agreements. On a recurring field service record you get a new "Agreement" field, shown on the recurring task form right after the equipment list. You pick the agreement there once, and it is remembered on that recurring task.
When the recurring task creates a sales order, the agreement you selected is copied onto that order automatically. In the same way, when a sales order line creates a recurring field service task, the agreement already set on the sales order is copied onto the new recurring task. So the agreement stays consistent in both directions between the recurring task and its sales order.
- Adds an Agreement field on
fsm.recurring. - Shows that field on the recurring task form.
- Copies the agreement onto generated sales orders.
- Copies the sales order agreement onto newly created recurring tasks.
It touches the recurring field service model fsm.recurring and sales order lines (sale.order.line), and relies on the agreement, field service and recurring sales modules. No new menus, reports, checks or scheduled jobs are added by this code.
Models and fields (1)
- fsm.recurring · extends an existing modelagreement_id (Agreement)
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/field-service.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.