diff options
| author | Martin Trigaux <mat@odoo.com> | 2016-02-11 10:01:04 +0100 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2016-02-17 13:57:13 +0100 |
| commit | d48f43ebff67a58f7d8d46c3463c4468234dbaad (patch) | |
| tree | cd47d52ef94955650ea75d2961f5de852fb15690 /doc/reference | |
| parent | d0556808deaf70026464280906dec9fde2a90ed1 (diff) | |
[IMP] doc: better workflow example
- Why is my workflow starting in b?
- It is not, it goes from a to b directly
- But I followed the example of the doc
- It's incomplete
Diffstat (limited to 'doc/reference')
| -rw-r--r-- | doc/reference/workflows.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/reference/workflows.rst b/doc/reference/workflows.rst index db57880436e..c67784797c4 100644 --- a/doc/reference/workflows.rst +++ b/doc/reference/workflows.rst @@ -86,6 +86,7 @@ instance, here is a simple sequence of two activities defined in XML <record id="trans_a_b" model="workflow.transition"> <field name="act_from" ref="activity_a"/> <field name="act_to" ref="activity_b"/> + <field name="signal">signal_goto_b</signal> </record> A worfklow is always defined with respect to a particular model (the model is @@ -107,9 +108,10 @@ is of kind ``function``, which means that the action ``print_a()`` is a method call on the model ``test.workflow`` (the usual ``cr, uid, ids, context`` arguments are passed for you). -The transition between "a" and "b" does not specify any condition. This means -that the workflow instance immediately goes from "a" to "b" after "a" has been -processed, and thus also processes activity "b". +The transition between "a" and "b" specify a signal but not any condition. This +means the workflow instance will immediately transition from "a" to "b" when the +signal ``signal_goto_b`` is recieved and thus processes activity "b"'s action +``print_b()``. Activities ---------- |