[IMP] core: menu tip ux/ui improvement
We would like to make the "no item found" screens more appealing.
Before this commit, it shows a small help tip in the top-left
corner of the screen, just below the "Create" button.
With this commit, these help tips have been replaced by onboarding
screens, which consist of a picture and some text below, both of which
are horizontally centered.
The texts have been slightly changed, so that they are shorter and clearer.
Considered modules:
(A)
account,
account_asset,
account_budget,
account_test,
account_voucher,
analytic
(B)
barcodes,
base,
base_automation,
board
(C)
calendar,
contacts,
crm
(D)
delivery
(E)
event
(F)
fleet
(G)
gamification,
google_drive
(H)
hr,
hr_attendance,
hr_contract,
hr_expense,
hr_gamification,
hr_holidays,
hr_payroll,
hr_recruitment,
hr_timesheet
(I)
im_livechat
(L)
l10n_fr_sale_closing,
link_tracker,
lunch
(M)
mail,
maintenance,
mass_mailing,
membership,
mrp
(N)
note
(P)
payment,
point_of_sale,
post_mercury,
pos_restaurant,
product,
project,
purchase,
purchase_requisition
(R)
rating,
repair,
resource
(S)
sale,
sale_timesheet,
sales_team,
stock,
stock_account,
stock_landed_costs,
stock_picking_batch,
survey
(U)
utm
(W)
web,
website,
website_blog,
website_customer,
website_event_track,
website_forum,
website_quote,
website_sale,
website_sale_digital,
website_slides
This commit is contained in:
committed by
Alexandre Kühn
parent
1f1c5f62c7
commit
a87d761fdb
@@ -1,12 +1,16 @@
|
||||
.o_kanban_view.o_kanban_dashboard.o_account_kanban {
|
||||
|
||||
&:not(.o_kanban_nocontent) .o_account_dashboard_header{
|
||||
&.o_kanban_ungrouped .o_account_dashboard_header {
|
||||
margin: (0 - @o-kanban-record-margin) (@o-kanban-record-margin - @odoo-horizontal-padding) @o-kanban-record-margin;
|
||||
}
|
||||
|
||||
.o_account_dashboard_header {
|
||||
.o-flex(1, 0, 100%);
|
||||
.o-flex-flow(column, nowrap);
|
||||
.o-align-self(flex-start);
|
||||
width: 100%;
|
||||
height: auto; // cancel o_form_view height 100%, which hides the help tip message at the bottom of the screen
|
||||
min-height: 0%; // cancel o_form_view min-height 100%, which hides the help tip message at the bottom of the screen
|
||||
background-color: @odoo-view-background-color;
|
||||
|
||||
.o_form_statusbar {
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">Create the first cash rounding</p>
|
||||
<p class="o_view_nocontent_smiling_face">Create the first cash rounding</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
@@ -663,16 +663,10 @@
|
||||
<field name="context">{'type':'out_invoice', 'journal_type': 'sale'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter_inherit_invoices"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a customer invoice.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a customer invoice
|
||||
</p><p>
|
||||
Odoo's electronic invoicing allows to ease and fasten the
|
||||
collection of customer payments. Your customer receives the
|
||||
invoice by email and he can pay online and/or import it
|
||||
in his own system.
|
||||
</p><p>
|
||||
The discussions with your customer are automatically displayed at
|
||||
the bottom of each invoice.
|
||||
Create invoices, register payments and keep track of the discussions with your customers.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -704,11 +698,11 @@
|
||||
<field name="context">{'default_type': 'out_refund', 'type': 'out_refund', 'journal_type': 'sale'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter_inherit_credit_notes"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a credit note.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a credit note
|
||||
</p><p>
|
||||
Note that the easiest way to create a credit note is to do it directly form
|
||||
the customer invoice, to refund it totally or partially.
|
||||
Note that the easiest way to create a credit note is to do it directly
|
||||
from the customer invoice.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -742,10 +736,10 @@
|
||||
<field name="context">{'default_type': 'in_invoice', 'type': 'in_invoice', 'journal_type': 'purchase'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter_inherit_invoices"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record a new vendor bill.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a new vendor bill
|
||||
</p><p>
|
||||
You can control the invoice from your vendor according to
|
||||
You can control the invoice from your vendor based on
|
||||
what you purchased or received.
|
||||
</p>
|
||||
</field>
|
||||
@@ -778,8 +772,10 @@
|
||||
<field name="context">{'default_type': 'in_refund', 'type': 'in_refund', 'journal_type': 'purchase'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter_inherit_credit_notes"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record a new vendor credit note.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a vendor credit note
|
||||
</p><p>
|
||||
Note that the easiest way to create a vendor credit note it to do it directly from the vendor bill.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -323,9 +323,10 @@
|
||||
<field name="context">{'search_default_dashboard':1}</field>
|
||||
<field name="domain">[('belongs_to_company', '=', True)]</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
This is the accounting dashboard. If you have not yet
|
||||
installed a chart of account, please install one first.
|
||||
<p class="o_view_nocontent_neutral_face">
|
||||
This is the accounting dashboard
|
||||
</p><p>
|
||||
If you have not installed a chart of account, please install one first.<br/>
|
||||
<a type="action" name="%(open_account_charts_modules)d">Browse available countries.</a>
|
||||
</p>
|
||||
</field>
|
||||
|
||||
@@ -192,10 +192,10 @@
|
||||
<field name="domain">[('partner_type', '=', 'customer')]</field>
|
||||
<field name="view_id" ref="view_account_payment_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a payment
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Register a payment
|
||||
</p><p>
|
||||
Payments are used to register operations made on bank/cash accounts (send, collect or transfer money) and will create a journal entry upon validation.
|
||||
Payments are used to register liquidity movements. You can process those payments by your own means or by using installed facilities.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -209,10 +209,10 @@
|
||||
<field name="domain">[('partner_type', '=', 'supplier')]</field>
|
||||
<field name="view_id" ref="view_account_supplier_payment_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a payment
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Register a payment
|
||||
</p><p>
|
||||
Payments are used to register operations made on bank/cash accounts (send, collect or transfer money) and will create a journal entry upon validation.
|
||||
Payments are used to register liquidity movements. You can process those payments by your own means or by using installed facilities.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -153,8 +153,8 @@
|
||||
<field name="search_view_id" ref="view_account_search"/>
|
||||
<field name="view_id" ref="view_account_list"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add an account.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new account
|
||||
</p><p>
|
||||
An account is part of a ledger allowing your company
|
||||
to register all kinds of debit and credit transactions.
|
||||
@@ -438,8 +438,8 @@
|
||||
<field name="domain">[('type', '=', 'bank')]</field>
|
||||
<field name="context">{'default_type': 'bank'}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a bank account.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a bank account
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -455,15 +455,11 @@
|
||||
(0, 0, {'view_mode': 'kanban', 'view_id': ref('account_journal_view_kanban')}),
|
||||
(0, 0, {'view_mode': 'form', 'view_id': ref('view_account_journal_form')})]"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a journal.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a journal
|
||||
</p><p>
|
||||
A journal is used to record transactions of all accounting data
|
||||
related to the day-to-day business.
|
||||
</p><p>
|
||||
A typical company may use one journal per payment method (cash,
|
||||
bank accounts, checks), one purchase journal, one sales journal
|
||||
and one for miscellaneous information.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -508,8 +504,8 @@
|
||||
<field name="res_model">account.account.tag</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -712,8 +708,8 @@
|
||||
<field name="context">{'journal_type':'bank'}</field>
|
||||
<field name="search_view_id" ref="view_bank_statement_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a bank statement.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Register a bank statement
|
||||
</p><p>
|
||||
A bank statement is a summary of all financial transactions
|
||||
occurring over a given period of time on a bank account. You
|
||||
@@ -799,8 +795,8 @@
|
||||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="view_bank_statement_line_search"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
A bank statement line is a financial transaction on a bank account.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
A bank statement line is a financial transaction on a bank account
|
||||
</p><p>
|
||||
Odoo allows you to reconcile a statement line directly with
|
||||
the related sale or puchase invoice(s).
|
||||
@@ -913,8 +909,8 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_reconcile_model_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a reconciliation model.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new reconciliation model
|
||||
</p><p>
|
||||
Those can be used to quickly create a journal items when reconciling
|
||||
a bank statement or an account.
|
||||
@@ -975,8 +971,8 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_type_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new account type.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Define a new account type
|
||||
</p><p>
|
||||
An account type is used to determine how an account is used in
|
||||
each journal. The deferral method of an account type determines
|
||||
@@ -1123,6 +1119,11 @@
|
||||
<field name="domain" eval="False"/> <!-- Force empty -->
|
||||
<field name="context">{'search_default_sale': True, 'search_default_purchase': True, 'active_test': False}</field>
|
||||
<field name="view_id" ref="view_tax_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new tax
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_tax_form" id="menu_action_tax_form" parent="account_account_menu" sequence="1"/>
|
||||
|
||||
@@ -1533,16 +1534,11 @@
|
||||
<field name="search_view_id" ref="view_account_move_filter"/>
|
||||
<field name="context">{'search_default_misc_filter':1, 'view_no_maturity': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a journal entry.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a journal entry
|
||||
</p><p>
|
||||
A journal entry consists of several journal items, each of
|
||||
which is either a debit or a credit transaction.
|
||||
</p><p>
|
||||
Odoo automatically creates one journal entry per accounting
|
||||
document: invoice, refund, vendor payment, bank statements,
|
||||
etc. So, you should record journal entries manually only/mainly
|
||||
for miscellaneous operations.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -2049,6 +2045,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_position_template_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new fiscal position
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="account_bank_statement_pivot" model="ir.ui.view">
|
||||
@@ -2085,8 +2086,8 @@
|
||||
<field name="domain">[('journal_id.type', '=', 'cash')]</field>
|
||||
<field name="context">{'journal_type':'cash'}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new cash log.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new cash log
|
||||
</p><p>
|
||||
A Cash Register allows you to manage cash entries in your cash
|
||||
journals. This feature provides an easy way to follow up cash
|
||||
@@ -2133,6 +2134,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="context">{'search_default_filter_to_sell': 1}</field>
|
||||
<field name="view_id" ref="product_product_view_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new sellable product
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="product_product_action_purchasable" model="ir.actions.act_window">
|
||||
@@ -2143,6 +2149,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="context">{'search_default_filter_to_purchase': 1}</field>
|
||||
<field name="view_id" ref="product_product_view_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new purchasable product
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="product_product_menu_sellable" name="Sellable Products" action="product_product_action_sellable" parent="account.menu_finance_receivables_master_data" sequence="100"/>
|
||||
@@ -2275,6 +2286,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_group_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new account group
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
</data>
|
||||
|
||||
@@ -179,6 +179,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="search_view_id" ref="view_account_position_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new fiscal position
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
||||
@@ -64,7 +64,9 @@
|
||||
<field name="domain">[('asset_category_id.type', '=', 'purchase')]</field>
|
||||
<field name="context">{}</field> <!-- force empty -->
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No content
|
||||
</p><p>
|
||||
From this report, you can have an overview on all depreciations. The
|
||||
search bar can also be used to personalize your assets depreciation reporting.
|
||||
</p>
|
||||
|
||||
@@ -214,8 +214,8 @@
|
||||
<field name="view_id" ref="crossovered_budget_view_tree"/>
|
||||
<field name="search_view_id" ref="view_crossovered_budget_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new budget.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new budget
|
||||
</p><p>
|
||||
A budget is a forecast of your company's income and/or expenses
|
||||
expected for a period in the future. A budget is defined on some
|
||||
|
||||
@@ -72,8 +72,8 @@ Example:
|
||||
<field name="res_model">accounting.assert.test</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create Accounting Test.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new accounting test
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -295,8 +295,8 @@
|
||||
<field name="search_view_id" ref="view_voucher_filter_sale"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a sale receipt.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new sale receipt
|
||||
</p><p>
|
||||
When the sale receipt is confirmed, you can record the customer
|
||||
payment related to this sales receipt.
|
||||
@@ -410,8 +410,8 @@
|
||||
<field name="search_view_id" eval="view_voucher_filter_vendor"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to register a purchase receipt.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Register a new purchase receipt
|
||||
</p><p>
|
||||
When the purchase receipt is confirmed, you can record the
|
||||
vendor payment related to this purchase receipt.
|
||||
|
||||
@@ -35,8 +35,8 @@
|
||||
<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 add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -66,8 +66,8 @@
|
||||
<field name="view_id" ref="view_account_analytic_line_tree"/>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No activity yet on this account.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No activity yet on this account
|
||||
</p><p>
|
||||
In Odoo, sales orders and projects are implemented using
|
||||
analytic accounts. You can track costs and revenues to analyse
|
||||
@@ -198,8 +198,8 @@
|
||||
<field name="context">{'search_default_active':1}</field>
|
||||
<field name="view_id" ref="view_account_analytic_account_list"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add an analytic account.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new analytic account
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -213,8 +213,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add an analytic account.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new analytic account
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -330,8 +330,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="search_view_id" ref="analytic.view_account_analytic_line_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No activity yet.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No activity yet
|
||||
</p><p>
|
||||
In Odoo, sales orders and projects are implemented using
|
||||
analytic accounts. You can track costs and revenues to analyse
|
||||
|
||||
@@ -57,8 +57,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a Barcode Nomenclature .
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new barcode nomenclature
|
||||
</p><p>
|
||||
A barcode nomenclature defines how the point of sale identify and interprets barcodes
|
||||
</p>
|
||||
|
||||
@@ -79,8 +79,8 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_base_automation_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to setup a new automated automation.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Setup a new automated automation
|
||||
</p><p>
|
||||
Use automated actions to automatically trigger actions for
|
||||
various screens. Example: a lead created by a specific user may
|
||||
|
||||
@@ -266,9 +266,12 @@ FormRenderer.include({
|
||||
return element.tag === "action"? element: false;
|
||||
});
|
||||
});
|
||||
this.$el.toggleClass('o_dashboard_nocontent', !hasAction);
|
||||
if (!hasAction) {
|
||||
return $('<div class="oe_view_nocontent">')
|
||||
.append($('<div>').html(this.noContentHelp || " "));
|
||||
var innerDiv = $('<div class="o_view_nocontent">')
|
||||
.append(this.noContentHelp || "<div/>");
|
||||
return $('<div class="o_view_nocontent_container">')
|
||||
.append(innerDiv);
|
||||
}
|
||||
// We should start with three columns available
|
||||
node = $.extend(true, {}, node);
|
||||
|
||||
@@ -1,4 +1,12 @@
|
||||
.o_dashboard {
|
||||
|
||||
// no content help
|
||||
&.o_dashboard_nocontent {
|
||||
.o-flex-display();
|
||||
.o-align-content(center);
|
||||
.o-justify-content(center);
|
||||
}
|
||||
|
||||
// Dashboard layout
|
||||
.oe_dashboard_layout_1 .oe_dashboard_column {
|
||||
&.index_0 {
|
||||
|
||||
@@ -67,7 +67,7 @@ QUnit.test('dashboard basic rendering', function (assert) {
|
||||
|
||||
assert.ok(form.renderer.$el.hasClass('o_dashboard'),
|
||||
"with a dashboard, the renderer should have the proper css class");
|
||||
assert.strictEqual(form.$('.o_dashboard .oe_view_nocontent').length, 1,
|
||||
assert.strictEqual(form.$('.o_dashboard .o_view_nocontent').length, 1,
|
||||
"should have a no content helper");
|
||||
assert.strictEqual(form.get('title'), "My Dashboard",
|
||||
"should have the correct title");
|
||||
@@ -93,7 +93,7 @@ QUnit.test('display the no content helper', function (assert) {
|
||||
},
|
||||
});
|
||||
|
||||
assert.strictEqual(form.$('.o_dashboard .oe_view_nocontent p:contains(click to add a partner)').length, 1,
|
||||
assert.strictEqual(form.$('.o_dashboard .o_view_nocontent p:contains(click to add a partner)').length, 1,
|
||||
"should have a no content helper with action help");
|
||||
form.destroy();
|
||||
});
|
||||
|
||||
@@ -24,18 +24,16 @@
|
||||
<field name="usage">menu</field>
|
||||
<field name="view_id" ref="board_my_dash_view"/>
|
||||
<field name="help" type="html">
|
||||
<div class="oe_empty_custom_dashboard">
|
||||
<p>
|
||||
<b>Your personal dashboard is empty.</b>
|
||||
</p><p>
|
||||
<p class="o_view_nocontent_neutral_face">
|
||||
Your personal dashboard is empty
|
||||
</p><p>
|
||||
To add your first report into this dashboard, go to any
|
||||
menu, switch to list or graph view, and click <i>'Add to
|
||||
Dashboard'</i> in the extended search options.
|
||||
</p><p>
|
||||
</p><p>
|
||||
You can filter and group data before inserting into the
|
||||
dashboard using the search options.
|
||||
</p>
|
||||
</div>
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
@@ -312,8 +312,8 @@
|
||||
<field name="view_id" ref="view_calendar_event_calendar"/>
|
||||
<field name="search_view_id" ref="view_calendar_event_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to schedule a new meeting.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Schedule a new meeting
|
||||
</p><p>
|
||||
The calendar is shared between employees and fully integrated with
|
||||
other applications such as the employee leaves or the business
|
||||
|
||||
@@ -8,12 +8,10 @@
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="search_view_id" ref="base.view_res_partner_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a contact in your contacts directory.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a contact in your address book
|
||||
</p><p>
|
||||
Odoo helps you easily track all activities related to
|
||||
a customer: discussions, history of business opportunities,
|
||||
documents, etc.
|
||||
Odoo helps you to easily track all activities related to a customer.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -925,11 +925,11 @@ class Lead(models.Model):
|
||||
email = '%s@%s' % (alias_record.alias_name, alias_record.alias_domain)
|
||||
email_link = "<a href='mailto:%s'>%s</a>" % (email, email)
|
||||
help_title = _('%s or send an email to %s') % (help_title, email_link)
|
||||
return '<p class="oe_view_nocontent_create">%s</p><p>%s</p>' % (help_title, help)
|
||||
return '<p class="o_view_nocontent_smiling_face">%s</p><p>%s</p>' % (help_title, help)
|
||||
return super(Lead, self.with_context(
|
||||
empty_list_help_model='crm.team',
|
||||
empty_list_help_id=self._context.get('default_team_id', False),
|
||||
empty_list_help_document_name= _('leads') if self._context.get('default_type') == 'lead' else _('opportunities'),
|
||||
empty_list_help_document_name= _('leads') if self._context.get('default_type') == 'lead' else _('opportunity'),
|
||||
)).get_empty_list_help(help)
|
||||
|
||||
@api.multi
|
||||
|
||||
@@ -135,10 +135,10 @@ class Team(models.Model):
|
||||
user_team_id = self.env.user.sale_team_id.id
|
||||
if not user_team_id:
|
||||
user_team_id = self.search([], limit=1).id
|
||||
action['help'] = """<p class='oe_view_nocontent_create'>Click here to add new opportunities</p><p>
|
||||
action['help'] = _("""<p class='o_view_nocontent_smiling_face'>Add new opportunities</p><p>
|
||||
Looks like you are not a member of a sales channel. You should add yourself
|
||||
as a member of one of the sales channel.
|
||||
</p>"""
|
||||
</p>""")
|
||||
if user_team_id:
|
||||
action['help'] += "<p>As you don't belong to any sales channel, Odoo opens the first one by default.</p>"
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ tour.register('crm_tour', {
|
||||
trigger: ".o-kanban-button-new",
|
||||
extra_trigger: '.o_opportunity_kanban',
|
||||
content: _t("Click here to <b>create your first opportunity</b> and add it to your pipeline."),
|
||||
position: "right",
|
||||
position: "bottom",
|
||||
}, {
|
||||
trigger: ".modal-body input:first",
|
||||
auto: true
|
||||
|
||||
@@ -162,7 +162,7 @@ QUnit.test('dashboard should be displayed even if there is no content', function
|
||||
|
||||
assert.strictEqual(kanban.$('div.o_sales_dashboard').length, 1,
|
||||
"should render the dashboard");
|
||||
assert.strictEqual(kanban.$('.oe_view_nocontent:contains(A help message)').length, 1,
|
||||
assert.strictEqual(kanban.$('.o_view_nocontent:contains(A help message)').length, 1,
|
||||
"should correctly render the nocontent helper");
|
||||
|
||||
kanban.destroy();
|
||||
|
||||
@@ -805,14 +805,13 @@ for rec in records:
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new lead
|
||||
</p><p>
|
||||
Use leads if you need a qualification step before creating an
|
||||
opportunity or a customer. It can be a business card you received,
|
||||
a contact form filled in your website, or a file of unqualified
|
||||
prospects you import, etc.
|
||||
</p><p>
|
||||
Once qualified, the lead can be converted into a business
|
||||
opportunity and/or a new customer in your address book.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -838,9 +837,15 @@ for rec in records:
|
||||
</field>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
You will be able to schedule activities, attach related documents,
|
||||
track all discussions, convert into a quotation and much more.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new opportunity
|
||||
</p><p>
|
||||
Odoo helps you keep track of your sales pipeline to follow
|
||||
up potential sales and better forecast your future revenues.
|
||||
</p><p>
|
||||
You will be able to plan meetings and phone calls from
|
||||
opportunities, convert them into quotations, attach related
|
||||
documents, track all discussions, and much more.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -893,9 +898,15 @@ for rec in records:
|
||||
(0, 0, {'view_mode': 'graph'})]"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
You will be able to schedule activities, attach related documents,
|
||||
track all discussions, convert into a quotation and much more.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new opportunity
|
||||
</p><p>
|
||||
Odoo helps you keep track of your sales pipeline to follow
|
||||
up potential sales and better forecast your future revenues.
|
||||
</p><p>
|
||||
You will be able to plan meetings and phone calls from
|
||||
opportunities, convert them into quotations, attach related
|
||||
documents, track all discussions, and much more.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -931,7 +942,9 @@ for rec in records:
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No next activity
|
||||
</p><p>
|
||||
Here is the list of your next activities. Those are linked to your opportunities.
|
||||
To set a next activity, go on an opportunity and add one. It will then appear in this list.
|
||||
</p>
|
||||
@@ -945,13 +958,10 @@ for rec in records:
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm_lead_tag_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new sales tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new tag for your opportunities
|
||||
</p><p>
|
||||
Create specific tags that fit your company's activities
|
||||
to better classify and analyse your leads and opportunities.
|
||||
Such categories could for instance reflect your product
|
||||
structure or the different types of sales you do.
|
||||
Create tags that fit your business (product structure, sales type, etc.) to better manage and tack your opportunities.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -970,8 +980,8 @@ for rec in records:
|
||||
<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 class="o_view_nocontent_smiling_face">
|
||||
Define a new lost reason
|
||||
</p><p>
|
||||
Use lost reasons to explain why an opportunity is lost.
|
||||
</p><p>
|
||||
|
||||
@@ -57,8 +57,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm.crm_stage_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to set a new stage in your opportunity pipeline.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Set a new stage in your opportunity pipeline
|
||||
</p><p>
|
||||
Stages allow salespersons to easily track how a specific opportunity
|
||||
is positioned in the sales cycle.
|
||||
|
||||
@@ -19,14 +19,13 @@
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new lead
|
||||
</p><p>
|
||||
Use leads if you need a qualification step before creating an
|
||||
opportunity or a customer. It can be a business card you received,
|
||||
a contact form filled in your website, or a file of unqualified
|
||||
prospects you import, etc.
|
||||
</p><p>
|
||||
Once qualified, the lead can be converted into a business
|
||||
opportunity and/or a new customer in your address book.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -47,9 +46,15 @@
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
You will be able to schedule activities, attach related documents,
|
||||
track all discussions, convert into a quotation and much more.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new lead
|
||||
</p><p>
|
||||
Odoo helps you keep track of your sales pipeline to follow
|
||||
up potential sales and better forecast your future revenues.
|
||||
</p><p>
|
||||
You will be able to plan meetings and phone calls from
|
||||
opportunities, convert them into quotations, attach related
|
||||
documents, track all discussions, and much more.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -23,8 +23,8 @@
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create an opportunity related to this customer.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create an new opportunity related to this customer
|
||||
</p><p>
|
||||
Use opportunities to keep track of your sales pipeline, follow
|
||||
up potential sales and better forecast your future revenues.
|
||||
|
||||
@@ -74,7 +74,7 @@ class DeliveryCarrier(models.Model):
|
||||
'res_model': 'ir.module.module',
|
||||
'domain': [['name', 'ilike', 'delivery_']],
|
||||
'type': 'ir.actions.act_window',
|
||||
'help': _('''<p class="oe_view_nocontent">
|
||||
'help': _('''<p class="o_view_nocontent">
|
||||
Buy Odoo Enterprise now to get more providers.
|
||||
</p>'''),
|
||||
}
|
||||
|
||||
@@ -142,8 +142,8 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{'search_default_group_by_provider': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new delivery method.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Define a new delivery method
|
||||
</p><p>
|
||||
Each carrier (e.g. UPS) can have several delivery methods (e.g.
|
||||
UPS Express, UPS Standard) with a set of pricing rules attached
|
||||
|
||||
@@ -158,9 +158,10 @@
|
||||
<field name="view_mode">tree,form,calendar,graph</field>
|
||||
<field name="context">{'search_default_event_id': active_id, 'default_event_id': active_id, 'search_default_expected': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new attendee.
|
||||
</p></field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new attendee
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<!-- EVENT.EVENT VIEWS -->
|
||||
@@ -407,13 +408,14 @@
|
||||
<field name="view_mode">kanban,calendar,tree,form,pivot</field>
|
||||
<field name="context">{"search_default_upcoming":1}</field>
|
||||
<field name="search_view_id" ref="view_event_search"/>
|
||||
<field name="help" type="html"><p class="oe_view_nocontent_create">
|
||||
Click to add a new event.
|
||||
</p><p>
|
||||
Odoo helps you schedule and efficiently organize your events:
|
||||
track registrations and participations, automate the confirmation emails,
|
||||
sell tickets, etc.
|
||||
</p></field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new event
|
||||
</p><p>
|
||||
Schedule and organize your events efficiently:
|
||||
track registrations and participations, automate the confirmation emails, sell tickets, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<act_window
|
||||
|
||||
@@ -8,11 +8,12 @@
|
||||
<field name="view_id"></field> <!-- force empty -->
|
||||
<field name="context">{"search_default_parent_false" : True,}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No data for analysis
|
||||
</p><p>
|
||||
Odoo helps you managing the costs for your different vehicles
|
||||
Costs are generally created from services and contract and appears here.
|
||||
</p>
|
||||
<p>
|
||||
</p><p>
|
||||
Thanks to the different filters, Odoo can only print the effective
|
||||
costs, sort them by type and by vehicle.
|
||||
</p>
|
||||
@@ -39,11 +40,12 @@
|
||||
<field name="view_id"></field> <!-- force empty -->
|
||||
<field name="context">{"search_default_parent_true" : True,}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No data for analysis
|
||||
</p><p>
|
||||
Odoo helps you managing the costs for your different vehicles
|
||||
Costs are generally created from services and contract and appears here.
|
||||
</p>
|
||||
<p>
|
||||
</p><p>
|
||||
Thanks to the different filters, Odoo can only print the effective
|
||||
costs, sort them by type and by vehicle.
|
||||
</p>
|
||||
|
||||
@@ -154,12 +154,11 @@
|
||||
<field name="view_mode">tree,kanban,form,graph</field>
|
||||
<field name="context">{"search_default_parent_false" : True, "search_default_groupby_vehicle_id" : True,}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new cost.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new cost
|
||||
</p><p>
|
||||
Odoo helps you managing the costs for your different
|
||||
vehicles. Costs are created automatically from services,
|
||||
contracts (fixed or recurring) and fuel logs.
|
||||
Manage the costs for your different vehicles.
|
||||
Costs are created automatically from services, contracts and fuel logs.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -351,8 +350,8 @@
|
||||
<field name="view_mode">tree,kanban,form,graph</field>
|
||||
<field name="context">{'search_default_open': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new contract.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new contract
|
||||
</p><p>
|
||||
Manage all your contracts (leasing, insurances, etc.) with
|
||||
their related services, costs. Odoo will automatically warn
|
||||
@@ -485,12 +484,10 @@
|
||||
<field name="view_mode">tree,kanban,form,graph</field>
|
||||
<field name="context">{"search_default_groupby_vehicle" : True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new fuel log.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new fuel log
|
||||
</p><p>
|
||||
Here you can add refuelling entries for all vehicles. You can
|
||||
also filter logs of a particular vehicle using the search
|
||||
field.
|
||||
Here you can add refuelling entries for all vehicles.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -618,12 +615,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form,graph</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new service entry.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new service entry
|
||||
</p><p>
|
||||
Odoo helps you keeping track of all the services done
|
||||
on your vehicle. Services can be of many type: occasional
|
||||
repair, fixed maintenance, etc.
|
||||
Track all the services done on your vehicle.
|
||||
Services can be of many types: occasional repair, fixed maintenance, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -74,8 +74,8 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{"search_default_groupby_brand" : True,}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new model.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new model
|
||||
</p><p>
|
||||
You can define several models (e.g. A3, A4) for each make (Audi).
|
||||
</p>
|
||||
@@ -148,8 +148,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new make.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new make
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -228,15 +228,10 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new vehicle.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new vehicle
|
||||
</p><p>
|
||||
You will be able to manage your fleet by keeping track of the
|
||||
contracts, services, fixed and recurring costs, odometers and
|
||||
fuel logs associated to each vehicle.
|
||||
</p><p>
|
||||
Odoo will warn you when services or contract have to be
|
||||
renewed.
|
||||
Manage your fleet by keeping track of the contracts, services, odometers and fuel logs associated to each vehicle.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -334,13 +329,10 @@
|
||||
<field name="view_mode">tree,kanban,form,graph</field>
|
||||
<field name="context">{"search_default_groupby_vehicle" : True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new odometer log.
|
||||
</p>
|
||||
<p>
|
||||
Here you can add various odometer entries for all vehicles.
|
||||
You can also show odometer value for a particular vehicle using
|
||||
the search field.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new odometer log
|
||||
</p><p>
|
||||
You can add various odometer entries for all vehicles.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -366,8 +358,8 @@
|
||||
<field name="domain">[('category','=','service')]</field>
|
||||
<field name="context">{'default_category':'service'}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new type of service.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new type of service
|
||||
</p><p>
|
||||
Each service can used in contracts, as a standalone service or both.
|
||||
</p>
|
||||
@@ -383,8 +375,8 @@
|
||||
<field name="domain">[('category','=','contract')]</field>
|
||||
<field name="context">{'default_category':'contract'}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new type of contract.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new type of contract
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -408,11 +400,11 @@
|
||||
<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 create a vehicle status.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new vehicle status
|
||||
</p><p>
|
||||
You can customize available status to track the evolution of
|
||||
each vehicle. Example: Active, Being Repaired, Sold.
|
||||
each vehicle. Example: active, being repaired, sold.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -436,8 +428,8 @@
|
||||
<field name="res_model">fleet.vehicle.tag</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -5,10 +5,9 @@
|
||||
<field name="res_model">gamification.badge</field>
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a badge.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new badge
|
||||
</p><p>
|
||||
A badge is a symbolic token granted to a user as a sign of reward.
|
||||
It can be deserved automatically when some conditions are met or manually by users.
|
||||
Some badges are harder than others to get with specific conditions.
|
||||
|
||||
@@ -18,8 +18,10 @@
|
||||
<field name="view_mode">kanban,tree</field>
|
||||
<field name="context">{'search_default_group_by_definition': True, 'search_default_inprogress': True, 'search_default_challenge_id': active_id, 'default_challenge_id': active_id}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
There is no goals associated to this challenge matching your search.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No goal found
|
||||
</p><p>
|
||||
There is no goal associated to this challenge matching your search.
|
||||
Make sure that your challenge is active and assigned to at least one user.
|
||||
</p>
|
||||
</field>
|
||||
@@ -172,10 +174,9 @@
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="context">{'search_default_inprogress':True, 'default_inprogress':True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a challenge.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new challenge
|
||||
</p><p>
|
||||
Assign a list of goals to chosen users to evaluate them.
|
||||
The challenge can use a period (weekly, monthly...) for automatic creation of goals.
|
||||
The goals are created for the specified users or member of the group.
|
||||
|
||||
@@ -6,10 +6,9 @@
|
||||
<field name="view_mode">tree,form,kanban</field>
|
||||
<field name="context">{'search_default_group_by_user': True, 'search_default_group_by_definition': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a goal.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new goal
|
||||
</p><p>
|
||||
A goal is defined by a user and a goal definition.
|
||||
Goals can be created automatically by using challenges.
|
||||
</p>
|
||||
@@ -199,10 +198,9 @@
|
||||
<field name="res_model">gamification.goal.definition</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a goal definition.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new goal definition
|
||||
</p><p>
|
||||
A goal definition is a technical model of goal defining a condition to reach.
|
||||
The dates, values to reach or users are defined in goal instance.
|
||||
</p>
|
||||
|
||||
@@ -91,8 +91,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name='view_id' ref='view_google_drive_config_tree' />
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new template.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new template
|
||||
</p>
|
||||
<p>
|
||||
Link your own google drive templates to any record of Odoo. If you have really specific documents you want your collaborator fill in, e.g. Use a spreadsheet to control the quality of your product or review the delivery checklist for each order in a foreign country, ... Its very easy to manage them, link them to Odoo and use them to collaborate with your employees.
|
||||
|
||||
@@ -254,8 +254,8 @@
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_employee_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new employee.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new employee
|
||||
</p><p>
|
||||
With just a quick glance on the Odoo employee screen, you
|
||||
can easily find all the information you need for each person;
|
||||
@@ -446,17 +446,10 @@
|
||||
<field name="search_view_id" ref="view_job_filter"/>
|
||||
<field name="context">{"search_default_Current":1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new job position.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Ready to recruit more efficiently?
|
||||
</p><p>
|
||||
Job Positions are used to define jobs and their requirements.
|
||||
You can keep track of the number of employees you have per job
|
||||
position and follow the evolution according to what you planned
|
||||
for the future.
|
||||
</p><p>
|
||||
You can attach a survey to a job position. It will be used in
|
||||
the recruitment process to evaluate the applicants for this job
|
||||
position.
|
||||
Let's create a job position.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -472,8 +465,8 @@
|
||||
"default_department_id": active_id}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new employee.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new employee
|
||||
</p><p>
|
||||
With just a quick glance on the Odoo employee screen, you
|
||||
can easily find all the information you need for each person;
|
||||
@@ -609,8 +602,8 @@
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="search_view_id" ref="view_department_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a department.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new department
|
||||
</p><p>
|
||||
Odoo's department structure is used to manage all documents
|
||||
related to employees by departments: expenses, timesheets,
|
||||
|
||||
@@ -117,8 +117,11 @@
|
||||
<field name="context">{"search_default_today":1}</field>
|
||||
<field name="search_view_id" ref="hr_attendance_view_filter" />
|
||||
<field name="help" type="html">
|
||||
<p>The attendance records of your employees will be displayed here.</p>
|
||||
<p>Please make sure you're using the correct filter if you expected to see any.</p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No attendance records found
|
||||
</p><p>
|
||||
The attendance records of your employees will be displayed here.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -129,7 +132,11 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{'search_default_employee_id': active_id, 'default_employee_id': active_id}</field>
|
||||
<field name="help" type="html">
|
||||
<p>No attendance records to display.</p>
|
||||
<p class="o_view_nocontent_empty_folder" type="html">
|
||||
No attendance records to display
|
||||
</p><p>
|
||||
The attendance records of your employees will be displayed here.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
@@ -112,10 +112,10 @@
|
||||
<field name="view_mode">kanban</field>
|
||||
<field name="view_id" ref="hr_employees_view_kanban"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Create a few employees to be able to select an employee here and perform his check in / check out.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new employee
|
||||
</p><p>
|
||||
Add a few employees to be able to select an employee here and perform his check in / check out.
|
||||
To create employees go to the Employees menu.
|
||||
</p>
|
||||
</field>
|
||||
|
||||
@@ -207,8 +207,8 @@
|
||||
<field name="context">{'search_default_current':1, 'search_default_group_by_state': 1}</field>
|
||||
<field name="search_view_id" ref="hr_contract_view_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create new contracts.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new contract
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -189,17 +189,9 @@
|
||||
<field name="view_mode">graph,pivot,tree,kanban,form</field>
|
||||
<field name="search_view_id" ref="view_hr_expense_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Create a new expense.<br/>
|
||||
<!-- Or send receipts to .... -->
|
||||
</p><p>
|
||||
Expenses will go through these steps:
|
||||
</p><ol>
|
||||
<li>You record expenses</li>
|
||||
<li>Periodically, you submit expenses report to your manager,</li>
|
||||
<li>Once approved, your expenses report goes to the accounting,</li>
|
||||
<li>The accountant validates journal entries and reimburse you.</li>
|
||||
</ol>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -211,14 +203,8 @@
|
||||
<field name="domain">[('employee_id.user_id', '=', uid)]</field>
|
||||
<field name="context">{'search_default_to_report': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
The steps to process expenses are:
|
||||
<ol>
|
||||
<li>You record expenses,</li>
|
||||
<li>Periodically, you submit expenses report to your manager,</li>
|
||||
<li>Once approved, your expense report, goes to the accounting,</li>
|
||||
<li>The accountant validates entries and reimburse you.</li>
|
||||
</ol>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -294,8 +280,8 @@
|
||||
<field name="context">{"default_can_be_expensed": 1, 'default_type': 'service'}</field>
|
||||
<field name="domain">[('can_be_expensed', '=', True)]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new expense category.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense category
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -330,7 +316,9 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{"search_default_approved": 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No approved employee expenses
|
||||
</p><p>
|
||||
From here the accountant will be able to approve as well as refuse the expenses which are verified by the HR Manager.
|
||||
</p>
|
||||
</field>
|
||||
@@ -345,7 +333,9 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{"search_default_unsubmitted": 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No unreported employee expenses
|
||||
</p><p>
|
||||
From here the accountant will be able to approve as well as refuse the expenses which are verified by the HR Manager.
|
||||
</p>
|
||||
</field>
|
||||
@@ -571,8 +561,8 @@
|
||||
<field name="domain">[('employee_id.user_id', '=', uid), ('state', '!=', 'cancel')]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new expense report.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense report
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
@@ -587,7 +577,9 @@
|
||||
<field name="domain">[('employee_id.user_id', '=', uid), ('state', '=', 'cancel')]</field>
|
||||
<field name="context">{'create': False}</field>
|
||||
<field name="help" type="html">
|
||||
<p>No refused reports to display.</p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No refused reports to display
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -599,10 +591,8 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{'search_default_submitted': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new expense report.
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No expense reports to approve
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -615,8 +605,8 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{'search_default_to_post': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new expense report.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense report
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
@@ -631,8 +621,8 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{'search_default_approved': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new expense report.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense report
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
@@ -647,8 +637,8 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new expense report.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense report
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
@@ -664,8 +654,8 @@
|
||||
<field name="search_view_id" ref="view_hr_expense_sheet_filter"/>
|
||||
<field name="view_id" ref="view_hr_expense_sheet_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create new expenses.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
@@ -681,8 +671,8 @@
|
||||
<field name="search_view_id" ref="view_hr_expense_sheet_filter"/>
|
||||
<field name="view_id" ref="view_hr_expense_sheet_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create new expenses.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
@@ -698,8 +688,8 @@
|
||||
<field name="search_view_id" ref="view_hr_expense_sheet_filter"/>
|
||||
<field name="view_id" ref="view_hr_expense_sheet_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create new expenses.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new expense
|
||||
</p><p>
|
||||
Once you have created your expense, submit it to your manager who will validate it.
|
||||
</p>
|
||||
|
||||
@@ -22,10 +22,9 @@
|
||||
<field name="context">{'search_default_group_by_user': True, 'search_default_group_by_definition': True}</field>
|
||||
<field name="domain">[('challenge_id.category', '=', 'hr')]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a goal.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new goal
|
||||
</p><p>
|
||||
A goal is defined by a user and a goal type.
|
||||
Goals can be created automatically by using challenges.
|
||||
</p>
|
||||
@@ -40,10 +39,9 @@
|
||||
<field name="domain">[('category', '=', 'hr')]</field>
|
||||
<field name="context">{'search_default_inprogress':True, 'default_inprogress':True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a challenge.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new challenge
|
||||
</p><p>
|
||||
Assign a list of goals to chosen users to evaluate them.
|
||||
The challenge can use a period (weekly, monthly...) for automatic creation of goals.
|
||||
The goals are created for the specified users or member of the group.
|
||||
|
||||
@@ -11,9 +11,9 @@
|
||||
<page string="Received Badges" attrs="{'invisible': [('user_id', '=', False)]}">
|
||||
<field name="has_badges" invisible="1"/>
|
||||
<button string="Grant a Badge" type="action" name="%(action_reward_wizard)d"/> to reward this employee for a good action
|
||||
<div class="oe_view_nocontent" attrs="{'invisible': [('has_badges', '=', True)]}">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to grant this employee his first badge
|
||||
<div class="o_view_nocontent" attrs="{'invisible': [('has_badges', '=', True)]}">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Grant this employee his first badge
|
||||
</p><p class="oe_grey">
|
||||
Badges are rewards of good work. Give them to people you believe deserve it.
|
||||
</p>
|
||||
|
||||
@@ -133,7 +133,7 @@
|
||||
]
|
||||
}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<p class="o_view_nocontent_create">
|
||||
Click here to create a new leave request.
|
||||
</p>
|
||||
</field>
|
||||
|
||||
@@ -137,7 +137,7 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<p class="o_view_nocontent_create">
|
||||
Click here to create a new leave allocation request.
|
||||
</p>
|
||||
</field>
|
||||
@@ -164,7 +164,7 @@
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{'search_default_department':1, 'search_default_approve':1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<p class="o_view_nocontent_create">
|
||||
Click here to create a new leave allocation.
|
||||
</p>
|
||||
</field>
|
||||
|
||||
@@ -202,14 +202,14 @@
|
||||
<field name="domain">[('user_id', '=', uid)]</field>
|
||||
<field name="search_view_id" ref="view_hr_holidays_filter"/>
|
||||
<field name="help" type="html">
|
||||
<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
|
||||
to a manager for validation. Be sure to set the right leave
|
||||
type (recuperation, legal leaves, sickness) and the exact
|
||||
number of open days related to your leave.
|
||||
</p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new leave request
|
||||
</p><p>
|
||||
Once you have recorded your leave request, it will be sent
|
||||
to a manager for validation. Be sure to set the right leave
|
||||
type (recuperation, legal leaves, sickness) and the exact
|
||||
number of open days related to your leave.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -272,8 +272,8 @@
|
||||
<field name="view_mode">tree,kanban,form,calendar</field>
|
||||
<field name="view_id" eval="view_holiday"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new leave request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new leave request
|
||||
</p>
|
||||
</field>
|
||||
<field name="search_view_id" ref="view_hr_holidays_filter"/>
|
||||
@@ -286,8 +286,13 @@
|
||||
<field name="view_mode">tree,form,calendar</field>
|
||||
<field name="context">{'search_default_department':1, 'search_default_approve':1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new leave request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new leave request
|
||||
</p><p>
|
||||
Once you have recorded your leave request, it will be sent
|
||||
to a manager for validation. Be sure to set the right leave
|
||||
type (recuperation, legal leaves, sickness) and the exact
|
||||
number of open days related to your leave.
|
||||
</p>
|
||||
</field>
|
||||
<field name="search_view_id" ref="view_hr_holidays_filter"/>
|
||||
|
||||
@@ -249,8 +249,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new contribution register.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new contribution register
|
||||
</p><p>
|
||||
A contribution register is a third party involved in the salary
|
||||
payment of the employees. It can be the social security, the
|
||||
|
||||
@@ -278,7 +278,7 @@ class Applicant(models.Model):
|
||||
def get_empty_list_help(self, help):
|
||||
return super(Applicant, self.with_context(empty_list_help_model='hr.job',
|
||||
empty_list_help_id=self.env.context.get('default_job_id'),
|
||||
empty_list_help_document_name=_("job applicants"))).get_empty_list_help(help)
|
||||
empty_list_help_document_name=_("job applicant"))).get_empty_list_help(help)
|
||||
|
||||
@api.multi
|
||||
def action_get_created_employee(self):
|
||||
|
||||
@@ -97,11 +97,10 @@
|
||||
<field name="view_id" ref="hr_recruitment.view_hr_job_kanban"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new job position.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Ready to recruit more efficiently?
|
||||
</p><p>
|
||||
Once a job position is created, you can track related applications
|
||||
and manage the recruitment process.
|
||||
Let's create a job position.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -10,8 +10,8 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new stage in the recruitment process.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new stage in the recruitment process
|
||||
</p><p>
|
||||
Define here your stages of the recruitment process, for example:
|
||||
qualification call, first interview, second interview, refused,
|
||||
@@ -328,7 +328,9 @@
|
||||
<field name="search_view_id" ref="view_crm_case_jobs_filter"/>
|
||||
<field name="context">{'search_default_job_id': [active_id], 'default_job_id': active_id}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No applications yet
|
||||
</p><p>
|
||||
Odoo helps you track applicants in the recruitment
|
||||
process and follow up all operations: meetings, interviews, etc.
|
||||
</p><p>
|
||||
@@ -348,8 +350,8 @@
|
||||
<field name="context">{'search_default_activities_my': 1}</field>
|
||||
<field name="domain">[('activity_date_deadline', '!=', False)]</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Currently there are not any activity scheduled.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
No scheduled activities for the moment
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -361,10 +363,9 @@
|
||||
<field name="domain">[('job_id', '=', active_id)]</field>
|
||||
<field name="context">{'default_job_id': active_id}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Create some aliases that will allow you to track where applicants come from.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create some aliases to track where applicants come from
|
||||
</p><p>
|
||||
These aliases can be emails or urls for every source. When the applicant arrives here through one of these you'll know where he came from.
|
||||
</p>
|
||||
</field>
|
||||
@@ -390,8 +391,8 @@
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="context">{'search_default_job_id': active_id}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new employee.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new employee
|
||||
</p><p>
|
||||
With just a quick glance on the Odoo employee screen, you
|
||||
can easily find all the information you need for each person;
|
||||
@@ -500,12 +501,10 @@
|
||||
(0, 0, {'view_mode': 'form', 'view_id': ref('hr.view_hr_job_form')})]"/>
|
||||
<field name="context">{'search_default_in_recruitment': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new job position.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Ready to recruit more efficiently?
|
||||
</p><p>
|
||||
Once a job position is created, you can track the applicants
|
||||
and manage the recruitment process related to the job
|
||||
position.
|
||||
Let's create a job position.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -519,7 +518,9 @@
|
||||
<field name="search_view_id" ref="view_crm_case_jobs_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No applications yet
|
||||
</p><p>
|
||||
Odoo helps you track applicants in the recruitment
|
||||
process and follow up all operations: meetings, interviews, etc.
|
||||
</p><p>
|
||||
@@ -624,8 +625,8 @@
|
||||
<field name="domain">[('res_model','=','hr.applicant')]</field>
|
||||
<field name="context">{'create': False}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No document yet.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No document yet
|
||||
</p><p>
|
||||
This menu helps you search through resumes and motivation
|
||||
letters. Odoo automatically indexes .PDF, .DOC, DOCX, .TXT
|
||||
@@ -705,8 +706,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="view_id" ref="hr_recruitment_stage_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new stage in the recruitment process.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new stage in the recruitment process
|
||||
</p><p>
|
||||
Don't forget to specify the department if your recruitment process
|
||||
is different according to the job position.
|
||||
@@ -742,8 +743,8 @@
|
||||
<field name="res_model">hr.applicant.category</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -8,8 +8,8 @@
|
||||
<field name="context">{'search_default_groupby_employee':1,}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record activities.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a new activity
|
||||
</p><p>
|
||||
You can register and track your workings hours by project every
|
||||
day. Every time spent on a project will become a cost and can be re-invoiced to
|
||||
@@ -46,8 +46,8 @@
|
||||
<field name="context">{'search_default_groupby_project':1,}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record activities.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a new activity
|
||||
</p><p>
|
||||
You can register and track your workings hours by project every
|
||||
day. Every time spent on a project will become a cost and can be re-invoiced to
|
||||
@@ -84,8 +84,8 @@
|
||||
<field name="context">{'search_default_groupby_task':1,}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record activities.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a new activity
|
||||
</p><p>
|
||||
You can register and track your workings hours by project every
|
||||
day. Every time spent on a project will become a cost and can be re-invoiced to
|
||||
|
||||
@@ -195,8 +195,8 @@
|
||||
<field name="context">{"search_default_week":1}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record activities.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a new activity
|
||||
</p><p>
|
||||
You can register and track your workings hours by project every
|
||||
day. Every time spent on a project will become a cost and can be re-invoiced to
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
<field name="context">{"default_project_id": active_id, "search_default_project_id": [active_id]}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record activities.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a new activity
|
||||
</p><p>
|
||||
You can register and track your workings hours by project every
|
||||
day. Every time spent on a project will become a cost and can be re-invoiced to
|
||||
|
||||
@@ -104,7 +104,7 @@ class MailChannel(models.Model):
|
||||
@api.model
|
||||
def get_empty_list_help(self, help):
|
||||
if help:
|
||||
return '<p">%s</p>' % (help)
|
||||
help
|
||||
return super(MailChannel, self).get_empty_list_help(help)
|
||||
|
||||
def _define_command_history(self):
|
||||
|
||||
@@ -7,8 +7,8 @@
|
||||
<field name="res_model">im_livechat.channel</field>
|
||||
<field name="view_mode">kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new website live chat channel.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Define a new website live chat channel
|
||||
</p><p>
|
||||
You can create channels for each website on which you want
|
||||
to integrate the website live chat widget, allowing your website
|
||||
@@ -206,8 +206,8 @@
|
||||
<field name="view_id" ref="im_livechat_canned_response_view_tree"/>
|
||||
<field name="domain">[('shortcode_type','=','text')]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new canned response.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new canned response
|
||||
</p><p>
|
||||
Canned responses allow you to insert prewritten responses in
|
||||
your messages by typing <i>:shortcut</i>. The shortcut is
|
||||
|
||||
@@ -75,8 +75,10 @@
|
||||
<field name="domain">[('livechat_channel_id', '!=', None)]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Your chatter history is empty. Create a channel and start chatting to fill up your history.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
Your chatter history is empty
|
||||
</p><p>
|
||||
Create a channel and start chatting to fill up your history.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -24,8 +24,8 @@
|
||||
<field name="domain">[('parent_res_model','=','im_livechat.channel'), ('consumed','=',True)]</field>
|
||||
<field name="search_view_id" ref="rating_rating_view_search_livechat"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
There is no rating for this channel at the moment.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
There is no rating for this channel at the moment
|
||||
</p>
|
||||
</field>
|
||||
<field name="context">{'search_default_rating_last_7_days': 1}</field>
|
||||
@@ -38,8 +38,8 @@
|
||||
<field name="domain">[('parent_res_model','=','im_livechat.channel'), ('consumed', '=', True)]</field>
|
||||
<field name="search_view_id" ref="rating_rating_view_search_livechat"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Customer ratings on livechat session.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No customer ratings on live chat session yet
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -56,7 +56,7 @@
|
||||
<field name="view_type">tree</field>
|
||||
<field name="view_mode">list,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_nocreate">
|
||||
<p class="o_view_nocontent_nocreate">
|
||||
The closings are created by Odoo
|
||||
</p><p>
|
||||
Sales closings run automatically on a daily, monthly and annual basis. It computes both period and cumulative totals from all the sales entries posted in the system after the previous closing.
|
||||
|
||||
@@ -111,6 +111,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form,graph</field>
|
||||
<field name="view_id" ref="view_link_tracker_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new link tracker
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<!-- Website links click views -->
|
||||
|
||||
@@ -159,7 +159,9 @@
|
||||
<field name="search_view_id" ref="lunch_order_line_view_search"/>
|
||||
<field name="context">{"search_default_is_mine":1}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No previous order found
|
||||
</p><p>
|
||||
There is no previous order recorded. Click on "My Lunch" and then create a new lunch order.
|
||||
</p>
|
||||
</field>
|
||||
@@ -187,7 +189,9 @@
|
||||
<field name="context">{"search_default_is_mine_group":1}</field>
|
||||
<field name="view_id" ref="lunch_cashmove_view_tree_2"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No cash move yet
|
||||
</p><p>
|
||||
Here you can see your cash moves.<br/>A cash moves can be either an expense or a payment.
|
||||
An expense is automatically created when an order is received while a payment is a reimbursement to the company encoded by the manager.
|
||||
</p>
|
||||
@@ -204,13 +208,14 @@
|
||||
<field name="search_view_id" ref="lunch_order_line_view_search"/>
|
||||
<field name="context">{"search_default_group_by_supplier":1, "search_default_today":1}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
Nothing to order today
|
||||
</p><p>
|
||||
Here you can see today's orders grouped by vendors.
|
||||
</p>
|
||||
<p>
|
||||
- Click on the <span class="fa fa-phone text-success"/> to announce that the order is ordered <br/>
|
||||
- Click on the <span class="fa fa-check text-success"/> to announce that the order is received <br/>
|
||||
- Click on the <span class="fa fa-times-circle text-danger"/> to announce that the order isn't available
|
||||
</p><p>
|
||||
Click on the <span class="fa fa-phone text-success"/> to announce that the order is ordered.<br/>
|
||||
Click on the <span class="fa fa-check text-success"/> to announce that the order is received.<br/>
|
||||
Click on the <span class="fa fa-times-circle text-danger"/> to announce that the order isn't available.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -224,13 +229,14 @@
|
||||
<field name="search_view_id" ref="lunch_order_line_view_search"/>
|
||||
<field name="context">{"search_default_group_by_date":1, "search_default_group_by_supplier":1}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No lunch order yet
|
||||
</p><p>
|
||||
Summary of all lunch orders, grouped by vendor and by date.
|
||||
</p>
|
||||
<p>
|
||||
- Click on the <span class="fa fa-phone text-success"/> to announce that the order is ordered <br/>
|
||||
- Click on the <span class="fa fa-check text-success"/> to announce that the order is received <br/>
|
||||
- Click on the <span class="fa fa-times-circle text-danger"/> red X to announce that the order isn't available
|
||||
</p><p>
|
||||
Click on the <span class="fa fa-phone text-success"/> to announce that the order is ordered.<br/>
|
||||
Click on the <span class="fa fa-check text-success"/> to announce that the order is received.<br/>
|
||||
Click on the <span class="fa fa-times-circle text-danger"/> red X to announce that the order isn't available.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -245,10 +251,9 @@
|
||||
<field name="context">{"search_default_group_by_user":1}</field>
|
||||
<field name="view_id" ref="lunch_cashmove_view_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new payment.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new payment
|
||||
</p><p>
|
||||
A cashmove can either be an expense or a payment.<br/>
|
||||
An expense is automatically created at the order receipt.<br/>
|
||||
A payment represents the employee reimbursement to the company.
|
||||
@@ -266,11 +271,10 @@
|
||||
<field name="context">{"search_default_is_payment":1}</field>
|
||||
<field name="view_id" ref="lunch_cashmove_view_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a payment.
|
||||
</p>
|
||||
<p>
|
||||
Here you can see the employees' payment. A payment is a cash move from the employee to the company.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Register a payment
|
||||
</p><p>
|
||||
Payments are used to register liquidity movements. You can process those payments by your own means or by using installed facilities.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -282,10 +286,9 @@
|
||||
<field name="res_model">lunch.product</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a product for lunch.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product for lunch
|
||||
</p><p>
|
||||
A product is defined by its name, category, price and vendor.
|
||||
</p>
|
||||
</field>
|
||||
@@ -298,10 +301,9 @@
|
||||
<field name="res_model">lunch.product.category</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a lunch category.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new lunch category
|
||||
</p><p>
|
||||
Here you can access all categories for the lunch products.
|
||||
</p>
|
||||
</field>
|
||||
@@ -328,18 +330,16 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="search_view_id" ref="lunch_alert_view_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a lunch alert.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new lunch alert
|
||||
</p><p>
|
||||
Alerts are used to warn employee from possible issues concerning the lunch orders.
|
||||
To create a lunch alert you have to define its recurrence, the time interval during which the alert should be executed and the message to display.
|
||||
</p>
|
||||
<p>
|
||||
Example: <br/>
|
||||
- Recurency: Everyday<br/>
|
||||
- Time interval: from 00h00 am to 11h59 pm<br/>
|
||||
- Message: "You must order before 10h30 am"
|
||||
</p><p>
|
||||
Example:<br/>
|
||||
Recurency: Everyday,<br/>
|
||||
Time interval: from 00h00 am to 11h59 pm,<br/>
|
||||
Message: "You must order before 10h30 am".
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -306,7 +306,7 @@ class MailThread(models.AbstractModel):
|
||||
res_id = self._context.get('empty_list_help_id')
|
||||
catchall_domain = self.env['ir.config_parameter'].sudo().get_param("mail.catchall.domain")
|
||||
document_name = self._context.get('empty_list_help_document_name', _('document'))
|
||||
add_arrow = not help or help.find("oe_view_nocontent_create") == -1
|
||||
nothing_here = not help
|
||||
alias = None
|
||||
|
||||
if catchall_domain and model and res_id: # specific res_id -> find its alias (i.e. section_id specified)
|
||||
@@ -329,27 +329,29 @@ class MailThread(models.AbstractModel):
|
||||
|
||||
if alias:
|
||||
email_link = "<a href='mailto:%(email)s'>%(email)s</a>" % {'email': alias.name_get()[0][1]}
|
||||
if add_arrow:
|
||||
return "<p class='oe_view_nocontent_create'>%(dyn_help)s</p>%(static_help)s" % {
|
||||
if nothing_here:
|
||||
return "<p class='o_view_nocontent_smiling_face'>%(dyn_help)s</p>%(static_help)s" % {
|
||||
'static_help': help or '',
|
||||
'dyn_help': _("Click here to add new %(document)s or send an email to: %(email_link)s") % {
|
||||
'dyn_help': _("Add new %(document)s or send an email to: %(email_link)s") % {
|
||||
'document': document_name,
|
||||
'email_link': email_link
|
||||
}
|
||||
}
|
||||
return "%(static_help)s<p>%(dyn_help)s" % {
|
||||
return "%(static_help)s<p>%(dyn_help)s</p>" % {
|
||||
'static_help': help or '',
|
||||
'dyn_help': _("You could also add a new %(document)s by sending an email to: %(email_link)s.") % {
|
||||
'dyn_help': _("You could also add a new %(document)s by sending an email to: %(email_link)s") % {
|
||||
'document': document_name,
|
||||
'email_link': email_link,
|
||||
}
|
||||
}
|
||||
|
||||
if add_arrow:
|
||||
return "<p class='oe_view_nocontent_create'>%(dyn_help)s</p>%(static_help)s" % {
|
||||
if nothing_here:
|
||||
return "<p class='o_view_nocontent_smiling_face'>%(dyn_help)s</p>%(static_help)s" % {
|
||||
'static_help': help or '',
|
||||
'dyn_help': _("Click here to add new %s") % document_name,
|
||||
'dyn_help': _("Create a new %(document)s") % {
|
||||
'document': document_name,
|
||||
}
|
||||
}
|
||||
|
||||
return help
|
||||
|
||||
|
||||
@@ -104,15 +104,23 @@
|
||||
</t>
|
||||
|
||||
<!-- When a channel is empty-->
|
||||
<div t-name="mail.EmptyChannel" class="o_mail_no_content">
|
||||
<t t-if="options.channel_id==='channel_inbox'">
|
||||
<div class="o_thread_title">Congratulations, your inbox is empty</div>
|
||||
<div>New messages appear here.</div>
|
||||
</t>
|
||||
<t t-if="options.channel_id==='channel_starred'">
|
||||
<div class="o_thread_title">No starred message</div>
|
||||
<div> You can mark any message as 'starred', and it shows up in this channel.</div>
|
||||
</t>
|
||||
<div t-name="mail.EmptyChannel" class="o_mail_no_content o_view_nocontent_container">
|
||||
<div class="o_view_nocontent">
|
||||
<t t-if="options.channel_id==='channel_inbox'">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Congratulations, your inbox is empty
|
||||
</p><p>
|
||||
New messages appear here.
|
||||
</p>
|
||||
</t>
|
||||
<t t-if="options.channel_id==='channel_starred'">
|
||||
<p class="o_view_nocontent_neutral_face">
|
||||
No starred message
|
||||
</p><p>
|
||||
You can mark any message as 'starred', and it shows up in this channel.
|
||||
</p>
|
||||
</t>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<t t-name="mail.ChatThread.Content">
|
||||
|
||||
@@ -167,8 +167,8 @@
|
||||
<record id="base.action_attachment" model="ir.actions.act_window">
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to attach a new document.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Attach a new document
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -8,8 +8,8 @@
|
||||
<field name="res_model">mail.shortcode</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new chat shortcode.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Define a new chat shortcode
|
||||
</p><p>
|
||||
A shortcode is a keyboard shortcut. For instance, you type #gm and it will be transformed into "Good Morning".
|
||||
</p>
|
||||
|
||||
@@ -234,8 +234,8 @@
|
||||
<field name="view_id" ref="hr_equipment_request_view_kanban"/>
|
||||
<field name="context">{'default_technician_user_id': uid}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new maintenance request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new maintenance request
|
||||
</p><p>
|
||||
Follow the process of the request and communicate with the collaborator.
|
||||
</p>
|
||||
@@ -253,8 +253,8 @@
|
||||
'default_category_id': active_id,
|
||||
}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new maintenance request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new maintenance request
|
||||
</p><p>
|
||||
Follow the process of the request and communicate with the collaborator.
|
||||
</p>
|
||||
@@ -270,6 +270,13 @@
|
||||
'default_equipment_id': active_id,
|
||||
}</field>
|
||||
<field name="domain">[('equipment_id', '=', active_id)]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new maintenance request
|
||||
</p><p>
|
||||
Follow the process of the request and communicate with the collaborator.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="hr_equipment_todo_request_action_from_dashboard" model="ir.actions.act_window">
|
||||
@@ -280,6 +287,13 @@
|
||||
'default_maintenance_team_id': active_id,
|
||||
}</field>
|
||||
<field name="domain">[('maintenance_team_id', '=', active_id), ('maintenance_type', 'in', context.get('maintenance_type', ['preventive', 'corrective']))]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new maintenance request
|
||||
</p><p>
|
||||
Follow the process of the request and communicate with the collaborator.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="hr_equipment_request_action_cal" model="ir.actions.act_window">
|
||||
@@ -287,6 +301,13 @@
|
||||
<field name="res_model">maintenance.request</field>
|
||||
<field name="view_mode">calendar,kanban,tree,form,pivot,graph</field>
|
||||
<field name="view_id" ref="hr_equipment_view_calendar"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new maintenance request
|
||||
</p><p>
|
||||
Follow the process of the request and communicate with the collaborator.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="maintenance_request_action_reports" model="ir.actions.act_window">
|
||||
@@ -294,8 +315,10 @@
|
||||
<field name="res_model">maintenance.request</field>
|
||||
<field name="view_mode">graph,pivot,kanban,tree,form,calendar</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No maintenance request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new maintenance request
|
||||
</p><p>
|
||||
Follow the process of the request and communicate with the collaborator.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -518,13 +541,11 @@
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="view_id" ref="hr_equipment_view_kanban"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new equipment.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new equipment
|
||||
</p><p>
|
||||
This application helps you to track equipments used by employees.
|
||||
Create some laptop, printer or phone and link each equipment to
|
||||
an employee or department. You will manage allocations, issues
|
||||
and maintenance of equipment.
|
||||
Track equipments and link it to an employee or department.
|
||||
You will be able to manage allocations, issues and maintenance of your equipment.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -541,12 +562,11 @@
|
||||
'default_category_id': active_id,
|
||||
}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new Engine.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new equipment
|
||||
</p><p>
|
||||
This application helps you to track equipments used by employees.
|
||||
Create some laptop, printer or phone and link each equipment to an employee or department.
|
||||
You will manage allocations, issues and maintenance of equipment.
|
||||
Track equipments and link it to an employee or department.
|
||||
You will be able to manage allocations, issues and maintenance of your equipment.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -665,8 +685,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="view_id" ref="hr_equipment_category_view_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new equipment category.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new equipment category
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -719,8 +739,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a stage in the maintenance request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new stage in the maintenance request
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -930,8 +950,8 @@
|
||||
(0, 0, {'view_mode': 'tree', 'view_id': ref('maintenance_team_view_tree')}),
|
||||
(0, 0, {'view_mode': 'kanban', 'view_id': ref('maintenance_team_view_kanban')})]"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a team in the maintenance request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a team in the maintenance request
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -943,8 +963,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="maintenance_team_kanban"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a stage in the maintenance request.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new stage in the maintenance request
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -176,6 +176,13 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form,graph,pivot</field>
|
||||
<field name="context">{'search_default_not_opt_out': 1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a contact in your address book
|
||||
</p><p>
|
||||
Odoo helps you to easily track all activities related to a customer.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window" id="action_view_mass_mailing_contacts_from_list">
|
||||
@@ -186,8 +193,8 @@
|
||||
<field name="domain">[('list_ids', 'in', [active_id])]</field>
|
||||
<field name="context">{'search_default_not_opt_out': 1, 'default_list_ids': [(4,active_id)]}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a recipient.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new recipient
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -286,12 +293,13 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new mailing list.
|
||||
</p><p>
|
||||
Mailing lists allows you to to manage customers and
|
||||
contacts easily and to send to mailings in a single click.
|
||||
</p></field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new mailing list
|
||||
</p><p>
|
||||
Mailing lists allow you to manage customers and
|
||||
contacts easily and to send to mailings in a single click.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Mailing Lists" id="menu_email_mass_mailing_lists"
|
||||
@@ -561,11 +569,13 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">kanban,tree,form,graph</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new mailing.
|
||||
</p><p>
|
||||
Mass mailing allows you to to easily design and send mass mailings to your contacts, customers or leads using mailing lists.
|
||||
</p></field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new mailing list
|
||||
</p><p>
|
||||
Mailing lists allow you to manage customers and
|
||||
contacts easily and to send to mailings in a single click.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_view_mass_mailings_from_campaign" model="ir.actions.act_window">
|
||||
@@ -579,11 +589,13 @@
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new mailing.
|
||||
</p><p>
|
||||
Mass mailing allows you to to easily design and send mass mailings to your contacts, customers or leads using mailing lists.
|
||||
</p></field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new mailing list
|
||||
</p><p>
|
||||
Mailing lists allow you to manage customers and
|
||||
contacts easily and to send to mailings in a single click.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_create_mass_mailings_from_campaign" model="ir.actions.act_window">
|
||||
@@ -597,11 +609,13 @@
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new mailing.
|
||||
</p><p>
|
||||
Mass mailing allows you to to easily design and send mass mailings to your contacts, customers or leads using mailing lists.
|
||||
</p></field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new mailing list
|
||||
</p><p>
|
||||
Mailing lists allow you to manage customers and
|
||||
contacts easily and to send to mailings in a single click.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_create_ab_mass_mailings_from_campaign" model="ir.actions.act_window">
|
||||
@@ -616,11 +630,13 @@
|
||||
}
|
||||
</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new mailing.
|
||||
</p><p>
|
||||
Mass mailing allows you to to easily design and send mass mailings to your contacts, customers or leads using mailing lists.
|
||||
</p></field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new mailing list
|
||||
</p><p>
|
||||
Mailing lists allow you to manage customers and
|
||||
contacts easily and to send to mailings in a single click.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Mass Mailings" id="menu_email_mass_mailings"
|
||||
@@ -654,6 +670,11 @@
|
||||
<field name="res_model">mail.mass_mailing.stage</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new mass mailing stage
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_mass_mailing_configuration" name="Configuration" parent="mass_mailing_menu_root"
|
||||
@@ -681,8 +702,8 @@
|
||||
<field name="res_model">mail.mass_mailing.tag</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -867,12 +888,12 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new mass mailing campaign.
|
||||
</p><p>
|
||||
Create a campaign to structure mass mailing and get analysis from email status.
|
||||
</p>
|
||||
</field>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a campaign
|
||||
</p><p>
|
||||
Create a campaign to structure mass mailing and get analysis from email status.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Campaigns" id="menu_email_campaigns"
|
||||
|
||||
@@ -51,11 +51,11 @@
|
||||
<field name="search_view_id" ref="view_res_partner_member_filter"/>
|
||||
<field name="context">{"search_default_all_members": 1, "default_free_member": True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new Member
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new member
|
||||
</p><p>
|
||||
Odoo helps you easily track all activities related to a member:
|
||||
Current Membership Status, Discussions and History of Membership, etc.
|
||||
Odoo helps you easily track all activities related to a member:
|
||||
Current Membership Status, Discussions and History of Membership, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -290,8 +290,8 @@ class MrpBomLine(models.Model):
|
||||
'views': [(attachment_view.id, 'kanban'), (False, 'form')],
|
||||
'view_mode': 'kanban,tree,form',
|
||||
'view_type': 'form',
|
||||
'help': _('''<p class="oe_view_nocontent_create">
|
||||
Click to upload files to your product.
|
||||
'help': _('''<p class="o_view_nocontent_smiling_face">
|
||||
Upload files to your product
|
||||
</p><p>
|
||||
Use this feature to store any files, like drawings or specifications.
|
||||
</p>'''),
|
||||
|
||||
@@ -607,3 +607,10 @@ class MrpProduction(models.Model):
|
||||
action = self.env.ref('stock.action_stock_scrap').read()[0]
|
||||
action['domain'] = [('production_id', '=', self.id)]
|
||||
return action
|
||||
|
||||
@api.model
|
||||
def get_empty_list_help(self, help):
|
||||
self = self.with_context(
|
||||
empty_list_help_document_name=_("manufacturing order"),
|
||||
)
|
||||
return super(MrpProduction, self).get_empty_list_help(help)
|
||||
|
||||
@@ -154,15 +154,12 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="search_view_id" ref="view_mrp_bom_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a bill of material.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a bill of materials
|
||||
</p><p>
|
||||
Bills of Materials allow you to define the list of required raw
|
||||
Bills of materials allow you to define the list of required raw
|
||||
materials used to make a finished product; through a manufacturing
|
||||
order or a pack of products.
|
||||
</p><p>
|
||||
Odoo uses these BoMs to automatically propose manufacturing
|
||||
orders according to procurement needs.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -136,8 +136,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="context">{'search_default_active_message': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new Work Order Message.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new work order message
|
||||
</p><p>
|
||||
Work Order Messages are used to warn users about any change in the product,
|
||||
process, etc. These messages will appear on the involved Work Orders.
|
||||
|
||||
@@ -297,14 +297,8 @@
|
||||
<field name="search_view_id" ref="view_mrp_production_filter"/>
|
||||
<field name="context">{'search_default_todo': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a Manufacturing Order.
|
||||
</p><p>
|
||||
Based on a Bill of Material, a Manufacturing Order will consume raw materials
|
||||
and produce finished products.
|
||||
</p><p>
|
||||
Manufacturing Orders can be generated automatically based on customer
|
||||
requirements or reordering rules.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new manufacturing order
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -335,8 +329,8 @@
|
||||
<field name="view_mode">tree,kanban,form,calendar,pivot,graph</field>
|
||||
<field name="domain">[('state', '=', 'confirmed'), ('routing_id', '!=', False)]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new manufacturing order.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new manufacturing order
|
||||
</p><p>
|
||||
A manufacturing order, based on a bill of materials, will
|
||||
consume raw materials and produce finished products.
|
||||
@@ -356,8 +350,8 @@
|
||||
<field name="view_mode">tree,form,kanban,calendar,pivot,graph</field>
|
||||
<field name="domain">[('availability', 'in', ('waiting', 'partially_available'))]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new manufacturing order.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new manufacturing order
|
||||
</p><p>
|
||||
A manufacturing order, based on a bill of materials, will
|
||||
consume raw materials and produce finished products.
|
||||
|
||||
@@ -162,8 +162,8 @@
|
||||
<field name="view_id" ref="mrp_routing_tree_view"/>
|
||||
<field name="search_view_id" ref="mrp_routing_search_view"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new Routing.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new routing
|
||||
</p><p>
|
||||
Routings define the successive operations that need to be
|
||||
done to realize a Manufacturing Order. Each operation from
|
||||
|
||||
@@ -50,6 +50,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="domain">['|', ('move_id.unbuild_id', '=', active_id), ('move_id.consume_unbuild_id', '=', active_id)]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
There's no product move yet
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="mrp_unbuild_kanban_view" model="ir.ui.view">
|
||||
@@ -163,10 +168,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a Unbuild Order.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create an unbuild order
|
||||
</p><p>
|
||||
Unbuild Orders are used to break down a product you manufactured or purchased into its components, based on its Bill of Material.</p>
|
||||
An unbuild order is used to break down a finished product into its components.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
@@ -19,8 +19,8 @@
|
||||
<field name="search_view_id" ref="view_mrp_production_work_order_search"/>
|
||||
<field name="domain">[('workcenter_id', '=', active_id), ('state', '!=', 'done')]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a work center.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a work center
|
||||
</p><p>
|
||||
Work Centers allow you to create and manage manufacturing
|
||||
units. They consist of workers and/or machines, which are
|
||||
@@ -89,8 +89,8 @@
|
||||
<field name="domain">[('workcenter_id','=',active_id')]</field>
|
||||
<field name="context">{'search_default_thismonth':True}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Overall Equipment Effectiveness: no working or blocked time.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
Overall Equipment Effectiveness: no working or blocked time
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -106,8 +106,8 @@
|
||||
'default_workcenter_id': active_id,
|
||||
'search_default_workcenter_id': [active_id]}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No productivity loss for this equipment.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No productivity loss for this equipment
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -119,6 +119,11 @@
|
||||
<field name="domain">[('workcenter_id','=', active_id),('state','=','done')]</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">graph,pivot,tree,form,gantt</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new work orders performance
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window" id="mrp_workorder_report">
|
||||
@@ -130,6 +135,11 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">graph,pivot,tree,form,gantt</field>
|
||||
<field name="search_view_id" ref="view_mrp_production_work_order_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new work orders performance
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<!-- Workcenter Kanban view-->
|
||||
@@ -384,8 +394,8 @@
|
||||
(0, 0, {'view_mode': 'form', 'view_id': ref('mrp_workcenter_view')})]"/>
|
||||
<field name="search_view_id" ref="view_mrp_workcenter_search"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click here to create a new Work Center
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new work center
|
||||
</p><p>
|
||||
Manufacturing operations are processed at Work Centers. A Work Center can be composed
|
||||
of workers and/or machines, they are used for costing, scheduling, capacity planning, etc.
|
||||
@@ -403,9 +413,8 @@
|
||||
<field name="view_id" ref="mrp_workcenter_kanban"/>
|
||||
<field name="search_view_id" ref="view_mrp_workcenter_search"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<a type="action" name="%(mrp_workcenter_action)d">Click here
|
||||
</a> to create a new Work Center.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new work center
|
||||
</p><p>
|
||||
Manufacturing operations are processed at Work Centers. A Work Center can be composed of
|
||||
workers and/or machines, they are used for costing, scheduling, capacity planning, etc.
|
||||
@@ -506,8 +515,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="domain">[]</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No productivity loss defined.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No productivity loss defined
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -619,8 +628,8 @@
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{'search_default_workcenter_group': 1, 'search_default_thismonth':True, 'create':False,'edit':False}</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Overall Equipment Effectiveness: no working or blocked time.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
Overall Equipment Effectiveness: no working or blocked time
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -29,8 +29,10 @@
|
||||
<field name="context">{'search_default_workcenter_id': active_id}</field>
|
||||
<field name="domain">[]</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No data to display. You will get here statistics about the
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No data to display
|
||||
</p><p>
|
||||
You will get here statistics about the
|
||||
work orders duration related to this routing.
|
||||
</p>
|
||||
</field>
|
||||
@@ -46,8 +48,10 @@
|
||||
<field name="search_view_id" ref="view_mrp_production_work_order_search"/>
|
||||
<field name="domain">[('production_id.routing_id', '=', active_id), ('state', '=', 'done')]</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
No data to display. You will get here statistics about the
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No data to display
|
||||
</p><p>
|
||||
You will get here statistics about the
|
||||
work orders duration related to this routing.
|
||||
</p>
|
||||
</field>
|
||||
@@ -61,7 +65,9 @@
|
||||
<field name="view_mode">tree,form,gantt,calendar,pivot,graph</field>
|
||||
<field name="domain">[('production_id', '=', active_id)]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Start a new work order
|
||||
</p><p>
|
||||
Work Orders are operations to be processed at a Work Center to realize a
|
||||
Manufacturing Order. Work Orders are trigerred by Manufacturing Orders,
|
||||
they are based on the Routing defined on these ones
|
||||
@@ -376,11 +382,13 @@
|
||||
<field name="view_id" ref="mrp_workorder_view_gantt"/>
|
||||
<field name="context">{'search_default_work_center': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Work Orders are operations to be processed at a Work Center to realize a
|
||||
Manufacturing Order. Work Orders are trigerred by Manufacturing Orders,
|
||||
they are based on the Routing defined on these ones.
|
||||
</p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Start a new work order
|
||||
</p><p>
|
||||
Work Orders are operations to be processed at a Work Center to realize a
|
||||
Manufacturing Order. Work Orders are trigerred by Manufacturing Orders,
|
||||
they are based on the Routing defined on these ones
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -395,8 +403,8 @@
|
||||
<field name="view_id" ref="workcenter_line_gantt_production"/>
|
||||
<field name="context">{'search_default_production': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new work order.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Start a new work order
|
||||
</p><p>
|
||||
To manufacture or assemble products, and use raw materials and
|
||||
finished products you must also handle manufacturing operations.
|
||||
@@ -416,11 +424,13 @@
|
||||
<field name="search_view_id" ref="view_mrp_production_workcenter_form_view_filter"/>
|
||||
<field name="context">{'search_default_ready': True, 'search_default_progress': True}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Start a new work order
|
||||
</p><p>
|
||||
Work Orders are operations to be processed at a Work Center to realize a
|
||||
Manufacturing Order. Work Orders are trigerred by Manufacturing Orders,
|
||||
they are based on the Routing defined on these ones.
|
||||
</p>
|
||||
they are based on the Routing defined on these ones
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
@@ -67,8 +67,8 @@
|
||||
<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 add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -207,8 +207,8 @@
|
||||
<field name="search_view_id" ref="view_note_note_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a personal note.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new personal note
|
||||
</p><p>
|
||||
Use notes to organize personal tasks or notes. All
|
||||
notes are private; no one else will be able to see them. However
|
||||
|
||||
@@ -198,8 +198,8 @@
|
||||
<field name='view_type'>form</field>
|
||||
<field name='view_mode'>kanban,tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a payment acquirer.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new payment acquirer
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -328,6 +328,11 @@
|
||||
<field name="res_model">payment.transaction</field>
|
||||
<field name='view_type'>form</field>
|
||||
<field name='view_mode'>tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new payment transaction
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
@@ -401,6 +406,11 @@
|
||||
<field name='res_model'>payment.token</field>
|
||||
<field name='view_type'>form</field>
|
||||
<field name='view_mode'>tree,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a saved payment data
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
@@ -438,8 +448,8 @@
|
||||
<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 create a payment icon.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a payment icon
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -8,8 +8,8 @@
|
||||
<field name="context" eval="{'default_journal_user': 1, 'default_type': 'cash'}"/>
|
||||
<field name="domain">[('journal_user','=', 1)]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a payment method.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new payment method
|
||||
</p><p>
|
||||
Payment methods are defined by accounting journals having the
|
||||
field <i>PoS Payment Method</i> checked. In order to be useable
|
||||
|
||||
@@ -64,15 +64,11 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new category.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Define a new category
|
||||
</p><p>
|
||||
Categories are used to browse your products through the
|
||||
touchscreen interface.
|
||||
</p><p>
|
||||
If you put a photo on the category, the layout of the
|
||||
touchscreen interface will automatically. We suggest not to put
|
||||
a photo on categories for small (1024x768) screens.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -549,8 +549,8 @@
|
||||
<field name="domain"></field>
|
||||
<field name="search_view_id" ref="view_pos_config_search" />
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new PoS config.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new PoS config
|
||||
</p><p>
|
||||
Configure at least one Point of Sale to be able to sell through the PoS interface.
|
||||
</p>
|
||||
|
||||
@@ -155,12 +155,10 @@
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="domain">[]</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new order.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No orders found
|
||||
</p><p>
|
||||
Use this menu to browse previous orders. To record new
|
||||
orders, you may use the menu <i>Your Session</i> for
|
||||
the touchscreen interface.
|
||||
To record new orders, start a new session.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -92,8 +92,8 @@
|
||||
<field name="cash_register_balance_end" nolabel="1" attrs="{'invisible' : [('state', '=', 'opening_control')]}" class="oe_bold oe_pos_total" widget="monetary" options="{'currency_field': 'currency_id'}"/>
|
||||
</group>
|
||||
<div class="oe_clear"/>
|
||||
<div attrs="{'invisible' : ['|', ('cash_journal_id', '=', False), ('state', '!=', 'opening_control')]}" class="oe_view_nocontent" groups="point_of_sale.group_pos_manager">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<div attrs="{'invisible' : ['|', ('cash_journal_id', '=', False), ('state', '!=', 'opening_control')]}" class="o_view_nocontent" groups="point_of_sale.group_pos_manager">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
You can define another list of available currencies on the
|
||||
<i>Cash Registers</i> tab of the <b><field name="cash_journal_id" class="oe_inline"/></b>
|
||||
payment method.
|
||||
@@ -209,16 +209,10 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="search_view_id" ref="view_pos_session_search" />
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to start a new session.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No sessions found
|
||||
</p><p>
|
||||
A session is a period of time, usually one day, during which
|
||||
you sell through the point of sale. The user has to check the
|
||||
currencies in your cash registers at the beginning and the end
|
||||
of each session.
|
||||
</p><p>
|
||||
Note that you may use the menu <i>Your Session</i>
|
||||
to quickly open a new session.
|
||||
A session is a period of time, usually one day, during which you sell through the Point of Sale.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -30,16 +30,11 @@
|
||||
<field name="search_view_id" eval="False"/> <!-- Force empty -->
|
||||
<field name="view_id" ref="product.product_product_tree_view"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new product.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product variant
|
||||
</p><p>
|
||||
You must define a product for everything you sell through
|
||||
the point of sale interface.
|
||||
</p><p>
|
||||
Do not forget to set the price and the point of sale category
|
||||
in which it should appear. If a product has no point of sale
|
||||
category, you can not sell it through the point of sale
|
||||
interface.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -62,8 +62,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to configure your card reader.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Configure your card reader
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -63,8 +63,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a Restaurant Floor.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new restaurant floor
|
||||
</p><p>
|
||||
A restaurant floor represents the place where customers are served, this is where you can
|
||||
define and position the tables.
|
||||
@@ -124,8 +124,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a Restaurant Order Printer.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new restaurant order printer
|
||||
</p><p>
|
||||
Order Printers are used by restaurants and bars to print the
|
||||
order updates in the kitchen/bar when the waiter updates the order.
|
||||
|
||||
@@ -550,6 +550,14 @@ class ProductProduct(models.Model):
|
||||
('datetime', '<=', date or fields.Datetime.now())], order='datetime desc,id desc', limit=1)
|
||||
return history.cost or 0.0
|
||||
|
||||
@api.model
|
||||
def get_empty_list_help(self, help):
|
||||
self = self.with_context(
|
||||
empty_list_help_document_name=_("product"),
|
||||
)
|
||||
return super(ProductProduct, self).get_empty_list_help(help)
|
||||
|
||||
|
||||
class ProductPackaging(models.Model):
|
||||
_name = "product.packaging"
|
||||
_description = "Packaging"
|
||||
|
||||
@@ -443,3 +443,10 @@ class ProductTemplate(models.Model):
|
||||
variant.write({'active': False})
|
||||
pass
|
||||
return True
|
||||
|
||||
@api.model
|
||||
def get_empty_list_help(self, help):
|
||||
self = self.with_context(
|
||||
empty_list_help_document_name=_("product"),
|
||||
)
|
||||
return super(ProductTemplate, self).get_empty_list_help(help)
|
||||
|
||||
@@ -188,15 +188,13 @@
|
||||
<field name="search_view_id" ref="product_pricelist_view_search" />
|
||||
<field name="context">{"default_base":'list_price'}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a pricelist.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new pricelist
|
||||
</p><p>
|
||||
A price list contains rules to be evaluated in order to compute
|
||||
the sale price of the products.
|
||||
A price is a set of sales prices or rules to compute the price of sales order lines based on products, product categories, dates and ordered quantities.
|
||||
This is the perfect tool to handle several pricings, seasonal discounts, etc.
|
||||
</p><p>
|
||||
Each rule include a set of applicability criteria (date range,
|
||||
product category...) and a computation that easily helps to achieve
|
||||
any kind of pricing.
|
||||
You can assign pricelists to your customers or select one when creating a new sales quotation.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -109,12 +109,11 @@
|
||||
<field name="view_id" ref="product_template_kanban_view"/>
|
||||
<field name="context">{"search_default_filter_to_sell":1}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product
|
||||
</p><p>
|
||||
You must define a product for everything you sell, whether it's a physical product, a consumable or a service you offer to customers.
|
||||
</p><p>
|
||||
The product form contains information to simplify the sale process: price, notes in the quotation, accounting data, procurement methods, etc.
|
||||
You must define a product for everything you purchase,
|
||||
whether it's a physical product, a consumable or services.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -52,8 +52,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="product_uom_tree_view"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new unit of measure.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new unit of measure
|
||||
</p><p>
|
||||
You must define a conversion rate between several Units of
|
||||
Measure within the same category.
|
||||
@@ -79,8 +79,8 @@
|
||||
<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 add a new unit of measure category.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Add a new unit of measure category
|
||||
</p><p>
|
||||
Units of measure belonging to the same category can be
|
||||
converted between each others. For example, in the category
|
||||
|
||||
@@ -140,8 +140,8 @@
|
||||
<field name="view_type">form</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -168,16 +168,11 @@
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="view_id" eval="False"/> <!-- Force empty -->
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product variant
|
||||
</p><p>
|
||||
You must define a product for everything you sell, whether it's
|
||||
a physical product, a consumable or a service you offer to
|
||||
customers.
|
||||
</p><p>
|
||||
The product form contains information to simplify the sale
|
||||
process: price, notes in the quotation, accounting data,
|
||||
procurement methods, etc.
|
||||
You must define a product for everything you purchase,
|
||||
whether it's a physical product, a consumable or services.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -255,16 +250,13 @@
|
||||
(0, 0, {'view_mode': 'form', 'view_id': ref('product_variant_easy_edit_view')}),
|
||||
(0, 0, {'view_mode': 'kanban'})]"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product variant
|
||||
</p><p>
|
||||
You must define a product for everything you sell, whether it's
|
||||
a physical product, a consumable or a service you offer to
|
||||
customers.
|
||||
</p><p>
|
||||
The product form contains information to simplify the sale
|
||||
process: price, notes in the quotation, accounting data,
|
||||
procurement methods, etc.
|
||||
You must define a product for everything you sell, whether it's a physical product,
|
||||
a consumable or a service you offer to customers.
|
||||
The product form contains information to simplify the sale process:
|
||||
price, notes in the quotation, accounting data, procurement methods, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -377,16 +369,13 @@
|
||||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to define a new product.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new product variant
|
||||
</p><p>
|
||||
You must define a product for everything you sell, whether it's
|
||||
a physical product, a consumable or a service you offer to
|
||||
customers.
|
||||
</p><p>
|
||||
The product form contains information to simplify the sale
|
||||
process: price, notes in the quotation, accounting data,
|
||||
procurement methods, etc.
|
||||
You must define a product for everything you sell, whether it's a physical product,
|
||||
a consumable or a service you offer to customers.
|
||||
The product form contains information to simplify the sale process:
|
||||
price, notes in the quotation, accounting data, procurement methods, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -123,7 +123,7 @@ class Project(models.Model):
|
||||
'view_id': False,
|
||||
'view_mode': 'kanban,tree,form',
|
||||
'view_type': 'form',
|
||||
'help': _('''<p class="oe_view_nocontent_create">
|
||||
'help': _('''<p class="o_view_nocontent_smiling_face">
|
||||
Documents are attached to the tasks and issues of your project.</p><p>
|
||||
Send messages or log internal notes with attachments to link
|
||||
documents to your project.
|
||||
@@ -151,7 +151,8 @@ class Project(models.Model):
|
||||
action_data = None
|
||||
if action:
|
||||
action.sudo().write({
|
||||
"help": _('''<p class="oe_view_nocontent_create">Click to create a new project.</p>''')
|
||||
"help": _('''<p class="o_view_nocontent_smiling_face">
|
||||
Create a new project</p>''')
|
||||
})
|
||||
action_data = action.read()[0]
|
||||
# Reload the dashboard
|
||||
@@ -693,7 +694,7 @@ class Task(models.Model):
|
||||
self = self.with_context(
|
||||
empty_list_help_id=self.env.context.get('default_project_id'),
|
||||
empty_list_help_model='project.project',
|
||||
empty_list_help_document_name=_("tasks")
|
||||
empty_list_help_document_name=_("task"),
|
||||
)
|
||||
return super(Task, self).get_empty_list_help(help)
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ tour.register('project_tour', {
|
||||
trigger: '.o-kanban-button-new',
|
||||
extra_trigger: '.o_project_kanban',
|
||||
content: _t('Let\'s create your first project.'),
|
||||
position: 'right',
|
||||
position: 'bottom',
|
||||
width: 200,
|
||||
}, {
|
||||
trigger: 'input.o_project_name',
|
||||
|
||||
@@ -71,11 +71,11 @@
|
||||
}</field>
|
||||
<field name="search_view_id" ref="view_task_search_form"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Here, you can create new tasks
|
||||
</p>
|
||||
<p>
|
||||
You can now manage your tasks in order to get things done efficiently. Track progress, discuss, attach documents, etc.
|
||||
</p><p>
|
||||
You can now manage your tasks in order to get things done efficiently.<br />
|
||||
Track progress, discuss, attach documents, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -379,9 +379,10 @@
|
||||
<field name="search_view_id" ref="view_project_project_filter"/>
|
||||
<field name="target">main</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a new project.<br/>
|
||||
<i>Or <a type="action" name="%(project.ir_actions_server_project_sample)d">activate a sample project</a> to play with.</i>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new project
|
||||
</p><p>
|
||||
Or <a type="action" name="%(project.ir_actions_server_project_sample)d">activate a sample project</a> to play with.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -398,8 +399,8 @@
|
||||
<field name="search_view_id" ref="view_project_project_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Create a new project.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
Create a new project
|
||||
</p><p>
|
||||
Organize your activities (plan tasks, track issues, invoice timesheets) for internal, personal or customer projects.
|
||||
</p>
|
||||
@@ -678,8 +679,11 @@
|
||||
<field name="context">{'search_default_my_tasks': 1}</field>
|
||||
<field name="search_view_id" ref="view_task_search_form"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Odoo's project management allows you to manage the pipeline of your tasks efficiently. You can track progress, discuss on tasks, attach documents, etc.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new task
|
||||
</p><p>
|
||||
Odoo's project management allows you to manage the pipeline of your tasks efficiently.<br/>
|
||||
You can track progress, discuss on tasks, attach documents, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -703,8 +707,8 @@
|
||||
<field name="context">{'search_default_activities_my':1}</field>
|
||||
<field name="domain">[('activity_date_deadline', '!=', False)]</field>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
Currently there are not any activity scheduled.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No scheduled activity at the moment
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -862,8 +866,8 @@
|
||||
<field name="view_mode">tree,kanban,form</field>
|
||||
<field name="view_id" ref="task_type_tree"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a stage in the task pipeline.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new stage in the task pipeline
|
||||
</p><p>
|
||||
Define the steps that will be used in the project from the
|
||||
creation of the task, up to the closing of the task or issue.
|
||||
@@ -911,8 +915,8 @@
|
||||
<field name="res_model">project.tags</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to add a new tag.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a new tag
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
@@ -25,8 +25,8 @@
|
||||
<field name="domain">[('consumed','=',True), ('parent_res_model','=','project.project')]</field>
|
||||
<field name="search_view_id" ref="rating_rating_view_search_project"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
There is no rating for this object at the moment.
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
There is no rating for this object at the moment
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
@@ -38,7 +38,9 @@
|
||||
<field name="domain">[('res_model', '=', 'project.task'), ('res_id', '=', active_id), ('consumed', '=', True)]</field>
|
||||
<field name="search_view_id" ref="rating_rating_view_search_project"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No customer ratings yet
|
||||
</p><p>
|
||||
Customer ratings on tasks. If you have no rating, change your project Settings to activate it.
|
||||
</p>
|
||||
</field>
|
||||
@@ -51,7 +53,9 @@
|
||||
<field name="domain">[('parent_res_model','=','project.project'), ('consumed', '=', True)]</field>
|
||||
<field name="search_view_id" ref="rating_rating_view_search_project"/>
|
||||
<field name="help" type="html">
|
||||
<p>
|
||||
<p class="o_view_nocontent_empty_folder">
|
||||
No customer ratings yet
|
||||
</p><p>
|
||||
Customer ratings on tasks. If you have no rating, change your project Settings to activate it.
|
||||
</p>
|
||||
</field>
|
||||
|
||||
@@ -10,8 +10,8 @@
|
||||
<field name="context">{'default_type':'in_invoice', 'type':'in_invoice', 'journal_type': 'purchase'}</field>
|
||||
<field name="search_view_id" ref="account.view_account_invoice_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to create a vendor bill.
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Create a vendor bill
|
||||
</p><p>
|
||||
Use this menu to control the invoices to be received from your
|
||||
vendors. When registering a new bill, set the purchase order
|
||||
@@ -31,13 +31,12 @@
|
||||
<field name="context">{'default_type': 'in_invoice', 'type': 'in_invoice', 'journal_type': 'purchase', 'default_purchase_id': active_id}</field>
|
||||
<field name="search_view_id" ref="account.view_account_invoice_filter"/>
|
||||
<field name="help" type="html">
|
||||
<p class="oe_view_nocontent_create">
|
||||
Click to record a vendor bill related to this purchase.
|
||||
</p>
|
||||
<p>
|
||||
<p class="o_view_nocontent_smiling_face">
|
||||
Record a vendor bill related to this purchase
|
||||
</p><p>
|
||||
You can control the invoice from your vendor according to
|
||||
what you purchased (services) or received (products).
|
||||
</p>
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_invoice_supplier_tree1_view1" model="ir.actions.act_window.view">
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user