NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IMP] sign: add content to top-level TOC page + improve structure

Browse Source 
This commit is part of a larger work to improve the documentation's
structure. The toctree structure used to add levels to create categories
and make the structure visually more understandable.
With the new version of the documentation, plenty of these categories
are now redundant.

This commit improves the structure of the "Sign" app:

- it removes a useless "overview" category
- it adds a brief explanation at the "app" level, including links to
  relevant docs

task-2535899
This commit is contained in:
Jonathan Castillo 2021-05-20 15:39:25 +02:00 committed by Antoine Vandevenne (anv)
parent 1f9cd600cc
commit 7f3b2a1edd
4 changed files with 71 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

71
content/applications/finance/sign.rst
View File

@ -1,8 +1,73 @@
:show-content:
====
Sign
====
.. toctree::
:titlesonly:
**Odoo Sign** allows you to send, sign and approve documents online.
sign/overview
You can upload any PDF file and add drag-and-dropping fields on it. These fields are automatically
filled out with the user's detail if they are logged in.
.. seealso::
- `Odoo Sign: product page <https://www.odoo.com/app/sign>`_
Validity of electronic signatures
=================================
The legal validity of electronic signatures generated by Odoo depends on the legislation of your
country. Companies doing business abroad should consider electronic signature laws of other
countries as well.
In the European Union
---------------------
The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ establishes the framework for
electronic signatures in all `27 member states of the European Union
<https://europa.eu/european-union/about-eu/countries_en>`_.
It distinguishes three types of electronic signatures:
#. Electronic signatures
#. Advanced electronic signatures
#. Qualified electronic signatures
Odoo generates the first type, regular electronic signatures, and these signatures can produce legal
effects in the EU, as the regulation states that “an electronic signature shall not be denied legal
effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an
electronic form or that it does not meet the requirements for qualified electronic signatures.”
Note that electronic signatures may not be automatically recognized as valid. You may need to bring
supporting evidence of a signature’s validity.
In the United States of America
-------------------------------
The `ESIGN Act (Electronic Signatures in Global and National Commerce Act)
<https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the interstate and
international levels, and the `UETA (Uniform Electronic Transactions Act)
<https://www.uniformlaws.org/committees/community-home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_,
at the state level, provide the legal framework for electronic signatures. Note that `Illinois
<https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York
<https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not adopted the UETA, but
similar acts instead.
Overall, to be recognized as valid, electronic signatures have to meet five criteria:
#. A signer must show a clear intent to sign. For example, using a mouse to draw a signature can
show intent. The signer must also have the option to opt-out of electronically signing a
document.
#. A signer must first express or imply their consent to conduct business electronically.
#. The signature must be clearly attributed. In Odoo, metadata, such as the signer’s IP address, is
added to the signature, which can be used as supporting evidence.
#. The signature must be associated with the document being signed, for example, by keeping a record
detailing how the signature was captured.
#. Electronically signed documents need to be retained and available for later reference by all
parties involved, for example, by providing the signer either a fully-executed copy or the option
to download a copy.
.. note::
The information provided here does not constitute legal advice; it is provided for general
informational purposes only. As laws governing electronic signatures evolve rapidly, we cannot
guarantee that the information is up to date. We advise you to should contact a local attorney to
obtain legal advice.

8
content/applications/finance/sign/overview.rst
View File

@ -1,8 +0,0 @@
========
Overview
========
.. toctree::
:titlesonly:
overview/signature_validity

60
content/applications/finance/sign/overview/signature_validity.rst
View File

@ -1,60 +0,0 @@
=================================
Validity of electronic signatures
=================================
The legal validity of electronic signatures generated by Odoo depends on the legislation of your
country. Companies doing business abroad should consider electronic signature laws of other
countries as well.
In the European Union
=====================
The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ establishes the framework for
electronic signatures in all `27 member states of the European Union
<https://europa.eu/european-union/about-eu/countries_en>`_.
It distinguishes three types of electronic signatures:
#. Electronic signatures
#. Advanced electronic signatures
#. Qualified electronic signatures
Odoo generates the first type, regular electronic signatures, and these signatures can produce legal
effects in the EU, as the regulation states that “an electronic signature shall not be denied legal
effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an
electronic form or that it does not meet the requirements for qualified electronic signatures.”
Note that electronic signatures may not be automatically recognized as valid. You may need to bring
supporting evidence of a signature’s validity.
In the United States of America
===============================
The `ESIGN Act (Electronic Signatures in Global and National Commerce Act)
<https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the interstate and
international levels, and the `UETA (Uniform Electronic Transactions Act)
<https://www.uniformlaws.org/committees/community-home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_,
at the state level, provide the legal framework for electronic signatures. Note that `Illinois
<https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York
<https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not adopted the UETA, but
similar acts instead.
Overall, to be recognized as valid, electronic signatures have to meet five criteria:
#. A signer must show a clear intent to sign. For example, using a mouse to draw a signature can
show intent. The signer must also have the option to opt-out of electronically signing a
document.
#. A signer must first express or imply their consent to conduct business electronically.
#. The signature must be clearly attributed. In Odoo, metadata, such as the signer’s IP address, is
added to the signature, which can be used as supporting evidence.
#. The signature must be associated with the document being signed, for example, by keeping a record
detailing how the signature was captured.
#. Electronically signed documents need to be retained and available for later reference by all
parties involved, for example, by providing the signer either a fully-executed copy or the option
to download a copy.
.. note::
The information provided here does not constitute legal advice; it is provided for general
informational purposes only. As laws governing electronic signatures evolve rapidly, we cannot
guarantee that the information is up to date. We advise you to should contact a local attorney to
obtain legal advice.

4
redirects.txt
View File

@ -187,4 +187,6 @@ discuss/overview.rst applications/productivity/discuss/overview/get_started.rst
crm/optimize/onsip.rst applications/general/voip/onsip.rst # crm/optimize/* --> general/voip/*
crm/optimize/setup.rst applications/general/voip/asterisk.rst # crm/optimize/setup --> general/voip/asterisk
general/odoo_basics/add_user.rst applications/general/odoo_basics/users.rst # add_user --> users
general/odoo_basics/add_user.rst applications/general/odoo_basics/users.rst # add_user --> users
applications/finance/sign/overview/signature_validity.rst applications/finance/sign.rst #sign/overview/signature_validity -> sign/*