OmniApproval™ - Flexible Flow
by Viindoo https://viindoo.com/apps/app/17.0/viin_approval_flexible_flow
Odoo
$ 177.82
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 22311 |
| Technical Name |
viin_approval_flexible_flow |
| License | OPL-1 |
| Website | https://viindoo.com/apps/app/17.0/viin_approval_flexible_flow |
Demo video: Approvals
What it does
Many companies outgrow the "fixed approval flow" model.
With standard approvals (including Odoo's Approval app), once a request is submitted, the approval route is typically locked. When reality changes, teams usually face an unpleasant choice:
- Cancel and re-submit just to add a missing approver (wasting time and losing momentum)
- Approve via chat/email "as an exception" (no traceability, no audit trail, high compliance risk)
- Let the request go through without the right stakeholder (decision risk)
OmniApproval™ - Flexible Flow brings real-world flexibility to approvals: you can insert or revoke additional approvers while a request is running, without breaking the default approval flow designed by the business.
Every change is governed, logged, and reportable - so operations stay fast, and controls stay strong.
Key Features
- Flexible approval flow for real life changes (without breaking the default flow)
- Add approvers after submission - no need to cancel and re-submit
- Insert before/after a selected default approval step
- Keep the default approval order intact (only insert, never reorder)
- Prevent duplicates across single-approver and multi-approver steps
- Enforce a maximum number of inserted approvers per Approval Type
- Controlled by policy, not by improvisation
- Configure who can add approvers per Approval Type (submitter, default approver, security groups)
- Revoke inserted approvers before they take any approval action
- Require a revoke reason to ensure transparency and accountability
- Audit-ready and reportable
- Full audit trail for every add/remove event: actor, target, anchor step, position, reason, timestamp
- Clear UI indicators for modified flows (ribbon + inserted approver badge)
- Control reports for Approval Admin to review modified requests and audit logs
Typical Use Cases
- A CFO/Legal/Compliance approval is required after submission due to a policy exception.
- A key stakeholder must be consulted urgently without restarting the request.
- Temporary escalation is needed for high-value or high-risk approvals.
- Avoid "approval outside the system" and keep decisions auditable.
Editions Supported
- Community Edition
- Enterprise Edition
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