Adrien Schoffeniels
2d7a49dab1
Purpose: -------- When the property field is added into a form view, the "add a property" button is shown by default. However, most of the time the users won't add properties when opening a form view, making this button take up space for nothing. To alleviate this issue, commit [1] added an option that allows to hide this button, and added actions to allow adding properties from the cog menu instead. Now that properties are being added into several views, one would like this "add properties" button to be hidden by default, and show an entry in the cogmenu allowing add properties by default, without needing to create an action for every view using a property field. Therefore, a new static action "Add Properties" has been added in the form controller that is available if a properties field has been encountered during the parsing of the form view's arch. The "hideAddButton" has been changed into "showAddButton" and now allows to show the "Add a Property" by default. Task-3458627 [1]: https://github.com/odoo/odoo/commit/1f80810e39f811122a65e11cd8cac99aa39a7960 Part-of: odoo/odoo#137589
47 lines
1.8 KiB
XML
47 lines
1.8 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<record forcecreate="True" id="ir_cron_contract_costs_generator" model="ir.cron">
|
|
<field name="name">Fleet: Generate contracts costs based on costs frequency</field>
|
|
<field name="model_id" ref="model_fleet_vehicle_log_contract"/>
|
|
<field name="state">code</field>
|
|
<field name="code">model.run_scheduler()</field>
|
|
<field name="user_id" ref="base.user_root" />
|
|
<field name="interval_number">1</field>
|
|
<field name="interval_type">days</field>
|
|
<field name="numbercall">-1</field>
|
|
<field eval="False" name="doall" />
|
|
</record>
|
|
|
|
<record id="fleet_vehicle_state_new_request" model="fleet.vehicle.state">
|
|
<field name="name">New Request</field>
|
|
<field name="sequence">4</field>
|
|
</record>
|
|
|
|
<record id="fleet_vehicle_state_to_order" model="fleet.vehicle.state">
|
|
<field name="name">To Order</field>
|
|
<field name="sequence">5</field>
|
|
</record>
|
|
|
|
<record id="fleet_vehicle_state_registered" model="fleet.vehicle.state">
|
|
<field name="name">Registered</field>
|
|
<field name="sequence">7</field>
|
|
</record>
|
|
|
|
<record id="fleet_vehicle_state_downgraded" model="fleet.vehicle.state">
|
|
<field name="name">Downgraded</field>
|
|
<field name="sequence">8</field>
|
|
</record>
|
|
|
|
<record id="type_contract_omnium" model="fleet.service.type">
|
|
<field name="name">Omnium</field>
|
|
<field name="category">contract</field>
|
|
</record>
|
|
|
|
<record id="type_contract_leasing" model="fleet.service.type">
|
|
<field name="name">Leasing</field>
|
|
<field name="category">contract</field>
|
|
</record>
|
|
</data>
|
|
</odoo>
|