Field Service - Sign
This module adds configurable customer signing features on Field Service orders:
On-site signature capture — uses the native signature widget and the signature fields already provided by fieldservice (signature, signed_by, signed_on). Capture can be enabled or disabled per company, and optionally required before an order can be completed.
Document signing — integrates with sign_oca to launch a signature request for a document linked to the order, expose its status on the order, and optionally require a signed document before completion.
Both features are independent. An administrator can enable none, either one, or both from Field Service settings.
Table of contents
Configuration
Go to Field Service > Configuration > Settings and open the Signatures section:
Enable On-site Signature Capture to surface customer signature capture on orders. Optionally enable Require Signature to Complete.
Enable Document Signing to allow launching sign_oca requests from orders. Optionally enable Require Document Signed to Complete.
Select the FSM Order Sign Template used when requesting a document signature. The template model must be fsm.order.
Usage
On-site signature capture
Open a Field Service order.
When the order stage requires a signature, use Sign to capture the customer signature.
Complete the order. If the company requires a signature, completion is blocked until one is captured.
The signature is also printed on the Service Order report when capture is enabled.
Document signing
Open a Field Service order.
Click Request Signature to create and send a sign_oca request from the company template.
Follow the linked signature requests from the smart button or the Document Signing tab.
Complete the order. If the company requires a signed document, completion is blocked until at least one request is signed.
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
-
Maxime Chambreuil <maxime.chambreuil@graymatterlogic.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.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file odoo_addon_fieldservice_sign-19.0.1.0.0.4-py3-none-any.whl.
File metadata
- Download URL: odoo_addon_fieldservice_sign-19.0.1.0.0.4-py3-none-any.whl
- Upload date:
- Size: 48.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/6.2.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
544f41a349556e5e38f98d7d6035336426452e1ca52f31e1f1f0cb030d2e2671
|
|
| MD5 |
acf73e0534b20366d4f9e98f1aaae1f8
|
|
| BLAKE2b-256 |
a9a1d7058af339dc4ea25b5ef2c82bfde5effbfd754eecea99266019ca122c51
|
