…ase order

FIX case of tests

DEL refund journal field on sale order type, now same invoice journal should be used for refunds

FIX case of test

FIX sale order test

Conflicts:
	sale_order_type/models/sale_order.py
	sale_order_type/models/stock_picking.py
	sale_order_type/tests/test_sale_order_type.py

ADD Payment Term, Pricelist and Incoterm to sale order type

Conflicts:
	sale_order_type/models/sale_order.py
	sale_order_type/tests/test_sale_order_type.py
	sale_order_type/views/sale_order_type_view.xml

ADD sale type for invoices

Conflicts:
	sale_order_type/README.rst
	sale_order_type/models/account_invoice.py
	sale_order_type/tests/test_sale_order_type.py

IMP description

ADD multicompany rule for sale.order.type and company in sale.order.type (OCA#292)

[IMP] sale_order_type: multicompany handle
Conflicts:
	sale_order_type/models/sale_order_type.py

… security

[UPD] Update sale_order_type.pot

The other one is a fake one that is dangling

If a contact doesn't have sale type, we use the commercial partner one.

Currently translated at 100.0% (31 of 31 strings)

Translation: sale-workflow-11.0/sale-workflow-11.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-11-0/sale-workflow-11-0-sale_order_type/es/

Currently translated at 100.0% (31 of 31 strings)

Translation: sale-workflow-12.0/sale-workflow-12.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-12-0/sale-workflow-12-0-sale_order_type/zh_CN/

Currently translated at 83.9% (26 of 31 strings)

Translation: sale-workflow-12.0/sale-workflow-12.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-12-0/sale-workflow-12-0-sale_order_type/it/

In the original onchange method by odoo, this return an dict with values(warnings and domians), but when inherit this method in this module they not return this dict. Because of this the alert setting in the partner was no working.

* Switch onchange on the main field to computed writable fields
* Record rule is not up to v13
* Added migration script for record rule
* Proper payment term field name in invoice
* Realign tests

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-13.0/sale-workflow-13.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-13-0/sale-workflow-13-0-sale_order_type/

…ide unnecessary features

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-13.0/sale-workflow-13.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-13-0/sale-workflow-13-0-sale_order_type/

Currently translated at 100.0% (32 of 32 strings)

Translation: sale-workflow-13.0/sale-workflow-13.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-13-0/sale-workflow-13-0-sale_order_type/es/

As the field is set as required on the Form view, any other module
that does not depend on sale_order_type and that uses test class
Form on sale.order would fail with "type_id is a required field"
if no default value is defined.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-13.0/sale-workflow-13.0-sale_order_type
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-13-0/sale-workflow-13-0-sale_order_type/

Actualy the field type is showed in all of the invoice types (customer and vendors), but the for the vendors invoices, it's not necesary to show it . Also the same apply for the compute method for that field.