OmniApproval™ - Fleet Booking Approval
by Viindoo
| Lines of Code | 568 |
| Technical name | viin_fleet_booking_approval |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/18.0/viin_fleet_booking_approval |
| Read description for | v 17.0 |
| Required Apps | Discuss (mail) Employees (hr) Fleet (fleet) |
| Included Dependencies | Fleet Drivers Management Fleet Booking & Trip Management Fleet Loading Capacity Employee Documents QR Code Mixin Viindoo Base OmniApproval™: One platform. Every approval. Advanced HR Management Viin Fleet Safe IR Metadata Proxies |
A vehicle booking somebody signed for
An approval gate on fleet bookings, driven entirely by the approval type's configuration rather than hard-coded logic.
OmniApproval™ - Fleet Booking Approval (technical name viin_fleet_booking_approval) is an Odoo 18.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for manager, operations, administrator, audit.
At a Glance
The facts of OmniApproval™ - Fleet Booking Approval, version 0.1.0, in one place. Published by Viindoo.
How It Works
Three screens.
The request
What a manager is asked to sign.
The bookings
Which are waiting, which are approved.
The queue
Across the whole company.
What You Get
Approval gate on fleet bookings
Submit creates a linked approval request
Confirm, approve, refuse and cancel driven by the approval type
Cancelling a booking cancels its pending requests
Validated and refused requests kept as history
Seeded approval type - nothing to build
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
Approval requests
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
Approvers come from the approval type.
An unapproved booking simply is not confirmed.
Everything lives in the approval type's configuration.
Fleet Booking and OmniApproval.
Works Well With
Apps from the same stack, built to fit this one:
Who Should Use OmniApproval™ - Fleet Booking Approval?
Manager
Signs, or does not.
Operations
Knows what is cleared to proceed.
Administrator
Grants configuration without granting the system.
Audit
Can trace a document to its decision.
Frequently Asked Questions
What does OmniApproval™ - Fleet Booking Approval do?
An approval gate on fleet bookings, driven entirely by the approval type's configuration rather than hard-coded logic.
What does OmniApproval™ - Fleet Booking Approval not do?
It does not decide who approves. Approvers come from the approval type. It does not block the fleet. An unapproved booking simply is not confirmed. It adds no booking logic. Everything lives in the approval type's configuration. It needs both apps. Fleet Booking and OmniApproval.
Who is OmniApproval™ - Fleet Booking Approval for?
Manager: Signs, or does not. Operations: Knows what is cleared to proceed. Administrator: Grants configuration without granting the system. Audit: Can trace a document to its decision.
Which Odoo version and editions does it support?
Odoo 18.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: viin_approval, viin_fleet_booking. Odoo installs them with it.
How do I set it up?
Three screens.
What works well with it?
Fleet Booking (viin_fleet_booking): The bookings themselves. OmniApproval (viin_approval): The approval engine. Fleet Trip Accounting (viin_fleet_booking_account): What the trip costs.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_fleet_booking_approval; pre-sales questions go to sales@viindoo.com.
See OmniApproval™ - Fleet Booking Approval in Action
Live demo: v18demo-int.viindoo.com/web#action=viin_fleet_booking.action_fleet_booking
Need help with OmniApproval™ - Fleet Booking Approval?
For questions, implementation support or a custom feature, contact Viindoo.
Pre-Sales & Partnership
sales@viindoo.comUpgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: Viindoo Apps
Technical Requirement
Changes log
0.1.0 - Latest on the 17.0 line
- Aligned with the 17.0 models of the apps it works with.
Fleet Booking Approval
For people who book vehicles, fleet managers, approvers and approval administrators.
Note
Extends OmniApproval™ - see its documentation for roles, approvers, snapshots and every other engine feature. This guide only describes what the Fleet Booking approval type adds.
Note
Extends Fleet Booking - see its documentation for bookings, trips and vehicles.
Overview
A vehicle booking can be confirmed only after the right people have agreed to it. The module adds one approval type to every company, Fleet Booking, and links it to the bookings:
- The person who books asks for approval from the booking. Only a booking in Draft can be submitted.
- Approving the request confirms the booking.
- Refusing or cancelling the request leaves the booking as it is.
- The booking shows its approval status in an Approval Coverage ribbon.
| Role | What they do | Access right to assign |
|---|---|---|
| Requester | Prepares the booking and asks for its approval. | Fleet Booking: User |
| Fleet manager | Follows all bookings and prepares bookings for other people. | Fleet: Operator |
| Approver | Decides on the requests that reach them. To complete an approval, the approver must also hold the Fleet: Operator right. | Team Approver or Officer (Approvals), and Fleet: Operator |
| Approval administrator | Adjusts the Fleet Booking type. | Administrator (Approvals) |
The Team Approver, Officer and Administrator rights of approvals are described in the Roles and Access Rights section of the OmniApproval™ guide.
Setup (for the Administrator)
- Go to Apps, search for OmniApproval™ - Fleet Booking Approval and click Install. It is installed together with Fleet Booking and OmniApproval™ when both are present.
- Open Approval > Configuration > Approval Types. Each company now has an approval type named Fleet Booking, ready to use.
- Give each person the access rights of their role under Settings > Users & Companies > Users.
The type asks the employee's manager for the first approval step and names no approver. Who approves, and in how many steps, is yours to decide: add approvers to the type as described in the Approvers section of the OmniApproval™ guide. Give the Fleet: Operator right to each person who approves.
What the Fleet Booking type adds
- The type applies to bookings that are in Draft. One request is created for each booking.
- The request shows the Booking Number, Booked For, Assigned To and Pickup Time of the booking. The request carries no lines.
- The type marks a booking as requiring approval when its booking type calls for one. Each module that provides a booking type declares this for its own bookings. Until such a booking is approved, its form shows a Missing Approval ribbon in Approval Coverage. A booking whose type does not call for an approval shows Not Applicable.
Using the approval
Asking for approval (Requester)
- Open the booking under Fleet Booking > Fleet Bookings.
- Check that the booking is in Draft.
- Click Actions > Get Approved.
- Check the approval type and the booking shown in the Submit for Approval window.
- Click Create Approval Request.
The request opens in Draft. Click Submit to send it to the approvers. A booking that has already left Draft cannot be submitted: the request stays in Draft and the message Only a draft booking can be submitted for approval (booking '...'). is shown.
Approving the request (Approver)
Open the request and click Approve. When the last required approval is given, the request is Approved and a booking in Draft becomes Confirmed; the chatter of the booking records Booking approved and confirmed via approval request ...
The approver confirms the booking with their own rights. An approver who does not hold the Fleet: Operator right gets an access error on the booking when giving the last approval, and the booking stays as it is: give the right to the approvers of the type, as described in Setup. Refusing needs no booking right.
Refusing, cancelling and resetting
Refusing or cancelling a request, or resetting it to Draft, leaves the booking as it is. The general behaviour of these actions is described in the Cancelling, Refusing and Resetting to Draft section of the OmniApproval™ guide.
Cancelling a booking
When a booking is cancelled with Cancel, its requests that are still in Draft or waiting for a decision are cancelled with it. Approved and refused requests stay as a record of the decision.
No lock on the booking
Approval never blocks changes to the booking by itself, including its confirmation by hand. The Missing Approval ribbon only shows the coverage. See the Business Documents section of the OmniApproval™ guide to add a block.
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.