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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Brian McMaster <brian@mcmpest.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.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-fieldservice-stage-validation 12.0.0.2.0
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 |
|---|---|---|---|---|
| odoo12_addon_fieldservice_stage_validation-12.0.0.2.0-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_fieldservice_stage_validation-12.0.0.2.0-py3-none-any.whl |
Release files / odoo12_addon_fieldservice_stage_validation-12.0.0.2.0-py3-none-any.whl
| Download URL | odoo12_addon_fieldservice_stage_validation-12.0.0.2.0-py3-none-any.whl |
|---|---|
| Size | 33.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cc684c54459cf0f50009f05002a8a4d5de5fc4a8e3dd2b5fc2ed328f7a199fe
|
|
BLAKE2b-256 checksum How to use checksums |
99ba37a75bb9a4655349db5b7a8ec399fd86e4dab0161097827f9e93946a1fe9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo12-addon-fieldservice-stage-validation 12.0.0.2.0
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.
