Added examples of workflows

symfony · Nyholm · Aug 12, 2016 · Aug 12, 2016 · Aug 12, 2016 · Aug 12, 2016
commit dceebec28cfd2737432028dd0052bf69d073651a
diff --git a/_images/components/workflow/job_application.png b/_images/components/workflow/job_application.png
diff --git a/_images/components/workflow/simple.png b/_images/components/workflow/simple.png
diff --git a/workflow.rst b/workflow.rst
@@ -1,17 +1,51 @@
 Workflow
---------
+========
 
 A workflow is a model of a process in your application. It may be the process
 of how a blog post goes from draft, review and publish. Another example is when
-a user submitts a series of different forms to complete a task. Such processes are
+a user submits a series of different forms to complete a task. Such processes are
 best kept away from your models and should be defined in configuration.
 
-A state machine is a subset of a workflow and its purpose is to hold a state of
-your model. Both the workflow and state machine defines what actions (transitions)
-are allowed on the model at each state.
+A **definition** of a workflow consist of places and actions how to get from one
+place to another. The actions are called **transistions**. A workflow does also
+need to know each object's position in the workflow. That **marking store** writes
+to a property of object to remember the current place.
+
+.. note::
+
+    The terminology above is commonly used when discussing workflows and
+    `Petri nets`_
+
+The workflow component does also support state machines. A state machine is a subset
+of a workflow and its purpose is to hold a state of your model. Read more about the
+differences and specific features of state machine in :doc:`/workflow/state-machines`
+
+Examples
+--------
+
+The simples workflow looks like this. It contains two places and one transition.
+
+.. image:: /_images/components/workflow/simple.png
+
+Workflows could be more complicated when they describes a real business case. The
+workflow below descirbes the process to fill in a job application.
+
+.. image:: /_images/components/workflow/job_application.png
+
+When you fill in a job application in this examplethere are 5 to 8 steps depending
+on the what job you are applying for. Some jobs requires personality test, logic tests
+and/or formal requirements to be answered by the user. Some jobs don't. We use the
+``GuardEvent`` to decide what next steps that are allowed for a specific application.
+
+By defining a workflow like this we have an over view how the process looks like. We
+do not have any of the process logic in our controllers, models or view. We can change
+the order of the steps by changing configuration only.
+
 
 .. toctree::
    :maxdepth: 1
    :glob:
 
    workflow/*
+
+.. _Petri nets: https://en.wikipedia.org/wiki/Petri_net