parent
5695da2277
commit
b363b1f622
|
@ -43,7 +43,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="context" eval="{'default_partner_id':ref('base.main_partner'), 'company_hide':False, 'default_company_id':ref('base.main_company'), 'search_default_my_bank':1}"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to setup a new bank account.
|
||||
</p><p>
|
||||
Configure your company's bank account and select those that must
|
||||
|
|
|
@ -510,7 +510,7 @@
|
|||
<field name="context">{'default_type':'out_invoice', 'type':'out_invoice', 'journal_type': 'sale'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a customer invoice.
|
||||
</p><p>
|
||||
OpenERP's electronic invoicing allows to ease and fasten the
|
||||
|
@ -550,7 +550,7 @@
|
|||
<field name="context">{'default_type': 'in_invoice', 'type': 'in_invoice', 'journal_type': 'purchase'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record a new supplier invoice.
|
||||
</p><p>
|
||||
You can control the invoice from your supplier according to
|
||||
|
@ -571,7 +571,7 @@
|
|||
<field name="context">{'default_type':'out_refund', 'type':'out_refund', 'journal_type': 'sale_refund'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a customer refund.
|
||||
</p><p>
|
||||
A refund is a document that credits an invoice completely or
|
||||
|
@ -607,7 +607,7 @@
|
|||
<field name="context">{'default_type': 'in_refund', 'type': 'in_refund', 'journal_type': 'purchase_refund'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a refund you received from a supplier.
|
||||
</p><p>
|
||||
Instead of creating the supplier refund manually, you can generate
|
||||
|
|
|
@ -79,7 +79,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new fiscal year.
|
||||
</p><p>
|
||||
Define your company's financial year according to your needs. A
|
||||
|
@ -166,7 +166,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{'search_default_draft': 1}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a fiscal period.
|
||||
</p><p>
|
||||
An accounting period typically is a month or a quarter. It
|
||||
|
@ -280,7 +280,7 @@
|
|||
<field name="search_view_id" ref="view_account_search"/>
|
||||
<field name="view_id" ref="view_account_list"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add an account.
|
||||
</p><p>
|
||||
An account is part of a ledger allowing your company
|
||||
|
@ -351,7 +351,7 @@
|
|||
<field name="view_id" ref="view_account_gain_loss_tree"/>
|
||||
<field name="domain">[('currency_id','!=',False)]</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add an account.
|
||||
</p><p>
|
||||
When doing multi-currency transactions, you may loose or gain
|
||||
|
@ -438,7 +438,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_journal_view_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to specify lists of columns to display for a type of journal.
|
||||
</p><p>
|
||||
Journal views determine the way you can record entries in
|
||||
|
@ -564,7 +564,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a journal.
|
||||
</p><p>
|
||||
A journal is used to record transactions of all accounting data
|
||||
|
@ -725,7 +725,7 @@
|
|||
<field name="context">{'journal_type':'bank'}</field>
|
||||
<field name="search_view_id" ref="view_bank_statement_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a bank statement.
|
||||
</p><p>
|
||||
A bank statement is a summary of all financial transactions
|
||||
|
@ -815,7 +815,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_type_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new account type.
|
||||
</p><p>
|
||||
An account type is used to determine how an account is used in
|
||||
|
@ -937,7 +937,7 @@
|
|||
<field name="view_id" ref="view_tax_code_tree"/>
|
||||
<field name="search_view_id" ref="view_tax_code_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new tax code.
|
||||
</p><p>
|
||||
Depending on the country, a tax code is usually a cell to fill
|
||||
|
@ -1282,7 +1282,7 @@
|
|||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="view_account_move_line_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a new journal item.
|
||||
</p><p>
|
||||
This view can be used by accountants in order to quickly record
|
||||
|
@ -1525,7 +1525,7 @@
|
|||
<field name="view_id" ref="view_move_tree"/>
|
||||
<field name="search_view_id" ref="view_account_move_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a journal entry.
|
||||
</p><p>
|
||||
A journal entry consists of several journal items, each of
|
||||
|
@ -1955,7 +1955,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_subscription_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new recurring entry.
|
||||
</p><p>
|
||||
A recurring entry occurs on a recurrent basis from a specific
|
||||
|
@ -2743,7 +2743,7 @@ action = pool.get('res.config').next(cr, uid, [], context)
|
|||
<field name="domain">[('journal_id.type', '=', 'cash')]</field>
|
||||
<field name="context">{'journal_type':'cash'}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new cash log.
|
||||
</p><p>
|
||||
A Cash Register allows you to manage cash entries in your cash
|
||||
|
|
|
@ -54,7 +54,7 @@
|
|||
<field name="domain">[('type','=','contract')]</field>
|
||||
<field name="search_view_id" ref="view_account_analytic_account_overdue_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new contract.
|
||||
</p><p>
|
||||
You will find here the contracts to be renewed because the
|
||||
|
|
|
@ -35,7 +35,7 @@
|
|||
<field name="search_view_id" ref="account_voucher.view_voucher_filter"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new check.
|
||||
</p><p>
|
||||
The check payment form allows you to track the payment you do
|
||||
|
|
|
@ -84,7 +84,7 @@
|
|||
<field name="search_view_id" ref="view_account_followup_filter"/>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define follow-up levels and their related messages.
|
||||
</p><p>
|
||||
For each step, specify the message and the day of delay. Use
|
||||
|
|
|
@ -235,7 +235,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_payment_order_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a payment order.
|
||||
</p><p>
|
||||
A payment order is a payment request from your company to pay a
|
||||
|
|
|
@ -259,7 +259,7 @@
|
|||
<field name="search_view_id" ref="view_voucher_filter_vendor_pay"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new supplier payment.
|
||||
</p><p>
|
||||
OpenERP helps you easily track payments you do and remining
|
||||
|
@ -428,7 +428,7 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a new payment.
|
||||
</p><p>
|
||||
Enter the customer and the payment method and then, either
|
||||
|
|
|
@ -166,7 +166,7 @@
|
|||
<field name="search_view_id" ref="view_voucher_filter_sale"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a sale receipt.
|
||||
</p><p>
|
||||
When the sale receipt is confirmed, you can record the customer
|
||||
|
@ -319,7 +319,7 @@
|
|||
<field name="search_view_id" eval="view_voucher_filter_vendor"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a purchase receipt.
|
||||
</p><p>
|
||||
When the purchase receipt is confirmed, you can record the
|
||||
|
|
|
@ -117,7 +117,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_base_action_rule_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to setup a new automated action rule.
|
||||
</p><p>
|
||||
Use automated actions to automatically trigger actions for
|
||||
|
|
|
@ -168,7 +168,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to setup a new alarm type.
|
||||
</p><p>
|
||||
You can define a customized type of calendar alarm that may be
|
||||
|
|
|
@ -321,7 +321,7 @@
|
|||
<field name="search_view_id" ref="view_crm_meeting_search"/>
|
||||
<field name="context">{"calendar_default_user_id": uid}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to schedule a new meeting.
|
||||
</p><p>
|
||||
The agenda is shared between employees and fully integrated with
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
<field name="search_view_id" ref="crm.view_crm_case_leads_filter"/>
|
||||
<field name="context">{'default_type':'lead', 'stage_type':'lead'}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create an unqualified lead.
|
||||
</p><p>
|
||||
A lead is usually the first step in your sales cycle. It can be
|
||||
|
@ -47,7 +47,7 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new opportunity.
|
||||
</p><p>
|
||||
OpenERP helps you keep track of your sales pipeline to follow
|
||||
|
|
|
@ -64,7 +64,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm.crm_case_stage_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to set a new stage in your lead/opportunity pipeline.
|
||||
</p><p>
|
||||
Stages will allow salespersons to easily track how a specific
|
||||
|
@ -88,7 +88,7 @@
|
|||
<field name="context" eval="{'object_id': ref('model_crm_lead')}"/>
|
||||
<field name="domain">[('object_id.model', '=', 'crm.lead')]</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new sales tag.
|
||||
</p><p>
|
||||
Create specific tags that fit your company's activities
|
||||
|
|
|
@ -69,7 +69,7 @@
|
|||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_phonecalls_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to log the summary of a phone call.
|
||||
</p><p>
|
||||
OpenERP allows you to log inbound calls on the fly to track the
|
||||
|
@ -117,7 +117,7 @@
|
|||
<field name="context" eval="'{\'default_state\':\'open\'}'"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_phonecalls_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to schedule a call
|
||||
</p><p>
|
||||
OpenERP allows you to easily define all the calls to be done
|
||||
|
|
|
@ -48,7 +48,7 @@
|
|||
<field name="domain">[('object_id.model', '=', 'crm.phonecall')]</field>
|
||||
<field name="context" eval="{'object_id': ref('model_crm_phonecall')}"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new category.
|
||||
</p><p>
|
||||
Create specific phone call categories to better define the type of
|
||||
|
|
|
@ -60,7 +60,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new channel.
|
||||
</p><p>
|
||||
Use channels to track the soure of your leads and opportunities. Channels
|
||||
|
@ -145,7 +145,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm_case_section_view_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new sales team.
|
||||
</p><p>
|
||||
Use sales team to organize your different salespersons or
|
||||
|
@ -404,7 +404,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new customer segmentation.
|
||||
</p><p>
|
||||
Create specific categories which you can assign to your
|
||||
|
|
|
@ -71,7 +71,7 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create an opportunity related to this customer.
|
||||
</p><p>
|
||||
Use opportunities to keep track of your sales pipeline, follow
|
||||
|
|
|
@ -16,7 +16,7 @@
|
|||
<field name="domain">[('object_id.model', '=', 'crm.claim')]</field>
|
||||
<field name="context" eval="{'object_id': ref('model_crm_claim')}"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a claim category.
|
||||
</p><p>
|
||||
Create claim categories to better manage and classify your
|
||||
|
@ -66,7 +66,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm_claim_stage_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to setup a new stage in the processing of the claims.
|
||||
</p><p>
|
||||
You can create claim stages to categorize the status of every
|
||||
|
|
|
@ -19,7 +19,7 @@
|
|||
<field name="search_view_id" ref="view_crm_case_helpdesk_filter"/>
|
||||
<field name="context">{"search_default_user_id":uid}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new request.
|
||||
</p><p>
|
||||
Helpdesk and Support allow you to track your interventions.
|
||||
|
|
|
@ -98,7 +98,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new deliver method.
|
||||
</p><p>
|
||||
Each carrier (e.g. UPS) can have several delivery methods (e.g.
|
||||
|
@ -165,7 +165,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a delivery price list for a specific region.
|
||||
</p><p>
|
||||
The delivery price list allows you to compute the cost and
|
||||
|
|
|
@ -316,7 +316,7 @@
|
|||
<field name="res_model">ir.attachment</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new document.
|
||||
</p><p>
|
||||
The Documents repository gives you access to all attachments, such
|
||||
|
|
|
@ -364,7 +364,7 @@
|
|||
<field name="context">{"search_default_upcoming":1}</field>
|
||||
<field name="search_view_id" ref="view_event_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new event.
|
||||
</p><p>
|
||||
OpenERP helps you schedule and efficiently organize your events:
|
||||
|
|
|
@ -51,7 +51,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="search_view_id" ref="view_department_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a department.
|
||||
</p><p>
|
||||
OpenERP's department structure is used to manage all documents
|
||||
|
|
|
@ -14,7 +14,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="hr.view_department_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new department.
|
||||
</p><p>
|
||||
Your departments structure is used to manage all documents
|
||||
|
|
|
@ -194,7 +194,7 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_employee_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new employee.
|
||||
</p><p>
|
||||
With just a quick glance on the OpenERP employee screen, you
|
||||
|
@ -452,7 +452,7 @@
|
|||
<field name="search_view_id" ref="view_job_filter"/>
|
||||
<field name="context">{"search_default_Current":1}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new job position.
|
||||
</p><p>
|
||||
Job Positions are used to define jobs and their requirements.
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new appraisal plan.
|
||||
</p><p>
|
||||
You can define appraisal plans (ex: first interview after 6
|
||||
|
|
|
@ -253,7 +253,7 @@
|
|||
<field name="search_view_id" ref="hr_evaluation.evaluation_search"/>
|
||||
<field name="context">{"search_default_next_month":1}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new appraisal.
|
||||
</p><p>
|
||||
Each employee may be assigned an Appraisal Plan. Such a plan
|
||||
|
@ -362,7 +362,7 @@
|
|||
<field name="context">{'default_is_evaluation': True, "search_default_todo":1,"search_default_user_id":uid}</field>
|
||||
<field name="search_view_id" ref="view_hr_evaluation_interview_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new interview request related to a personnal evaluation.
|
||||
</p><p>
|
||||
Interview requests are usually generated automatically by
|
||||
|
|
|
@ -160,7 +160,7 @@
|
|||
<field name="search_view_id" ref="view_hr_expense_filter"/>
|
||||
<field name="view_id" ref="view_expenses_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register new expenses.
|
||||
</p><p>
|
||||
OpenERP will ensure the whole process is followed; the expense
|
||||
|
|
|
@ -302,7 +302,7 @@
|
|||
<field name="domain">[('type','=','remove')]</field>
|
||||
<field name="search_view_id" ref="view_hr_holidays_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new leave request.
|
||||
</p><p>
|
||||
Once you have recorded your leave request, it will be sent
|
||||
|
|
|
@ -530,7 +530,7 @@
|
|||
<field name="res_model">hr.contribution.register</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new contribution register.
|
||||
</p><p>
|
||||
A contribution register is a third party involved in the salary
|
||||
|
|
|
@ -10,7 +10,7 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_crm_case_jobs_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new job applicant.
|
||||
</p><p>
|
||||
OpenERP helps you track applicants in the recruitment
|
||||
|
|
|
@ -23,7 +23,7 @@
|
|||
<field name="domain">[]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new stage in the recruitment process.
|
||||
</p><p>
|
||||
Define here your stages of the recruitment process, for example:
|
||||
|
@ -392,7 +392,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="hr_recruitment_stage_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new stage in the recruitment process.
|
||||
</p><p>
|
||||
Don't forget to specify the department if your recruitment process
|
||||
|
|
|
@ -105,7 +105,7 @@
|
|||
<field name="context">{"search_default_today":1}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to your timesheets.
|
||||
</p><p>
|
||||
Through this menu you can register and follow your workings
|
||||
|
|
|
@ -131,7 +131,7 @@
|
|||
<field name="context">{'search_default_to_invoice': 1}</field>
|
||||
<field name="search_view_id" ref="account.view_account_analytic_line_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add some tasks work to be invoiced.
|
||||
</p><p>
|
||||
This list shows every task you can invoice to the customer.
|
||||
|
@ -190,7 +190,7 @@
|
|||
<field name="view_id" ref="view_hr_timesheet_invoice_factor_tree"/>
|
||||
<field name="search_view_id" ref="view_hr_timesheet_invoice_factor_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new type of invoicing.
|
||||
</p><p>
|
||||
OpenERP allows you to create default invoicing types. You might
|
||||
|
|
|
@ -178,7 +178,7 @@
|
|||
<field name="context">{'search_default_my_timesheet':1}</field>
|
||||
<field name="search_view_id" ref="view_hr_timesheet_sheet_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to go to your timesheet.
|
||||
</p><p>
|
||||
You must record timesheets every day and confirm at the end
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new product that can be ordered for the lunch.
|
||||
</p><p>
|
||||
We suggest you to put the real price so that the exact due
|
||||
|
@ -35,7 +35,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new cash box.
|
||||
</p><p>
|
||||
You can create on cash box by employee if you want to keep
|
||||
|
|
|
@ -134,7 +134,7 @@
|
|||
<field name="context">{'group_by': []}</field>
|
||||
<field name="search_view_id" ref="view_marketing_campaign_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a marketing campaign.
|
||||
</p><p>
|
||||
OpenERP's marketing campaign allows you to automate communication
|
||||
|
|
|
@ -42,7 +42,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a group of properties.
|
||||
</p><p>
|
||||
Define specific property groups that can be assigned to your
|
||||
|
@ -118,7 +118,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_mrp_property_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new property.
|
||||
</p><p>
|
||||
The Properties in OpenERP are used to select the right bill of
|
||||
|
@ -336,7 +336,7 @@
|
|||
<field name="view_id" ref="mrp_routing_tree_view"/>
|
||||
<field name="search_view_id" ref="mrp_routing_search_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a routing.
|
||||
</p><p>
|
||||
Routings allow you to create and manage the manufacturing
|
||||
|
@ -495,7 +495,7 @@
|
|||
<field name="domain">[('bom_id','=',False)]</field>
|
||||
<field name="search_view_id" ref="view_mrp_bom_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a bill of material.
|
||||
</p><p>
|
||||
Bills of Materials allow you to define the list of required raw
|
||||
|
@ -515,7 +515,7 @@
|
|||
<field name="view_id" ref="mrp_bom_component_tree_view"/>
|
||||
<field name="domain">[('bom_id','!=',False)]</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a component to a bill of material.
|
||||
</p><p>
|
||||
Bills of materials components are components and sub-products
|
||||
|
@ -884,7 +884,7 @@
|
|||
<field name="search_view_id" ref="view_mrp_production_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a manufacturing order.
|
||||
</p><p>
|
||||
A manufacuring order, based on a bill of materials, will
|
||||
|
@ -907,7 +907,7 @@
|
|||
<field name="view_mode">calendar,tree,form,graph</field>
|
||||
<field name="domain">[('state','in',('ready','confirmed','in_production'))]</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new manufacturing order.
|
||||
</p><p>
|
||||
A manufacuring order, based on a bill of materials, will
|
||||
|
@ -1060,7 +1060,7 @@
|
|||
<field name="view_id" ref="mrp_workcenter_tree_view"/>
|
||||
<field name="search_view_id" ref="view_mrp_workcenter_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a work center.
|
||||
</p><p>
|
||||
Work Centers allow you to create and manage manufacturing
|
||||
|
|
|
@ -178,7 +178,7 @@
|
|||
<field name="view_mode">tree,form,gantt,calendar,graph</field>
|
||||
<field name="search_view_id" ref="view_mrp_production_workcenter_form_view_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new work order.
|
||||
</p><p>
|
||||
Work Orders is the list of operations to be performed for each
|
||||
|
@ -199,7 +199,7 @@
|
|||
<field name="domain">[('production_state','in',('ready','confirmed','in_production'))]</field>
|
||||
<field name="view_mode">gantt,tree,form,graph,calendar</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new work order.
|
||||
</p><p>
|
||||
To manufacture or assemble products, and use raw materials and
|
||||
|
|
|
@ -219,7 +219,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_repair_order_form_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a reparation order.
|
||||
</p><p>
|
||||
In a repair order, you can detail the components you remove,
|
||||
|
|
|
@ -169,7 +169,7 @@
|
|||
<field name="view_id" ref="product.product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product.product_search_form_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you sell through
|
||||
|
@ -706,7 +706,7 @@
|
|||
<field name="context" eval="{'default_journal_user': 1, 'default_type': 'cash'}"/>
|
||||
<field name="domain">[('journal_user','=', 1)]</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a payment method.
|
||||
</p><p>
|
||||
Payment methods are defined by accounting journals having the
|
||||
|
|
|
@ -56,7 +56,7 @@
|
|||
<!-- a context is necessary to get the right portal form view -->
|
||||
<field name="context">{'form_view_ref': 'portal.portal_form_view'}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new portal.
|
||||
</p><p>
|
||||
A portal helps defining specific views and rules for a group of
|
||||
|
|
|
@ -71,7 +71,7 @@
|
|||
<field name="context">{"search_default_user_id":'', "search_default_draft":'', "search_default_todo":''}</field>
|
||||
<field name="search_view_id" ref="project_issue.view_project_issue_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create an issue.
|
||||
</p><p>
|
||||
OpenERP's kanban view will help you track easily your current
|
||||
|
|
|
@ -146,7 +146,7 @@
|
|||
<field name="search_view_id" ref="view_procurement_filter"/>
|
||||
<field name="context">{'search_default_current':1}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a procurement order.
|
||||
</p><p>
|
||||
A procurement order is used to record a need for a specific
|
||||
|
|
|
@ -46,7 +46,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="product_pricelist_version_tree_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a pricelist version.
|
||||
</p><p>
|
||||
There can be more than one version of a pricelist, each of
|
||||
|
@ -188,7 +188,7 @@
|
|||
<field name="search_view_id" ref="product_pricelist_view_search" />
|
||||
<field name="context">{"default_type":"sale", "search_default_type":"sale"}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a pricelist.
|
||||
</p><p>
|
||||
A price list contains rules to be evaluated in order to compute
|
||||
|
@ -210,7 +210,7 @@
|
|||
<field name="search_view_id" ref="product_pricelist_view_search" />
|
||||
<field name="context">{"default_type":"purchase", "search_default_type":"purchase"}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a pricelist.
|
||||
</p><p>
|
||||
A price list contains rules to be evaluated in order to compute
|
||||
|
|
|
@ -240,7 +240,7 @@
|
|||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you buy or sell,
|
||||
|
@ -258,7 +258,7 @@
|
|||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you sell, wether it's
|
||||
|
@ -306,7 +306,7 @@
|
|||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you purchase, wheter
|
||||
|
@ -478,7 +478,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="product_uom_tree_view"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new unit of measure.
|
||||
</p><p>
|
||||
You must define a conversion rate between several Units of
|
||||
|
@ -508,7 +508,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new unit of measure category.
|
||||
</p><p>
|
||||
Units of measure belonging to the same category can be
|
||||
|
@ -551,7 +551,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new packaging type.
|
||||
</p><p>
|
||||
The packaging type define the dimensions as well as the number
|
||||
|
|
|
@ -692,7 +692,7 @@
|
|||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="view_task_search_form"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new task.
|
||||
</p><p>
|
||||
OpenERP's project management allows you to manage the pipeline
|
||||
|
@ -795,7 +795,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="task_type_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a stage in the task pipeline.
|
||||
</p><p>
|
||||
Define the steps that will be used in the project from the
|
||||
|
|
|
@ -14,7 +14,7 @@
|
|||
<field name="domain" eval=""/>
|
||||
<field name="search_view_id" ref="view_project_issue_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to report a new issue.
|
||||
</p><p>
|
||||
The OpenERP issues tacker allows you to efficiantly manage things
|
||||
|
|
|
@ -70,7 +70,7 @@
|
|||
<field name="res_model">project.issue.version</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new version.
|
||||
</p><p>
|
||||
Define here the different versions of your products on which
|
||||
|
|
|
@ -97,7 +97,7 @@
|
|||
<field name="context">{'search_default_to_invoice': 1}</field>
|
||||
<field name="view_id" ref="view_account_analytic_line_tree_inherit_account_id"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a work to invoice.
|
||||
</p><p>
|
||||
You will find here all works made on tasks that you can
|
||||
|
@ -129,7 +129,7 @@
|
|||
<field name="domain">[('type','=','normal')]</field>
|
||||
<field name="search_view_id" ref="account_analytic_analysis.view_account_analytic_account_overdue_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a customer contract.
|
||||
</p><p>
|
||||
You will find here the contracts related to your customer
|
||||
|
|
|
@ -82,7 +82,7 @@
|
|||
<field name="context">{'default_type':'in_invoice', 'type':'in_invoice', 'journal_type': 'purchase', 'search_default_draft': 1}</field>
|
||||
<field name="search_view_id" ref="account.view_account_invoice_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a draft invoice.
|
||||
</p><p>
|
||||
Use this menu to control the invoices to be received from your
|
||||
|
@ -354,7 +354,7 @@
|
|||
<field name="view_mode">tree,form,graph,calendar</field>
|
||||
<field name="search_view_id" ref="view_purchase_order_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a request for quotation.
|
||||
</p><p>
|
||||
The quotation contains the history of the discussion/negociation
|
||||
|
@ -378,7 +378,7 @@
|
|||
<field name="context">{'search_default_approved': 1}</field>
|
||||
<field name="search_view_id" ref="view_purchase_order_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a quotation that will be converted into a purchase order.
|
||||
</p><p>
|
||||
Use this menu to search within your purchase orders by
|
||||
|
|
|
@ -163,7 +163,7 @@
|
|||
<field name="context">{"search_default_create_uid":uid}</field>
|
||||
<field name="search_view_id" ref="view_purchase_requisition_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new purchase requisition process.
|
||||
</p><p>
|
||||
A purchase requisition is the step before a request for quotation.
|
||||
|
|
|
@ -9,7 +9,7 @@
|
|||
<field name="context">{'search_default_partner_id': active_id}</field>
|
||||
<field name="groups_id" eval="[(4, ref('base.group_sale_salesman'))]"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a quotation or sale order for this customer.
|
||||
</p><p>
|
||||
OpenERP will help you efficiently handle the complete sale flow:
|
||||
|
|
|
@ -59,7 +59,7 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_shop_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new sale shop.
|
||||
</p><p>
|
||||
Each quotation or sale order must be linked to a shop. The
|
||||
|
@ -400,7 +400,7 @@
|
|||
<field name="search_view_id" ref="view_sales_order_filter"/>
|
||||
<field name="context">{"search_default_sales":1}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a quotation that can be converted into a sale
|
||||
order.
|
||||
</p><p>
|
||||
|
@ -442,7 +442,7 @@
|
|||
<field name="context">{"search_default_draft":1}</field>
|
||||
<field name="search_view_id" ref="view_sales_order_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a quotation, the first step of a new sale.
|
||||
</p><p>
|
||||
OpenERP will help you handle efficiently the complete sale flow:
|
||||
|
@ -453,8 +453,7 @@
|
|||
order, and allow your customers to keep track of the evolution
|
||||
of the sale order.
|
||||
</p>
|
||||
</p>
|
||||
</field>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_sale_quotations"
|
||||
|
|
|
@ -135,7 +135,7 @@
|
|||
<field name="context" eval="'{\'search_default_product_id\': [active_id]}'"/>
|
||||
<field name="search_view_id" ref="view_move_search_reception_incoming_picking"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a reception for this product.
|
||||
</p><p>
|
||||
Here you will find the history of all receptions related to
|
||||
|
@ -156,7 +156,7 @@
|
|||
<field name="context" eval="'{\'search_default_product_id\': [active_id]}'"/>
|
||||
<field name="search_view_id" ref="view_move_search_reception_outcoming_picking"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a delivery order for this product.
|
||||
</p><p>
|
||||
Here you will find the history of all past deliveries related to
|
||||
|
|
|
@ -201,7 +201,7 @@
|
|||
<field name="view_id" ref="view_inventory_tree"/>
|
||||
<field name="search_view_id" ref="view_inventory_filter"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start an inventory.
|
||||
</p><p>
|
||||
Periodical Inventories are used to count the number of products
|
||||
|
@ -265,7 +265,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_tracking_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a tracking number.
|
||||
</p><p>
|
||||
This is the list of all your packs. When you select a Pack, you
|
||||
|
@ -431,7 +431,7 @@
|
|||
<field name="search_view_id" ref="search_product_lot_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a serial number.
|
||||
</p><p>
|
||||
This is the list of all the production lots you recorded. When
|
||||
|
@ -614,7 +614,7 @@
|
|||
<field name="search_view_id" ref="view_location_search"/>
|
||||
<field name="context">{'search_default_in_location':1}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a location.
|
||||
</p><p>
|
||||
Define your locations to reflect your warehouse structure and
|
||||
|
@ -654,7 +654,7 @@
|
|||
<field name="view_type">tree</field>
|
||||
<field name="view_id" ref="view_location_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a location.
|
||||
</p><p>
|
||||
This is the structure of your company's warehouses and
|
||||
|
@ -712,7 +712,7 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_warehouse_tree"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new warehouse.
|
||||
</p>
|
||||
</field>
|
||||
|
@ -956,7 +956,7 @@
|
|||
<field name="context">{'contact_display': 'partner_address', 'search_default_available': 1}</field>
|
||||
<field name="search_view_id" ref="view_picking_internal_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create an internal move request.
|
||||
</p><p>
|
||||
Most operations are prepared automatically by OpenERP according
|
||||
|
@ -1067,7 +1067,7 @@
|
|||
<field name="context">{'default_type': 'out', 'contact_display': 'partner_address'}</field>
|
||||
<field name="search_view_id" ref="view_picking_out_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a delivery order.
|
||||
</p><p>
|
||||
This is the list of all delivery orders that have to be
|
||||
|
@ -1177,7 +1177,7 @@
|
|||
<field name="context">{'contact_display': 'partner_address', 'default_type': 'in'}</field>
|
||||
<field name="search_view_id" ref="view_picking_in_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create an incoming shipment.
|
||||
</p><p>
|
||||
The Incoming Shipments is the list of all orders you will
|
||||
|
@ -1372,7 +1372,7 @@
|
|||
<field name="search_view_id" ref="view_move_search"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a stock movement.
|
||||
</p><p>
|
||||
This menu gives you the full traceability of inventory
|
||||
|
|
|
@ -346,7 +346,7 @@
|
|||
<field name="view_id" ref="view_survey_kanban"></field>
|
||||
<field name="search_view_id" ref="survey_search"/>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new survey.
|
||||
</p><p>
|
||||
You can create survey for different purposes: recruitment
|
||||
|
|
Loading…
Reference in New Issue