Purpose: Having the res_group defined in base and sales_team auto installed with mail doens't make sense. - Move the empty res_config class and the related view from base_setup to sales_team (base_setup only contains the 'General Settings' model and views - Move the 'sale' related content from product to sale module (Access rights, menuitems,...) - Set sales_team at autoinstall False. The module is installed when needed by crm or sale for example - Set sales_team as a dependency of voip. (Access rights defined for configuration purpose) - Set sales_team ad a dependency of subscription (Access rights issue too) [FIX] account: move some ir.model.access to sale module [FIX] payment: Move some ir.rule to website_sale [FIX] stock: move some ir.model.access rule to sale_stock [FIX] project: Move some ir.model.access rules to crm_project_issue [FIX] mrp: Move some ir.model.access rules to sale_mrp [FIX] calendar: move some ir.model.access rules to crm Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes sales_team.group_sale_manager. [ADD] sales_team: See own documents => See only his sales team Moved the "User: Own Leads Only", "User: All Leads" and "Manager" groups from sale and crm into sales_team module. Add the record rules so that user can see only his Own Sales Team if "See Own Leads" is sales right and can see all sales teams if he is having sales rights of "See All Leads" or manager.
67 lines
2.8 KiB
XML
67 lines
2.8 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<openerp>
|
|
<data>
|
|
|
|
<!-- Top menu item -->
|
|
<!--
|
|
This menu item's purpose is to overwrite another one defined in
|
|
the base module in order to set new groups.
|
|
-->
|
|
<menuitem name="CRM"
|
|
id="sales_team.menu_base_partner"
|
|
web_icon="crm,static/description/icon.png"/>
|
|
|
|
<menuitem id="base.menu_crm_config_lead" name="Leads & Opportunities"
|
|
parent="sales_team.menu_sale_config" sequence="5" groups="sales_team.group_sale_manager"/>
|
|
|
|
<menuitem id="base.menu_crm_config_opportunity" name="Opportunities"
|
|
parent="sales_team.menu_sale_config" sequence="1" groups="sales_team.group_sale_manager"/>
|
|
|
|
<menuitem id="sales_team.menu_sale_config_sales" name="Sales"
|
|
parent="sales_team.menu_sale_config" sequence="0" groups="sales_team.group_sale_manager"/>
|
|
|
|
<!-- CRM.LOST.REASON VIEWS -->
|
|
<record id="crm_lost_reason_view_search" model="ir.ui.view">
|
|
<field name="name">crm.lost.reason.view.search</field>
|
|
<field name="model">crm.lost.reason</field>
|
|
<field name="arch" type="xml">
|
|
<search string="Search Opportunities">
|
|
<filter string="Include archived" name="archived"
|
|
domain="['|', ('active', '=', True), ('active', '=', False)]"/>
|
|
</search>
|
|
</field>
|
|
</record>
|
|
|
|
<record id="crm_lost_reason_view_form" model="ir.ui.view">
|
|
<field name="name">crm.lost.reason.form</field>
|
|
<field name="model">crm.lost.reason</field>
|
|
<field name="arch" type="xml">
|
|
<form string="Channel">
|
|
<group>
|
|
<field name="name"/>
|
|
<field name="active"/>
|
|
</group>
|
|
</form>
|
|
</field>
|
|
</record>
|
|
<record id="crm_lost_reason_action" model="ir.actions.act_window">
|
|
<field name="name">Lost Reasons</field>
|
|
<field name="res_model">crm.lost.reason</field>
|
|
<field name="view_type">form</field>
|
|
<field name="view_mode">tree,form</field>
|
|
<field name="help" type="html">
|
|
<p class="oe_view_nocontent_create">
|
|
Click to define a new lost reason.
|
|
</p><p>
|
|
Use lost reasons to explain why an opportunity is lost.
|
|
</p><p>
|
|
Some examples of lost reasons: "We don't have people/skill", "Price too high"
|
|
</p>
|
|
</field>
|
|
</record>
|
|
|
|
<menuitem action="crm_lost_reason_action" id="menu_crm_lost_reason" parent="base.menu_crm_config_lead" sequence="6" groups="base.group_no_one"/>
|
|
|
|
</data>
|
|
</openerp>
|