[MERGE]merged with latest
bzr revid: vba@tinyerp.com-20120823050807-gixlq6xlba63bwrx
This commit is contained in:
commit
5f2c37186b
|
@ -19,11 +19,11 @@
|
|||
#
|
||||
##############################################################################
|
||||
{
|
||||
"name" : "eInvoicing",
|
||||
"version" : "1.1",
|
||||
"author" : "OpenERP SA",
|
||||
"category": 'Accounting & Finance',
|
||||
"description": """
|
||||
'name' : 'eInvoicing',
|
||||
'version' : '1.1',
|
||||
'author' : 'OpenERP SA',
|
||||
'category' : 'Accounting & Finance',
|
||||
'description' : """
|
||||
Accounting and Financial Management.
|
||||
====================================
|
||||
|
||||
|
@ -44,14 +44,13 @@ Creates a dashboard for accountants that includes:
|
|||
* Company Analysis
|
||||
* Graph of Treasury
|
||||
|
||||
The processes like maintaining of general ledger is done through the defined financial Journals (entry move line orgrouping is maintained through journal) for a particular
|
||||
financial year and for preparation of vouchers there is a module named account_voucher.
|
||||
The processes like maintaining of general ledger is done through the defined financial Journals (entry move line orgrouping is maintained through journal)
|
||||
for a particular financial year and for preparation of vouchers there is a module named account_voucher.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'images' : ['images/accounts.jpeg','images/bank_statement.jpeg','images/cash_register.jpeg','images/chart_of_accounts.jpeg','images/customer_invoice.jpeg','images/journal_entries.jpeg'],
|
||||
'init_xml': [],
|
||||
"depends" : ["base_setup", "product", "analytic", "process", "board", "edi"],
|
||||
'update_xml': [
|
||||
'depends' : ['base_setup', 'product', 'analytic', 'process', 'board', 'edi'],
|
||||
'data': [
|
||||
'security/account_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'account_menuitem.xml',
|
||||
|
@ -122,12 +121,12 @@ financial year and for preparation of vouchers there is a module named account_v
|
|||
'ir_sequence_view.xml',
|
||||
'company_view.xml',
|
||||
'board_account_view.xml',
|
||||
"edi/invoice_action_data.xml",
|
||||
"account_bank_view.xml",
|
||||
"res_config_view.xml",
|
||||
"account_pre_install.yml"
|
||||
'edi/invoice_action_data.xml',
|
||||
'account_bank_view.xml',
|
||||
'res_config_view.xml',
|
||||
'account_pre_install.yml'
|
||||
],
|
||||
'demo_xml': [
|
||||
'demo': [
|
||||
'demo/account_demo.xml',
|
||||
'project/project_demo.xml',
|
||||
'project/analytic_account_demo.xml',
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
currency_id: base.EUR
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 450.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
currency_id: base.EUR
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 450.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -20,7 +20,7 @@
|
|||
currency_id: base.EUR
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC3] Medium PC'
|
||||
name: '[PC-DEM] PC on Demand'
|
||||
price_unit: 900.0
|
||||
quantity: 10.0
|
||||
product_id: product.product_product_5
|
||||
|
|
|
@ -28,7 +28,7 @@
|
|||
currency_id: base.EUR
|
||||
invoice_line:
|
||||
- account_id: account.a_expense
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 300.0
|
||||
product_id: product.product_product_3
|
||||
quantity: 10.0
|
||||
|
|
|
@ -24,7 +24,7 @@
|
|||
uos_id: 1
|
||||
quantity: 5.0
|
||||
price_unit: 100.0
|
||||
name: 'Medium PC'
|
||||
name: 'PC on Demand'
|
||||
account_id: account.a_pay
|
||||
tax_line:
|
||||
- name: sale tax
|
||||
|
@ -104,9 +104,9 @@
|
|||
"__model": "account.invoice.line",
|
||||
"__id": "account:b22acf7a-ddcd-11e0-a4db-701a04e25543.account_invoice_line-1RP3so",
|
||||
"uos_id": ["product:b22acf7a-ddcd-11e0-a4db-701a04e25543.product_uom_unit", "Unit"],
|
||||
"name": "Basic PC",
|
||||
"name": "PC Assemble SC234",
|
||||
"price_unit": 10.0,
|
||||
"product_id": ["product:b22acf7a-ddcd-11e0-a4db-701a04e25543.product_product_3", "[PC1] Basic PC"],
|
||||
"product_id": ["product:b22acf7a-ddcd-11e0-a4db-701a04e25543.product_product_3", "[PCSC234] PC Assemble SC234"],
|
||||
"quantity": 1.0
|
||||
},
|
||||
{
|
||||
|
@ -114,9 +114,9 @@
|
|||
"__model": "account.invoice.line",
|
||||
"__id": "account:b22acf7a-ddcd-11e0-a4db-701a04e25543.account_invoice_line-u2XV5",
|
||||
"uos_id": ["product:b22acf7a-ddcd-11e0-a4db-701a04e25543.product_uom_unit", "Unit"],
|
||||
"name": "Medium PC",
|
||||
"name": "PC on Demand",
|
||||
"price_unit": 100.0,
|
||||
"product_id": ["product:b22acf7a-ddcd-11e0-a4db-701a04e25543.product_product_5", "[PC3] Medium PC"],
|
||||
"product_id": ["product:b22acf7a-ddcd-11e0-a4db-701a04e25543.product_product_5", "[PC-DEM] PC on Demand"],
|
||||
"quantity": 5.0
|
||||
}]
|
||||
}
|
||||
|
@ -137,12 +137,12 @@
|
|||
assert invoice_new.type == 'in_invoice', "Invoice type was not set properly"
|
||||
assert len(invoice_new.invoice_line) == 2, "invoice lines are not same"
|
||||
for inv_line in invoice_new.invoice_line:
|
||||
if inv_line.name == 'Basic PC':
|
||||
if inv_line.name == 'PC Assemble SC234':
|
||||
assert inv_line.uos_id.name == "Unit" , "uom is not same"
|
||||
assert inv_line.price_unit == 10 , "price unit is not same"
|
||||
assert inv_line.quantity == 1 , "product qty is not same"
|
||||
assert inv_line.price_subtotal == 10, "price sub total is not same"
|
||||
elif inv_line.name == 'Medium PC':
|
||||
elif inv_line.name == 'PC on Demand':
|
||||
assert inv_line.uos_id.name == "Unit" , "uom is not same"
|
||||
assert inv_line.price_unit == 100 , "price unit is not same"
|
||||
assert inv_line.quantity == 5 , "product qty is not same"
|
||||
|
|
|
@ -19,13 +19,13 @@
|
|||
#
|
||||
##############################################################################
|
||||
{
|
||||
"name" : "Accounting and Finance",
|
||||
"version" : "1.1",
|
||||
"author" : "OpenERP SA",
|
||||
"category": 'Accounting & Finance',
|
||||
"sequence": 10,
|
||||
"summary": "Financial and Analytic Accounting",
|
||||
"description": """
|
||||
'name' : 'Accounting and Finance',
|
||||
'version' : '1.1',
|
||||
'author' : 'OpenERP SA',
|
||||
'category': 'Accounting & Finance',
|
||||
'sequence': 10,
|
||||
'summary': 'Financial and Analytic Accounting',
|
||||
'description': """
|
||||
Accounting Access Rights.
|
||||
=========================
|
||||
|
||||
|
@ -36,13 +36,12 @@ It assigns manager and user access rights to the Administrator and only
|
|||
user rights to Demo user.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
"depends" : ["account_voucher"],
|
||||
'update_xml': [
|
||||
'depends' : ['account_voucher'],
|
||||
'data': [
|
||||
'security/account_security.xml',
|
||||
'account_accountant_data.xml'
|
||||
],
|
||||
'demo_xml': ['account_accountant_demo.xml'],
|
||||
'demo': ['account_accountant_demo.xml'],
|
||||
'test': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
|
|
|
@ -1,10 +1,10 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<openerp>
|
||||
<data>
|
||||
<!-- rename root menu "Accounting" -->
|
||||
<record id="account.menu_finance" model="ir.ui.menu">
|
||||
<field name="name">Accounting</field>
|
||||
</record>
|
||||
<!-- Rename root menu "Accounting" -->
|
||||
<!-- Top menu item -->
|
||||
<menuitem name="Accounting"
|
||||
id="account.menu_finance"/>
|
||||
</data>
|
||||
|
||||
<data noupdate="1">
|
||||
|
@ -19,10 +19,8 @@
|
|||
<field name="type">automatic</field>
|
||||
<field name="sequence">100</field>
|
||||
</record>
|
||||
</data>
|
||||
|
||||
<data noupdate="1">
|
||||
<!-- notify all employees of module installation -->
|
||||
<!-- Notify all employees of module installation -->
|
||||
<function model="mail.group" name="message_append_note">
|
||||
<!-- ids, subject, body, parent_id=False, type='notification', content_subtype='html' -->
|
||||
<value eval="[ref('mail.group_all_employees')]"/>
|
||||
|
|
|
@ -28,22 +28,19 @@
|
|||
This module is for modifying account analytic view to show important data to project manager of services companies.
|
||||
===================================================================================================================
|
||||
|
||||
Adds menu to show relevant information to each manager.
|
||||
You can also view the report of account analytic summary
|
||||
user-wise as well as month-wise.
|
||||
Adds menu to show relevant information to each manager.You can also view the report of account analytic summary user-wise as well as month-wise.
|
||||
""",
|
||||
"author": "Camptocamp",
|
||||
"website": "http://www.camptocamp.com/",
|
||||
"images": ["images/bill_tasks_works.jpeg","images/overpassed_accounts.jpeg"],
|
||||
"depends": ["hr_timesheet_invoice", "sale"], #although sale is technically not required to install this module, all menuitems are located under 'Sales' application
|
||||
"init_xml": [],
|
||||
"update_xml": [
|
||||
"security/ir.model.access.csv",
|
||||
"account_analytic_analysis_view.xml",
|
||||
"account_analytic_analysis_menu.xml",
|
||||
"account_analytic_analysis_cron.xml",
|
||||
'author': 'Camptocamp',
|
||||
'website': 'http://www.camptocamp.com/',
|
||||
'images': ['images/bill_tasks_works.jpeg','images/overpassed_accounts.jpeg'],
|
||||
'depends': ['hr_timesheet_invoice', 'sale'], #although sale is technically not required to install this module, all menuitems are located under 'Sales' application
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'account_analytic_analysis_view.xml',
|
||||
'account_analytic_analysis_menu.xml',
|
||||
'account_analytic_analysis_cron.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0042927202589',
|
||||
|
|
|
@ -22,10 +22,10 @@
|
|||
{
|
||||
'name': 'Account Analytic Defaults',
|
||||
'version': '1.0',
|
||||
"category": 'Accounting & Finance',
|
||||
'category': 'Accounting & Finance',
|
||||
'description': """
|
||||
Set default values for your analytic accounts.
|
||||
=============================================
|
||||
==============================================
|
||||
|
||||
Allows to automatically select analytic accounts based on criterions:
|
||||
---------------------------------------------------------------------
|
||||
|
@ -39,13 +39,12 @@ Allows to automatically select analytic accounts based on criterions:
|
|||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/analytic_defaults.jpeg'],
|
||||
'depends': ['sale'],
|
||||
'init_xml' : [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'security/account_analytic_default_security.xml',
|
||||
'account_analytic_default_view.xml'
|
||||
],
|
||||
'demo_xml' : [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0074229833581',
|
||||
|
|
|
@ -26,45 +26,48 @@
|
|||
'category': 'Accounting & Finance',
|
||||
'description': """
|
||||
This module allows to use several analytic plans according to the general journal.
|
||||
===================================================================================
|
||||
==================================================================================
|
||||
|
||||
Here multiple analytic lines are created when the invoice or the entries
|
||||
are confirmed.
|
||||
|
||||
For example, you can define the following analytic structure:
|
||||
Projects
|
||||
Project 1
|
||||
SubProj 1.1
|
||||
SubProj 1.2
|
||||
-------------------------------------------------------------
|
||||
* **Projects**
|
||||
* Project 1
|
||||
+ SubProj 1.1
|
||||
|
||||
Project 2
|
||||
Salesman
|
||||
Eric
|
||||
Fabien
|
||||
+ SubProj 1.2
|
||||
|
||||
Here, we have two plans: Projects and Salesman. An invoice line must
|
||||
be able to write analytic entries in the 2 plans: SubProj 1.1 and
|
||||
Fabien. The amount can also be split. The following example is for
|
||||
an invoice that touches the two subproject and assigned to one salesman:
|
||||
* Project 2
|
||||
|
||||
Plan1:
|
||||
SubProject 1.1 : 50%
|
||||
SubProject 1.2 : 50%
|
||||
Plan2:
|
||||
* **Salesman**
|
||||
* Eric
|
||||
|
||||
* Fabien
|
||||
|
||||
Here, we have two plans: Projects and Salesman. An invoice line must be able to write analytic entries in the 2 plans: SubProj 1.1 and Fabien. The amount can also be split.
|
||||
|
||||
The following example is for an invoice that touches the two subprojects and assigned to one salesman:
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
**Plan1:**
|
||||
|
||||
* SubProject 1.1 : 50%
|
||||
|
||||
* SubProject 1.2 : 50%
|
||||
|
||||
**Plan2:**
|
||||
Eric: 100%
|
||||
|
||||
So when this line of invoice will be confirmed, it will generate 3 analytic lines,
|
||||
for one account entry.
|
||||
So when this line of invoice will be confirmed, it will generate 3 analytic lines,for one account entry.
|
||||
|
||||
The analytic plan validates the minimum and maximum percentage at the time of creation
|
||||
of distribution models.
|
||||
The analytic plan validates the minimum and maximum percentage at the time of creation of distribution models.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/analytic_plan.jpeg'],
|
||||
'depends': ['account', 'account_analytic_default'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/account_analytic_plan_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'account_analytic_plans_view.xml',
|
||||
|
@ -72,7 +75,7 @@ of distribution models.
|
|||
'wizard/analytic_plan_create_model_view.xml',
|
||||
'wizard/account_crossovered_analytic_view.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'test': ['test/acount_analytic_plans_report.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
|
|
|
@ -19,32 +19,34 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name": "Anglo-Saxon Accounting",
|
||||
"version": "1.2",
|
||||
"author": "OpenERP SA, Veritos",
|
||||
"website": "http://openerp.com - http://veritos.nl",
|
||||
"description": """
|
||||
'name': 'Anglo-Saxon Accounting',
|
||||
'version': '1.2',
|
||||
'author': 'OpenERP SA, Veritos',
|
||||
'website': 'http://openerp.com - http://veritos.nl',
|
||||
'description': """
|
||||
This module supports the Anglo-Saxon accounting methodology by changing the accounting logic with stock transactions.
|
||||
=====================================================================================================================
|
||||
|
||||
The difference between the Anglo-Saxon accounting countries and the Rhine (or also called
|
||||
Continental accounting) countries is the moment of taking the Cost of Goods Sold versus
|
||||
Cost of Sales. Anglo-Saxons accounting does take the cost when sales invoice is created,
|
||||
Continental accounting will take the cost at the moment the goods are shipped.
|
||||
The difference between the Anglo-Saxon accounting countries and the Rhine
|
||||
(or also called Continental accounting) countries is the moment of taking
|
||||
the Cost of Goods Sold versus Cost of Sales. Anglo-Saxons accounting does
|
||||
take the cost when sales invoice is created, Continental accounting will
|
||||
take the cost at the moment the goods are shipped.
|
||||
|
||||
This module will add this functionality by using a interim account, to store the value of
|
||||
shipped goods and will contra book this interim account when the invoice is created to
|
||||
transfer this amount to the debtor or creditor account. Secondly, price differences between
|
||||
actual purchase price and fixed product standard price are booked on a separate account.""",
|
||||
"images": ["images/account_anglo_saxon.jpeg"],
|
||||
"depends": ["product", "purchase"],
|
||||
"category": "Accounting & Finance",
|
||||
"init_xml": [],
|
||||
"demo_xml": [],
|
||||
"update_xml": ["product_view.xml",],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"certificate":"00557423080410733581",
|
||||
This module will add this functionality by using a interim account, to
|
||||
store the value of shipped goods and will contra book this interim
|
||||
account when the invoice is created to transfer this amount to the
|
||||
debtor or creditor account. Secondly, price differences between actual
|
||||
purchase price and fixed product standard price are booked on a separate
|
||||
account.""",
|
||||
'images': ['images/account_anglo_saxon.jpeg'],
|
||||
'depends': ['product', 'purchase'],
|
||||
'category': 'Accounting & Finance',
|
||||
'demo': [],
|
||||
'data': ['product_view.xml',],
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'certificate':'00557423080410733581',
|
||||
}
|
||||
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -20,42 +20,40 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Assets Management",
|
||||
"version" : "1.0",
|
||||
"depends" : ["account"],
|
||||
"author" : "OpenERP S.A.",
|
||||
"description": """
|
||||
'name': 'Assets Management',
|
||||
'version': '1.0',
|
||||
'depends': ['account'],
|
||||
'author': 'OpenERP S.A.',
|
||||
'description': """
|
||||
Financial and accounting asset management.
|
||||
==========================================
|
||||
|
||||
This Module manages the assets owned by a company or an individual. It will keep track of depreciation's occurred on those assets.
|
||||
And it allows to create Move's of the depreciation lines.
|
||||
This Module manages the assets owned by a company or an individual. It will keep
|
||||
track of depreciation's occurred on those assets. And it allows to create Move's
|
||||
of the depreciation lines.
|
||||
|
||||
""",
|
||||
"website" : "http://www.openerp.com",
|
||||
"category" : "Accounting & Finance",
|
||||
"sequence": 32,
|
||||
"init_xml" : [
|
||||
],
|
||||
"demo_xml" : [ 'account_asset_demo.xml'
|
||||
],
|
||||
'website': 'http://www.openerp.com',
|
||||
'category': 'Accounting & Finance',
|
||||
'sequence': 32,
|
||||
'demo': [ 'account_asset_demo.xml'],
|
||||
'test': [
|
||||
'test/account_asset_demo.yml',
|
||||
'test/account_asset.yml',
|
||||
'test/account_asset_wizard.yml',
|
||||
],
|
||||
"update_xml" : [
|
||||
"security/account_asset_security.xml",
|
||||
"security/ir.model.access.csv",
|
||||
"wizard/account_asset_change_duration_view.xml",
|
||||
"wizard/wizard_asset_compute_view.xml",
|
||||
"account_asset_view.xml",
|
||||
"account_asset_invoice_view.xml",
|
||||
"report/account_asset_report_view.xml",
|
||||
'data': [
|
||||
'security/account_asset_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/account_asset_change_duration_view.xml',
|
||||
'wizard/wizard_asset_compute_view.xml',
|
||||
'account_asset_view.xml',
|
||||
'account_asset_invoice_view.xml',
|
||||
'report/account_asset_report_view.xml',
|
||||
],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"application": False,
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'application': False,
|
||||
}
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
||||
|
|
|
@ -30,19 +30,20 @@ Module that extends the standard account_bank_statement_line object for improved
|
|||
===================================================================================================
|
||||
|
||||
This module adds:
|
||||
-----------------
|
||||
- valuta date
|
||||
- batch payments
|
||||
- traceability of changes to bank statement lines
|
||||
- bank statement line views
|
||||
- bank statements balances report
|
||||
- performance improvements for digital import of bank statement (via 'ebanking_import' context flag)
|
||||
- name_search on res.partner.bank enhanced to allow search on bank and iban account numbers
|
||||
- performance improvements for digital import of bank statement (via
|
||||
'ebanking_import' context flag)
|
||||
- name_search on res.partner.bank enhanced to allow search on bank
|
||||
and iban account numbers
|
||||
''',
|
||||
'depends': ['account'],
|
||||
'demo_xml': [],
|
||||
'init_xml': [
|
||||
],
|
||||
'update_xml' : [
|
||||
'demo': [],
|
||||
'data' : [
|
||||
'security/ir.model.access.csv',
|
||||
'account_bank_statement_view.xml',
|
||||
'account_bank_statement_report.xml',
|
||||
|
|
|
@ -32,23 +32,26 @@ Once the Budgets are defined (in Invoicing/Budgets/Budgets), the Project Manager
|
|||
can set the planned amount on each Analytic Account.
|
||||
|
||||
The accountant has the possibility to see the total of amount planned for each
|
||||
Budget in order to ensure the total planned is not greater/lower than what he planned
|
||||
for this Budget. Each list of record can also be switched to a graphical view of it.
|
||||
Budget in order to ensure the total planned is not greater/lower than what he
|
||||
planned for this Budget. Each list of record can also be switched to a graphical
|
||||
view of it.
|
||||
|
||||
Three reports are available:
|
||||
----------------------------
|
||||
1. The first is available from a list of Budgets. It gives the spreading, for
|
||||
these Budgets, of the Analytic Accounts.
|
||||
|
||||
1. The first is available from a list of Budgets. It gives the spreading, for these Budgets, of the Analytic Accounts.
|
||||
2. The second is a summary of the previous one, it only gives the spreading,
|
||||
for the selected Budgets, of the Analytic Accounts.
|
||||
|
||||
2. The second is a summary of the previous one, it only gives the spreading, for the selected Budgets, of the Analytic Accounts.
|
||||
|
||||
3. The last one is available from the Analytic Chart of Accounts. It gives the spreading, for the selected Analytic Accounts of Budgets.
|
||||
3. The last one is available from the Analytic Chart of Accounts. It gives
|
||||
the spreading, for the selected Analytic Accounts of Budgets.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/budget.jpeg','images/budgetary_position.jpeg'],
|
||||
'depends': ['account'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'security/account_budget_security.xml',
|
||||
'account_budget_view.xml',
|
||||
|
@ -59,7 +62,7 @@ Three reports are available:
|
|||
'wizard/account_budget_crossovered_summary_report_view.xml',
|
||||
'wizard/account_budget_crossovered_report_view.xml',
|
||||
],
|
||||
'demo_xml': ['account_budget_demo.xml'],
|
||||
'demo': ['account_budget_demo.xml'],
|
||||
'test':[
|
||||
'test/account_budget.yml',
|
||||
'test/account_budget_report.yml',
|
||||
|
|
|
@ -20,26 +20,25 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Cancel Journal Entries",
|
||||
"version" : "1.1",
|
||||
"author" : "OpenERP SA",
|
||||
"category": 'Accounting & Finance',
|
||||
"description": """
|
||||
Allows cancelling accounting entries.
|
||||
=====================================
|
||||
'name': 'Cancel Journal Entries',
|
||||
'version': '1.1',
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Accounting & Finance',
|
||||
'description': """
|
||||
Allows canceling accounting entries.
|
||||
====================================
|
||||
|
||||
This module adds 'Allow Cancelling Entries' field on form view of account journal.
|
||||
This module adds 'Allow Canceling Entries' field on form view of account journal.
|
||||
If set to true it allows user to cancel entries & invoices.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
"images" : ["images/account_cancel.jpeg"],
|
||||
"depends" : ["account"],
|
||||
'init_xml': [],
|
||||
'update_xml': ['account_cancel_view.xml' ],
|
||||
'demo_xml': [],
|
||||
'images': ['images/account_cancel.jpeg'],
|
||||
'depends' : ['account'],
|
||||
'data': ['account_cancel_view.xml' ],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
"certificate" : "001101250473177981989",
|
||||
'certificate': '001101250473177981989',
|
||||
|
||||
|
||||
}
|
||||
|
|
|
@ -23,7 +23,7 @@
|
|||
{
|
||||
'name': 'Template of Charts of Accounts',
|
||||
'version': '1.1',
|
||||
"category": 'Hidden/Dependency',
|
||||
'category': 'Hidden/Dependency',
|
||||
'description': """
|
||||
Remove minimal account chart.
|
||||
=============================
|
||||
|
@ -33,9 +33,8 @@ Deactivates minimal chart of accounts.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['account'],
|
||||
'init_xml': [],
|
||||
'update_xml': [],
|
||||
'demo_xml': [],
|
||||
'data': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'certificate': '0073332443901',
|
||||
}
|
||||
|
|
|
@ -19,29 +19,24 @@
|
|||
#
|
||||
##############################################################################
|
||||
{
|
||||
"name" : "Check Writing",
|
||||
"version" : "1.1",
|
||||
"author" : "OpenERP SA, NovaPoint Group",
|
||||
"category": "Generic Modules/Accounting",
|
||||
"description": """
|
||||
'name': 'Check Writing',
|
||||
'version': '1.1',
|
||||
'author': 'OpenERP SA, NovaPoint Group',
|
||||
'category': 'Generic Modules/Accounting',
|
||||
'description': """
|
||||
Module for the Check Writing and Check Printing.
|
||||
================================================
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
"depends" : [
|
||||
"account_voucher",
|
||||
],
|
||||
'update_xml': [
|
||||
'depends' : ['account_voucher'],
|
||||
'data': [
|
||||
'account_check_writing_report.xml',
|
||||
'account_view.xml',
|
||||
'account_voucher_view.xml',
|
||||
'account_check_writing_data.xml',
|
||||
],
|
||||
'demo_xml': [
|
||||
'account_demo.xml',
|
||||
],
|
||||
'test': [
|
||||
],
|
||||
'demo': ['account_demo.xml'],
|
||||
'test': [],
|
||||
'installable': True,
|
||||
'active': False,
|
||||
}
|
||||
|
|
|
@ -20,74 +20,92 @@
|
|||
#
|
||||
##############################################################################
|
||||
{
|
||||
"name": 'Belgium - Import Bank CODA Statements',
|
||||
"version": '2.1',
|
||||
"author": 'Noviat',
|
||||
"category": 'Accounting & Finance',
|
||||
"description": '''
|
||||
'name': 'Belgium - Import Bank CODA Statements',
|
||||
'version': '2.1',
|
||||
'author': 'Noviat',
|
||||
'category': 'Accounting & Finance',
|
||||
'description': '''
|
||||
Module to import CODA bank statements.
|
||||
======================================
|
||||
|
||||
Supported are CODA flat files in V2 format from Belgian bank accounts.
|
||||
----------------------------------------------------------------------
|
||||
* CODA v1 support.
|
||||
* CODA v2.2 support.
|
||||
* Foreign Currency support.
|
||||
* Support for all data record types (0, 1, 2, 3, 4, 8, 9).
|
||||
* Parsing & logging of all Transaction Codes and Structured Format Communications.
|
||||
* Parsing & logging of all Transaction Codes and Structured Format
|
||||
Communications.
|
||||
* Automatic Financial Journal assignment via CODA configuration parameters.
|
||||
* Support for multiple Journals per Bank Account Number.
|
||||
* Support for multiple statements from different bank accounts in a single CODA file.
|
||||
* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
|
||||
* Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
|
||||
* Support for multiple statements from different bank accounts in a single
|
||||
CODA file.
|
||||
* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in
|
||||
the CODA Bank Account configuration records).
|
||||
* Multi-language CODA parsing, parsing configuration data provided for EN,
|
||||
NL, FR.
|
||||
|
||||
The machine readable CODA Files are parsed and stored in human readable format in
|
||||
CODA Bank Statements. Also Bank Statements are generated containing a subset of
|
||||
the CODA information (only those transaction lines that are required for the creation
|
||||
of the Financial Accounting records). The CODA Bank Statement is a 'read-only'
|
||||
object, hence remaining a reliable representation of the original CODA file whereas
|
||||
the Bank Statement will get modified as required by accounting business processes.
|
||||
the CODA information (only those transaction lines that are required for the
|
||||
creation of the Financial Accounting records). The CODA Bank Statement is a
|
||||
'read-only' object, hence remaining a reliable representation of the original
|
||||
CODA file whereas the Bank Statement will get modified as required by accounting
|
||||
business processes.
|
||||
|
||||
CODA Bank Accounts configured as type 'Info' will only generate CODA Bank Statements.
|
||||
|
||||
A removal of one object in the CODA processing results in the removal of the associated
|
||||
objects. The removal of a CODA File containing multiple Bank Statements will also
|
||||
remove those associated statements.
|
||||
A removal of one object in the CODA processing results in the removal of the
|
||||
associated objects. The removal of a CODA File containing multiple Bank
|
||||
Statements will also remove those associated statements.
|
||||
|
||||
The following reconciliation logic has been implemented in the CODA processing:
|
||||
|
||||
1) The Company's Bank Account Number of the CODA statement is compared against the Bank Account Number field of the Company's CODA Bank Account configuration records (whereby bank accounts defined in type='info' configuration records are ignored). If this is the case an 'internal transfer' transaction is generated using the 'Internal Transfer Account' field of the CODA File Import wizard.
|
||||
2) As a second step the 'Structured Communication' field of the CODA transaction line is matched against the reference field of in- and outgoing invoices (supported : Belgian Structured Communication Type).
|
||||
3) When the previous step doesn't find a match, the transaction counterparty is located via the Bank Account Number configured on the OpenERP Customer and Supplier records.
|
||||
4) In case the previous steps are not successful, the transaction is generated by using the 'Default Account for Unrecognized Movement' field of the CODA File Import wizard in order to allow further manual processing.
|
||||
-------------------------------------------------------------------------------
|
||||
1) The Company's Bank Account Number of the CODA statement is compared against
|
||||
the Bank Account Number field of the Company's CODA Bank Account
|
||||
configuration records (whereby bank accounts defined in type='info'
|
||||
configuration records are ignored). If this is the case an 'internal transfer'
|
||||
transaction is generated using the 'Internal Transfer Account' field of the
|
||||
CODA File Import wizard.
|
||||
2) As a second step the 'Structured Communication' field of the CODA transaction
|
||||
line is matched against the reference field of in- and outgoing invoices
|
||||
(supported : Belgian Structured Communication Type).
|
||||
3) When the previous step doesn't find a match, the transaction counterparty is
|
||||
located via the Bank Account Number configured on the OpenERP Customer and
|
||||
Supplier records.
|
||||
4) In case the previous steps are not successful, the transaction is generated
|
||||
by using the 'Default Account for Unrecognized Movement' field of the CODA
|
||||
File Import wizard in order to allow further manual processing.
|
||||
|
||||
In stead of a manual adjustment of the generated Bank Statements, you can also
|
||||
re-import the CODA after updating the OpenERP database with the information that
|
||||
was missing to allow automatic reconciliation.
|
||||
|
||||
Remark on CODA V1 support:
|
||||
In some cases a transaction code, transaction category or structured communication code has been given a new or clearer description in CODA V2.
|
||||
The description provided by the CODA configuration tables is based upon the CODA V2.2 specifications.
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
In some cases a transaction code, transaction category or structured
|
||||
communication code has been given a new or clearer description in CODA V2.The
|
||||
description provided by the CODA configuration tables is based upon the CODA
|
||||
V2.2 specifications.
|
||||
If required, you can manually adjust the descriptions via the CODA configuration menu.
|
||||
''',
|
||||
"images" : ["images/coda_logs.jpeg","images/import_coda_logs.jpeg"],
|
||||
"depends": ['account_voucher','base_iban', 'l10n_be_invoice_bba', 'account_bank_statement_extensions'],
|
||||
"demo_xml": [],
|
||||
"init_xml": [
|
||||
'images' : ['images/coda_logs.jpeg','images/import_coda_logs.jpeg'],
|
||||
'depends': ['account_voucher','base_iban', 'l10n_be_invoice_bba', 'account_bank_statement_extensions'],
|
||||
'demo': [],
|
||||
'data': [
|
||||
'account_coda_trans_type.xml',
|
||||
'account_coda_trans_code.xml',
|
||||
'account_coda_trans_category.xml',
|
||||
'account_coda_comm_type.xml',
|
||||
],
|
||||
"update_xml" : [
|
||||
'security/ir.model.access.csv',
|
||||
'security/account_security.xml',
|
||||
'account_coda_wizard.xml',
|
||||
'account_coda_view.xml',
|
||||
],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"license": 'AGPL-3',
|
||||
"certificate" : "001237207321716002029",
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'license': 'AGPL-3',
|
||||
'certificate' : '001237207321716002029',
|
||||
}
|
||||
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -28,30 +28,27 @@ Module to automate letters for unpaid invoices, with multi-level recalls.
|
|||
==========================================================================
|
||||
|
||||
You can define your multiple levels of recall through the menu:
|
||||
---------------------------------------------------------------
|
||||
**Invoicing** / **Configuration** / **Miscellaneous** / **Follow-ups**
|
||||
|
||||
Invoicing/Configuration/Miscellaneous/Follow-ups
|
||||
|
||||
Once it is defined, you can automatically print recalls every day through simply
|
||||
clicking on the menu:
|
||||
|
||||
Invoicing/Periodical Processing/Billing/Send follow-ups
|
||||
Once it is defined, you can automatically print recalls every day through simply clicking on the menu:
|
||||
------------------------------------------------------------------------------------------------------
|
||||
**Invoicing** / **Periodical Processing** / **Billing** / **Send follow-ups**
|
||||
|
||||
It will generate a PDF with all the letters according to the the different levels
|
||||
of recall defined. You can define different policies for different companies. You
|
||||
can also send mail to the customer.
|
||||
|
||||
Note that if you want to check the follow-up level for a given partner/account
|
||||
entry, you can do from in the menu:
|
||||
|
||||
Invoicing/Reporting/Generic Reporting/Partners/Follow-ups Sent
|
||||
Note that if you want to check the follow-up level for a given partner/account entry, you can do from in the menu:
|
||||
------------------------------------------------------------------------------------------------------------------
|
||||
**Invoicing** / **Reporting** / **Generic Reporting** / **Partners** / **Follow-ups Sent**
|
||||
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/follow_ups.jpeg','images/send_followups.jpeg'],
|
||||
'depends': ['account_accountant', 'mail'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/account_followup_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/account_followup_print_view.xml',
|
||||
|
@ -60,7 +57,7 @@ entry, you can do from in the menu:
|
|||
'account_followup_view.xml',
|
||||
'account_followup_data.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'test': [
|
||||
'test/account_followup.yml',
|
||||
'test/account_followup_report.yml',
|
||||
|
|
|
@ -20,26 +20,31 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name": "Suppliers Payment Management",
|
||||
"version": "1.1",
|
||||
"author": "OpenERP SA",
|
||||
"category": "Accounting & Finance",
|
||||
"description": """
|
||||
'name': 'Suppliers Payment Management',
|
||||
'version': '1.1',
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Accounting & Finance',
|
||||
'description': """
|
||||
Module to manage the payment of your supplier invoices.
|
||||
=======================================================
|
||||
|
||||
This module allows you to create and manage your payment orders, with purposes to
|
||||
---------------------------------------------------------------------------------
|
||||
* serve as base for an easy plug-in of various automated payment mechanisms.
|
||||
* provide a more efficient way to manage invoice payment.
|
||||
|
||||
Warning:
|
||||
--------
|
||||
The confirmation of a payment order does _not_ create accounting entries, it just records the fact that you gave your payment order to your bank. The booking of your order must be encoded as usual through a bank statement. Indeed, it's only when you get the confirmation from your bank that your order has been accepted that you can book it in your accounting. To help you with that operation, you have a new option to import payment orders as bank statement lines.
|
||||
~~~~~~~~
|
||||
The confirmation of a payment order does _not_ create accounting entries, it just
|
||||
records the fact that you gave your payment order to your bank. The booking of
|
||||
your order must be encoded as usual through a bank statement. Indeed, it's only
|
||||
when you get the confirmation from your bank that your order has been accepted
|
||||
that you can book it in your accounting. To help you with that operation, you
|
||||
have a new option to import payment orders as bank statement lines.
|
||||
""",
|
||||
'images': ['images/payment_mode.jpeg','images/payment_order.jpeg'],
|
||||
'depends': ['account','account_voucher'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/account_payment_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/account_payment_pay_view.xml',
|
||||
|
@ -51,7 +56,7 @@ The confirmation of a payment order does _not_ create accounting entries, it jus
|
|||
'account_invoice_view.xml',
|
||||
'account_payment_report.xml',
|
||||
],
|
||||
'demo_xml': ['account_payment_demo.xml'],
|
||||
'demo': ['account_payment_demo.xml'],
|
||||
'test': [
|
||||
'test/account_payment_demo.yml',
|
||||
'test/cancel_payment_order.yml',
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
{
|
||||
'name': 'Entries Sequence Numbering',
|
||||
'version': '1.1',
|
||||
"category": 'Accounting & Finance',
|
||||
'category': 'Accounting & Finance',
|
||||
'description': """
|
||||
This module maintains internal sequence number for accounting entries.
|
||||
======================================================================
|
||||
|
@ -30,6 +30,7 @@ This module maintains internal sequence number for accounting entries.
|
|||
Allows you to configure the accounting sequences to be maintained.
|
||||
|
||||
You can customize the following attributes of the sequence:
|
||||
-----------------------------------------------------------
|
||||
* Prefix
|
||||
* Suffix
|
||||
* Next Number
|
||||
|
@ -40,13 +41,12 @@ You can customize the following attributes of the sequence:
|
|||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/internal_sequence_number.jpeg'],
|
||||
'depends': ['account'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'account_sequence_data.xml',
|
||||
'account_sequence_installer_view.xml',
|
||||
'account_sequence.xml'
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '00475376442024623469',
|
||||
|
|
|
@ -20,12 +20,12 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "eInvoicing & Payments",
|
||||
"version" : "1.0",
|
||||
"author" : 'OpenERP SA',
|
||||
"summary": 'Send Invoices and Track Payments',
|
||||
"description": """
|
||||
eInvoicing & Payments module manage all Voucher Entries such as "Reconciliation Entries", "Adjustment Entries", "Closing or Opening Entries" for Sales, Purchase, Bank, Cash, Expense, Contra.
|
||||
'name' : 'eInvoicing & Payments',
|
||||
'version' : '1.0',
|
||||
'author' : 'OpenERP SA',
|
||||
'summary': 'Send Invoices and Track Payments',
|
||||
'description': """
|
||||
eInvoicing & Payments module manage all Voucher Entries such as 'Reconciliation Entries', 'Adjustment Entries', 'Closing or Opening Entries' for Sales, Purchase, Bank, Cash, Expense, Contra.
|
||||
==============================================================================================================================================================================================
|
||||
|
||||
* Voucher Entry
|
||||
|
@ -33,47 +33,43 @@ eInvoicing & Payments module manage all Voucher Entries such as "Reconciliation
|
|||
* Voucher Payment [Customer & Supplier]
|
||||
* Cheque Register
|
||||
""",
|
||||
"category": 'Accounting & Finance',
|
||||
"sequence": 4,
|
||||
"website" : "http://openerp.com",
|
||||
"images" : ["images/customer_payment.jpeg","images/journal_voucher.jpeg","images/sales_receipt.jpeg","images/supplier_voucher.jpeg"],
|
||||
"depends" : ["account"],
|
||||
"init_xml" : [
|
||||
'category': 'Accounting & Finance',
|
||||
'sequence': 4,
|
||||
'website' : 'http://openerp.com',
|
||||
'images' : ['images/customer_payment.jpeg','images/journal_voucher.jpeg','images/sales_receipt.jpeg','images/supplier_voucher.jpeg'],
|
||||
'depends' : ['account'],
|
||||
'demo' : [],
|
||||
'data' : [
|
||||
'security/ir.model.access.csv',
|
||||
'account_voucher_sequence.xml',
|
||||
'account_voucher_workflow.xml',
|
||||
'account_voucher_report.xml',
|
||||
'wizard/account_statement_from_invoice_view.xml',
|
||||
'account_voucher_view.xml',
|
||||
'voucher_payment_receipt_view.xml',
|
||||
'voucher_sales_purchase_view.xml',
|
||||
'account_voucher_wizard.xml',
|
||||
'account_voucher_pay_invoice.xml',
|
||||
'report/account_voucher_sales_receipt_view.xml',
|
||||
'security/account_voucher_security.xml',
|
||||
'account_voucher_data.xml',
|
||||
],
|
||||
|
||||
"demo_xml" : [],
|
||||
|
||||
"update_xml" : [
|
||||
"security/ir.model.access.csv",
|
||||
"account_voucher_sequence.xml",
|
||||
"account_voucher_workflow.xml",
|
||||
"account_voucher_report.xml",
|
||||
"wizard/account_statement_from_invoice_view.xml",
|
||||
"account_voucher_view.xml",
|
||||
"voucher_payment_receipt_view.xml",
|
||||
"voucher_sales_purchase_view.xml",
|
||||
"account_voucher_wizard.xml",
|
||||
"account_voucher_pay_invoice.xml",
|
||||
"report/account_voucher_sales_receipt_view.xml",
|
||||
"security/account_voucher_security.xml"
|
||||
],
|
||||
"test" : [
|
||||
"test/account_voucher.yml",
|
||||
"test/sales_receipt.yml",
|
||||
"test/sales_payment.yml",
|
||||
"test/account_voucher_report.yml",
|
||||
"test/case1_usd_usd.yml",
|
||||
"test/case2_usd_eur_debtor_in_eur.yml",
|
||||
"test/case2_usd_eur_debtor_in_usd.yml",
|
||||
"test/case3_eur_eur.yml",
|
||||
"test/case4_cad_chf.yml",
|
||||
"test/case_eur_usd.yml",
|
||||
'test' : [
|
||||
'test/account_voucher.yml',
|
||||
'test/sales_receipt.yml',
|
||||
'test/sales_payment.yml',
|
||||
'test/account_voucher_report.yml',
|
||||
'test/case1_usd_usd.yml',
|
||||
'test/case2_usd_eur_debtor_in_eur.yml',
|
||||
'test/case2_usd_eur_debtor_in_usd.yml',
|
||||
'test/case3_eur_eur.yml',
|
||||
'test/case4_cad_chf.yml',
|
||||
'test/case_eur_usd.yml',
|
||||
],
|
||||
'certificate': '0037580727101',
|
||||
"auto_install": False,
|
||||
"application": True,
|
||||
"installable": True,
|
||||
'auto_install': False,
|
||||
'application': True,
|
||||
'installable': True,
|
||||
}
|
||||
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -54,7 +54,7 @@
|
|||
currency_id: base.EUR
|
||||
journal_id: account.bank_journal
|
||||
name: Voucher Axelor
|
||||
narration: Basic PC
|
||||
narration: PC Assemble SC234
|
||||
line_dr_ids:
|
||||
- account_id: account.cash
|
||||
amount: 1000.0
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
company_id: base.main_company
|
||||
journal_id: account.bank_journal
|
||||
name: Voucher Axelor
|
||||
narration: Basic PC
|
||||
narration: PC Assemble SC234
|
||||
amount: 1000.0
|
||||
line_ids:
|
||||
- account_id: account.cash
|
||||
|
|
|
@ -79,7 +79,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 200.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
@ -112,7 +112,7 @@
|
|||
period_id: account.period_2
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 100.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -50,7 +50,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_expense
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 200.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
@ -85,7 +85,7 @@
|
|||
type : in_invoice
|
||||
invoice_line:
|
||||
- account_id: account.a_expense
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 100.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -85,7 +85,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 200.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
@ -118,7 +118,7 @@
|
|||
period_id: account.period_2
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 100.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -85,7 +85,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 200.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
@ -118,7 +118,7 @@
|
|||
period_id: account.period_2
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 100.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -39,7 +39,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 150.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
@ -72,7 +72,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 80.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -73,7 +73,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 200.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -52,7 +52,7 @@
|
|||
period_id: account.period_1
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 1000.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
currency_id: base.EUR
|
||||
invoice_line:
|
||||
- account_id: account.a_sale
|
||||
name: '[PC1] Basic PC'
|
||||
name: '[PCSC234] PC Assemble SC234'
|
||||
price_unit: 450.0
|
||||
quantity: 1.0
|
||||
product_id: product.product_product_3
|
||||
|
|
|
@ -20,13 +20,13 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Analytic Accounting",
|
||||
"version": "1.1",
|
||||
"author" : "OpenERP SA",
|
||||
"website" : "http://www.openerp.com",
|
||||
"category": 'Hidden/Dependency',
|
||||
"depends" : ["base", "decimal_precision", "mail"],
|
||||
"description": """
|
||||
'name' : 'Analytic Accounting',
|
||||
'version': '1.1',
|
||||
'author' : 'OpenERP SA',
|
||||
'website' : 'http://www.openerp.com',
|
||||
'category': 'Hidden/Dependency',
|
||||
'depends' : ['base', 'decimal_precision', 'mail'],
|
||||
'description': """
|
||||
Module for defining analytic accounting object.
|
||||
===============================================
|
||||
|
||||
|
@ -34,16 +34,15 @@ In OpenERP, analytic accounts are linked to general accounts but are treated
|
|||
totally independently. So, you can enter various different analytic operations
|
||||
that have no counterpart in the general financial accounts.
|
||||
""",
|
||||
"init_xml" : [],
|
||||
"update_xml": ['security/analytic_security.xml',
|
||||
"security/ir.model.access.csv",
|
||||
"analytic_sequence.xml",
|
||||
"analytic_view.xml"
|
||||
],
|
||||
'demo_xml': [
|
||||
'data': [
|
||||
'security/analytic_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'analytic_sequence.xml',
|
||||
'analytic_view.xml'
|
||||
],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate' : "00462253285027988541",
|
||||
'certificate' : '00462253285027988541',
|
||||
}
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -26,18 +26,14 @@
|
|||
'category': 'Hidden',
|
||||
'description': """
|
||||
This module is for modifying project view to show some data related to the hr_expense module.
|
||||
|
||||
=============================================================================================
|
||||
""",
|
||||
"author": "OpenERP S.A.",
|
||||
"website": "http://www.openerp.com/",
|
||||
"depends": ["analytic_contract_hr_expense","project"],
|
||||
"init_xml": [],
|
||||
"update_xml": [
|
||||
"analytic_contract_expense_project_view.xml",
|
||||
],
|
||||
'demo_xml': [],
|
||||
"css" : [
|
||||
],
|
||||
'author': 'OpenERP S.A.',
|
||||
'website': 'http://www.openerp.com/',
|
||||
'depends': ['analytic_contract_hr_expense','project'],
|
||||
'data': ['analytic_contract_expense_project_view.xml'],
|
||||
'demo': [],
|
||||
'css' : [],
|
||||
'installable': True,
|
||||
'auto_install': True,
|
||||
}
|
||||
|
|
|
@ -26,18 +26,14 @@
|
|||
'category': 'Hidden',
|
||||
'description': """
|
||||
This module is for modifying account analytic view to show some data related to the hr_expense module.
|
||||
|
||||
======================================================================================================
|
||||
""",
|
||||
"author": "OpenERP S.A.",
|
||||
"website": "http://www.openerp.com/",
|
||||
"depends": ["hr_expense","account_analytic_analysis"],
|
||||
"init_xml": [],
|
||||
"update_xml": [
|
||||
"analytic_contract_hr_expense_view.xml",
|
||||
],
|
||||
'demo_xml': [],
|
||||
"css" : [
|
||||
],
|
||||
'author': 'OpenERP S.A.',
|
||||
'website': 'http://www.openerp.com/',
|
||||
'depends': ['hr_expense','account_analytic_analysis'],
|
||||
'data': ['analytic_contract_hr_expense_view.xml'],
|
||||
'demo': [],
|
||||
'css' : [],
|
||||
'installable': True,
|
||||
'auto_install': True,
|
||||
}
|
||||
|
|
|
@ -20,18 +20,18 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Contract on Project",
|
||||
"version": "1.1",
|
||||
"author" : "OpenERP SA",
|
||||
'name' : 'Contract on Project',
|
||||
'version': '1.1',
|
||||
'author' : 'OpenERP SA',
|
||||
'category': 'Hidden',
|
||||
"website" : "http://www.openerp.com",
|
||||
"depends" : ["project", "account_analytic_analysis"],
|
||||
"description": """
|
||||
'website' : 'http://www.openerp.com',
|
||||
'depends' : ['project', 'account_analytic_analysis'],
|
||||
'description': """
|
||||
Add "Contract Data" in project view.
|
||||
====================================
|
||||
""",
|
||||
"init_xml" : [],
|
||||
"update_xml": ["analytic_contract_project_view.xml"],
|
||||
'demo_xml': [],
|
||||
'data': ['analytic_contract_project_view.xml'],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': True,
|
||||
}
|
||||
|
|
|
@ -41,9 +41,8 @@ compatible with older configurations.
|
|||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/analytic_user_function.jpeg'],
|
||||
'depends': ['hr_timesheet_sheet'],
|
||||
'init_xml': [],
|
||||
'update_xml': ['analytic_user_function_view.xml', 'security/ir.model.access.csv'],
|
||||
'demo_xml': [],
|
||||
'data': ['analytic_user_function_view.xml', 'security/ir.model.access.csv'],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0082277138269',
|
||||
|
|
|
@ -40,11 +40,7 @@ anonymization process to recover your previous data.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [],
|
||||
'demo_xml': [
|
||||
'anonymization_demo.xml',
|
||||
],
|
||||
'demo': ['anonymization_demo.xml'],
|
||||
'data': [
|
||||
'ir.model.fields.anonymization.csv',
|
||||
'security/ir.model.access.csv',
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" ?>
|
||||
<openerp>
|
||||
<data>
|
||||
<data noupdate="1">
|
||||
|
||||
<!-- FIELD LIST -->
|
||||
|
||||
|
|
|
@ -33,8 +33,8 @@ membership products (schemes).
|
|||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['base_setup', 'membership', 'event'],
|
||||
'update_xml': ['security/ir.model.access.csv', 'profile_association.xml'],
|
||||
'demo_xml': [],
|
||||
'data': ['security/ir.model.access.csv', 'profile_association.xml'],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0078696047261',
|
||||
|
|
|
@ -34,13 +34,12 @@ and can check logs.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'wizard/audittrail_view_log_view.xml',
|
||||
'audittrail_view.xml',
|
||||
'security/ir.model.access.csv',
|
||||
],
|
||||
'demo_xml': ['audittrail_demo.xml'],
|
||||
'demo': ['audittrail_demo.xml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0062572348749',
|
||||
|
|
|
@ -1,19 +1,16 @@
|
|||
{
|
||||
'name': 'Anonymous',
|
||||
'description': 'Allow anonymous access to OpenERP.',
|
||||
'description': """
|
||||
Allow anonymous access to OpenERP.
|
||||
==================================
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'version': '1.0',
|
||||
'category': 'Authentication',
|
||||
'website': 'http://www.openerp.com',
|
||||
'installable': True,
|
||||
'depends': ['web'],
|
||||
'data': [
|
||||
'auth_anonymous.xml',
|
||||
],
|
||||
'js': [
|
||||
'static/src/js/auth_anonymous.js',
|
||||
],
|
||||
'qweb': [
|
||||
'static/src/xml/auth_anonymous.xml',
|
||||
],
|
||||
'data': ['auth_anonymous.xml'],
|
||||
'js': ['static/src/js/auth_anonymous.js'],
|
||||
'qweb': ['static/src/xml/auth_anonymous.xml'],
|
||||
}
|
||||
|
|
|
@ -19,18 +19,18 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Authentication via LDAP",
|
||||
"version" : "1.0",
|
||||
"depends" : ["base"],
|
||||
"images" : ["images/ldap_configuration.jpeg"],
|
||||
"author" : "OpenERP SA",
|
||||
"description": """
|
||||
'name' : 'Authentication via LDAP',
|
||||
'version' : '1.0',
|
||||
'depends' : ['base'],
|
||||
'images' : ['images/ldap_configuration.jpeg'],
|
||||
'author' : 'OpenERP SA',
|
||||
'description': """
|
||||
Adds support for authentication by LDAP server.
|
||||
===============================================
|
||||
This module allows users to login with their LDAP username and password, and
|
||||
will automatically create OpenERP users for them on the fly.
|
||||
|
||||
Note: This module only work on servers who have Python's ``ldap`` module installed.
|
||||
**Note:** This module only work on servers who have Python's ``ldap`` module installed.
|
||||
|
||||
Configuration:
|
||||
--------------
|
||||
|
@ -64,7 +64,7 @@ It is also possible to have local OpenERP users in the database along with
|
|||
LDAP-authenticated users (the Administrator account is one obvious example).
|
||||
|
||||
Here is how it works:
|
||||
|
||||
---------------------
|
||||
* The system first attempts to authenticate users against the local OpenERP
|
||||
database;
|
||||
* if this authentication fails (for example because the user has no local
|
||||
|
@ -84,7 +84,7 @@ Template*. If set, this user will be used as template to create the local users
|
|||
whenever someone authenticates for the first time via LDAP authentication. This
|
||||
allows pre-setting the default groups and menus of the first-time users.
|
||||
|
||||
Warning: if you set a password for the user template, this password will be
|
||||
**Warning:** if you set a password for the user template, this password will be
|
||||
assigned as local password for each new LDAP user, effectively setting
|
||||
a *master password* for these users (until manually changed). You
|
||||
usually do not want this. One easy way to setup a template user is to
|
||||
|
@ -98,19 +98,17 @@ Interaction with base_crypt:
|
|||
The base_crypt module is not compatible with this module, and will disable LDAP
|
||||
authentication if installed at the same time.
|
||||
""",
|
||||
|
||||
|
||||
"website" : "http://www.openerp.com",
|
||||
"category" : "Authentication",
|
||||
"data" : [
|
||||
"users_ldap_view.xml",
|
||||
"user_ldap_installer.xml",
|
||||
"security/ir.model.access.csv",
|
||||
'website' : 'http://www.openerp.com',
|
||||
'category' : 'Authentication',
|
||||
'data' : [
|
||||
'users_ldap_view.xml',
|
||||
'user_ldap_installer.xml',
|
||||
'security/ir.model.access.csv',
|
||||
],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"certificate" : "001141446349334700221",
|
||||
"external_dependencies" : {
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'certificate' : '001141446349334700221',
|
||||
'external_dependencies' : {
|
||||
'python' : ['ldap'],
|
||||
}
|
||||
}
|
||||
|
|
|
@ -24,27 +24,21 @@
|
|||
'name': 'OAuth2 Authentication',
|
||||
'version': '1.0',
|
||||
'category': 'Tools',
|
||||
'description': """Allow users to login through Google OAuth2.""",
|
||||
'description': """
|
||||
Allow users to login through Google OAuth2.
|
||||
===========================================
|
||||
""",
|
||||
'author': 'Victor Tabuenca',
|
||||
'maintainer': 'OpenERP s.a.',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base', 'web', 'base_setup'],
|
||||
'data': [
|
||||
'auth_oauth_data.xml',
|
||||
'auth_oauth_view.xml'
|
||||
],
|
||||
'update_xml': [
|
||||
'auth_oauth_view.xml',
|
||||
'res_config.xml',
|
||||
],
|
||||
'js': [
|
||||
'static/src/js/auth_oauth.js',
|
||||
],
|
||||
'css': [
|
||||
'static/lib/zocial/css/zocial.css',
|
||||
],
|
||||
'qweb': [
|
||||
'static/src/xml/auth_oauth.xml',
|
||||
],
|
||||
'js': ['static/src/js/auth_oauth.js'],
|
||||
'css': ['static/lib/zocial/css/zocial.css'],
|
||||
'qweb': ['static/src/xml/auth_oauth.xml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
}
|
||||
|
|
|
@ -24,23 +24,18 @@
|
|||
'name': 'OpenID Authentification',
|
||||
'version': '2.0',
|
||||
'category': 'Tools',
|
||||
'description': """Allow users to login through OpenID.""",
|
||||
'description': """
|
||||
Allow users to login through OpenID.
|
||||
====================================
|
||||
""",
|
||||
'author': 'OpenERP s.a.',
|
||||
'maintainer': 'OpenERP s.a.',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base', 'web'],
|
||||
'data': [
|
||||
'res_users.xml',
|
||||
],
|
||||
'js': [
|
||||
'static/src/js/auth_openid.js',
|
||||
],
|
||||
'css': [
|
||||
'static/src/css/openid.css',
|
||||
],
|
||||
'qweb': [
|
||||
'static/src/xml/auth_openid.xml',
|
||||
],
|
||||
'data': ['res_users.xml'],
|
||||
'js': ['static/src/js/auth_openid.js'],
|
||||
'css': ['static/src/css/openid.css'],
|
||||
'qweb': ['static/src/xml/auth_openid.xml'],
|
||||
'external_dependencies': {
|
||||
'python' : ['openid'],
|
||||
},
|
||||
|
|
|
@ -1,22 +1,17 @@
|
|||
{
|
||||
'name': 'Reset Password',
|
||||
'description': 'Allow users to reset their password from the login page',
|
||||
'description': """
|
||||
Allow users to reset their password from the login page.
|
||||
========================================================
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'version': '1.0',
|
||||
'category': 'Authentication',
|
||||
'website': 'http://www.openerp.com',
|
||||
'installable': True,
|
||||
'depends': ['auth_anonymous', 'email_template'],
|
||||
'data': [
|
||||
'auth_reset_password.xml',
|
||||
],
|
||||
'js': [
|
||||
'static/src/js/reset_password.js',
|
||||
],
|
||||
'css': [
|
||||
'static/src/css/reset_password.css',
|
||||
],
|
||||
'qweb': [
|
||||
'static/src/xml/reset_password.xml',
|
||||
],
|
||||
'data': ['auth_reset_password.xml'],
|
||||
'js': ['static/src/js/reset_password.js'],
|
||||
'css': ['static/src/css/reset_password.css'],
|
||||
'qweb': ['static/src/xml/reset_password.xml'],
|
||||
}
|
||||
|
|
|
@ -21,20 +21,17 @@
|
|||
|
||||
{
|
||||
'name': 'Signup',
|
||||
'description': 'Allow users to sign up',
|
||||
'description': """
|
||||
Allow users to sign up.
|
||||
=======================
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'version': '1.0',
|
||||
'category': 'Authentication',
|
||||
'website': 'http://www.openerp.com',
|
||||
'installable': True,
|
||||
'depends': ['base_setup'],
|
||||
'data': [
|
||||
'res_config.xml',
|
||||
],
|
||||
'js': [
|
||||
'static/src/js/auth_signup.js',
|
||||
],
|
||||
'qweb': [
|
||||
'static/src/xml/auth_signup.xml',
|
||||
],
|
||||
'data': ['res_config.xml'],
|
||||
'js': ['static/src/js/auth_signup.js'],
|
||||
'qweb': ['static/src/xml/auth_signup.xml'],
|
||||
}
|
||||
|
|
|
@ -29,21 +29,19 @@ This module allows to implement action rules for any object.
|
|||
|
||||
Use automated actions to automatically trigger actions for various screens.
|
||||
|
||||
Example: A lead created by a specific user may be automatically set to a specific
|
||||
**Example:** A lead created by a specific user may be automatically set to a specific
|
||||
sales team, or an opportunity which still has status pending after 14 days might
|
||||
trigger an automatic reminder email.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base', 'mail'],
|
||||
'init_xml': [
|
||||
'base_action_rule_data.xml'
|
||||
],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'base_action_rule_view.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'base_action_rule_data.xml'
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate' : '001017908446466333429',
|
||||
|
|
|
@ -20,14 +20,15 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name": "Calendar Layer",
|
||||
"version": "1.0",
|
||||
"depends": ["base", "base_status", "mail", "base_action_rule"],
|
||||
'name': 'Calendar Layer',
|
||||
'version': '1.0',
|
||||
'depends': ['base', 'base_status', 'mail', 'base_action_rule'],
|
||||
'description': """
|
||||
This is a full-featured calendar system.
|
||||
========================================
|
||||
|
||||
It supports:
|
||||
------------
|
||||
- Calendar of events
|
||||
- Alerts (create requests)
|
||||
- Recurring events
|
||||
|
@ -35,25 +36,23 @@ It supports:
|
|||
|
||||
If you need to manage your meetings, you should install the CRM module.
|
||||
""",
|
||||
"author": "OpenERP SA",
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Hidden/Dependency',
|
||||
'website': 'http://www.openerp.com',
|
||||
"init_xml": [
|
||||
'base_calendar_data.xml',
|
||||
'crm_meeting_data.xml',
|
||||
],
|
||||
"demo_xml": ['crm_meeting_demo.xml'],
|
||||
"update_xml": [
|
||||
'demo': ['crm_meeting_demo.xml'],
|
||||
'data': [
|
||||
'security/calendar_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/base_calendar_invite_attendee_view.xml',
|
||||
'base_calendar_view.xml',
|
||||
'crm_meeting_view.xml',
|
||||
'base_calendar_data.xml',
|
||||
'crm_meeting_data.xml',
|
||||
],
|
||||
"test" : ['test/base_calendar_test.yml'],
|
||||
"installable": True,
|
||||
"auto_install": False,
|
||||
"certificate": "00694071962960352821",
|
||||
'test' : ['test/base_calendar_test.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '00694071962960352821',
|
||||
'images': ['images/base_calendar1.jpeg','images/base_calendar2.jpeg','images/base_calendar3.jpeg','images/base_calendar4.jpeg',],
|
||||
}
|
||||
|
||||
|
|
|
@ -16,6 +16,14 @@
|
|||
<field name="name">Off-site Meeting</field>
|
||||
</record>
|
||||
|
||||
<record model="crm.meeting.type" id="categ_meet4">
|
||||
<field name="name">Open Discussion</field>
|
||||
</record>
|
||||
|
||||
<record model="crm.meeting.type" id="categ_meet5">
|
||||
<field name="name">Feedback Meeting</field>
|
||||
</record>
|
||||
|
||||
<record model="res.request.link" id="request_link_meeting">
|
||||
<field name="name">Meeting</field>
|
||||
<field name="object">crm.meeting</field>
|
||||
|
|
|
@ -27,7 +27,7 @@
|
|||
<field eval="time.strftime('%Y-%m-05 12:00:00')" name="date"/>
|
||||
<field eval="time.strftime('%Y-%m-05 19:00:00')" name="date_deadline"/>
|
||||
<field eval="7.0" name="duration"/>
|
||||
<field name="state">draft</field>
|
||||
<field name="state">open</field>
|
||||
</record>
|
||||
|
||||
<record id="crm_meeting_3" model="crm.meeting">
|
||||
|
@ -39,7 +39,7 @@
|
|||
<field eval="time.strftime('%Y-%m-12 15:55:05')" name="date"/>
|
||||
<field eval="time.strftime('%Y-%m-12 18:55:05')" name="date_deadline"/>
|
||||
<field eval="3.0" name="duration"/>
|
||||
<field name="state">done</field>
|
||||
<field name="state">open</field>
|
||||
</record>
|
||||
|
||||
<record id="crm_meeting_4" model="crm.meeting">
|
||||
|
@ -61,7 +61,7 @@
|
|||
<field eval="time.strftime('%Y-%m-22 11:05:00')" name="date"/>
|
||||
<field eval="time.strftime('%Y-%m-22 16:05:00')" name="date_deadline"/>
|
||||
<field eval="5" name="duration"/>
|
||||
<field name="state">draft</field>
|
||||
<field name="state">open</field>
|
||||
</record>
|
||||
|
||||
<record id="crm_meeting_6" model="crm.meeting">
|
||||
|
@ -72,7 +72,7 @@
|
|||
<field eval="time.strftime('%Y-%m-18 2:00:00')" name="date"/>
|
||||
<field eval="time.strftime('%Y-%m-18 10:30:00')" name="date_deadline"/>
|
||||
<field eval="8.5" name="duration"/>
|
||||
<field name="state">done</field>
|
||||
<field name="state">open</field>
|
||||
</record>
|
||||
</data>
|
||||
</openerp>
|
||||
|
|
|
@ -70,7 +70,7 @@
|
|||
<field name="arch" type="xml">
|
||||
<form string="Meetings" version="7.0">
|
||||
<header>
|
||||
<field name="state"/>
|
||||
<field name="state" invisible="True"/>
|
||||
</header>
|
||||
<sheet>
|
||||
<div class="oe_title">
|
||||
|
@ -115,7 +115,7 @@
|
|||
<label for="allday" string="All Day?"/>)
|
||||
</div>
|
||||
<field name="recurrency"
|
||||
attrs="{'readonly': ['|', ('recurrent_uid','!=',False), ('state','=','done')]}"/>
|
||||
attrs="{'readonly': [('recurrent_uid','!=',False)]}"/>
|
||||
</group>
|
||||
<group>
|
||||
<field name="alarm_id" widget="selection" />
|
||||
|
@ -171,7 +171,6 @@
|
|||
<button string="Invite People"
|
||||
name="%(base_calendar.action_view_calendar_invite_attendee_wizard)d"
|
||||
icon="terp-partner" type="action"
|
||||
attrs="{'readonly': [('state', '=', 'done')]}"
|
||||
context="{'model' : 'crm.meeting', 'attendee_field':'attendee_ids'}" colspan="2"/>
|
||||
<field name="attendee_ids" widget="one2many" mode="tree">
|
||||
<tree string="Invitation details" editable="top">
|
||||
|
@ -245,12 +244,11 @@
|
|||
<field name="name">CRM - Meetings Tree</field>
|
||||
<field name="model">crm.meeting</field>
|
||||
<field name="arch" type="xml">
|
||||
<tree string="Meetings" fonts="bold:needaction_pending==True"
|
||||
colors="red:state=='open';black:state in ('draft', 'cancel','done','pending')">
|
||||
<tree string="Meetings" fonts="bold:needaction_pending==True">
|
||||
<field name="name" string="Subject" />
|
||||
<field name="user_id"/>
|
||||
<field name="date"/>
|
||||
<field name="state"/>
|
||||
<field name="state" invisible="True"/>
|
||||
<field name="duration" />
|
||||
<field name="needaction_pending" invisible="1"/>
|
||||
</tree>
|
||||
|
|
|
@ -19,18 +19,18 @@
|
|||
#
|
||||
##############################################################################
|
||||
{
|
||||
"name" : "DB Password Encryption",
|
||||
"version" : "1.1",
|
||||
"author" : ['OpenERP SA', "FS3"],
|
||||
"maintainer" : "OpenERP SA",
|
||||
"website" : "http://www.openerp.com",
|
||||
"category" : "Tools",
|
||||
"description": """
|
||||
'name': 'DB Password Encryption',
|
||||
'version': '1.1',
|
||||
'author': ['OpenERP SA', 'FS3'],
|
||||
'maintainer': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'category': 'Tools',
|
||||
'description': """
|
||||
Replaces cleartext passwords in the database with a secure hash.
|
||||
================================================================
|
||||
|
||||
For your existing user base, the removal of the cleartext passwords occurs
|
||||
immediately when you instal base_crypt.
|
||||
immediately when you install base_crypt.
|
||||
|
||||
All passwords will be replaced by a secure, salted, cryptographic hash,
|
||||
preventing anyone from reading the original password in the database.
|
||||
|
@ -49,16 +49,16 @@ contain critical data. Appropriate security measures need to be implemented
|
|||
by the system administrator in all areas, such as: protection of database
|
||||
backups, system files, remote shell access, physical server access.
|
||||
|
||||
Interation with LDAP authentication:
|
||||
------------------------------------
|
||||
Interaction with LDAP authentication:
|
||||
-------------------------------------
|
||||
This module is currently not compatible with the ``user_ldap`` module and
|
||||
will disable LDAP authentication completely if installed at the same time.
|
||||
""",
|
||||
"depends" : ["base"],
|
||||
"data" : [],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"certificate" : "00721290471310299725",
|
||||
'depends': ['base'],
|
||||
'data': [],
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'certificate': '00721290471310299725',
|
||||
}
|
||||
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -21,10 +21,10 @@
|
|||
{
|
||||
'name': 'IBAN Bank Accounts',
|
||||
'version': '1.0',
|
||||
"category": 'Hidden/Dependency',
|
||||
'category': 'Hidden/Dependency',
|
||||
'description': """
|
||||
This module installs the base for IBAN (International Bank Account Number) bank accounts and checks for it's validity.
|
||||
=====================================================================================================================
|
||||
======================================================================================================================
|
||||
|
||||
The ability to extract the correctly represented local accounts from IBAN accounts
|
||||
with a single statement.
|
||||
|
@ -32,8 +32,7 @@ with a single statement.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': ['base_iban_data.xml'],
|
||||
'update_xml': ['base_iban_view.xml'],
|
||||
'data': ['base_iban_data.xml' , 'base_iban_view.xml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0050014379549',
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<openerp>
|
||||
<data>
|
||||
<data noupdate="1">
|
||||
|
||||
<!--
|
||||
Default bank account description
|
||||
|
|
|
@ -34,14 +34,13 @@ This module generates the Technical Guides of selected modules in Restructured T
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'base_module_doc_rst_view.xml',
|
||||
'wizard/generate_relation_graph_view.xml',
|
||||
'wizard/tech_guide_rst_view.xml',
|
||||
'module_report.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'certificate': '001288481437217734509',
|
||||
'images': ['images/base_module_doc_rst1.jpeg'],
|
||||
|
|
|
@ -39,19 +39,19 @@ This should help you to easily create reusable and publishable modules for custo
|
|||
configurations and demo/testing data.
|
||||
|
||||
How to use it?:
|
||||
---------------
|
||||
Run Settings/Technical/Module Creation/Export Customizations As a Module wizard.
|
||||
Select datetime criteria of recording and objects to be recorded and Record module.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/base_module_record_object_view.xml',
|
||||
'wizard/base_module_record_data_view.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'certificate': '0083134865813',
|
||||
'images': ['images/base_module_record1.jpeg','images/base_module_record2.jpeg','images/base_module_record3.jpeg',]
|
||||
|
|
|
@ -60,9 +60,8 @@ def _create_module(self, cr, uid, ids, context=None):
|
|||
"category" : "%(category)s",
|
||||
"description": \"\"\"%(description)s\"\"\",
|
||||
"depends" : [%(depends)s],
|
||||
"init_xml" : [ ],
|
||||
"demo_xml" : [ %(demo_name)s],
|
||||
"update_xml" : [%(update_name)s],
|
||||
"demo" : [ %(demo_name)s],
|
||||
"data" : [%(update_name)s],
|
||||
"installable": True
|
||||
} """ % data
|
||||
filewrite = {
|
||||
|
|
|
@ -34,9 +34,8 @@ Once you have modified it you can upload the report using the same wizard.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': ['wizard/base_report_design_view.xml'],
|
||||
'update_xml': ['base_report_designer_installer.xml'],
|
||||
'demo_xml': [],
|
||||
'data': ['wizard/base_report_design_view.xml' , 'base_report_designer_installer.xml'],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0056379010493',
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<openerp>
|
||||
<data>
|
||||
<data noupdate="1">
|
||||
<record id="view_base_report_sxw" model="ir.ui.view">
|
||||
<field name="name">Base Report sxw</field>
|
||||
<field name="model">base.report.sxw</field>
|
||||
|
|
|
@ -24,9 +24,8 @@
|
|||
'version': '1.0',
|
||||
'category': 'Hidden',
|
||||
'description': """
|
||||
This module handles state and stage. It is derived from the crm_base and
|
||||
crm_case classes from crm.
|
||||
========================================================================
|
||||
This module handles state and stage. It is derived from the crm_base and crm_case classes from crm.
|
||||
===================================================================================================
|
||||
|
||||
* ``base_state``: state management
|
||||
* ``base_stage``: stage management
|
||||
|
@ -34,9 +33,8 @@ crm_case classes from crm.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [],
|
||||
'demo_xml': [],
|
||||
'data': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
}
|
||||
|
|
|
@ -1,22 +1,19 @@
|
|||
# -*- encoding: utf-8 -*-
|
||||
{
|
||||
"name": "Base Tools",
|
||||
"author": "OpenERP SA",
|
||||
"version": "1.0",
|
||||
"depends": ["base"],
|
||||
"category" : "Hidden/Dependency",
|
||||
'name': 'Base Tools',
|
||||
'author': 'OpenERP SA',
|
||||
'version': '1.0',
|
||||
'depends': ['base'],
|
||||
'category' : 'Hidden/Dependency',
|
||||
'description': """
|
||||
Common base for tools modules.
|
||||
==============================
|
||||
|
||||
Creates menu link for Tools from where tools like survey, lunch, idea are accessible if installed.
|
||||
""",
|
||||
"init_xml": [],
|
||||
"update_xml": [
|
||||
'tools_view.xml'
|
||||
],
|
||||
"installable": True,
|
||||
"certificate" : "00571588675379342237"
|
||||
'data': ['tools_view.xml'],
|
||||
'installable': True,
|
||||
'certificate' : '00571588675379342237'
|
||||
}
|
||||
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
{
|
||||
'name': 'VAT Number Validation',
|
||||
'version': '1.0',
|
||||
"category": 'Hidden/Dependency',
|
||||
'category': 'Hidden/Dependency',
|
||||
'description': """
|
||||
VAT validation for Partner's VAT numbers.
|
||||
=========================================
|
||||
|
@ -33,11 +33,12 @@ be validated for all supported countries. The country is inferred from the
|
|||
will be validated using the Belgian rules.
|
||||
|
||||
There are two different levels of VAT number validation:
|
||||
|
||||
--------------------------------------------------------
|
||||
* By default, a simple off-line check is performed using the known validation
|
||||
rules for the country, usually a simple check digit. This is quick and
|
||||
always available, but allows numbers that are perhaps not truly allocated,
|
||||
or not valid anymore.
|
||||
|
||||
* When the "VAT VIES Check" option is enabled (in the configuration of the user's
|
||||
Company), VAT numbers will be instead submitted to the online EU VIES
|
||||
database, which will truly verify that the number is valid and currently
|
||||
|
|
|
@ -34,21 +34,14 @@ The user can also publish notes.
|
|||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['base'],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'board_view.xml',
|
||||
'board_mydashboard_view.xml'
|
||||
],
|
||||
"js": [
|
||||
'static/src/js/dashboard.js',
|
||||
],
|
||||
"css": [
|
||||
'static/src/css/dashboard.css',
|
||||
],
|
||||
'qweb': [
|
||||
"static/src/xml/*.xml",
|
||||
],
|
||||
|
||||
'js': ['static/src/js/dashboard.js'],
|
||||
'css': ['static/src/css/dashboard.css'],
|
||||
'qweb': ['static/src/xml/*.xml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0076912305725',
|
||||
|
|
|
@ -21,11 +21,11 @@
|
|||
|
||||
|
||||
{
|
||||
"name": "Share Calendar Using CalDAV",
|
||||
"version": "1.1",
|
||||
"depends": [
|
||||
"base",
|
||||
"document_webdav",
|
||||
'name': 'Share Calendar Using CalDAV',
|
||||
'version': '1.1',
|
||||
'depends': [
|
||||
'base',
|
||||
'document_webdav',
|
||||
],
|
||||
'description': """
|
||||
This module contains basic functionality for Caldav system.
|
||||
|
@ -37,34 +37,39 @@ This module contains basic functionality for Caldav system.
|
|||
- Provides iCal Import/Export functionality
|
||||
|
||||
To access Calendars using CalDAV clients, point them to:
|
||||
--------------------------------------------------------
|
||||
http://HOSTNAME:PORT/webdav/DATABASE_NAME/calendars/users/USERNAME/c
|
||||
|
||||
To access OpenERP Calendar using WebCal to remote site use the URL like:
|
||||
------------------------------------------------------------------------
|
||||
http://HOSTNAME:PORT/webdav/DATABASE_NAME/Calendars/CALENDAR_NAME.ics
|
||||
|
||||
Where,
|
||||
HOSTNAME: Host on which OpenERP server(With webdav) is running
|
||||
PORT : Port on which OpenERP server is running (By Default : 8069)
|
||||
DATABASE_NAME: Name of database on which OpenERP Calendar is created
|
||||
CALENDAR_NAME: Name of calendar to access
|
||||
**HOSTNAME:** Host on which OpenERP server(With webdav) is running
|
||||
|
||||
**PORT :** Port on which OpenERP server is running (By Default : 8069)
|
||||
|
||||
**DATABASE_NAME:** Name of database on which OpenERP Calendar is created
|
||||
|
||||
**CALENDAR_NAME:** Name of calendar to access
|
||||
""",
|
||||
'category': 'Hidden/Dependency',
|
||||
"author": "OpenERP SA",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
"init_xml": ["caldav_data.xml"],
|
||||
"demo_xml": [],
|
||||
"update_xml": [
|
||||
'demo': [],
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/calendar_event_export_view.xml',
|
||||
'wizard/calendar_event_import_view.xml',
|
||||
'wizard/calendar_event_subscribe_view.xml',
|
||||
'wizard/caldav_browse_view.xml',
|
||||
'caldav_view.xml',
|
||||
'caldav_setup.xml'
|
||||
'caldav_setup.xml',
|
||||
'caldav_data.xml'
|
||||
],
|
||||
"installable": True,
|
||||
"auto_install": False,
|
||||
"certificate": "00924841426645403741",
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '00924841426645403741',
|
||||
'images': ['images/calendar_collections.jpeg','images/calendars.jpeg','images/export_ics_file.jpeg'],
|
||||
}
|
||||
|
||||
|
|
|
@ -18,23 +18,22 @@
|
|||
#
|
||||
##############################################################################
|
||||
{
|
||||
"name" : "Claim on Deliveries",
|
||||
"version" : "1.0",
|
||||
"author" : "OpenERP SA",
|
||||
"category" : "Warehouse Management",
|
||||
"depends" : ["base", "crm_claim", "stock"],
|
||||
"init_xml" : [],
|
||||
"demo_xml" : [],
|
||||
"description": '''
|
||||
'name' : 'Claim on Deliveries',
|
||||
'version' : '1.0',
|
||||
'author' : 'OpenERP SA',
|
||||
'category' : 'Warehouse Management',
|
||||
'depends' : ['base', 'crm_claim', 'stock'],
|
||||
'demo' : [],
|
||||
'description': """
|
||||
Create a claim from a delivery order.
|
||||
=====================================
|
||||
|
||||
Adds a Claim link to the delivery order.
|
||||
''',
|
||||
"update_xml" : ["claim_delivery_view.xml"],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"certificate" : "001101649349223746957",
|
||||
""",
|
||||
'data' : ['claim_delivery_view.xml'],
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'certificate' : '001101649349223746957',
|
||||
'images': ['images/1_claim_link_delivery_order.jpeg'],
|
||||
}
|
||||
|
||||
|
|
|
@ -24,8 +24,8 @@
|
|||
'name': 'CRM',
|
||||
'version': '1.0',
|
||||
'category': 'Customer Relationship Management',
|
||||
"sequence": 2,
|
||||
"summary": "Leads, Opportunities, Agenda",
|
||||
'sequence': 2,
|
||||
'summary': 'Leads, Opportunities, Agenda',
|
||||
'description': """
|
||||
The generic OpenERP Customer Relationship Management.
|
||||
=====================================================
|
||||
|
@ -70,12 +70,11 @@ Creates a dashboard for CRM that includes:
|
|||
'board',
|
||||
'fetchmail'
|
||||
],
|
||||
'init_xml': [
|
||||
'data': [
|
||||
'crm_data.xml',
|
||||
'crm_lead_data.xml',
|
||||
'crm_phonecall_data.xml',
|
||||
],
|
||||
'update_xml': [
|
||||
|
||||
'security/crm_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
|
||||
|
@ -115,7 +114,7 @@ Creates a dashboard for CRM that includes:
|
|||
'res_config_view.xml',
|
||||
|
||||
],
|
||||
'demo_xml': [
|
||||
'demo': [
|
||||
'crm_demo.xml',
|
||||
'crm_lead_demo.xml',
|
||||
'crm_phonecall_demo.xml',
|
||||
|
|
|
@ -49,7 +49,6 @@ Can you send details,</field>
|
|||
<field name="section_id" ref="crm_case_section_3"/>
|
||||
<field name="user_id" ref="base.user_admin"/>
|
||||
<field name="stage_id" ref="stage_lead1"/>
|
||||
<field name="description">Want to know features and benifits to use the new software.</field>
|
||||
<field eval="1" name="active"/>
|
||||
</record>
|
||||
|
||||
|
@ -550,53 +549,86 @@ Andrew</field>
|
|||
|
||||
<!-- Some messages linked to the previous opportunity -->
|
||||
<record id="message_email0" model="mail.message">
|
||||
<field name="subject">Kitchen design</field>
|
||||
<field name="subject">Plan to buy a Laptop</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><![CDATA[Email0 inquiry]]></field>
|
||||
<field name="type">email</field>
|
||||
<field name="state">sent</field>
|
||||
<field name="user_id" ref="base.user_root"></field>
|
||||
</record>
|
||||
<record id="message_note0" model="mail.message">
|
||||
<field name="subject">Reply</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><![CDATA[Internal note0]]></field>
|
||||
<field name="type">comment</field>
|
||||
<field name="user_id" ref="base.user_root"></field>
|
||||
</record>
|
||||
<record id="message_note0_comment0" model="mail.message">
|
||||
<field name="subject">Reply</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><![CDATA[comment on note0]]></field>
|
||||
<field name="parent_id" ref="message_note0"/>
|
||||
<field name="type">comment</field>
|
||||
<field name="user_id" ref="base.user_root"></field>
|
||||
</record>
|
||||
<record id="message_note0_comment1" model="mail.message">
|
||||
<field name="subject">Reply</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><![CDATA[comment1 on note0]]></field>
|
||||
<field name="parent_id" ref="message_note0"/>
|
||||
<field name="type">comment</field>
|
||||
<field name="user_id" ref="base.user_root"></field>
|
||||
</record>
|
||||
<record id="message_email1" model="mail.message">
|
||||
<field name="subject">Your inquiry</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><![CDATA[hello, outgoing email]]></field>
|
||||
<field name="body_html"><![CDATA[Email0 inquiry]]><div><font size="2">Hello,</font></div><div><font size="2"><br></font></div><div><font size="2">I am interested in your company's product and I plan to buy a new laptop having latest technologies and affordable price.</font></div><div><font size="2">Can you please send me product catalogue?</font></div></field>
|
||||
<field name="type">email</field>
|
||||
<field name="state">received</field>
|
||||
<field name="user_id" ref="base.user_root"></field>
|
||||
<field name="user_id" ref="base.user_demo"/>
|
||||
</record>
|
||||
<record id="message_note0" model="mail.message">
|
||||
<field name="subject">Re: Plan to buy a Laptop</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="parent_id" ref="message_email0"/>
|
||||
<field name="content_subtype">plain</field>
|
||||
<field name="body_text">Dear Customer,
|
||||
Thanks for showing interest in our products.
|
||||
We have attached the catalogue,
|
||||
We would like to know your interests, Let us know if we can call you for more details.
|
||||
|
||||
Thanks</field>
|
||||
<field name="type">email</field>
|
||||
<field name="user_id" ref="base.user_root"/>
|
||||
<field name="state">sent</field>
|
||||
</record>
|
||||
<record id="message_note0_comment0" model="mail.message">
|
||||
<field name="subject">Re: Plan to buy a Laptop</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><div>Thanks for the information,</div><div>I will visit the store soon.</div></field>
|
||||
<field name="parent_id" ref="message_note0"/>
|
||||
<field name="type">email</field>
|
||||
<field name="user_id" ref="base.user_demo"/>
|
||||
<field name="state">received</field>
|
||||
</record>
|
||||
<record id="message_note0_comment1" model="mail.message">
|
||||
<field name="subject">Re: Plan to buy a Laptop</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">html</field>
|
||||
<field name="body_html"><font color="#1f1f1f">Can you tell me if the store is open at 9:00 PM?</b></font></field>
|
||||
<field name="parent_id" ref="message_note0"/>
|
||||
<field name="type">email</field>
|
||||
<field name="state">received</field>
|
||||
<field name="user_id" ref="base.user_demo"/>
|
||||
</record>
|
||||
<record id="message_email1" model="mail.message">
|
||||
<field name="subject">Re: Plan to buy a Laptop</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_15"/>
|
||||
<field name="content_subtype">plain</field>
|
||||
<field name="body_text">Yes, its open till 10:00 PM, you are welcome!</field>
|
||||
<field name="type">email</field>
|
||||
<field name="state">sent</field>
|
||||
<field name="user_id" ref="base.user_root"/>
|
||||
</record>
|
||||
|
||||
<record id="message_email_12" model="mail.message">
|
||||
<field name="subject">Inquiry</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_1"/>
|
||||
<field name="content_subtype">plain</field>
|
||||
<field name="body_text">Hello,
|
||||
I am Jason from Le Club SARL,
|
||||
I am intertested to attend Training organized in your company,
|
||||
Can you send details,</field>
|
||||
<field name="type">email</field>
|
||||
<field name="state">received</field>
|
||||
<field name="user_id" ref="base.user_demo"/>
|
||||
</record>
|
||||
|
||||
<record id="message_email_13" model="mail.message">
|
||||
<field name="subject">Need Details</field>
|
||||
<field name="model">crm.lead</field>
|
||||
<field name="res_id" ref="crm_case_2"/>
|
||||
<field name="content_subtype">plain</field>
|
||||
<field name="body_text">Want to know features and benifits to use the new software.</field>
|
||||
<field name="type">comment</field>
|
||||
<field name="user_id" ref="base.user_demo"/>
|
||||
</record>
|
||||
|
||||
|
||||
|
|
|
@ -3,7 +3,6 @@
|
|||
<data>
|
||||
|
||||
<!-- Calendar Attendee Form View -->
|
||||
|
||||
<record id="attendee_form_view_inherit" model="ir.ui.view">
|
||||
<field name="name">calendar.attendee.form.inherit</field>
|
||||
<field name="model">calendar.attendee</field>
|
||||
|
|
File diff suppressed because it is too large
Load Diff
|
@ -34,13 +34,12 @@ Caldav features in Meeting.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['caldav', 'crm' ],
|
||||
'init_xml': [
|
||||
'data': [
|
||||
'crm_caldav_data.xml',
|
||||
'crm_caldav_setup.xml',
|
||||
'crm_caldav_view.xml'
|
||||
],
|
||||
|
||||
'update_xml': ['crm_caldav_view.xml'],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate' : '001088048737252670109',
|
||||
|
|
|
@ -34,20 +34,15 @@ automatically new claims based on incoming emails.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['crm'],
|
||||
'init_xml': [
|
||||
'crm_claim_data.xml',
|
||||
],
|
||||
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'crm_claim_view.xml',
|
||||
'crm_claim_menu.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'report/crm_claim_report_view.xml',
|
||||
'res_config_view.xml',
|
||||
'crm_claim_data.xml',
|
||||
],
|
||||
'demo_xml': [
|
||||
'crm_claim_demo.xml',
|
||||
],
|
||||
'demo': ['crm_claim_demo.xml'],
|
||||
'test': ['test/process/claim.yml',
|
||||
'test/ui/claim_demo.yml'
|
||||
],
|
||||
|
|
|
@ -21,8 +21,8 @@
|
|||
|
||||
|
||||
{
|
||||
'category': 'Customer Relationship Management',
|
||||
'name': 'Helpdesk',
|
||||
'category': 'Customer Relationship Management',
|
||||
'version': '1.0',
|
||||
'description': """
|
||||
Helpdesk Management.
|
||||
|
@ -36,18 +36,14 @@ and categorize your interventions with a channel and a priority level.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['crm'],
|
||||
'init_xml': [
|
||||
'crm_helpdesk_data.xml',
|
||||
],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'crm_helpdesk_view.xml',
|
||||
'crm_helpdesk_menu.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'report/crm_helpdesk_report_view.xml',
|
||||
'crm_helpdesk_data.xml',
|
||||
],
|
||||
'demo_xml': [
|
||||
'crm_helpdesk_demo.xml',
|
||||
],
|
||||
'demo': ['crm_helpdesk_demo.xml'],
|
||||
'test': ['test/process/help-desk.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
|
|
|
@ -32,15 +32,14 @@ You can geolocalize your opportunities by using this module.
|
|||
|
||||
Use geolocalization when assigning opportunities to partners.
|
||||
Determine the GPS coordinates according to the address of the partner.
|
||||
|
||||
The most appropriate partner can be assigned.
|
||||
You can also use the geolocalization without using the GPS coordinates.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['crm', 'account'],
|
||||
'demo_xml': [
|
||||
'res_partner_demo.xml',
|
||||
],
|
||||
'update_xml': [
|
||||
'demo': ['res_partner_demo.xml'],
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'res_partner_view.xml',
|
||||
'wizard/crm_forward_to_partner_view.xml',
|
||||
|
@ -48,9 +47,7 @@ You can also use the geolocalization without using the GPS coordinates.
|
|||
'report/crm_lead_report_view.xml',
|
||||
'report/crm_partner_report_view.xml',
|
||||
],
|
||||
'test': [
|
||||
'test/partner_assign.yml'
|
||||
],
|
||||
'test': ['test/partner_assign.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '00503409558942442061',
|
||||
|
|
|
@ -35,15 +35,13 @@ questionnaire and directly use it on a partner.
|
|||
It also has been merged with the earlier CRM & SRM segmentation tool because they
|
||||
were overlapping.
|
||||
|
||||
* Note: this module is not compatible with the module segmentation, since
|
||||
it's the same which has been renamed.
|
||||
**Note:** this module is not compatible with the module segmentation, since it's the same which has been renamed.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base', 'crm'],
|
||||
'init_xml': [],
|
||||
'update_xml': ['security/ir.model.access.csv', 'wizard/open_questionnaire_view.xml', 'crm_profiling_view.xml'],
|
||||
'demo_xml': ['crm_profiling_demo.xml'],
|
||||
'data': ['security/ir.model.access.csv', 'wizard/open_questionnaire_view.xml', 'crm_profiling_view.xml'],
|
||||
'demo': ['crm_profiling_demo.xml'],
|
||||
'test': [
|
||||
#'test/process/profiling.yml', #TODO:It's not debuging because problem to write data for open.questionnaire from partner section.
|
||||
],
|
||||
|
|
|
@ -23,18 +23,15 @@
|
|||
{
|
||||
'name': 'Tasks on CRM',
|
||||
'version': '1.0',
|
||||
"category": 'Customer Relationship Management',
|
||||
'category': 'Customer Relationship Management',
|
||||
'description': """
|
||||
Todo list for CRM leads and opportunities.
|
||||
==========================================
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['crm','project_gtd'],
|
||||
'update_xml': [
|
||||
'crm_todo_view.xml',
|
||||
],
|
||||
'demo': [
|
||||
'crm_todo_demo.xml',
|
||||
],
|
||||
'data': ['crm_todo_view.xml'],
|
||||
'demo': ['crm_todo_demo.xml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
}
|
||||
|
|
|
@ -20,25 +20,24 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name": "Decimal Precision Configuration",
|
||||
"description": """
|
||||
'name': 'Decimal Precision Configuration',
|
||||
'description': """
|
||||
Configure the price accuracy you need for different kinds of usage: accounting, sales, purchases.
|
||||
=================================================================================================
|
||||
|
||||
The decimal precision is configured per company.
|
||||
""",
|
||||
"author": "OpenERP SA",
|
||||
"version": "0.1",
|
||||
"depends": ["base"],
|
||||
"category" : "Hidden/Dependency",
|
||||
"init_xml": [],
|
||||
"update_xml": [
|
||||
'author': 'OpenERP SA',
|
||||
'version': '0.1',
|
||||
'depends': ['base'],
|
||||
'category' : 'Hidden/Dependency',
|
||||
'data': [
|
||||
'decimal_precision_view.xml',
|
||||
'security/ir.model.access.csv',
|
||||
],
|
||||
"demo_xml": [],
|
||||
"installable": True,
|
||||
"certificate" : "001307317809612974621",
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'certificate' : '001307317809612974621',
|
||||
'images': ['images/1_decimal_accuracy_form.jpeg','images/1_decimal_accuracy_list.jpeg'],
|
||||
}
|
||||
|
||||
|
|
|
@ -33,17 +33,15 @@ invoices from picking, OpenERP is able to add and compute the shipping line.
|
|||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['sale', 'purchase', 'stock'],
|
||||
'init_xml': ['delivery_data.xml'],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'delivery_report.xml',
|
||||
'delivery_view.xml',
|
||||
'partner_view.xml'
|
||||
],
|
||||
'demo_xml': ['delivery_demo.xml'],
|
||||
'test': [
|
||||
'test/delivery_cost.yml',
|
||||
'partner_view.xml',
|
||||
'delivery_data.xml'
|
||||
],
|
||||
'demo': ['delivery_demo.xml'],
|
||||
'test': ['test/delivery_cost.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0033981912253',
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<openerp>
|
||||
<data noupdate="True">
|
||||
<data noupdate="1">
|
||||
<record forcecreate="True" id="property_delivery_carrier" model="ir.property">
|
||||
<field name="name">property_delivery_carrier</field>
|
||||
<field name="fields_id" search="[('model','=','res.partner'),('name','=','property_delivery_carrier')]"/>
|
||||
|
|
|
@ -37,6 +37,7 @@ This is a complete document management system.
|
|||
* Files Size by Month (graph)
|
||||
|
||||
ATTENTION:
|
||||
----------
|
||||
- When you install this module in a running company that have already PDF
|
||||
files stored into the database, you will lose them all.
|
||||
- After installing this module PDF's are no longer stored into the database,
|
||||
|
@ -45,8 +46,7 @@ ATTENTION:
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['process','board', 'knowledge'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/document_security.xml',
|
||||
'document_view.xml',
|
||||
'document_data.xml',
|
||||
|
@ -55,10 +55,8 @@ ATTENTION:
|
|||
'report/document_report_view.xml',
|
||||
'board_document_view.xml',
|
||||
],
|
||||
'demo_xml': [ 'document_demo.xml','board_document_demo.xml'],
|
||||
'test': [
|
||||
'test/document_test2.yml',
|
||||
],
|
||||
'demo': [ 'document_demo.xml','board_document_demo.xml'],
|
||||
'test': ['test/document_test2.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0070515416461',
|
||||
|
|
|
@ -35,14 +35,13 @@ FTP client.
|
|||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base', 'document'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'wizard/ftp_configuration_view.xml',
|
||||
'wizard/ftp_browse_view.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'res_config_view.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'test': [
|
||||
'test/document_ftp_test2.yml',
|
||||
'test/document_ftp_test4.yml',
|
||||
|
|
|
@ -31,20 +31,15 @@ Web pages
|
|||
'author': ['OpenERP SA'],
|
||||
'website': 'http://www.openerp.com/',
|
||||
'depends': ['knowledge'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'wizard/document_page_create_menu_view.xml',
|
||||
'wizard/document_page_show_diff_view.xml',
|
||||
'document_page_view.xml',
|
||||
'security/document_page_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
],
|
||||
'demo_xml': [
|
||||
'document_page_demo.xml'
|
||||
],
|
||||
'test': [
|
||||
'test/document_page_test00.yml'
|
||||
],
|
||||
'demo': ['document_page_demo.xml'],
|
||||
'test': ['test/document_page_test00.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0086363630317',
|
||||
|
@ -53,8 +48,6 @@ Web pages
|
|||
'static/src/lib/wiky/wiky.js',
|
||||
'static/src/js/document_page.js'
|
||||
],
|
||||
'css' : [
|
||||
"static/src/css/document_page.css"
|
||||
],
|
||||
'css' : ['static/src/css/document_page.css'],
|
||||
}
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -29,12 +29,12 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Shared Repositories (WebDAV)",
|
||||
"version" : "2.3",
|
||||
"author" : "OpenERP SA",
|
||||
"category" : "Knowledge Management",
|
||||
"website": "http://www.openerp.com",
|
||||
"description": """
|
||||
'name': 'Shared Repositories (WebDAV)',
|
||||
'version': '2.3',
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Knowledge Management',
|
||||
'website': 'http://www.openerp.com',
|
||||
'description': """
|
||||
With this module, the WebDAV server for documents is activated.
|
||||
===============================================================
|
||||
|
||||
|
@ -42,34 +42,35 @@ You can then use any compatible browser to remotely see the attachments of OpenO
|
|||
|
||||
After installation, the WebDAV server can be controlled by a [webdav] section in
|
||||
the server's config.
|
||||
Server Configuration Parameter:
|
||||
|
||||
[webdav]
|
||||
; enable = True ; Serve webdav over the http(s) servers
|
||||
; vdir = webdav ; the directory that webdav will be served at
|
||||
; this default val means that webdav will be
|
||||
; on "http://localhost:8069/webdav/
|
||||
; verbose = True ; Turn on the verbose messages of webdav
|
||||
; debug = True ; Turn on the debugging messages of webdav
|
||||
; since the messages are routed to the python logging, with
|
||||
; levels "debug" and "debug_rpc" respectively, you can leave
|
||||
; these options on
|
||||
Server Configuration Parameter:
|
||||
-------------------------------
|
||||
[webdav]:
|
||||
+++++++++
|
||||
* enable = True ; Serve webdav over the http(s) servers
|
||||
* vdir = webdav ; the directory that webdav will be served at
|
||||
* this default val means that webdav will be
|
||||
* on "http://localhost:8069/webdav/
|
||||
* verbose = True ; Turn on the verbose messages of webdav
|
||||
* debug = True ; Turn on the debugging messages of webdav
|
||||
* since the messages are routed to the python logging, with
|
||||
* levels "debug" and "debug_rpc" respectively, you can leave
|
||||
* these options on
|
||||
|
||||
Also implements IETF RFC 5785 for services discovery on a http server,
|
||||
which needs explicit configuration in openerp-server.conf too.
|
||||
""",
|
||||
"depends" : ["base", "document"],
|
||||
"init_xml" : [],
|
||||
"update_xml" : ['security/ir.model.access.csv',
|
||||
'depends': ['base', 'document'],
|
||||
'data': ['security/ir.model.access.csv',
|
||||
'webdav_view.xml',
|
||||
'webdav_setup.xml',
|
||||
],
|
||||
"demo_xml" : [],
|
||||
"test": [ #'test/webdav_test1.yml',
|
||||
'demo': [],
|
||||
'test': [ #'test/webdav_test1.yml',
|
||||
],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"certificate" : "001236490750845657973",
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'certificate' : '001236490750845657973',
|
||||
'images': ['images/dav_properties.jpeg','images/directories_structure_principals.jpeg'],
|
||||
}
|
||||
|
||||
|
|
|
@ -36,21 +36,11 @@ documentation at http://doc.openerp.com.
|
|||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base', 'email_template'],
|
||||
'icon': '/edi/static/src/img/knowledge.png',
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
],
|
||||
'test': [
|
||||
'test/edi_partner_test.yml',
|
||||
],
|
||||
'js': [
|
||||
'static/src/js/edi.js',
|
||||
],
|
||||
"css": [
|
||||
"static/src/css/edi.css"
|
||||
],
|
||||
'qweb': [
|
||||
"static/src/xml/*.xml",
|
||||
],
|
||||
'data': ['security/ir.model.access.csv'],
|
||||
'test': ['test/edi_partner_test.yml'],
|
||||
'js': ['static/src/js/edi.js'],
|
||||
'css': ['static/src/css/edi.css'],
|
||||
'qweb': ['static/src/xml/*.xml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '002046536359186',
|
||||
|
|
|
@ -21,13 +21,13 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Email Templates",
|
||||
"version" : "1.1",
|
||||
"author" : "OpenERP,OpenLabs",
|
||||
"website" : "http://openerp.com",
|
||||
"category" : "Marketing",
|
||||
"depends" : ['mail'],
|
||||
"description": """
|
||||
'name' : 'Email Templates',
|
||||
'version' : '1.1',
|
||||
'author' : 'OpenERP,OpenLabs',
|
||||
'website' : 'http://openerp.com',
|
||||
'category' : 'Marketing',
|
||||
'depends' : ['mail'],
|
||||
'description': """
|
||||
Email Templating (simplified version of the original Power Email by Openlabs).
|
||||
==============================================================================
|
||||
|
||||
|
@ -53,22 +53,19 @@ These email templates are also at the heart of the marketing campaign system
|
|||
(see the ``marketing_campaign`` application), if you need to automate larger
|
||||
campaigns on any OpenERP document.
|
||||
|
||||
Technical note: only the templating system of the original Power Email by
|
||||
Openlabs was kept.
|
||||
**Technical note:** only the templating system of the original Power Email by Openlabs was kept.
|
||||
""",
|
||||
"data": [
|
||||
'data': [
|
||||
'wizard/email_template_preview_view.xml',
|
||||
'email_template_view.xml',
|
||||
'res_partner_view.xml',
|
||||
'wizard/mail_compose_message_view.xml',
|
||||
'security/ir.model.access.csv'
|
||||
],
|
||||
"demo": [
|
||||
'res_partner_demo.yml',
|
||||
],
|
||||
"installable": True,
|
||||
"auto_install": False,
|
||||
"certificate" : "00817073628967384349",
|
||||
'demo': ['res_partner_demo.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate' : '00817073628967384349',
|
||||
'images': ['images/1_email_account.jpeg','images/2_email_template.jpeg','images/3_emails.jpeg'],
|
||||
}
|
||||
|
||||
|
|
|
@ -30,19 +30,20 @@
|
|||
Organization and management of Events.
|
||||
======================================
|
||||
|
||||
This module allows you
|
||||
This module allows you:
|
||||
-----------------------
|
||||
* to manage your events and their registrations
|
||||
* to use emails to automatically confirm and send acknowledgements for any
|
||||
registration to an event
|
||||
|
||||
Note that:
|
||||
----------
|
||||
- You can define new types of events in
|
||||
Events/Configuration/Types of Events
|
||||
**Events** / **Configuration** / **Types of Events**
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['base_setup', 'board', 'email_template', 'google_map'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/event_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'wizard/event_confirm_view.xml',
|
||||
|
@ -52,7 +53,7 @@ Note that:
|
|||
'res_partner_view.xml',
|
||||
'email_template.xml',
|
||||
],
|
||||
'demo_xml': ['event_demo.xml'],
|
||||
'demo': ['event_demo.xml'],
|
||||
'test': ['test/process/event_draft2done.yml'],
|
||||
'css': ['static/src/css/event.css'],
|
||||
'installable': True,
|
||||
|
|
|
@ -34,10 +34,10 @@ to avoid wasting time.
|
|||
Now you have a simple way to create training or courses with OpenERP and moodle.
|
||||
|
||||
STEPS TO CONFIGURE:
|
||||
------------------
|
||||
-------------------
|
||||
|
||||
1. Activate web service in moodle.
|
||||
----------------------------------
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
>site administration >plugins >web services >manage protocols activate the xmlrpc web service
|
||||
|
||||
|
||||
|
@ -48,26 +48,27 @@ STEPS TO CONFIGURE:
|
|||
|
||||
|
||||
2. Create confirmation email with login and password.
|
||||
-----------------------------------------------------
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
We strongly suggest you to add those following lines at the bottom of your event
|
||||
confirmation email to communicate the login/password of moodle to your subscribers.
|
||||
|
||||
|
||||
........your configuration text.......
|
||||
|
||||
URL: your moodle link for exemple: http://openerp.moodle.com
|
||||
LOGIN: ${object.moodle_username}
|
||||
PASSWORD: ${object.moodle_user_password}
|
||||
**URL:** your moodle link for exemple: http://openerp.moodle.com
|
||||
|
||||
**LOGIN:** ${object.moodle_username}
|
||||
|
||||
**PASSWORD:** ${object.moodle_user_password}
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['event'],
|
||||
'init_xml': [],
|
||||
'data': [
|
||||
'wizard_moodle.xml',
|
||||
'event_view.xml',
|
||||
'security/ir.model.access.csv'
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'test': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
|
|
|
@ -32,9 +32,8 @@ This module allows you to create retro planning for managing your events.
|
|||
'author': 'OpenERP SA',
|
||||
'images': ['images/event.jpeg'],
|
||||
'depends': ['project_retro_planning', 'event'],
|
||||
'init_xml': [],
|
||||
'update_xml': ['wizard/event_project_retro_view.xml', 'event_project_view.xml'],
|
||||
'demo_xml': [],
|
||||
'data': ['wizard/event_project_retro_view.xml', 'event_project_view.xml'],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0069726863885',
|
||||
|
|
|
@ -39,10 +39,8 @@ this event.
|
|||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['event','sale','sale_crm'],
|
||||
'update_xml': [
|
||||
'event_sale_view.xml',
|
||||
],
|
||||
'demo_xml': ['event_demo.xml'],
|
||||
'data': ['event_sale_view.xml'],
|
||||
'demo': ['event_demo.xml'],
|
||||
'test': ['test/confirm.yml'],
|
||||
'installable': True,
|
||||
'active': False,
|
||||
|
|
|
@ -21,12 +21,12 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Email Gateway",
|
||||
"version" : "1.0",
|
||||
"depends" : ["base", 'mail'],
|
||||
"author" : "OpenERP SA",
|
||||
"category": 'Tools',
|
||||
"description": """
|
||||
'name' : 'Email Gateway',
|
||||
'version' : '1.0',
|
||||
'depends' : ['base', 'mail'],
|
||||
'author' : 'OpenERP SA',
|
||||
'category': 'Tools',
|
||||
'description': """
|
||||
Retrieve incoming email on POP/IMAP servers.
|
||||
============================================
|
||||
|
||||
|
@ -35,9 +35,8 @@ these accounts will be automatically downloaded into your OpenERP system. All
|
|||
POP3/IMAP-compatible servers are supported, included those that require an
|
||||
encrypted SSL/TLS connection.
|
||||
|
||||
This can be used to easily create email-based workflows for many email-enabled
|
||||
OpenERP documents, such as:
|
||||
|
||||
This can be used to easily create email-based workflows for many email-enabled OpenERP documents, such as:
|
||||
----------------------------------------------------------------------------------------------------------
|
||||
* CRM Leads/Opportunities
|
||||
* CRM Claims
|
||||
* Project Issues
|
||||
|
@ -56,16 +55,13 @@ For more specific needs, you may also assign custom-defined actions
|
|||
(technically: Server Actions) to be triggered for each incoming mail.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
"fetchmail_view.xml",
|
||||
"fetchmail_data.xml",
|
||||
'data': [
|
||||
'fetchmail_view.xml',
|
||||
'fetchmail_data.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'fetchmail_installer_view.xml'
|
||||
],
|
||||
'demo_xml': [
|
||||
|
||||
],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate' : '00692978332890137453',
|
||||
|
|
|
@ -24,16 +24,18 @@
|
|||
'name': 'Google Users',
|
||||
'version': '1.0',
|
||||
'category': 'Tools',
|
||||
'description': """The module adds google user in res user.""",
|
||||
'description': """
|
||||
The module adds google user in res user.
|
||||
========================================
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'google_base_account_view.xml',
|
||||
'wizard/google_login_view.xml',
|
||||
],
|
||||
'demo_xml': [],
|
||||
'demo': [],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
}
|
||||
|
|
|
@ -29,10 +29,13 @@
|
|||
'auto_install': False,
|
||||
'web': True,
|
||||
'js': ['static/src/js/gdocs.js'],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'res_config_user_view.xml'
|
||||
],
|
||||
'depends': ['google_base_account'],
|
||||
'description': 'Module to attach a google document to any model.'
|
||||
'description': """
|
||||
Module to attach a google document to any model.
|
||||
================================================
|
||||
"""
|
||||
}
|
||||
|
|
|
@ -33,9 +33,8 @@ Using this you can directly open Google Map from the URL widget.""",
|
|||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/google_map.jpeg'],
|
||||
'depends': ['base'],
|
||||
'init_xml': [],
|
||||
'update_xml': [ ],
|
||||
'demo_xml': [],
|
||||
'data': [],
|
||||
'demo': [],
|
||||
'js': ['static/src/js/google_map.js'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
|
|
|
@ -20,18 +20,19 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name": "Employee Directory",
|
||||
"version": "1.1",
|
||||
"author": "OpenERP SA",
|
||||
"category": "Human Resources",
|
||||
"sequence": 12,
|
||||
"website": "http://www.openerp.com",
|
||||
"summary": "All Infos on Employees",
|
||||
"description": """
|
||||
'name': 'Employee Directory',
|
||||
'version': '1.1',
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Human Resources',
|
||||
'sequence': 12,
|
||||
'website': 'http://www.openerp.com',
|
||||
'summary': 'All Infos on Employees',
|
||||
'description': """
|
||||
Module for Human Resource Management.
|
||||
=====================================
|
||||
|
||||
You can manage:
|
||||
---------------
|
||||
* Employees and hierarchies : You can define your employee with User and display hierarchies
|
||||
* HR Departments
|
||||
* HR Jobs
|
||||
|
@ -45,8 +46,7 @@ You can manage:
|
|||
'static/src/img/default_image.png',
|
||||
],
|
||||
'depends': ['base_setup','mail', 'resource', 'board'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/hr_security.xml',
|
||||
'security/ir.model.access.csv',
|
||||
'board_hr_view.xml',
|
||||
|
@ -57,9 +57,7 @@ You can manage:
|
|||
'hr_data.xml',
|
||||
'res_config_view.xml',
|
||||
],
|
||||
'demo_xml': [
|
||||
'hr_demo.xml',
|
||||
],
|
||||
'demo': ['hr_demo.xml'],
|
||||
'test': [
|
||||
'test/open2recruit2close_job.yml',
|
||||
'test/hr_demo.yml',
|
||||
|
@ -68,6 +66,6 @@ You can manage:
|
|||
'application': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0086710558965',
|
||||
"css": [ 'static/src/css/hr.css' ],
|
||||
'css': [ 'static/src/css/hr.css' ],
|
||||
}
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -34,7 +34,7 @@ actions(Sign in/Sign out) performed by them.
|
|||
'author': 'OpenERP SA',
|
||||
'images': ['images/hr_attendances.jpeg'],
|
||||
'depends': ['hr'],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'hr_attendance_view.xml',
|
||||
'hr_attendance_report.xml',
|
||||
|
@ -45,7 +45,7 @@ actions(Sign in/Sign out) performed by them.
|
|||
'wizard/hr_attendance_error_view.xml',
|
||||
'wizard/hr_attendance_sign_in_out_view.xml',
|
||||
],
|
||||
'demo_xml': ['hr_attendance_demo.xml'],
|
||||
'demo': ['hr_attendance_demo.xml'],
|
||||
'test': [
|
||||
'test/attendance_process.yml',
|
||||
'test/hr_attendance_report.yml',
|
||||
|
|
|
@ -21,7 +21,7 @@
|
|||
|
||||
|
||||
{
|
||||
'name': "Employee Contracts",
|
||||
'name': 'Employee Contracts',
|
||||
'version': '1.0',
|
||||
'category': 'Human Resources',
|
||||
'description': """
|
||||
|
@ -39,15 +39,13 @@ You can assign several contracts per employee.
|
|||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/hr_contract.jpeg'],
|
||||
'depends': ['hr'],
|
||||
'init_xml': ['hr_contract_data.xml'],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'hr_contract_view.xml'
|
||||
],
|
||||
'demo_xml': [],
|
||||
'test': [
|
||||
'test/test_hr_contract.yml'
|
||||
'hr_contract_view.xml',
|
||||
'hr_contract_data.xml'
|
||||
],
|
||||
'demo': [],
|
||||
'test': ['test/test_hr_contract.yml'],
|
||||
'installable': True,
|
||||
'auto_install': False,
|
||||
'certificate': '0046298028637',
|
||||
|
|
|
@ -20,15 +20,15 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name" : "Employee Appraisals",
|
||||
"version": "0.1",
|
||||
"author": "OpenERP SA",
|
||||
"category": "Human Resources",
|
||||
"website": "http://www.openerp.com",
|
||||
"summary": "Periodical Evaluations, Surveys",
|
||||
"images": ["images/hr_evaluation_analysis.jpeg","images/hr_evaluation.jpeg"],
|
||||
"depends": ["hr","base_calendar","survey"],
|
||||
"description": """
|
||||
'name' : 'Employee Appraisals',
|
||||
'version': '0.1',
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Human Resources',
|
||||
'website': 'http://www.openerp.com',
|
||||
'summary': 'Periodical Evaluations, Surveys',
|
||||
'images': ['images/hr_evaluation_analysis.jpeg','images/hr_evaluation.jpeg'],
|
||||
'depends': ['hr','base_calendar','survey'],
|
||||
'description': """
|
||||
Ability to create employees evaluation.
|
||||
=======================================
|
||||
|
||||
|
@ -38,24 +38,24 @@ created and it can be defined which level of employee hierarchy fills what and
|
|||
final review and evaluation is done by the manager. Every evaluation filled by
|
||||
the employees can be viewed in the form of pdf file.
|
||||
""",
|
||||
"demo": ["hr_evaluation_demo.xml"],
|
||||
"data": [
|
||||
"security/ir.model.access.csv",
|
||||
"security/hr_evaluation_security.xml",
|
||||
# "wizard/hr_evaluation_mail_view.xml",
|
||||
"hr_evaluation_view.xml",
|
||||
"report/hr_evaluation_report_view.xml",
|
||||
"board_hr_evaluation_view.xml",
|
||||
'demo': ['hr_evaluation_demo.xml'],
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'security/hr_evaluation_security.xml',
|
||||
# 'wizard/hr_evaluation_mail_view.xml',
|
||||
'hr_evaluation_view.xml',
|
||||
'report/hr_evaluation_report_view.xml',
|
||||
'board_hr_evaluation_view.xml',
|
||||
'hr_evaluation_data.xml',
|
||||
'hr_evaluation_installer.xml',
|
||||
],
|
||||
"test": [
|
||||
"test/test_hr_evaluation.yml",
|
||||
"test/hr_evalution_demo.yml",
|
||||
'test': [
|
||||
'test/test_hr_evaluation.yml',
|
||||
'test/hr_evalution_demo.yml',
|
||||
],
|
||||
"auto_install": False,
|
||||
"installable": True,
|
||||
"certificate" : "00883207679172998429",
|
||||
'auto_install': False,
|
||||
'installable': True,
|
||||
'certificate' : '00883207679172998429',
|
||||
'application': True,
|
||||
}
|
||||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:
|
||||
|
|
|
@ -24,13 +24,14 @@
|
|||
'name': 'Expenses Management',
|
||||
'version': '1.0',
|
||||
'category': 'Human Resources',
|
||||
"sequence": 30,
|
||||
"summary": "Expenses Validation, Invoicing",
|
||||
'sequence': 30,
|
||||
'summary': 'Expenses Validation, Invoicing',
|
||||
'description': """
|
||||
This module aims to manage employee's expenses.
|
||||
===============================================
|
||||
|
||||
The whole workflow is implemented:
|
||||
----------------------------------
|
||||
* Draft expense
|
||||
* Confirmation of the sheet by the employee
|
||||
* Validation by his manager
|
||||
|
@ -44,8 +45,7 @@ re-invoice your customer's expenses if your work by project.
|
|||
'website': 'http://www.openerp.com',
|
||||
'images': ['images/hr_expenses_analysis.jpeg', 'images/hr_expenses.jpeg'],
|
||||
'depends': ['hr', 'account_voucher'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'hr_expense_data.xml',
|
||||
'hr_expense_sequence.xml',
|
||||
|
@ -58,9 +58,7 @@ re-invoice your customer's expenses if your work by project.
|
|||
'board_hr_expense_view.xml',
|
||||
'hr_expense_installer_view.xml',
|
||||
],
|
||||
'demo_xml': [
|
||||
'hr_expense_demo.xml',
|
||||
],
|
||||
'demo': ['hr_expense_demo.xml'],
|
||||
'test': [
|
||||
'test/expense_demo.yml',
|
||||
'test/expense_process.yml',
|
||||
|
|
|
@ -21,14 +21,14 @@
|
|||
|
||||
|
||||
{
|
||||
"name": "Leaves Management",
|
||||
"version": "1.5",
|
||||
"author": "OpenERP SA",
|
||||
"category": "Human Resources",
|
||||
"sequence": 28,
|
||||
"summary": "Holidays, Allocation and Leave Requests",
|
||||
"website": "http://www.openerp.com",
|
||||
"description": """
|
||||
'name': 'Leaves Management',
|
||||
'version': '1.5',
|
||||
'author': 'OpenERP SA',
|
||||
'category': 'Human Resources',
|
||||
'sequence': 28,
|
||||
'summary': 'Holidays, Allocation and Leave Requests',
|
||||
'website': 'http://www.openerp.com',
|
||||
'description': """
|
||||
This module allows you to manage leaves and leave's requests.
|
||||
=============================================================
|
||||
|
||||
|
@ -37,27 +37,29 @@ Implements a dashboard for human resource management that includes:
|
|||
* Leaves
|
||||
|
||||
Note that:
|
||||
~~~~~~~~~~
|
||||
- A synchronisation with an internal agenda (use of the CRM module) is
|
||||
possible: in order to automatically create a case when an holiday request
|
||||
is accepted, you have to link the holidays status to a case section. You
|
||||
can setup this info and your colour preferences in
|
||||
Human Resources/Configuration/Leave Type
|
||||
|
||||
**Human Resources** / **Configuration** / **Leave Type**
|
||||
- An employee can make an ask for more off-days by making a new Allocation. It will increase his total of that leave type available (if the request is accepted).
|
||||
- There are two ways to print the employee's holidays:
|
||||
* The first will allow to choose employees by department and is used by clicking the menu item located in
|
||||
Reporting/Human Resources/Leaves/Leaves by Department
|
||||
**Reporting** / **Human Resources** / **Leaves** / **Leaves by Department**
|
||||
* The second will allow you to choose the holidays report for specific employees. Go on the list
|
||||
Human Resources/Human Resources/Employees
|
||||
**Human Resources** / **Human Resources** / **Employees**
|
||||
then select the ones you want to choose, click on the print icon and select the option
|
||||
'Leaves Summary'
|
||||
- The wizard allows you to choose if you want to print either the Approved & Confirmed holidays or both. These states must be set up by a user from the group 'HR'. You can define these features in the security tab from the user data in
|
||||
Settings/Users/Users
|
||||
**Settings** / **Users** / **Users**
|
||||
|
||||
for example, you maybe will do it for the user 'admin'.
|
||||
""",
|
||||
'images': ['images/hr_allocation_requests.jpeg', 'images/hr_leave_requests.jpeg', 'images/leaves_analysis.jpeg'],
|
||||
'depends': ['hr', 'base_calendar', 'process', 'resource'],
|
||||
'init_xml': [],
|
||||
'update_xml': [
|
||||
'data': [
|
||||
'security/ir.model.access.csv',
|
||||
'security/ir_rule.xml',
|
||||
'hr_holidays_workflow.xml',
|
||||
|
@ -70,7 +72,7 @@ Note that:
|
|||
'wizard/hr_holidays_summary_employees_view.xml',
|
||||
'board_hr_holidays_view.xml',
|
||||
],
|
||||
'demo_xml': ['hr_holidays_demo.xml',],
|
||||
'demo': ['hr_holidays_demo.xml',],
|
||||
'test': ['test/test_hr_holiday.yml',
|
||||
'test/hr_holidays_report.yml',
|
||||
],
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue