Alexandre Kühn
a87d761fdb
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
84 lines
3.4 KiB
XML
84 lines
3.4 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
|
|
<record model="ir.ui.view" id="account_assert_tree">
|
|
<field name="name">accounting.assert.test.tree</field>
|
|
<field name="model">accounting.assert.test</field>
|
|
<field name="arch" type="xml">
|
|
<tree string="Tests">
|
|
<field name="sequence"/>
|
|
<field name="name"/>
|
|
<field name="desc"/>
|
|
</tree>
|
|
</field>
|
|
</record>
|
|
|
|
<record model="ir.ui.view" id="account_assert_form">
|
|
<field name="name">accounting.assert.test.form</field>
|
|
<field name="model">accounting.assert.test</field>
|
|
<field name="arch" type="xml">
|
|
<form string="Tests">
|
|
<sheet>
|
|
<group>
|
|
<group>
|
|
<field name="name"/>
|
|
<field name="sequence"/>
|
|
</group>
|
|
<group>
|
|
<field name="active"/>
|
|
</group>
|
|
</group>
|
|
<notebook>
|
|
<page string="Description">
|
|
<field name="desc" nolabel="1"/>
|
|
</page>
|
|
<page string="Expression">
|
|
<group string="Python Code">
|
|
<field colspan="4" name="code_exec" nolabel="1"/>
|
|
</group>
|
|
<group string="Code Help">
|
|
<pre>
|
|
Code should always set a variable named `result` with the result of your test, that can be a list or
|
|
a dictionary. If `result` is an empty list, it means that the test was succesful. Otherwise it will
|
|
try to translate and print what is inside `result`.
|
|
|
|
If the result of your test is a dictionary, you can set a variable named `column_order` to choose in
|
|
what order you want to print `result`'s content.
|
|
|
|
Should you need them, you can also use the following variables into your code:
|
|
* cr: cursor to the database
|
|
* uid: ID of the current user
|
|
|
|
In any ways, the code must be legal python statements with correct indentation (if needed).
|
|
|
|
Example:
|
|
sql = '''SELECT id, name, ref, date
|
|
FROM account_move_line
|
|
WHERE account_id IN (SELECT id FROM account_account WHERE type = 'view')
|
|
'''
|
|
cr.execute(sql)
|
|
result = cr.dictfetchall()
|
|
</pre>
|
|
</group>
|
|
</page>
|
|
</notebook>
|
|
</sheet>
|
|
</form>
|
|
</field>
|
|
</record>
|
|
|
|
<record model="ir.actions.act_window" id="action_accounting_assert">
|
|
<field name="name">Accounting Tests</field>
|
|
<field name="res_model">accounting.assert.test</field>
|
|
<field name="view_mode">tree,form</field>
|
|
<field name="help" type="html">
|
|
<p class="o_view_nocontent_smiling_face">
|
|
Create a new accounting test
|
|
</p>
|
|
</field>
|
|
</record>
|
|
|
|
<menuitem name="Accounting Tests" parent="account.menu_finance_reports" id="menu_action_license" action="action_accounting_assert" sequence="50" groups="base.group_no_one"/>
|
|
|
|
</odoo>
|