Rephrase workflow explanation

Signed-off-by: Roberto Rosario <roberto.rosario.gonzalez@gmail.com>
This commit is contained in:
Roberto Rosario
2019-05-18 01:10:17 -04:00
parent 5b45769423
commit 484f09db75

View File

@@ -96,21 +96,18 @@ Implementation
============== ==============
Internally, workflows are implemented as a finite state machines Internally, workflows are implemented as a finite state machines
(https://en.wikipedia.org/wiki/Finite-state_machine). And have the limitation (https://en.wikipedia.org/wiki/Finite-state_machine). To make them simpler to
that only one state can be the current active state for a workflow being use, workflow have been designed so that only one state can be the current
executed. The other limitation of the current implementation is that every active state for a workflow being executed. Another design decision is that
workflow needs at least one state marked as the initial state. These limitations every workflow needs at least one state marked as the initial state.
are the result of a compromised in the design between flexibility and ease of
use.
Visualizations Visualizations
============== ==============
The graphical representation of a workflow (or a finite state machine style The graphical representation of a workflow is similar to a flowchart. The
in Mayan EDMS's case) is similar to a flowchart. The states are represented states are represented with circles. The transitions are represented with
with circles. The transitions are represented with arrows. Circle with a arrows. Circle with a double border represent the initial state of the workflow.
double border represent the initial state of the workflow.
To view the graphical representations of workflow use **Preview** button of To view the graphical representations of workflow use **Preview** button of
the workflow in the setup view. the workflow in the setup view.