File tree Expand file tree Collapse file tree 1 file changed +0
-13
lines changed
Filter options
Expand file tree Collapse file tree 1 file changed +0
-13
lines changed
Original file line number Diff line number Diff line change @@ -197,10 +197,6 @@ As configured, the following property is used by the marking store::
197
197
Setting the ``audit_trail.enabled `` option to ``true `` makes the application
198
198
generate detailed log messages for the workflow activity.
199
199
200
- .. versionadded :: 3.3
201
-
202
- The ``audit_trail `` option was introduced in Symfony 3.3.
203
-
204
200
With this workflow named ``blog_publishing ``, you can get help to decide
205
201
what actions are allowed on a blog post::
206
202
@@ -406,10 +402,6 @@ This means that each event has access to the following information:
406
402
:method: `Symfony\\ Component\\ Workflow\\ Event\\ Event::getWorkflowName `
407
403
Returns a string with the name of the workflow that triggered the event.
408
404
409
- .. versionadded :: 3.3
410
-
411
- The ``getWorkflowName() `` method was introduced in Symfony 3.3.
412
-
413
405
For Guard Events, there is an extended class :class: `Symfony\\ Component\\ Workflow\\ Event\\ GuardEvent `.
414
406
This class has two more methods:
415
407
@@ -475,11 +467,6 @@ of domain logic in your templates:
475
467
``workflow_has_marked_place() ``
476
468
Returns ``true `` if the marking of the given object has the given state.
477
469
478
- .. versionadded :: 3.3
479
-
480
- The ``workflow_marked_places() `` and ``workflow_has_marked_place() ``
481
- functions were introduced in Symfony 3.3.
482
-
483
470
The following example shows these functions in action:
484
471
485
472
.. code-block :: html+twig
You can’t perform that action at this time.
0 commit comments