simplification of payments objects and refactoring of the code
* registering payment(s) from the list of invoice now generate a single payment per invoice selected
* no more abstract object for payments/payment wizard as the logic is now really simple:
- group_invoices option is now removed and we never try to group payments based on the currency/customer of whatsoever (see above),
- the payment amount is the full residual amount of invoice and users cannot change it anymore
* partner_bank_account_id not required as soon as visible (depends on the payment method)
* refactoring to name tags and allow easier inheritance via xpath
part of task #1918423
22 lines
1.1 KiB
XML
22 lines
1.1 KiB
XML
<?xml version="1.0"?>
|
|
<odoo>
|
|
<data>
|
|
<record id="view_account_payment_form_inherit_payment" model="ir.ui.view">
|
|
<field name="name">view.account.payment.form.inherit.payment</field>
|
|
<field name="model">account.payment</field>
|
|
<field name="inherit_id" ref="account.view_account_payment_form"/>
|
|
<field name="arch" type="xml">
|
|
<xpath expr='//group[2]' position="inside">
|
|
<field name="payment_transaction_id" groups="base.group_no_one" attrs="{'invisible': [('payment_method_code', '!=', 'electronic')]}"/>
|
|
</xpath>
|
|
<field name="payment_method_id" position="after">
|
|
<field name="payment_method_code" invisible="1"/>
|
|
<field name="payment_token_id" options="{'no_create': True}"
|
|
attrs="{'invisible': [('payment_method_code', '!=', 'electronic')],
|
|
'required': [('payment_method_code', '=', 'electronic')]}"/>
|
|
</field>
|
|
</field>
|
|
</record>
|
|
</data>
|
|
</odoo>
|