|
|
1640.
|
|
|
The first diagram represent a very basic workflow of an order:
|
|
|
|
|
Первая диаграмма The first diagram представляет очень простой рабочий процесс заказа:
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
52a9411fe52044d6bdacd18b6c70503d
|
|
Located in
../../source/developer/07_workflows.rst:27
|
|
|
1641.
|
|
|
The order starts in the 'draft' state, when it is being written and has not been approved yet. When the user presses on the 'Confirm' button, the invoice is created and the order transitions to the 'CONFIRMED' state.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:31
|
|
|
1642.
|
|
|
Then, two operations are possible:
|
|
|
|
|
Далее возможны две операции:
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
ee4579bcf4674559a4cb89a390c65dea
|
|
Located in
../../source/developer/07_workflows.rst:34
|
|
|
1643.
|
|
|
the order is done (shipped)
|
|
|
|
|
заказ выполнен (доставлен)
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
f5363d16172c43a4ba392442642d62eb
|
|
Located in
../../source/developer/07_workflows.rst:36
|
|
|
1644.
|
|
|
the order is canceled
|
|
|
|
|
заказ отменен
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
1acac0c4a36d453c99d02b1b76b4e3de
|
|
Located in
../../source/developer/07_workflows.rst:38
|
|
|
1645.
|
|
|
Let's suppose a company has a need not implemented in OpenERP. For example, their sales staff can only offer discounts of 15% or less. Every order having a discount above 15% must be approved by the sales manager.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:40
|
|
|
1646.
|
|
|
This modification in the sales logic doesn't need any lines of Python code! A simple modification of the workflow allows us to take this new need into account and add the extra validation step.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:42
|
|
|
1647.
|
|
|
The workflow is modified as above and the orders will react as requested. We then only need to modify the order form view and add a validation button at the desired location.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:46
|
|
|
1648.
|
|
|
We could then further improve this workflow by sending a request to the sales manager when an order enters the 'Validation' state. Workflow nodes can execute object methods; only two lines of Python are needed to send a request asking the sales manager to validate or reject the order.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:48
|
|
|
1649.
|
|
|
Example 2: A sale order that generates an invoice and a shipping order
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:52
|
