Yannick Tivisse
4aa2fad313
PURPOSE ======= The field auto_confirm is complicated to understand for common users. Furthermore, on of its options is only useful for authorize module. SPECIFICATION ============= Remove the auto_confirm field. The destinies of its options are the following: - none: Simply disappear. - authorize: Become capture_manually. It has nothing to do with the auto_confirm field has it's related to the autorize module (And could be extended to other payment acquirers too). - confirm_so: Remove it. Will be automatic, and we will always validate the sales order and generate the accounting entries on acquirer validation. - generate_and_pay_invoice: Is linked to the journal_id. The field journal_id is always set and we will use it to validate the sales order and generate the accounting entries on acquirer validation. Bonus: website_sale: Allow to create/validate invoice automatically on `Mark as Paid`
23 lines
1.1 KiB
XML
23 lines
1.1 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<record id="payment_acquirer_view_form_inherit_transfer" model="ir.ui.view">
|
|
<field name="name">payment.acquirer.view.form.inherit.transfer</field>
|
|
<field name="model">payment.acquirer</field>
|
|
<field name="inherit_id" ref="payment.acquirer_form"/>
|
|
<field name="arch" type="xml">
|
|
<page name="acquirer_credentials" position="attributes">
|
|
<attribute name="attrs">{'invisible': [('provider', '=', 'transfer')]}</attribute>
|
|
</page>
|
|
<field name="done_msg" position="attributes">
|
|
<attribute name="attrs">{'invisible': [('provider', '=', 'transfer')]}</attribute>
|
|
</field>
|
|
<field name="cancel_msg" position="attributes">
|
|
<attribute name="attrs">{'invisible': [('provider', '=', 'transfer')]}</attribute>
|
|
</field>
|
|
<field name="error_msg" position="attributes">
|
|
<attribute name="attrs">{'invisible': [('provider', '=', 'transfer')]}</attribute>
|
|
</field>
|
|
</field>
|
|
</record>
|
|
</odoo>
|