-
-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ADD] contract_digitized_signature #102
[ADD] contract_digitized_signature #102
Conversation
Hmmmm I wonder if we need to think about integration of this against #88, which also has signature. I'm curious though, what is the purpose of the signature field in the backend view? Is this instead for an employee to sign off on a contract completion? |
This module completes these others: The purpose is that commercial user with a tablet or similar, in customer home, shows him a document (project, sale, contract or picking) and he signs document. Company can now continue commercial flow. |
Customer signature is shown in printed document too. |
@rafaelbn give your last try. |
Runbot says By the way @cubells @pedrobaeza |
@lasley I could probs just add this module as a dependency for website_sale_contract. Most of the backend logic in website_sale_contract lies in the checkout wizard, so should not be an issue. @cubells would it be possible to add a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on runbot. Just two non blocking comments
|
||
This module is part of the OCA/web suite. | ||
|
||
Configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this section needed. It's the same instructions as in Usage
changes on it. | ||
#. You can clear signature in any moment by clicking on the **Clear** link | ||
located on the top right side of signature box. | ||
#. If you print Contract, signature was added to contact report . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you print the contract the signature will be shown in the contract report.
@BMW95 - if you can easily make our module compatible with this strategy, please do it. I'd rather not have a fractured ecosystem |
Please @cubells could you answer to #102 (comment). Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested functionaly in runbot 👍
@@ -12,6 +12,11 @@ class AccountAnalyticAccount(models.Model): | |||
customer_signature = fields.Binary( | |||
string='Customer acceptance', | |||
) | |||
signature_name = fields.Many2one( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO this should be a plain text field, possibly containing a capture of the name from the partner (not sure how your workflow works). Linking a signature to a dynamic record means that the actual data can change out from underneath the legal data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, you shouldn't modify contacts when there are changes, but deactivate them and create new ones. The problem with the plain text is that requires to fully type it. With this, you can select directly by direct search.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pedrobaeza - none of my customers do that, so while yeah it's the best option, it's still not a legal field.
An alternative would be to add a signatory_id
column that is the relation, with an onchange to update the signature_name
.
Furthermore- this creates an incompatibility with the way Odoo does it, which is the way we did it. The goal of adding this was to make our addons live in harmony. Adding this, but making it a relation, takes us further from that goal than simply not having the column
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also - to be a relation, it needs to be suffixed with _id
, which is not the case with signature_name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, let's change it to a char field. At the end, we don't have that requirement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cubells. One note, non-functional change
def create(self, values): | ||
contract = super(AccountAnalyticAccount, self).create(values) | ||
if contract.customer_signature: | ||
values = {'customer_signature': contract.customer_signature} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test for this please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lasley done!
Thanks @cubells |
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
* [ADD] contract_digitized_signature * Correct README and add signature_name * Change to char field * Improve tests to acchieve full coverage
New module that allows to add digitized signature to contracts and send by mail.
cc @Tecnativa
Related: #79