1 .. -*- coding: utf-8 -*- |
|
2 |
|
3 Defining a Workflow |
|
4 =================== |
|
5 |
|
6 General |
|
7 ------- |
|
8 |
|
9 A workflow can be defined in a `LAX` application thanks to the system |
|
10 entities ``State`` and ``Transition``. Those are defined within all |
|
11 LAX application and can be set-up through the main administrator interface. |
|
12 |
|
13 Once your schema is defined, you can start creating the set of states and |
|
14 the required transitions for your applications entities. |
|
15 |
|
16 You first need to define the states and then the transitions between those |
|
17 to complete your workflow. |
|
18 |
|
19 A ``State`` defines the status of an entity. While creating a new state, |
|
20 you will be first given the option to select the entity type the state |
|
21 can be applied to. By choosing ``Apply``, a new section will be displayed |
|
22 in the editing screen to enable you to add relation to the state you are |
|
23 creating. |
|
24 |
|
25 A ``Transition`` is also based on an entity type it can be applied to. |
|
26 By choosing ``Apply``, a new section will be displayed in the editing |
|
27 screen to enable you to add relation to the transition you are |
|
28 creating. |
|
29 |
|
30 At the transition level you will also define the group of user which can |
|
31 aplly this transition to an object. |
|
32 |
|
33 |
|
34 Example of a simple workflow |
|
35 ---------------------------- |
|
36 |
|
37 Please see the tutorial to view and example of a simple workflow. |
|
38 |
|
39 |
|
40 [Create a simple workflow for BlogDemo, to have a moderator approve new blog |
|
41 entry to be published. This implies, specify a dedicated group of blog |
|
42 moderator as well as hide the view of a blog entry to the user until |
|
43 it reaches the published state.] |
|