Forms | QWeb Reports

by
Odoo
v 11.0 v 12.0 Third Party 2227
Download for v 11.0 Deploy on Odoo.sh
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 4563
Technical Name formio_report_qweb
LicenseLGPL-3
Websitehttps://www.novacode.nl
Versions 12.0 16.0 13.0 14.0 15.0 11.0 17.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 4563
Technical Name formio_report_qweb
LicenseLGPL-3
Websitehttps://www.novacode.nl
Versions 12.0 16.0 13.0 14.0 15.0 11.0 17.0

Forms | QWeb Reports

Generate (PDF) reports for every Form, in just a click

Developed on the (Odoo) QWeb Reports engine

Installation Requirements
  • PyPi package formio-data (version >= 0.3.3)
    - Install: pip3 install -U formio-data
    - GitHub project: https://github.com/novacode-nl/python-formio-data

In just a click, generate and download a PDF-report for every Form.

Available report types:

  • Form - My preferences
    PDF report with translastions (e.g. labels) in language of the logged in user.
  • Form - Assigned user preferences
    PDF report with translastions (e.g. labels) in language of the assigned (form) user.

Generic PDF report of Form (see below)

Form

Features & Benefits:
  • Out-of-the-box generated PDF report, for every Form.
  • Generated report has identical layout as the form. Even for complex form designs.
  • Fully QWeb customizable reports, regarding layout (fields, header etc.) and styling (CSS).
  • Open source, so contributions are welcome.

Visit the online Demo (Odoo Community v13)

Demo

Users (Email / Password)

  • demo / demo
  • portal / portal

Releases

3.0

  • MAJOR IMPROVEMENT: "Simple" conditional visibility of components, by checking new property component.is_visible.
    Possible by recent improvements in the Python formiodata library (version: 0.3.3).

    This release is backwards incompatible for overrides/customizations of the following QWeb XML.
    Moved the visibility check:
    - From: <template id="report_formio_form_template"> ... <t t-if="component.hidden != True">
    - To: <template id="component"> ... <t t-if="component.is_visible">

2.0

  • MAJOR IMPROVEMENT: Rendering of nested components e.g. in datagrid, layout components.
    Possible by recent improvements in the Python formiodata library (version: 0.3.0).
    This release is backwards incompatible (eg in case of implemented custom QWeb Reports which inherit from this QWeb XML).
  • Don't escape a component label (lets' trust this). This ensures the label (inner) HTML/styling shall be preserved in reports.

1.1

  • Fix and re-implement components (file, content/html, table, tabs), got broken after recent changes in 2.0.

1.0

  • Improves Rendering of nested components e.g. in datagrid, layout components.
    Possible by recent improvements in the Python formiodata library (version: 0.2.0).
  • Improves datagrid component rendering.
    Possible by recent improvements in the Python formiodata library (version: 0.2.0).
  • New datetime component
  • Improve columns component:
    Complex columns/grids with identical layout (row wrapping ) as in the Form. For example 3 rows with specified column widths [[6,6], [12], [8, 4]].
  • The QWeb component (object) now is the Python formiodata Component object, instead of a Dictionary component['_object'].
    This release is backwards incompatible, in case of implemented custom QWeb Reports which inherit from this QWeb XML.

0.12

  • New radio (input) component

0.11

  • New datagrid component
  • Refactor component (object) loading/reader.

0.10

  • New file upload component (storage: base64)

0.9

  • Don't print/render hidden components.
  • Smaller report header (h3 instead of h2).

0.8

  • Avoid rendering/printing of file component (no image, without diplaying).

0.7

  • New layout components: tabs, table

0.6

  • New components/fields: number, phoneNumber, email, signature (image), content

0.5

  • Annotate required components.
  • Render not stored (optional and empty) components/fields.

0.4

  • Reports configuration per Builder:
    Show not implemented components/fields (setting and implementation).
    Improves the feature introduced in version 0.3.

0.3

  • Render not implemented components (raw data) with a warning.

0.2

  • New select (one, multiple) component.
  • Some layout/design improvements.

0.1

  • Initial version

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.