-
Lunch - Get your T-shirts - 2022 OCA Members get first dibs
Done
-
Lunch
Done
-
Writing tests to Odoo frontend: JS Tours and QUnit
Iván TodorovichDone
-
Board AMA
Odoo Community Association (OCA)Done
-
oca-port: new OCA tool to help with modules migration
Sébastien Alix and Simone OrsiDone
-
GraphQL API on Odoo powered by OCA
Yannick PayotDone
-
Mozaik - managing Political Parties with open source
Guillaume Vandamme and Vincent Van Osta.Done
-
Revisiting How To Deliver to Customers while Contributing to the OCA
Daniel ReisDone
-
Field Service: New features and roadmap
Maxime ChambreuilDone
-
Open discussion on Practices with Community Accounting and Instability on Odoo Accounting
Julien Jézéquel-BréardDone
Tom has been an Odoo developer for the last 8 years with the Sunflower IT team. Recently this team merged with the Therp team, of which Nikos is a developer since 4 years.
A module was designed by me and colleague Nikos Tsirintanis, that allows Odoo users to create a report on any model without the need of a developer. Report content is a sequence of Jinja-capable HTML template blocks. Each block can be conditionally shown or hidden by evaluation of an Odoo domain or a Python expression. Aliases can be defined as shorthand expressions to more complicated ones. As the original requirement was for generating contracts, it also includes a macro for automatic section numbering (1.1, 1.2, 1.2.1 etc). For usage, the module adds a "More.." server action to generate the report from the record's form view. If multiple templates match the record, it pops up to let the user choose which one.