fieldservice_recurring

Field Service Recurring Work Orders

This module allows you to manage your recurring field service work orders

Recurring settings are configured via the FSM Frequency model. Multiple FSM Frequency can be combined on a FSM Frequency Rule Set which enables highly configurable recurring rules calculated using the dateutil rrule python library.

Table of contents

• Installation
• Configuration
• Usage
• Known issues / Roadmap
• Bug Tracker
• Credits
  • Authors
  • Contributors
  • Other credits
  • Maintainers

Installation

To install Field Service and have the mapping features, you need to install GeoEngine.

Please refer to the installation instructions available at: https://github.com/OCA/geospatial/tree/12.0/base_geoengine

Configuration

To configure this module, you need to:

• Setup your Frequencies to establish recurring rules

1. In fieldservice app go to Menu > Configuration > Orders > Frequencies
2. Create a Frequency
3. Setup your Frequency by giving it a descriptive name, set your interval and the interval type. Use the additional settings to build a recurring rule based on python's dateutil rrule parameters.

• Setup your Frequency Rule Sets used to calculate recurring order dates

1. In fieldservice app go to Menu > Configuration > Orders > Frequency Rule Set
2. Create a Frequency Rule Set
3. Setup your Frequency Rule by first giving it a descriptive name. Complete the form by entering the number of days ahead this rule will schedule work.
4. Finally, choose which Frequencies this rule will use to compute the dates used for scheduling.

• Setup your recurring order templates to define standard recurring orders

1. In fieldservice app go to Menu > Configuration > Orders > Recurring Templates
2. Name the template and set fields to define which order template is repeated and what Frequency Rule Set will be used

Usage

To use this module, you need to:

• In fieldservice app go to Menu > Operations > Recurring Orders
• Create a new Recurring Order model
• Select a Recurring Template and modify as needed.
• Set other fields for fsm location, etc
• Confirm the recurrence to create first order
• Future orders will be created via cron task

Known issues / Roadmap

The roadmap of the Field Service application is documented on Github.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Brian McMaster
• Open Source Integrators

Contributors

• Brian McMaster <brian@mcmpest.com>
• Kitti Upariphutthiphone <kittiu@ecosoft.co.th>
• Raphaël Reverdy <raphael.reverdy@akretion.com>
• Freni Patel <fpatel@opensourceintegrators.com>
• APSL:
  • Antoni Marroig <amarroig@apsl.net>

Other credits

The development of this module has been financially supported by:

• Open Source Integrators <https://opensourceintegrators.com>

Maintainers

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.

Current maintainers:

This module is part of the OCA/field-service project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.