| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 955 |
| Technical Name |
pragtech_approval_hub_payment |
| License | OPL-1 |
| Website | http://pragtech.co.in |
| Versions | 17.0 16.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 955 |
| Technical Name |
pragtech_approval_hub_payment |
| License | OPL-1 |
| Website | http://pragtech.co.in |
| Versions | 17.0 16.0 |
Approve Hub Management System for Sale module
Our Pricing includes User Manual, 90 Days Support (Monday-Friday 10am to 7pm IST) and One time Setup
support@pragtech.co.in pragtech
We support for English / French / Spanish at an additional cost
| Supported Odoo versions & platforms | |||||||||
| Odoo.sh | Self Hosted | Enterprise | Community | Odoo Online | |||||
 |
|
|
|
 |
|||||
| Supported Odoo versions & platforms | |
| Odoo.sh | |
| Self Hosted | |
| Enterprise | |
| Community | |
| Odoo Online | |
Works & tested on standard installations of Odoo with no third party apps
Free support only for odoo installations with no third party apps
Paid support availaible for Odoo installations with third party apps.
Our Service Offerings
Odoo Dedicated Resources
Odoo Success Packs
Odoo Turnkey Projects
To connect with us: support@pragtech.co.in
Approve Hub Management System for Payment module
The “ApproveHub” Project is a custom Odoo application designed to streamline the Invoice 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 Invoice 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...
In the "ApproveHub" Approval form, there are a total of 4 fields: “Reference”, “Model Name”, “Domain Filter ” and “Approver User List”.
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_apporval_hub_payment module, in the “ApproveHub” module the “Model” field should display the Payment.
If a domain filter condition has been added to the payment 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 customer equal to “Azure Interior” should undergo the approval flow; otherwise, the normal payment flow will continue.
In this given record, the customer is equal to “Azure Interior”, 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 payment 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 record.
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 Payment model
And if it's configured, the submit button will be displayed, and after approve state, the confirm button will be shown again
After submitting the data the state will be change to waiting for approval
The users who have been assigned to it will now be able to Approve or Reject the Payment 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 Payment 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 created data user, 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
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.
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
Help Support Covid Relief
Pragmatic has always been contributing itswarsa social causes by exercising its Corporate Social Responsibility. We are pledged to COVID relief and have been donating a major share of our profits to COVID Pandemic Relief. By purchasing our apps and services you are becoming a part of helping the needy in these critical times. If you want to help further please connect with us and we will help you find NGOs whom you can donate directly.
Contact / Support
(Monday-Friday 10am to 7pm IST)
Pragmatic Techsoft Pvt. Ltd.
Pragmatic is a global open source enterprise software development, consulting and products company. Our philosophy is to use Open Source tools and technologies to provide cost effective and green solutions for our customers.
We are a dynamic and fast growing company committed towards creating value for our customers. Located in Pune, India the educational and IT hub of western India, we take pride in delivering rapid, customized open source enterprise applications following agile and lean software methods. Whether you are developing an application from scratch, working on an existing application or porting your application to a new platform or framework, we can meet your business needs.
If you need any help or want more additional features, you may contact us through:
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