FSM Stage Validation
fieldservice_stage_validation
Validate input data when reaching a Field Service stage
FSM Stage Validation
As the stage of a field service document progresses, it may be important for specific fields of the document be completed.
For example, when a field service order enters the ‘Complete’ stage, the fields for ‘Actual End Date’ and/or ‘Resolution Notes’ should be set.
This module allows you to raise a Validation Error if the designated fields are not set when moving to a new stage. Since stages can be used for field service orders, workers, locations, or equipments, this logic is available to be applied to each document type.
Table of contents
Configuration
- Go to Field Service > Configuration > Stages
- Create or select a stage
- Select one or more fields to be validated
Usage
- Follow steps outlined in Configuration.
- User will receive validation error if a field is not set when attempting to move to a new stage.
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
Contributors
- Brian McMaster <brian@mcmpest.com>
- APSL:
- Antoni Marroig <amarroig@apsl.net>
- PyTech:
- Simone Rubino <simone.rubino@pytech.it>
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.
Ce que l'application ne fait pas
- The roadmap of the Field Service application is documented on Github .
Applications du magasin nécessaires
- Field Service
fieldservice
Modules Odoo Community utilisés
Aucun.
| Série | Version | État | Publiée le |
|---|---|---|---|
| 19.0 | 19.0.1.0.0 | En développement | 25/09/2026 |
Fiche générée depuis julien2364/omnifloo-oca-field-service (branche 19.0, commit 21946f6a27bb).
Contrôle automatique du magasin (distinct de l'éditeur), appliqué à toutes les applications. Conforme.
| Contrôle | Résultat | Effet si absent |
|---|---|---|
| Manifeste lisible sans exécution | conforme | bloquant |
| Licence reconnue (AGPL-3) | conforme | bloquant |
| Aucune dépendance vers Odoo Enterprise | conforme | bloquant |
| Aucun import de code Enterprise | conforme | bloquant |
| Aucun en-tête de licence Enterprise | conforme | bloquant |
| Icône static/description/icon.png | conforme | déclasse |
| Description (static/description/index.html ou README) | conforme | déclasse |
| Tests automatisés (tests/test_*.py) | conforme | déclasse |
| Traduction française (i18n/fr.po) | conforme | info |
| Section « Ce que le module ne fait pas » | conforme | info |
Avis des clients connectés. Un avis noté par client ; l'éditeur peut y répondre. Connectez-vous pour laisser un avis.
- Éditeur
- Odoo Community Association (OCA)
- Signaler un problème
- https://github.com/OCA/field-service
- Clients Omnifloo
- Support inclus selon votre formule : centre d'aide.