diff --git a/sign_oca/README.rst b/sign_oca/README.rst index 995666b8..969d5ce9 100644 --- a/sign_oca/README.rst +++ b/sign_oca/README.rst @@ -7,7 +7,7 @@ Sign Oca !! This file is generated by oca-gen-addon-readme !! !! changes will be overwritten. !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - !! source digest: sha256:42a5e3d7fee8a597c68a320cee2c54d6825c2a5f5434c0e638604937bf41cbc6 + !! source digest: sha256:6f2bbf4d5809509b940a5870c5ca38a80bb83d58624e815a74c46b309030a0ac !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! .. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png @@ -35,6 +35,31 @@ This module allows to create documents for signature inside Odoo using OWL. .. contents:: :local: +Configuration +============= + +There is a wizard (sign.oca.template.generate.multi) that can be used for any model needed, an example would be `maintenance_sign_oca`. + +It would be necessary to set an action linked to the model with the code: + +.. code-block:: xml + + model.action_sign_oca_template_generate_multi() + +and code method: + +.. code-block:: python + + def action_sign_oca_template_generate_multi(self): + action = self.env.ref("sign_oca.sign_oca_template_generate_multi_act_window") + result = action.read()[0] + ctx = dict(self.env.context) + ctx.update({"default_model": self._name}) + result["context"] = ctx + return result + +this would allow to create `sign.request` records for the selected records (in a tree view for example). + Usage ===== @@ -49,12 +74,34 @@ Creation of templates * Click on the field in order to delete or edit some configuration of it * The template is autosaved -Sign a document -~~~~~~~~~~~~~~~ +Sign role +~~~~~~~~~~ + +* Access `Sign / Settings / Roles` +* Create a new role (Equipment employee for example) +* You can set the Partner type you need (empty, default or expression). +* With the expression option you can set: ${object.field_name.id} +* If you create a sign request from template signer will be auto-create according to roles + + +Sign a document from template +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Access `Sign / Templates` * Press the `Sign` button from a template * Fill all the possible partners that will sign the document +* You can link the template to a model (maintenance.equipment for example) +* The signature action will be opened. +* There, you can fill all the data you need. +* Once you finish, press the sign button on the top +* When the last signer signs it, the final file will be generated as a PDF + + +Sign a pending document +~~~~~~~~~~~~~~~~~~~~~~~ + +* Go to the pencil icon in the upper right corner (systray) of the sign request to access the pending signatures. +* Press the `Sign` button from signer request * The signature action will be opened. * There, you can fill all the data you need. * Once you finish, press the sign button on the top @@ -93,6 +140,11 @@ Contributors * Enric Tobella (www.dixmit.com) + +* `Tecnativa `_: + + * Víctor Martínez + Maintainers ~~~~~~~~~~~ diff --git a/sign_oca/readme/CONFIGURE.rst b/sign_oca/readme/CONFIGURE.rst new file mode 100644 index 00000000..ce75cd5f --- /dev/null +++ b/sign_oca/readme/CONFIGURE.rst @@ -0,0 +1,21 @@ +There is a wizard (sign.oca.template.generate.multi) that can be used for any model needed, an example would be `maintenance_sign_oca`. + +It would be necessary to set an action linked to the model with the code: + +.. code-block:: xml + + model.action_sign_oca_template_generate_multi() + +and code method: + +.. code-block:: python + + def action_sign_oca_template_generate_multi(self): + action = self.env.ref("sign_oca.sign_oca_template_generate_multi_act_window") + result = action.read()[0] + ctx = dict(self.env.context) + ctx.update({"default_model": self._name}) + result["context"] = ctx + return result + +this would allow to create `sign.request` records for the selected records (in a tree view for example). diff --git a/sign_oca/readme/CONTRIBUTORS.rst b/sign_oca/readme/CONTRIBUTORS.rst index c0465388..f9748b2e 100644 --- a/sign_oca/readme/CONTRIBUTORS.rst +++ b/sign_oca/readme/CONTRIBUTORS.rst @@ -1 +1,6 @@ * Enric Tobella (www.dixmit.com) + + +* `Tecnativa `_: + + * Víctor Martínez diff --git a/sign_oca/readme/USAGE.rst b/sign_oca/readme/USAGE.rst index 688783b1..9dfb82fa 100644 --- a/sign_oca/readme/USAGE.rst +++ b/sign_oca/readme/USAGE.rst @@ -9,12 +9,34 @@ Creation of templates * Click on the field in order to delete or edit some configuration of it * The template is autosaved -Sign a document -~~~~~~~~~~~~~~~ +Sign role +~~~~~~~~~~ + +* Access `Sign / Settings / Roles` +* Create a new role (Equipment employee for example) +* You can set the Partner type you need (empty, default or expression). +* With the expression option you can set: ${object.field_name.id} +* If you create a sign request from template signer will be auto-create according to roles + + +Sign a document from template +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Access `Sign / Templates` * Press the `Sign` button from a template * Fill all the possible partners that will sign the document +* You can link the template to a model (maintenance.equipment for example) +* The signature action will be opened. +* There, you can fill all the data you need. +* Once you finish, press the sign button on the top +* When the last signer signs it, the final file will be generated as a PDF + + +Sign a pending document +~~~~~~~~~~~~~~~~~~~~~~~ + +* Go to the pencil icon in the upper right corner (systray) of the sign request to access the pending signatures. +* Press the `Sign` button from signer request * The signature action will be opened. * There, you can fill all the data you need. * Once you finish, press the sign button on the top diff --git a/sign_oca/static/description/index.html b/sign_oca/static/description/index.html index 0913a1fa..2ed88892 100644 --- a/sign_oca/static/description/index.html +++ b/sign_oca/static/description/index.html @@ -366,35 +366,57 @@

