This release is a pre-release and may not be stable for production use.
Odoo and the Field Service App do not provide a way to track what is required and/or missing at the different stages of the FSM order process. Some organizations needs a way to track documentation, materials, signature and various activities.
This module allows you to have a list of sub-statuses and set them as default or potential sub-statuses on each FSM stage. The stage configuration will drive:
the sub-status set when entering a stage
the list of potential sub-statuses available depending on the stage
Table of contents
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/11.0/base_geoengine
Configuration
To configure this module, you need to:
Go to Field Service > Configuration > Orders > Sub-Statuses
Create your list of sub-statuses
Go to Field Service > Configuration > Orders > Stages
Select a stage and set the default sub-statuses as well as the potential sub-statuses
Usage
To use this module, you need to:
Go to Field Service > Operations > Orders
Create a new service order.
The sub-status is set to the default sub-status of the New stage.
The list of sub-statuses is filtered based on the potential sub-statuses of the New stage.
Move the service order in the process. The sub-status is set and filtered according to the 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
Contributors
Brian McMaster <brian@mcmpest.com>
Bhavesh Odedra <bodedra@opensourceintegrators.com>
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo11-addon-fieldservice-substatus 11.0.0.0.1.99.dev5
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 |
|---|---|---|---|---|
| odoo11_addon_fieldservice_substatus-11.0.0.0.1.99.dev5-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_fieldservice_substatus-11.0.0.0.1.99.dev5-py2.py3-none-any.whl |
Release files / odoo11_addon_fieldservice_substatus-11.0.0.0.1.99.dev5-py2.py3-none-any.whl
| Download URL | odoo11_addon_fieldservice_substatus-11.0.0.0.1.99.dev5-py2.py3-none-any.whl |
|---|---|
| Size | 35.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
6cd5cf8ebca3012c965fdeabfe458f4b6344d5ece5a82ea4971debce71183b97
|
|
BLAKE2b-256 checksum How to use checksums |
6c7fb5442f7177ab538fc577b5316ff734573ebe70cb104e6161c1bf13b76230
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo11-addon-fieldservice-substatus 11.0.0.0.1.99.dev5
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.
