P
Patrick Weigert
Description of the Problem:
When sending documents and contracts via workflow automation using the "Send Document" action, the system currently applies only the globally configured default email template from the Documents & Contracts settings — regardless of which email template has been individually configured within the specific document/contract template settings.
Per-document notification templates that are configured directly inside each contract template are completely ignored by the workflow engine.
Why This Is a Problem:
We send multiple different contract types (e.g. Data Processing Agreement, Service Agreement, Framework Contract, Setup Contract, etc.). Each of these contracts requires its own individual, explanatory email to the client — with customized content that describes:
what type of contract this is
what the content covers
what the client is expected to do
A single global email template cannot fulfill this need. Clients receiving a document have no context about what they are signing, why they are receiving it, or what action is required from them.
Expected Behavior:
The "Send Document" workflow action should use the individually configured email template from the respective document/contract template — exactly as it already works when sending manually via the send modal.
Alternatively: The "Send Document" workflow action should include a dropdown to select a specific email template directly within the action step itself, allowing a different template to be chosen per workflow.
Priority / Impact:
This affects every user who automates the sending of multiple different contract types via workflows — which represents a large portion of professional users. This is fundamental functionality for professional client communication and should be treated as a high-priority improvement.