[RFC] website_sale_contract: Contract Signing

[lasley]

This module will inject a Contract Signing step in the e-commerce process, immediately before payment. The user will skip this stage if there is not a product in their cart set to is_contract, similar to how we do for prescriptions in medical. It will depend on product_contract and website_portal_contract.

In order to support contract signatures, a Binary field signature will be added to account.analytic.account along with a signatory char field to indicate who signed it.

During this stage, the first unsigned contract in the user's cart will be displayed (using the website_template_id provided in website_portal_contract). Below that, a freeform field will be provided to type the signatory name, as well as a jSignature for the actual signing.

Clicking Accept will continue either loop the above operation for the next unsigned contract in the cart, or proceed to payment.

The gotcha here is that the contract hasn't actually been created until after the sale is completed, which is after payment during e-commerce. This means that we will need to temporarily store the signature information, then assign it correctly during the action_done when the contract is actually created.

This module will also add the signer's information into the contract's detailed view in the website portal (provided in website_portal_contract), as well as show it in the backend for employees viewing the contract through the standard form view.

Anyone see something I'm missing, or a better way to go about this?

[pedrobaeza]

👍 for me

[lasley]

Closing to track in #88