- Do not copy the contextual action nor the submitter role with a
template: a copy sharing the action would rewrite or delete the
original's.
- Make the template ID read-only once fetched from Docuseal: another
Docuseal template needs a new entry.
- Report an invalid API URL or token, an unexpected (non-JSON) response
and a connection dropped mid-response as a readable UserError.
- Refuse to email a signature request to contacts without a valid email
address (email_normalize), before any call to Docuseal.
- Stop logging the field values and the Docuseal response, which hold
personal data and the signing links.
- Prevent adding mapping lines by hand: they come from Docuseal only.
Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
- Reserve the generated "Request signature" action to administrators
(base.group_system), who are the only ones able to read the Docuseal
templates, instead of letting other users hit an AccessError.
- Request the signature of a single contact from the contextual action
(_action_request_signature): with several contacts, a failure could
leave some of them already emailed while the action reports an error.
A notification confirms the request.
- Share the Docuseal API call in _docuseal_request: a missing token or a
Docuseal error (with the explanation it sends) now raises a readable
UserError when sending submissions too, not only when fetching.
Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
The submitter role was a free text field. It is now a dropdown listing
only the submitter roles of the Docuseal template
(docuseal.template.role), fetched with the Docuseal UUID of each role.
- The "Fetch from Docuseal" button, now above the role, syncs the roles
(matched by UUID then name, in the Docuseal order, the first one
selected by default) and the fields of the selected role only,
keeping the existing mappings.
- Changing the role fetches the fields of the new role from Docuseal
with an empty mapping, and warns that saving loses the current one.
- Signature requests only send the fields of the submitter role.
- Docuseal API errors and a missing token raise a clear UserError.
- Keep the Docuseal field name of new mapping lines on save
(force_save on the read-only column).
Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Cover with a mocked Docuseal API (shared ``DocusealApiMockMixin``
capturing every request):
- field value conversion matrix in ``_create_submissions``: char,
selection label, many2one/many2many display names, date formatting,
empty value left editable while set values are locked
- payload structure and one-submission-per-partner behavior
- draft submissions created with ``send_email`` disabled
- API URL trailing slash stripped
- server action creation is idempotent
Assisted-By: GLM-5.3-Flash
- Deleting a ``docuseal.template`` now removes its generated contextual
server action; an orphaned action would browse a deleted template at
runtime and crash.
- The display notification strings are wrapped in ``_()`` so they are
translatable, with their French translations in the catalog.
- Add a short manifest description so the Apps page renders plain text
instead of parsing the markdown README as reStructuredText.
Covered by a unit test on the template deletion lifecycle.
Assisted-By: GLM-5.3-Flash
Fields are now ordered as returned by the Docuseal API: a sequence
field (reorderable with drag & drop) is written by
``action_fetch_fields`` according to the API field order, so deleting
a mapping line and re-fetching restores the original order instead of
appending it at the end.
Also refresh the French catalog (new Sequence field, new help texts,
stale smart_search entries dropped).
Covered by a unit test reproducing the delete-then-refetch scenario.
Assisted-By: GLM-5.3-Flash
``action_fetch_fields`` wiped the whole ``field_ids`` mapping on every
fetch, dropping the res.partner fields configured by the administrator.
Reconcile instead: keep existing mappings untouched, add fields new to
the Docuseal template and drop the ones removed from it.
Covered by unit tests running against a mocked Docuseal API.
Assisted-By: GLM-5.3-Flash
Add the module README documenting purpose, features (template
registry, field mapping, contextual server action, settings) and
installation requirements.
Remove ``res.partner#request_docuseal_signature``, which was introduced
as a public entry point for other code but was never called: the
generated server action calls ``docuseal.template._create_submissions``
directly. The template method is now the single entry point for
signature requests.
Assisted-By: GLM-5.3-Flash
Pre-filled values were converted with str(), so a Many2one such as the
partner title was sent as "res.partner.title(5,)" and a selection field
as its technical key. Send the display name of relational fields and the
label of selection fields instead.
Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
_create_submissions gets a send_email parameter (default True, so the
"Request signature" contextual action is unchanged), passed to the Docuseal
API. It now returns the Docuseal response of each created submission
(submitter id, slug, submission_id...) so callers can build a link to it.
New _create_draft_submissions helper: creates pre-filled submissions with
send_email=False, to be reviewed then sent for signature from Docuseal.
Also adds help texts on template_id and submitter_role.
Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>