|
|
1688.
|
|
|
Defining activities using XML files
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:221
|
|
|
1689.
|
|
|
The general structure of an activity record is as follows
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:223
|
|
|
1690.
|
|
|
The first two arguments **wkf_id** and name are mandatory.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:241
|
|
|
1691.
|
|
|
Examples
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:245
../../source/developer/Web_client_v6/mako_template.rst:79
|
|
|
1692.
|
|
|
There are too many possibilities of activity definition to choose from using this definition. We recommend you to have a look at the file ``server/addons/sale/sale_workflow.xml`` for several examples of activity definitions.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:247
|
|
|
1693.
|
|
|
Transition
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:250
|
|
|
1694.
|
|
|
Workflow transitions are the conditions which need to be satisfied to move from one activity to the next. They are represented by one-way arrows joining two activities.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:255
|
|
|
1695.
|
|
|
The conditions are of different types:
|
|
|
|
|
role to satisfy by the user
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
e16691b148f34a589d8bdf0ee6a24cbc
|
|
Located in
../../source/developer/07_workflows.rst:258
|
|
|
1696.
|
|
|
role that the user must satisfy
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/07_workflows.rst:260
|
|
|
1697.
|
|
|
button pressed in the interface
|
|
|
|
|
end of a subflow through a selected activity of subflow
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
48553d4cb8da425189ce900e925a3df9
|
|
Located in
../../source/developer/07_workflows.rst:261
|
