summaryrefslogtreecommitdiff
path: root/doc/reference/workflows.rst
diff options
context:
space:
mode:
authorChristophe Simonis <chs@odoo.com>2016-02-17 18:01:11 +0100
committerChristophe Simonis <chs@odoo.com>2016-02-17 18:01:11 +0100
commit87a01c75ef1dde98bc31f714d8ac4b2ea598e316 (patch)
tree4fe33a648fc7de34294113ff2c69e2e28b133b85 /doc/reference/workflows.rst
parentd70fde0330550d510668e49807da83e646e8ccec (diff)
parent5be43b8d9ae4485ac28e9afb7dd7cdecefb58abc (diff)
[MERGE] forward port of branch saas-7 up to 5be43b8
Diffstat (limited to 'doc/reference/workflows.rst')
-rw-r--r--doc/reference/workflows.rst8
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
----------