Sign Oca

!! This file is generated by oca-gen-addon-readme !! !! changes will be overwritten. !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -!! source digest: sha256:42a5e3d7fee8a597c68a320cee2c54d6825c2a5f5434c0e638604937bf41cbc6 +!! source digest: sha256:6f2bbf4d5809509b940a5870c5ca38a80bb83d58624e815a74c46b309030a0ac !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->

Beta License: AGPL-3 OCA/sign Translate me on Weblate Try me on Runboat

This module allows to create documents for signature inside Odoo using OWL.

Table of contents

+
+

Configuration

+

There is a wizard (sign.oca.template.generate.multi) that can be used for any model needed, an example would be maintenance_sign_oca.

+

It would be necessary to set an action linked to the model with the code:

+
+model.action_sign_oca_template_generate_multi()
+
+

and code method:

+
+def action_sign_oca_template_generate_multi(self):
+  action = self.env.ref("sign_oca.sign_oca_template_generate_multi_act_window")
+  result = action.read()[0]
+  ctx = dict(self.env.context)
+  ctx.update({"default_model": self._name})
+  result["context"] = ctx
+  return result
+
+

this would allow to create sign.request records for the selected records (in a tree view for example).

+
-

Usage

+

Usage

-

Creation of templates

+

Creation of templates

  • Access Sign / Templates
  • Create a new template
  • @@ -405,12 +427,34 @@

    Creation of templates

  • The template is autosaved
-
-

Sign a document

+
+

Sign role

+
    +
  • Access Sign / Settings / Roles
  • +
  • Create a new role (Equipment employee for example)
  • +
  • You can set the Partner type you need (empty, default or expression).
  • +
  • With the expression option you can set: ${object.field_name.id}
  • +
  • If you create a sign request from template signer will be auto-create according to roles
  • +
+
+
+

Sign a document from template

  • Access Sign / Templates
  • Press the Sign button from a template
  • Fill all the possible partners that will sign the document
  • +
  • You can link the template to a model (maintenance.equipment for example)
  • +
  • The signature action will be opened.
  • +
  • There, you can fill all the data you need.
  • +
  • Once you finish, press the sign button on the top
  • +
  • When the last signer signs it, the final file will be generated as a PDF
  • +
+
+
+

Sign a pending document

+
    +
  • Go to the pencil icon in the upper right corner (systray) of the sign request to access the pending signatures.
  • +
  • Press the Sign button from signer request
  • The signature action will be opened.
  • There, you can fill all the data you need.
  • Once you finish, press the sign button on the top
  • @@ -419,9 +463,9 @@

    Sign a document

-

Known issues / Roadmap

+

Known issues / Roadmap

-

Tasks

+

Tasks

  • Ensure that the signature is inalterable. Maybe we might need to use some tools like endevise or pyHanko with a certificate. @@ -430,7 +474,7 @@

    Tasks

-

Bug Tracker

+

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 @@ -438,21 +482,25 @@

Bug Tracker

Do not contact contributors directly about support or help with technical issues.

-

Credits

+

Credits

-

Authors

+

Authors

  • Dixmit
-

Contributors

+

Contributors

  • Enric Tobella (www.dixmit.com)
  • +
  • Tecnativa:
      +
    • Víctor Martínez
    • +
    +
-

Maintainers

+

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose