Fieldservice Availability
This module defines blackout days (non-operational days), stress days (high-demand periods), and delivery time ranges for field service operations. It provides the necessary models to store this information, which can be used by other modules to manage scheduling, availability, and workload adjustments.
Blackout Days (`fsm.blackout.day`): Represent dates when field service operations are unavailable (e.g., holidays, company-wide closures).
Blackout Groups (`fsm.blackout.group`): Represent groups of days when field service operations are unavailable (e.g., holidays, company-wide closures).
Stress Days (`fsm.stress.day`): Indicate dates with increased service demand (e.g., peak business periods requiring additional workforce).
Delivery Time Ranges (`fsm.delivery.time.range`): Define available time slots for scheduling field service operations.
Restricts blackout days for Scheduled Start (ETA) orders with the same date
This module validates Scheduled Start (ETA) dates on field service orders against blackout days configured on their route. Orders with an ETA that falls on a matching blackout day cannot be saved.
Table of contents
Usage
Navigate to Field Service > Configuration > Availability. Once there, you can select Delivery Time Ranges, Blackout Days, Blackout Groups or Stress Days to create new records.
Steps to restrict blackout days for Scheduled Start (ETA) orders with the same date
Set up Blackout Days on Configuration > Blackout Groups and create or edit one with blackout days
Go to Field Service > Master Data > Routes > Create or edit route and assign Blackout Group Days and a Person
Create a Field Service order and set up Scheduled Start (ETA) with date that you put on blackout days and the Odoo will throw an error
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
Contributors
-
Patryk Pyczko <ppyczko@apsl.net>
Antoni Marroig <amarroig@apsl.net>
Bernat Obrador <bobrador@apsl.net>
-
Linto Antony <l.antony@cit-services.eu>
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 maintainer:
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-fieldservice-availability 19.0.1.0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_fieldservice_availability-19.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_fieldservice_availability-19.0.1.0.0.4-py3-none-any.whl |
Release files / odoo_addon_fieldservice_availability-19.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_fieldservice_availability-19.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 51.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9320b02b8e3caa1b4aa5ad7b5e3d9684ab4dc39b7abc60bd7dad23e51e11399
|
|
BLAKE2b-256 checksum How to use checksums |
3e9551f9ad45d48c59357b5b6198d7ca31936920a079da683dd756482cc35a6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-fieldservice-availability 19.0.1.0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
