Approve Hub Management System for Purchase module

The “ApproveHub” Project is a custom Odoo application designed to streamline the Purchase Order approval process. It allows users to submit orders for approval, offers a structured approval workflow, handles rejections, sends email notifications, and seamlessly integrates with the existing Odoo system, enhancing efficiency and transparency in the purchase order approval process.

How to Install the module

To install the module you need to go on the Apps menu and remove the filter from the search bar and type the module name pragtech_approval after that it will be displayed the names of modules and click on the Activate button.

After installation, the name 'ApproveHub' will be displayed in the menu.

After installation, the ApproveHub user interface looks like

If the ApproveHub model is not configured for the selected model, then the submit button will not be displayed, and only the confirm order button will be shown (Model Name: ‘purchase order’)

In the "Model" field of ApproveHub, the list of installed modules model names will be displayed.

Note:- If no modules are installed, it will be displayed as blank.

After installing the pragtech_approval_purchase module, in the "ApproveHub” module the "Model Name" field should display the purchase order.

Need to select a model to add the domain filter on the selected model After adding the "Purchase Order" model, you can apply a domain filter using the "New Rule" button. Upon clicking this button, you can add conditions to specify the criteria for filtering records for approval flow.

And if it's configured, the submit button will be displayed in the purchase order form view.

The list of users that we have added in the "Approver User List" field in the ApproveHub model will be displayed in the User Approvals in Purchase order form.

If a domain filter condition has been added to the purchase order model, then the approval flow will only continue for records that satisfy that condition. However, if the domain filter condition is not added, the approval flow will be applied to all records.

For example: only records with a total greater than 1200 should undergo the approval flow; otherwise, the normal purchase order flow will continue.

In this given record, the total is greater than 1200, so this record undergoes the approval flow because the domain filter condition matches with the record.

After submitting the records, the state will change to 'waiting for approval' because the given record matches the domain filter condition.

And after that the approval user will perform the approval functionality to either approve or reject the order.

The record does not match the domain filter condition, so it will continue its default sale order flow.

If the domain filter is not added in the ApproveHub model for a specific model, then the normal approval flow will continue for all records.

After submitting the data, the state has changed from 'draft' to 'waiting for approval'.

The users who have been assigned to it will now be able to Approve or Reject the order.

If all mandatory users in the list have approved the request, the state will change from "Waiting for Approval" to "Approved," and an email notification will be sent to the salesperson.

Note : After approval, the purchase order process will continue as usual

When a user clicks the “Reject” button, a wizard will be displayed, allowing the user to add a rejection reason.

After submitting, an email notification will be sent to the salesperson, and the status in the state will change from “Waiting for Approval” to “Reject”

Users who have rejected a request won't be able to approve or reject the same request again in the list of users who can approve or reject it

You can also specify the number of mandatory users required to approve the order by entering a value in the “Minimum Approvers” field. If the value is “Zero”, then all mandatory users should approve the order.

If any two approver users order, the order will be approved because we have set the value of minimum approvers to 2.

Actions

When the form is in a submitted state, it should not be deleted, and if there is a need to delete it, it should be moved to the draft state

If the user name in the user list is the same, a validation error will be displayed.

Email

1. After assigning a user to a specific model to handle the approve or reject functionality, that user will receive an email saying, 'You have been selected to handle the model.

2. After filling out the data and submitting it, an email notification will be sent to the user

3. After the order is approved, an email will be sent to the salesperson user

4. And if the order is rejected, an email will be sent to the salesperson user