Model Signature Base

Several modules need a signature drawn on screen. This technical module supplies one abstract model with a digitised signature field so that they do not each rebuild it. It has no menu of its own. Developers inherit it in company, invoice or order models, and end users then see the signature widget. It keeps signature handling uniform across the system.

1. 1

   Provide a signature field

   An abstract model defines a Signature binary field named digitized signature. It is stored as an image. It is designed to be reused, not used alone.

   • Field: digitized_signature
   • Stored as image
   • Abstract model
2. 2

   Inherit in a model

   A developer adds the mixin to a model through _inherit. The model then gets the field and can place it on its form. The company signature module does exactly this.

   • Use _inherit
   • Place field in view
   • Example: company signature
3. 3

   Draw the signature

   In the form the user sees a signature widget and draws or uploads the image. The image is saved with the record. It can be shown on printed documents.

   • Draw or upload
   • Saved with record
   • Printable
4. 4

   Keep signatures consistent

   Because all modules reuse one field definition, storage and display behave the same. Fixes in one place benefit every user. No data migration is needed between them.

   • One definition
   • Same display
   • Easy maintenance

Back to version applications