diff --git a/report_display_name_in_footer/README.rst b/report_display_name_in_footer/README.rst index d89639e2c..98ac60c3c 100644 --- a/report_display_name_in_footer/README.rst +++ b/report_display_name_in_footer/README.rst @@ -107,6 +107,29 @@ To use this module, you need to: 3. Print a report for you desired model. 4. Check Footer to see document name. +Known issues / Roadmap +====================== + +When this module is checking if the model has to display the name in the +footer is done at the level of the initial model of the report you are +printing. + +Examples of strange cases/uses: *stock_picking_batch_print_pickings* and +*stock_picking_batch_print_invoices* modules print the delivery notes or +invoices of the Pickings associated with the Batch, but the report is +being launched from the Batch. So, the header and footer belongs to the +Batch. + +Within that report, calls are made to the invoice or delivery note +reports, but the check to see if the name of the document has to be +printed in the footer is done on the Batch. + +Therefore, if you set the configuration parameter to "stock.picking, +account.move" , the names printed from that report will not appear. By +setting it to "stock.picking.batch", the module will establish that all +the documents contained in that report (whether invoices or delivery +notes) must include the name in the footer. + Bug Tracker =========== diff --git a/report_display_name_in_footer/data/report_data.xml b/report_display_name_in_footer/data/report_data.xml index 915827055..3ad1883a0 100644 --- a/report_display_name_in_footer/data/report_data.xml +++ b/report_display_name_in_footer/data/report_data.xml @@ -1,5 +1,5 @@ - + report.display_name_in_footer_models all diff --git a/report_display_name_in_footer/readme/ROADMAP.md b/report_display_name_in_footer/readme/ROADMAP.md new file mode 100644 index 000000000..616d2a99a --- /dev/null +++ b/report_display_name_in_footer/readme/ROADMAP.md @@ -0,0 +1,18 @@ +When this module is checking if the model has to display the name in the footer +is done at the level of the initial model of the report you are printing. + +Examples of strange cases/uses: +*stock_picking_batch_print_pickings* and *stock_picking_batch_print_invoices* modules +print the delivery notes or invoices of the Pickings associated with the Batch, +but the report is being launched from the Batch. So, the header and footer +belongs to the Batch. + +Within that report, calls are made to the invoice or delivery note reports, +but the check to see if the name of the document has to be printed in the +footer is done on the Batch. + +Therefore, if you set the configuration parameter to "stock.picking, account.move" +, the names printed from that report will not appear. +By setting it to "stock.picking.batch", the module will establish that all the +documents contained in that report (whether invoices or delivery notes) +must include the name in the footer. diff --git a/report_display_name_in_footer/static/description/index.html b/report_display_name_in_footer/static/description/index.html index d6043b8b4..624e8803e 100644 --- a/report_display_name_in_footer/static/description/index.html +++ b/report_display_name_in_footer/static/description/index.html @@ -8,10 +8,11 @@ /* :Author: David Goodger (goodger@python.org) -:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $ +:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $ :Copyright: This stylesheet has been placed in the public domain. Default cascading style sheet for the HTML output of Docutils. +Despite the name, some widely supported CSS2 features are used. See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to customize this style sheet. @@ -274,7 +275,7 @@ pre.literal-block, pre.doctest-block, pre.math, pre.code { margin-left: 2em ; margin-right: 2em } -pre.code .ln { color: grey; } /* line numbers */ +pre.code .ln { color: gray; } /* line numbers */ pre.code, code { background-color: #eeeeee } pre.code .comment, code .comment { color: #5C6576 } pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold } @@ -300,7 +301,7 @@ span.option { span.pre { white-space: pre } -span.problematic { +span.problematic, pre.problematic { color: red } span.section-subtitle { @@ -387,11 +388,12 @@ Only for development or testing purpose, do not use in production.
  • Use Cases / Context
  • Configuration
  • Usage
    • -
  • Bug Tracker
    • -
  • Credits @@ -452,8 +454,27 @@ type of documents.
  • Check Footer to see document name.
    • +
    +

    Known issues / Roadmap

    +

    When this module is checking if the model has to display the name in the +footer is done at the level of the initial model of the report you are +printing.

    +

    Examples of strange cases/uses: stock_picking_batch_print_pickings and +stock_picking_batch_print_invoices modules print the delivery notes or +invoices of the Pickings associated with the Batch, but the report is +being launched from the Batch. So, the header and footer belongs to the +Batch.

    +

    Within that report, calls are made to the invoice or delivery note +reports, but the check to see if the name of the document has to be +printed in the footer is done on the Batch.

    +

    Therefore, if you set the configuration parameter to “stock.picking, +account.move” , the names printed from that report will not appear. By +setting it to “stock.picking.batch”, the module will establish that all +the documents contained in that report (whether invoices or delivery +notes) must include the name in the footer.

    +
    -

    Bug Tracker

    +

    Bug Tracker

    Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed @@ -461,24 +482,26 @@ If you spotted it first, help us to smash it by providing a detailed and welcome

    Do not contact contributors directly about support or help with technical issues.

    -

    Credits

    +

    Credits

    -

    Authors

    +

    Authors

    • Moduon
    -

    Contributors

    +

    Contributors

    -

    Maintainers

    +

    Maintainers

    This module is maintained by the OCA.

    -Odoo Community Association + +Odoo Community Association +

    OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.