Approval Rules Management
by CLuedoo https://www.cluedoo.com/shop/lic-clu-set-wfm-0002-approval-rules-management-6065$ 196.40
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Studio (web_studio)
• Discuss (mail) |
| Lines of code | 361 |
| Technical Name |
fal_approval_rules |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-wfm-0002-approval-rules-management-6065 |
| Versions | 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Studio (web_studio)
• Discuss (mail) |
| Lines of code | 361 |
| Technical Name |
fal_approval_rules |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-wfm-0002-approval-rules-management-6065 |
| Versions | 18.0 |
STORY BEHIND THE FEATURES
ODOO BEHAVIOR
Odoo's studio allows customizing approval process of Sales, Purchase, Accounting, etc. according to company policy.
CLUEDOO BEHAVIOUR
Cluedoo adds additional features to personalize approval workflow by:
- Managing approval rules by groups and option to specify a hierarchical approval procedure
- Recording approval histories
- Adding a button to revoke the whole approval sequence
- Automation tab in Studio Approvals Rules Group that list the automation rules linked to that group
- Auto Confirm Action checkbox to automatically confirm the PO after the last approval
USE CASE
Company needs to setup approval rules on purchasing as below:
- For RFQ under $1000, needs approval from Department Manager to confirm RFQ.
- For RFQ from $1000, needs approval from Department Manager, then Accounting Manager, to confirm RFQ.
HOW TO USE THIS MODULE ?
Create Approval Rules
There are 2 ways to create Approval Rules:
- By studio
- By go to Studio Approval Rules
Option 1: By studio
1
. Open an RFQ in studio, click on Confirm button to edit
2
. Check "Set approval rules" checkbox
3
. Select Approval Group and Responsible person for the Rule
(note: Any users in the selected Approval Group can approve the rule, but only Responsible will be notified for the scheduled activities)
4 . Add condition for the rule by clicking on the Funnel icon next to Approval Group box
5
. Close Studio.
Option 2: By go to Studio Approval Rules
User can also view/create new Approval Rules by activating developer mode, then go to Settings/Technical/Studio Approval Rules.
For the use case, 3 rules were created:
- For RFQ under $1000, rule (5).
- For RFQ from $1000, rule (3) and (4).
At this step, the rules are still separate rules.
Approval Rules Group
To group the rules created above
Action:
1.
Go to Settings/Technical/Studio Approval Rules Group, and create a new Group
2.
Fill out Group name
3. Select Model (Sales Order, Purchase Order, etc.)
4 . Add a line to select the created rules to the Group. Popup wizard will suggest rules related to the selected model only.
5.
"
Approve in Order
" check box:
- If not checked, approvals can be done in any order.
- If checked, approvals need to be done in chronological order, from the top to bottom rules in the list. (For example, Accounting Mgr. cannot approve before Dept Mgr. approves)
Note:
User can change the order by dragging the arrow handle next to the rules.
.
Result:
Now that 2 Approval Rules Groups were created:
- Purchase > 1000
- Purchase < 1000
.
"Revoke all approvals" button
Action:
1. Go to Settings/Uses & Companies/Groups, choose "Can Reset Approval" group.
2. "Add a line" to assign user capable of revoking all approvals of an RFQ/Quotation/Payment request, etc.
.
Result:
On approval table, the assigned user can click on the Red button to revoke all approval process.
.
Approval History
To create an action to view approval history of a Sales Order, Purchase Order, etc.
Action:
1.
Go to Settings/Technical/Server Actions,
2.
Search for and choose "Approval History"
3.
Duplicate
4.
Fill out new action name, for example: Purchase Approval History
5.
Choose model Purchase Order
6.
Click "Create Contextual Action" to create the new action on Purchase Order form.
.
Result:
User cam view approval history of an RFQ by clicking on Action/Purchase Order History
.
User can also view all approval entries of all models (Sales Order, Purchase Order, etc.) by go to Settings/Technical/Studio Approval Entries.
AUTOMATION TAB ON STUDIO APPROVALS RULES GROUP
1. Go to Settings > Technical > User Interface > Studio Approvals Rules Group > Create a new group
e.g. Purchase Approval Process
2. Go to Settings > Technical > Automation > Automation Rules > Create a new rule and select the approval rule group that we just created in step 1 > Save
3. Go back to the approval rule group > Under the Automation tab, the automation rule has been automatically added
You can add Automation Rules from any models.
"AUTO CONFIRM ACTION" CHECKBOX
In the Studio Approvals Rules Group , there is an Auto Confirm Action checkbox
Result:
- If it is checked > After the last approval, the PO will be auto-confirmed
- If it is unchecked > After the last approval, we still have to click Confirm Order manually
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