Skip to Content
Menu

Approval Workflow

by
Odoo

456.44

v 16.0 Third Party 6
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 20970
Technical Name x2_approval_workflow
LicenseOPL-1
Versions 13.0 14.0 15.0 16.0 17.0 18.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 20970
Technical Name x2_approval_workflow
LicenseOPL-1
Versions 13.0 14.0 15.0 16.0 17.0 18.0

Approval Workflow Process

This module is a generic approval module for Odoo, designed to support user-defined approval workflows.

It can be applied to a wide range of approval processes that you need to incorporate into your system, such as Quotations approvals, Contract approvals, HR leave approvals, and any other modules requiring an approval process.

The module allows users to either define their own approvers or assign approvers based on the organizational structure within the system, such as the initiator's leader or department head. This ensures the approval process is flexible and adaptable to fit various organizational requirements.

User Manual And Function Introduction

1、Define Approval Model

2、Define Approval Workflow

Click the button to enter the workflow design interface.

1、☑ Define the workflow by dragging and dropping nodes from the left panel; what you see is what you get (WYSIWYG)

We also support branching approval workflows based on different conditions within the process. For example, different approval branches can be triggered depending on the type of leave requested

2、☑ Set the details for each node, such as HOD (Head of Department).

Manager: Automatically selects the direct manager of the person initiating the approval request, as defined in the Employee module.
HOD (Head of Department): Assigns the department's head (Head of Department) as the approver for requests initiated by members of that department.
Designated User: Allows the selection of a specific user from the system to serve as the approver, providing flexibility for custom workflows.
System Role: Utilizes predefined roles within the system to designate approvers, enabling any user with the specified role to perform the approval
Record Field: Determines the approver based on a user field within the approval record itself, such as assigning the salesperson related to the record as the approver. This ties the approval directly to the context of the record.

3、Initiate Approval Process

Based on the configurations mentioned above, we have removed the previous buttons but retained the Preview button.

Click the button to submit for approval.

Click the button to view the approval process and details.

Approvers can receive approval notifications via the system's Systray Menu (without needing to refresh the page) or through Email.

Once all approvers have approved, the system automatically calls the user-configured method to update the status to Sales Order.

4、Others

Approval Setting

Disable Withdraw:
Anytime: Withdrawal is not allowed at any point.
In Review: Withdrawal is not allowed once someone has started the approval process.

Email Notifications
Support for Sending Approval Status Emails, Including Arrival Notifications to Approvers, Approval or Rejection Notifications to Submitters, and Completion Notifications to Submitters

Require Reasons
Support for Four Types of Reason Entry: Submission, Approve, Refuse, and Withdrawal. Reasons are required only if configured; it is recommended to require reasons during rejection.

Approval Model List
We have automatically added an Approval Status column to the list view of the approval models, and this column supports quick search functionality.

Workflow Setting

Pass Rate:
When multiple approvers are assigned to the same node, this setting determines the minimum proportion of approvers that must approve for the node to be completed. For example, setting it to 1 requires all approvers to approve before the node is completed. If set to 0.7, then at least 70% of the approvers (e.g., 2 out of 3) must approve for the node to be completed.

Branching in Approval Workflows
Supporting the Approval Process with Branching Conditions

Transfer and Additional Sign-off
The system supports Additional Sign-off and Transfer operations, allowing approvers to add new approvers or delegate their approval responsibility during the approval process. If a node is configured to allow these operations, approvers can perform them when reviewing an approval request.

You can learn how it works by visiting the following address

ADDRESS: https://demo.x2soft.cn

User Password Description
ap_manager a Approval Process Designer/Administrator
ap_user1 a
ap_user2 a

Our Recommended Modules


Direct Print Report

Edit Button In Form

Attachment Preview

Tree View Freeze Header Columns

Form Viewing

Should you have any questions or other specific customization requirements, don't hesitate to reach out to me

Mail: yuze@x2soft.cn   Skype: live:5888101

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.