Clean In-Session File Downloads (Client Action)
by Cerevantix Technologies https://cerevantix.com$ 13.67
Clean downloads, zero disruption to your workflow
A drop-in client action for Odoo 17–19 that streams files straight to the browser — no new tab, no page reload, no lost form state — with batch downloads, live progress, descriptive errors, and a full audit trail built in.
Odoo's native download paths open a new browser tab or force a full page reload, breaking session continuity and discarding unsaved form state. Developers are left hand-rolling client-side download logic on every project — with no batch support, no progress feedback, no descriptive errors, and no record of who downloaded what.
A single service builds a client action that fetches files via an XHR blob request and saves them in-session, with zero navigation. Call it from a server action, any backend method, or a button. Batch multiple files into one action, show live progress, surface plain-language errors, and log every download to a searchable audit trail.
A complete download toolkit, drop in
Every capability below is implemented in the module.
Trigger from server actions
Bind the download builder to any server action and it appears right in a record's Actions cog menu, ready to run against one or many selected records.
Trigger from backend methods
Call a helper from any Python method to turn a binary field, an attachment, or a generated document into a clean, in-session download.
Button-initiated downloads
Wire any object button on a form or list view to return a download action, so a single click delivers the file without any extra scaffolding.
No new tab, no reload
Files are fetched via an XHR blob and saved by the browser's own downloader — the page never navigates, and unsaved form state survives.
Batch downloads
Pass a list of files to download several attachments or generated documents in a single action, tracked together in the audit trail under a shared batch.
Live progress feedback
A sticky notification tracks the percent complete for each file, so large downloads never look stalled or unresponsive.
Descriptive error handling
Failed downloads surface a plain-language notification naming the file and the reason — never a silent failure or a raw traceback.
Download history & audit trail
Every download is logged with user, filename, size, mimetype, source, and timestamp — viewable in list, form, and graph views.
Configurable retention
Toggle audit logging and set a log retention period in Settings; a daily scheduled job clears logs past the configured age automatically.
How it works
Build the action
Call the download builder from a server action, a backend method, or a button, passing the file URL(s) to send.
User clicks
The client action runs in the background: the browser fetches each file over XHR — no new tab, no reload.
Progress & delivery
A live progress notification tracks each file; on completion the browser saves it exactly like a native download.
Review the trail
Every download, success or failure, appears in the History list and graph — filterable by user, source, and status.
See it in action
Four screens covering the audit trail, settings, and a live in-session download.
The Download History list shows every download — user, filename, human-readable size, mimetype, source, and status — with color-coded badges and batch rows grouped by a shared token.
Each log opens to a full record: a status bar for pending, success, and error states, complete metadata, and a plain-language error message shown only when a download fails.
Administrators toggle audit logging and set the log retention period, in days, from a dedicated Settings screen; a daily scheduled job then clears logs past that age automatically.
Triggered from a partner's Actions cog menu, a demo server action downloads a generated vCard in-session — no new tab, no reload — and the download is written to the audit trail in real time.
Frequently asked
Does this module open a new browser tab or reload the page?
No. Every download is fetched via an XHR blob request and saved by the browser's native downloader, so the current page — and any unsaved form data — never changes.
Can I download multiple files in a single action?
Yes. Pass a list of files to the download builder and the module downloads them all in one client action, tracked together in the audit trail under a shared batch token.
Which Odoo versions are supported?
The module is available for Odoo 17.0, 18.0, and 19.0, each installed from its own dedicated version-specific package.
How do I trigger a download from my own module?
Call the download builder from a server action, any backend Python method, or an object button — the README includes copy-paste examples covering all three, plus the batch and attachment helpers.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Clean, in-session file downloads for Odoo — batch support, live progress, descriptive errors, and a full audit trail, with no new tab and no page reload.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 515 |
| Technical Name |
cerevantix_client_action_file_download |
| License | OPL-1 |
| Website | https://cerevantix.com |
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