@@ -27,6 +27,7 @@ like this:
27
27
workflows :
28
28
blog_publishing :
29
29
type : ' workflow' # or 'state_machine'
30
+ audit_trail : ' enabled'
30
31
marking_store :
31
32
type : ' multiple_state' # or 'single_state'
32
33
arguments :
@@ -62,7 +63,7 @@ like this:
62
63
>
63
64
64
65
<framework : config >
65
- <framework : workflow name =" blog_publishing" type =" workflow" >
66
+ <framework : workflow name =" blog_publishing" type =" workflow" audit_trail = " enabled " >
66
67
<framework : marking-store type =" single_state" >
67
68
<framework : argument >currentPlace</framework : argument >
68
69
</framework : marking-store >
@@ -106,6 +107,7 @@ like this:
106
107
'workflows' => array(
107
108
'blog_publishing' => array(
108
109
'type' => 'workflow', // or 'state_machine'
110
+ 'audit_trail' => 'enabled',
109
111
'marking_store' => array(
110
112
'type' => 'multiple_state', // or 'single_state'
111
113
'arguments' => array('currentPlace')
@@ -157,6 +159,14 @@ like this:
157
159
attributes of the ``marking_store `` option are optional. If omitted, their default values
158
160
will be used.
159
161
162
+ .. tip ::
163
+
164
+ Setting the ``audit_trail `` option to ``enabled `` makes the application
165
+ generate detailed log messages for the workflow activity.
166
+
167
+ .. versionadded :: 3.3
168
+ The ``audit_trail `` option was introduced in Symfony 3.3.
169
+
160
170
With this workflow named ``blog_publishing ``, you can get help to decide
161
171
what actions are allowed on a blog post::
162
172
@@ -241,10 +251,10 @@ order:
241
251
* ``workflow.entered ``
242
252
* ``workflow.[workflow name].entered ``
243
253
* ``workflow.[workflow name].entered.[place name] ``
244
-
254
+
245
255
``workflow.completed ``
246
256
The object has completed this transition.
247
-
257
+
248
258
The three events being dispatched are:
249
259
250
260
* ``workflow.completed ``
0 commit comments