summaryrefslogtreecommitdiff
path: root/addons/account/data/payment_receipt_data.xml
AgeCommit message (Collapse)Author
2020-09-29[FIX] account, mail: properly evaluate and clean xml contextAnkit Sathvara
Before this commit, there were some traceback while performing several actions due to context that was not properly evaluated. This commit fixes those traceback by evaluating the context and thus enabling user to perform those actions without traceback. We also clean some badly-configured email actions in accounting. Task Id : 2302572 PR #56501 Co-authored-by: D J <dja@odoo.com> Co-authored-by: Thibault Delavallée <tde@odoo.com>
2020-07-28[REM] core, *: deprecate <act_window> and <report>Xavier Morel
Convert deprecated tags through the codebase.
2020-07-06[FIX] account: change composition mode to allow multi sendAndrea Grazioso (agr-odoo)
Go to Payments view Select multiple confirmed payments, click on Actions>Send receipt by email Only for the first payment will be sent an email. This occur because in composition mode 'comment' (the default) mail composer sens the mail to a single record Adding a duplicate action to handle multi send Updating translation accordingly opw-2278971 closes odoo/odoo#54108 X-original-commit: 11fd7687047b2c17e9464e8415087d9a9fcf58a8 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
2020-02-11[REF] mail, various: remove user_signature field from mail.templatemcm-odoo
RATIONALE Mail template model holds a field telling odoo mail engine to automatically add the current user's signature to the body. Its use depends on the use case * using the template in the composer on a single record: it is displayed in the rendered template in the composer, meaning people could change it. This behavior is interesting as it allows to see the email content; * using the template in the composer in mass mail mode: it is not displayed as only the raw jinja is displayed. It is therefore not obvious that it will be appended to the body of the mail. People could add it manually and have 2 signatures as a result; A mechanism automatically adding a signature to sent emails when posting a message is already implemented and is based on template existence. If a template has been used when posting, no signature is added in sent emails. Otherwise it is automatically added. This behavior should not change. Behavior will therefore be * use a template -> specify signature usage in it manually through jinja; * do not use a template -> signature added in sent emails; SPECIFICATIONS Remove user_signature. Update template body accordingly. In customer oriented templates that are using it and do not already contain it, manually add a call to user.signature within the jinja code. When set to False, just remove its declaration. Quickly clean some signature integration. LINKS Task ID 2089252 Community PR odoo/odoo#39482 Enterprise PR odoo/enterprise#6459 Upgrade PR odoo/upgrate#761 Related: odoo/enterprise#6459 Related: odoo/upgrade#761 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> Co-authored-by: Michaël Mattiello <mcm@odoo.com> Co-authored-by: Thibault Delavallée <tde@odoo.com>
2020-01-22[IMP] account: add a readonly groupwan
Task 2092079 Accounting firms that want to give access to their customers avoiding mistakes and risks will love this profile that can't do anything wrong... Maybe as well as companies auditors..? closes odoo/odoo#39860 Related: odoo/enterprise#6576 Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
2019-07-10[IMP] account(_*): clean the controlpanel actionsHiral Bhavsar
* check_printing, voucher For the model 'account.account', - Replace the action menu 'Journal Items' by the stat button. - Hide menu 'Journal Items for Tax Audit' from actions menu. For the model 'account.invoice', - Set action menu 'Share' only for the form view. - Rename the action menu 'Confirm Draft Invoices' by 'Validate'. - Rename 'Register Payment' by 'Register payment'. - Rename 'Send' by 'Send & print'. For the model 'account.move', - Remove the menu 'Journal Items'. - Rename 'Reverse Moves' by 'Reverse' and set it only for the list view. - Rename 'Post Journal Entries' by 'Post entries' and set it only for the list view. For the model 'account.move.line',r ename 'Reconcile Entries' by 'Reconcile' and 'Unreconcile Entries' by 'Unreconcile' and set it only for the list view. For the model 'account.payment', - Rename 'Send Receipt By Email' by 'Send receipt by email' and set it for both form and list views. - Rename 'Post Payments' by 'Confirm' and set it for the list view only - Rename 'Print Checks' by 'Print checks' and set it for the list view only. For the model 'account.journal', remove the menus 'Unpaid Invoices', 'Bank statements' and 'Voucher Entries'. Linked to task 1984526 Related to PR #33720
2019-06-10[FIX] generic: fix typo in email templates.Prakash Prajapati
Replace the email template content form if you have any question to if you have any questions. task-1962924 Closes #33520 Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
2019-05-27[REM] multi from ir.actions.act_windowXavier Morel
Task 1843603 * src_model is redundant with binding_model_id * multi -> binding_view_types (if empty => all views) (maybe should be empty by default yo?) * in convert, type => rec.get(type) but no @type possible on <act_window>... * removed deprecated auto_refresh & auto_search (not used anywhere (?)) closes odoo/odoo#24738 Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
2018-07-24[IMP] account, l10n_be_invoice: make templates more modern and updated with ↵Pratima Gupta
Odoo guidelines In this commit we improve templates used in account and l10n_be. Purpose of this commit is to have templates that embed or use standard Odoo email layouts to make them look modern and have a common style across all emails. Main guidelines * better use of div / p / br to try to lessen layout issues, especially when updating templates using the editor; * correctly sequence the templates fields definition; * correctly set templates values notably auto_delete and user_signature fields to avoid confusion; * correctly layout the email content using light notification email. It can either propagate the layout choice through various send mail methods or directly embed the styling in the templates for more technical or complex templates; * use email_formatted computed field when possible to avoid having hand-made from / to addresses; * fix various typos and improve subjects when necessary; Content of emails is not necessarily updated as the purpose of this task is about styling, not content itself. This commit is linked to task ID 1843395 and 1843376 (and 1868112) and to PR #25294 and #25349 (and #25889). Co-Authored-By: Mitali Patel <mpa@odoo.com>
2018-02-28[FIX] *: correcly format amounts in mail templatesChristophe Simonis
2017-09-29[FIX] account: enforce simple res.partner form on send receiptLucas Perais (lpe)
Before this commit, when Sending the receipt by email (payments) the full partner form was displayed in case the partner didn't have an email set. Now, just like invoices, the simpler version is displayed
2017-07-10[IMP] account: Print payment receipts from `Print` menu.jpr-odoo
PURPOSE ======= Users don't find where to print the payment receipts because it's under the `Action` menu SPECIFICATION ============= Allow to print the payment receipt pdf directly from the print menu
2017-05-08[REM] odoo/report: remove deprecated stuffLaurent Smet
- RML Reports - Webkit Reports (most part already removed by 13b9982c6298021289707ed364e3c1d622a09f13) - LocalService in netsvc.py - rename attributes like rml_% to report_% - rename ir.actions.report.xml to ir.actions.report - allow rendering directly on an ir.actions.report by calling render method - remove 'controller' report_type - remove unused res.font stuff - remove print_report method in models.py (not used) - restore removed call to pdftotext process in test_reports
2017-01-10[IMP] account: Add a payment receipt report that can be sent by mailJitendra Prajapati
- create a report for payment to print a receipt. Simple report with the amount received and name of the partner header of the company - add a new action in action menu for print receipt - add a new button action menu to send the receipt by email : STRING of the button = Send Receipt - default template of payment receipt like sales - add chatter history same as sales object - this report use for both ('customer payment' & 'vendor payment)