$ 160.33
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Sign (sign)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1052 |
| Technical Name |
template_sign_approval_omax |
| License | OPL-1 |
| Website | https://www.omaxinformatics.com |
| Versions | 13.0 14.0 15.0 16.0 17.0 18.0 19.0 |
Signature Approval Flow
OMAX INFORMATICS
Overview
This app streamlines departmental workflows by automating the sequential approval and signing process. It allows to define specific approval chains within departments, ensuring documents are handled by the right people in the right order.
By auto-filling signer information and enforcing strict priority logic, this module eliminates manual field placement and prevents unauthorized signing, making your document approval process secure and efficient.
Features
- Configure Department-based approvers with custom titles and sequences.
- Sequential Signing: Automated mail notifications sent based on user priority.
- Auto-Set: Automatically set predefined fields in the document for the all department signers.
- Auto-Fill: Automatically populates signature, initials, name, email, phone, and company from user profiles, along with the current date.
- Rejection Management: Ability to reject documents with a mandatory reason, instantly halting the process.
- Collaborative Feedback: Integrated comment system with automated mail alerts for all parties.
- Unique Audit Trail: Generates unique document numbers and tracks creator for better accountability.
- Priority Enforcement: Built-in alerts prevent users from signing out of their designated turn.
How It Works
1. Department & Approver Setup
Configure Approval Workflow
Define departments under Configuration > Departments. Assign specific users as approvers, set their Priority (approval order), and define their field titles as name. These users will be responsible for signing documents in the sequence defined here.
Here need to select the person in Assign to according to that the default name is added which can be change.
When we add partners in department related role is added with that partner in Configuration > Roles.
2. Document Upload & Routing
Select Department for Approval
When uploading a document, select the relevant department from the dropdown. The system automatically injects predefined fields (Signature, Name, Email, etc.) for all designated approvers within that department. If department is not selected then default without priority flow executes.
Setting the fields as predefined.
Now we upload document for signature with selected department with user Mark Demo.
3. Sequential Email Notification
Priority-Based Alerts
Once sent, the system verifies the Priority. Only the first priority user receives the initial email notification. Subsequent users are notified only after the previous person has signed.
4. Signature Process
Automatic Data Population
Approvers can click Sign Document. If it's their turn, the system auto-fills fields like Signature, Name, Phone, and Company based on their profile. If they try to sign out of turn or if the doc is rejected, they receive an instant alert.
5. Complete Approval Flow
Sequential Signing Process
This flow demonstrates the complete approval cycle.
The process follows priority:
Joel Willis → Adam Page → John Doe.
Each user receives the email only after the previous signer completes their action,
ensuring a controlled approval chain.
Step-by-Step Signing Flow
When document is sent the Joel Willis get email.
Joel Willis signing the document.
After Validate the email notification is sent to Adam Page.
Now before Adam sign if John Doe try to sign then he get this alert.
Adam Page signing the document.
After Validate the email notification is sent to John Doe.
John Doe signing the document.
Now the document is fully signed.
Note: Fully signed mail to document sender and all the signers are sent as default.
6. Comment & Discussion Flow
Collaborative Feedback
Comments allow approvers to share feedback without interrupting the approval flow.
All participants are notified instantly when a comment is added.
In this example same document is sent to same persons.
Adding Comment
Here we will add the comment by Joel Willis.
Comment is added which is visible for all signers as we see with Adam Page login in this example.
Comment Notification Email
All relevant users receive an email notification when a comment is added.
7. Rejection Flow
Rejection Process
If any approver rejects the document, the process stops immediately.
A rejection reason is mandatory, and no further signing is allowed.
Fully signed documents cannot be rejected. Individuals cannot reject their own signed document.
Reject Document
The user must provide a reason before rejecting the document.
Rejected person and reason of reject is visible in right side. If any signer try to sign the rejected document then they got alert. Here we try to sign by Adam Page.
Rejection Email
Once rejected, all relevant users are notified via email.
8. Tracking & Communications
Backend Visibility
Every document is assigned a Unique Number and tracks the creator. Monitor all approval activities through the Documents Kanban and List views.
Release 15.0.1.0
- Module base functionality established.
Free Support
Recommended & Suggested Apps
Get In Touch
OMAX INFORMATICS
| Our Odoo Services |
|
|
|
|
|
|
|
|
|
|
| For support, query and question contact us. |
|
|
|
Thank you for visiting
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module