blob: 0c8fc6119f6a984da5ade7ab947f5ca3640cd920 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
#
# documentsignoffstate.pystate
#
# state machine model of the states and associated behaviors and properties for each
# different state of a document in a document control system
#
# example using named state transitions
# This implements a state model for submitting,
# approving, activating, and purging document
# revisions in a document management system.
#
# The state model looks like:
#
# New
# |
# | (create)
# |
# v
# Editing ----------------------------------------------+
# | ^ |
# | | |
# | +----------+ |
# | | |
# | (submit) | | (cancel)
# | | (reject) |
# v | |
# PendingApproval-+ |
# | |
# | (approve) |
# | |
# v |
# Approved <--------------------------+ (deactivate) |
# | | | |
# | +--------------+ | |
# | | (activate) | |
# | v | |
# | (retire) Active ----------+ |
# | |
# v |
# Retired |
# | |
# | (purge) |
# | |
# v |
# Deleted <---------------------------------------------+
#
#
# There is no behavior attached to these states, this is
# just an example of a state machine with named transitions.
#
statemachine DocumentRevisionState:
New -( create )-> Editing
Editing -( cancel )-> Deleted
Editing -( submit )-> PendingApproval
PendingApproval -( reject )-> Editing
PendingApproval -( approve )-> Approved
Approved -( activate )-> Active
Active -( deactivate )-> Approved
Approved -( retire )-> Retired
Retired -( purge )-> Deleted
New.description = 'creating...'
Editing.description = 'editing...'
PendingApproval.description = 'reviewing...'
Approved.description = 'approved/inactive...'
Active.description = 'approved/active...'
Deleted.description = 'deleted...'
Retired.description = 'retired...'
|
