summaryrefslogtreecommitdiff
path: root/addons/purchase/views/purchase_views.xml
diff options
context:
space:
mode:
authorLaurent Stukkens (LTU) <ltu@odoo.com>2020-03-17 09:54:51 +0000
committerThibault Delavallée <tde@odoo.com>2020-03-31 08:08:22 +0000
commit38294dbc99a344ea1a3c7e534ddf7d92b17b0be9 (patch)
tree6f805fad72abcfd3c4c08fca201f5c256b1c419c /addons/purchase/views/purchase_views.xml
parent30ab8ac0222514a37d232e63da925ac6fdfe96b1 (diff)
[IMP] purchase, purchase_requisition: improve UX
Several improvements in order to improve user interface are done here. [IMP] purchase: Prevent create PO&RFQ in calendar It was possible to create PO's and RFQ's from the calendar view. The Product Owner wanted to prevent the users from doing so. [IMP] purchase: Add tooltip to Receipt Date [FIX] purchase: Align report & stat button data on product form The use of Last 365 days time_range in the purchase analysis was automatically excluding today's purchases wich was confusing users as the stat button info was taking those into account. Different behaviours were implemented for product template and product product in the filters that were used which makes no sense. Use of context_today() instead of datetime.now() in order to take the user's timezone into account. [IMP] purchase: Use relevant dates for RFQ's and PO's in calendar view The date used in order to display RFQs and POs in the calendar was date_planned which is not mandatory and so not always filled. It has been decided to use the order_date for the RFQ's and date_approve for PO's. [IMP] purchase_requisition: Making Agreement selection type more explicit [IMP] purchase: Show UOM menu only if installed [IMP] purchase: Add product variant in settings [IMP] purchase: Remove Favorites predefined filters [IMP] purchase: Rephrase PO action helper [IMP] purchase: Allow open/edit Agreement Type [IMP] purchase: Rephrase RFQ action helper [IMP] purchase: Remove PO's and RFQ's name from fields in calendar The Product Owner originally wanted to have a link on the PO name field that was shown in the calendat popover. As the Edit button already allows to edit the PO's or RFQ's from the popover it was decided to simply remove the field (as it was already displayed at the top of the popover) [IMP] purchase: Open the right view when click on Reporting top menu Task ID #2196688 Closes #47810 Related: odoo/enterprise#9294 Related: odoo/upgrade#961 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Diffstat (limited to 'addons/purchase/views/purchase_views.xml')
-rw-r--r--addons/purchase/views/purchase_views.xml35
1 files changed, 23 insertions, 12 deletions
diff --git a/addons/purchase/views/purchase_views.xml b/addons/purchase/views/purchase_views.xml
index de63c1550c4..da5d47989b4 100644
--- a/addons/purchase/views/purchase_views.xml
+++ b/addons/purchase/views/purchase_views.xml
@@ -24,19 +24,31 @@
<menuitem
id="menu_product_in_config_purchase" name="Products"
- parent="menu_purchase_config" sequence="30" groups="base.group_no_one"/>
+ parent="menu_purchase_config" sequence="30"/>
+
+ <record model="ir.ui.menu" id="menu_product_in_config_purchase">
+ <field name="groups_id" eval="False"/>
+ </record>
+
+ <menuitem id="menu_product_attribute_action"
+ action="product.attribute_action" name="Product Attributes"
+ parent="purchase.menu_product_in_config_purchase" groups="product.group_product_variant" sequence="1"/>
<menuitem
action="product.product_category_action_form" id="menu_product_category_config_purchase"
- parent="purchase.menu_product_in_config_purchase" sequence="1" />
+ parent="purchase.menu_product_in_config_purchase" sequence="3" />
- <menuitem
- action="uom.product_uom_categ_form_action" id="menu_purchase_uom_categ_form_action"
- parent="purchase.menu_product_in_config_purchase" sequence="10" groups="uom.group_uom"/>
+ <menuitem
+ id="menu_unit_of_measure_in_config_purchase" name="Units of Measures"
+ parent="menu_purchase_config" sequence="40" groups="uom.group_uom" />
<menuitem
action="uom.product_uom_form_action" id="menu_purchase_uom_form_action"
- parent="purchase.menu_product_in_config_purchase" sequence="5" groups="uom.group_uom"/>
+ parent="purchase.menu_unit_of_measure_in_config_purchase" sequence="5" groups="uom.group_uom"/>
+
+ <menuitem
+ action="uom.product_uom_categ_form_action" id="menu_purchase_uom_categ_form_action"
+ parent="purchase.menu_unit_of_measure_in_config_purchase" sequence="10" groups="uom.group_uom"/>
<!-- Products Control Menu -->
<menuitem id="menu_purchase_products" name="Products" parent="purchase.menu_purchase_root" sequence="5"/>
@@ -87,9 +99,8 @@
<field name="model">purchase.order</field>
<field name="priority" eval="2"/>
<field name="arch" type="xml">
- <calendar string="Calendar View" date_start="date_planned" color="partner_id" hide_time="true" event_limit="5">
+ <calendar string="Calendar View" date_start="date_calendar_start" color="partner_id" hide_time="true" event_limit="5" create="false">
<field name="currency_id" invisible="1"/>
- <field name="name"/>
<field name="partner_ref"/>
<field name="amount_total" widget="monetary"/>
<field name="partner_id" filters="1"/>
@@ -548,8 +559,8 @@
<p class="o_view_nocontent_smiling_face">
Create a request for quotation
</p><p>
- The quotation contains the history of the discussion
- you had with your vendor.
+ The requests for quotation are documents that will be sent to your suppliers to request prices for different products you consider buying.
+ Once an agreement has been found with the supplier, they will be confirmed and turned into purchase orders.
</p>
</field>
</record>
@@ -568,9 +579,9 @@
<field name="context">{}</field>
<field name="help" type="html">
<p class="o_view_nocontent_smiling_face">
- Create a quotation
+ Create a purchase order
</p><p>
- It will be converted into a purchase order.
+ Once you ordered your products to your supplier, confirm your request for quotation and it will turn into a purchase order.
</p>
</field>
</record>