[DOC] workflows: added Signals section.
bzr revid: vmt@openerp.com-20130723132751-lwn5r6y1m51jhj9o
This commit is contained in:
parent
2397c1a98b
commit
3f9fb6eacc
|
@ -113,6 +113,19 @@ defined:
|
||||||
Signals
|
Signals
|
||||||
'''''''
|
'''''''
|
||||||
|
|
||||||
|
In addition of a condition, a transition can specify a signal name. When such
|
||||||
|
signal name is present, the transition will not be taken directly (even if the
|
||||||
|
condition evaluates to true). Instead the transition will block, waiting to be
|
||||||
|
woken up.
|
||||||
|
|
||||||
|
To wake up a transition with a defined signal name, the signal must be sent to
|
||||||
|
the workflow. A common way to send a signal is to use a button in the web
|
||||||
|
interface, using the ``<button/>`` element with the signal name as the ``name``
|
||||||
|
attribute of the button.
|
||||||
|
|
||||||
|
.. note:: The condition is still evaluated when the signal is sent to the
|
||||||
|
workflow instance.
|
||||||
|
|
||||||
Triggers
|
Triggers
|
||||||
''''''''
|
''''''''
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue