@@ -27,6 +27,7 @@ like this:
2727workflows :
2828blog_publishing :
2929type :' workflow' # or 'state_machine'
30+ audit_trail :' enabled'
3031marking_store :
3132type :' multiple_state' # or 'single_state'
3233arguments :
@@ -62,7 +63,7 @@ like this:
6263 >
6364
6465 <framework : config >
65- <framework : workflow name =" blog_publishing" type =" workflow"
66+ <framework : workflow name =" blog_publishing" type =" workflow" audit_trail = " enabled "
6667 <framework : marking-store type =" single_state"
6768 <framework : argument >currentPlace</framework : argument >
6869 </framework : marking-store >
@@ -106,6 +107,7 @@ like this:
106107 'workflows' => array(
107108 'blog_publishing' => array(
108109 'type' => 'workflow', // or 'state_machine'
110+ 'audit_trail' => 'enabled',
109111 'marking_store' => array(
110112 'type' => 'multiple_state', // or 'single_state'
111113 'arguments' => array('currentPlace')
@@ -157,6 +159,14 @@ like this:
157159 attributes of the ``marking_store `` option are optional. If omitted, their default values
158160 will be used.
159161
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+
160170With this workflow named ``blog_publishing ``, you can get help to decide
161171what actions are allowed on a blog post::
162172
@@ -241,10 +251,10 @@ order:
241251 * ``workflow.entered ``
242252 * ``workflow.[workflow name].entered ``
243253 * ``workflow.[workflow name].entered.[place name] ``
244-
254+
245255``workflow.completed ``
246256 The object has completed this transition.
247-
257+
248258 The three events being dispatched are:
249259
250260 * ``workflow.completed ``