This release is a pre-release and may not be stable for production use.
Field Service - Change Management
This module adds change logs to the Field Service Location. Change logs are used to track changes at a location. Example could be structural changes or configuration changes.
Table of contents
Installation
Either install the module from Apps or via the Field Service settings.
Configuration
Users with Change Log Manager access can configure via the Configuration Menu in the Change Log app. * Open the Change Logs app. * Go to Configuration menu. * Configure Stages, Tags, Types, and Impacts according to your needs.
Usage
To use this module, you need to:
Open a FSM Location
Click on ‘Change Log’ smart button
Create or view Change Logs
You can print change logs from the location, location list or change log list.
Users with Change Log Manager access will have access to all change logs via the menu on the main dashboard.
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
Patrick Wilson <patrickraymondwilson@gmail.com>
Other credits
The development of this module has been financially supported by:
Pavlov Media <https://pavlovmedia.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 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 odoo12-addon-fieldservice-change-management 12.0.1.1.0.99.dev37
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_change_management-12.0.1.1.0.99.dev37-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_fieldservice_change_management-12.0.1.1.0.99.dev37-py3-none-any.whl |
Release files / odoo12_addon_fieldservice_change_management-12.0.1.1.0.99.dev37-py3-none-any.whl
| Download URL | odoo12_addon_fieldservice_change_management-12.0.1.1.0.99.dev37-py3-none-any.whl |
|---|---|
| Size | 50.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e21c94b77481c10eb1518e6c691cafb5d8ec2b6c42ad606e64fc0f700609fca
|
|
BLAKE2b-256 checksum How to use checksums |
ec5b0ae0e6b0623fb58833008d9aaee4d1f00fe79ee2aaa3ee683f4106aa2d4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo12-addon-fieldservice-change-management 12.0.1.1.0.99.dev37
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.
