[IMP] : Update Description for modules
bzr revid: cha@tinyerp.com-20120713091324-sengeariqawfira9
This commit is contained in:
parent
5847fae7a3
commit
339051cadf
|
@ -29,9 +29,11 @@ This module lets you calculate discounts on Sale Order lines and Invoice lines b
|
||||||
To this end, a new check box named "Visible Discount" is added to the pricelist form.
|
To this end, a new check box named "Visible Discount" is added to the pricelist form.
|
||||||
|
|
||||||
Example:
|
Example:
|
||||||
For the product PC1 and the partner "Asustek": if listprice=450, and the price calculated using Asustek's pricelist is 225
|
For the product PC1 and the partner "Asustek": if listprice=450, and the price
|
||||||
If the check box is checked, we will have on the sale order line: Unit price=450, Discount=50,00, Net price=225
|
calculated using Asustek's pricelist is 225. If the check box is checked, we
|
||||||
If the check box is unchecked, we will have on Sale Order and Invoice lines: Unit price=225, Discount=0,00, Net price=225
|
will have on the sale order line: Unit price=450, Discount=50,00, Net price=225.
|
||||||
|
If the check box is unchecked, we will have on Sale Order and Invoice lines:
|
||||||
|
Unit price=225, Discount=0,00, Net price=225.
|
||||||
""",
|
""",
|
||||||
"depends": ["sale"],
|
"depends": ["sale"],
|
||||||
"demo_xml": [],
|
"demo_xml": [],
|
||||||
|
|
|
@ -31,14 +31,18 @@
|
||||||
Long Term Project management module that tracks planning, scheduling, resources allocation.
|
Long Term Project management module that tracks planning, scheduling, resources allocation.
|
||||||
===========================================================================================
|
===========================================================================================
|
||||||
|
|
||||||
Features
|
Features:
|
||||||
--------
|
---------
|
||||||
* Manage Big project.
|
* Manage Big project.
|
||||||
* Define various Phases of Project.
|
* Define various Phases of Project.
|
||||||
* Compute Phase Scheduling: Compute start date and end date of the phases which are in draft,open and pending state of the project given.
|
* Compute Phase Scheduling: Compute start date and end date of the phases
|
||||||
If no project given then all the draft,open and pending state phases will be taken.
|
which are in draft, open and pending state of the project given. If no
|
||||||
* Compute Task Scheduling: This works same as the scheduler button on project.phase. It takes the project as argument and computes all the open,draft and pending tasks.
|
project given then all the draft, open and pending state phases will be taken.
|
||||||
* Schedule Tasks: All the tasks which are in draft,pending and open state are scheduled with taking the phase's start date
|
* Compute Task Scheduling: This works same as the scheduler button on
|
||||||
|
project.phase. It takes the project as argument and computes all the open,
|
||||||
|
draft and pending tasks.
|
||||||
|
* Schedule Tasks: All the tasks which are in draft,pending and open state
|
||||||
|
are scheduled with taking the phase's start date
|
||||||
""",
|
""",
|
||||||
"init_xml": [],
|
"init_xml": [],
|
||||||
"demo_xml": ["project_long_term_demo.xml"],
|
"demo_xml": ["project_long_term_demo.xml"],
|
||||||
|
|
|
@ -29,8 +29,8 @@
|
||||||
"images": ["images/project_mailgate_task.jpeg"],
|
"images": ["images/project_mailgate_task.jpeg"],
|
||||||
"depends": ["project", "mail"],
|
"depends": ["project", "mail"],
|
||||||
"description": """
|
"description": """
|
||||||
This module can automatically create Project Tasks based on incoming emails
|
This module can automatically create Project Tasks based on incoming emails.
|
||||||
===========================================================================
|
============================================================================
|
||||||
|
|
||||||
Allows creating tasks based on new emails arriving at a given mailbox,
|
Allows creating tasks based on new emails arriving at a given mailbox,
|
||||||
similarly to what the CRM application has for Leads/Opportunities.
|
similarly to what the CRM application has for Leads/Opportunities.
|
||||||
|
@ -41,7 +41,6 @@ There are two common alternatives to configure the mailbox integration:
|
||||||
* Set it up manually on your mail server based on the 'mail gateway' script
|
* Set it up manually on your mail server based on the 'mail gateway' script
|
||||||
provided in the ``mail`` module - and connect it to the `project.task` model.
|
provided in the ``mail`` module - and connect it to the `project.task` model.
|
||||||
|
|
||||||
|
|
||||||
""",
|
""",
|
||||||
"init_xml": [],
|
"init_xml": [],
|
||||||
"update_xml": ["security/ir.model.access.csv",
|
"update_xml": ["security/ir.model.access.csv",
|
||||||
|
|
|
@ -25,24 +25,24 @@
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
"category": "Project Management",
|
"category": "Project Management",
|
||||||
'description': """
|
'description': """
|
||||||
Automatically creates project tasks from procurement lines
|
Automatically creates project tasks from procurement lines.
|
||||||
==========================================================
|
===========================================================
|
||||||
|
|
||||||
This module will automatically create a new task for each procurement
|
This module will automatically create a new task for each procurement order line
|
||||||
order line (e.g. for sale order lines), if the corresponding product
|
(e.g. for sale order lines), if the corresponding product meets the following
|
||||||
meets the following characteristics:
|
characteristics:
|
||||||
|
|
||||||
* Type = Service
|
* Type = Service
|
||||||
* Procurement method (Order fulfillment) = MTO (make to order)
|
* Procurement method (Order fulfillment) = MTO (make to order)
|
||||||
* Supply/Procurement method = Produce
|
* Supply/Procurement method = Produce
|
||||||
|
|
||||||
If on top of that a projet is specified on the product form (in the Procurement
|
If on top of that a projet is specified on the product form (in the Procurement
|
||||||
tab), then the new task will be created in that specific project.
|
tab), then the new task will be created in that specific project. Otherwise, the
|
||||||
Otherwise, the new task will not belong to any project, and may be added to a
|
new task will not belong to any project, and may be added to a project manually
|
||||||
project manually later.
|
later.
|
||||||
|
|
||||||
When the project task is completed or cancelled, the workflow of the corresponding
|
When the project task is completed or cancelled, the workflow of the corresponding
|
||||||
procurement line is updated accordingly. For example if this procurement corresponds
|
procurement line is updated accordingly. For example, if this procurement corresponds
|
||||||
to a sale order line, the sale order line will be considered delivered when the
|
to a sale order line, the sale order line will be considered delivered when the
|
||||||
task is completed.
|
task is completed.
|
||||||
|
|
||||||
|
|
|
@ -27,7 +27,8 @@
|
||||||
Changes dates according to change in project End Date.
|
Changes dates according to change in project End Date.
|
||||||
======================================================
|
======================================================
|
||||||
|
|
||||||
If end date of project is changed then the deadline date and start date for all the tasks will change accordingly.
|
If end date of project is changed then the deadline date and start date for all
|
||||||
|
the tasks will change accordingly.
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['base', 'project'],
|
'depends': ['base', 'project'],
|
||||||
|
|
Loading…
Reference in New Issue