OmniApproval™ - Purpose-Based Routing
This module extends OmniApproval with purpose-based approval routing.
It allows approval steps to be configured in two ways within the same approval type:
- General approval steps: apply to all approval requests of the approval type.
- Purpose-specific approval steps: apply only when the approval request is created with a matching usage purpose.
With this approach, one approval type can combine a shared approval flow with additional
approval steps for specific business purposes, instead of creating many duplicated approval types.
Key Features
- Centralized Usage Purpose Management
- Define and manage a list of usage purposes in Approval settings.
- Configure basic information such as name, description, sequence and active status.
- Reuse the same usage purposes across multiple approval types.
- Apply Usage Purpose to Approval Steps
- Add a usage purpose to an approval step in the approval type.
- Approval steps with a usage purpose are considered purpose-specific steps.
- Approval steps without a usage purpose are treated as general steps.
- Select Usage Purpose on Approval Requests
- Add Usage Purpose to approval requests.
- Let request creators specify the intended purpose of the request.
- Use the selected purpose to determine which additional approval steps should be applied.
- Support Both General and Purpose-Specific Approval Steps
- If an approval step has a usage purpose, it applies only to approval requests with the same usage purpose.
- If an approval step has no usage purpose, it applies to all approval requests of the approval type.
- This helps combine a common approval flow with additional routing branches for different business scenarios.
Benefits
- Reduce duplicated approval types created only for different request purposes.
- Make approval configuration easier to maintain and extend.
- Improve clarity when one approval type serves multiple request scenarios.
Who should use this module
- Organizations that need different additional approval steps depending on request purpose.
- Administrators who want to keep one approval type while handling multiple routing scenarios.
- Implementers and developers extending OmniApproval for more flexible approval flows.
Supported Editions
- Community Edition
- Enterprise Edition
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.
