Skip to content

Commit 014f02d

Browse files
committed
Minor tweak
1 parent 05b9034 commit 014f02d

File tree

1 file changed

+13
-6
lines changed

1 file changed

+13
-6
lines changed

workflow.rst

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -505,14 +505,21 @@ when needed and vice-versa when working with your objects::
505505
Using Weighted Transitions
506506
~~~~~~~~~~~~~~~~~~~~~~~~~~
507507

508-
Weighted transitions allow you to define transitions where multiple tokens (instances)
509-
are consumed from or produced to places. This is useful for modeling complex workflows
510-
such as manufacturing processes, resource allocation, or any scenario where multiple
511-
instances of something need to be produced or consumed.
512-
513508
.. versionadded:: 7.4
514509

515-
The support for weighted transitions was introduced in Symfony 7.4.
510+
Support for weighted transitions was introduced in Symfony 7.4.
511+
512+
A key feature of workflows (as opposed to state machines) is that an object can
513+
be in multiple places simultaneously. For example, when building a product, you
514+
might assemble several components in parallel. However, in the previous example,
515+
each place could only record whether the object was there or not, like a binary flag.
516+
517+
**Weighted transitions** introduce multiplicity: a place can now track how many
518+
times an object is in that place. Technically, weighted transitions allow you to
519+
define transitions where multiple tokens (instances) are consumed from or produced
520+
to places. This is useful for modeling complex workflows such as manufacturing
521+
processes, resource allocation, or any scenario where multiple instances of something
522+
need to be produced or consumed.
516523

517524
For example, imagine a table-making workflow where you need to create 4 legs, 1 top,
518525
and track the process with a stopwatch. You can use weighted transitions to model this:

0 commit comments

Comments
 (0)