Download Workflow Patterns - Information Systems

F Domino Workow
pattern
1 (seq)
2 (par-spl)
3 (synch)
4 (ex-ch)
5 (simple-m)
6 (m-choice)
7 (sync-m)
score
+
+
+
+
+
+
+
8 (multi-m)
+/-
9 (disc)
10 (arb-c)
11 (impl-t)
12 (mi-no-s)
+
+
+/-
13 (mi-dt)
14 (mi-rt)
+
-
15 (mi-no)
16 (def-c)
17 (int-par)
-
18 (milest)
19 (can-a)
20 (can-c)
+
motivation
Directly supported through routing relations connecting activities.
By making each output routing relation of type \always".
By setting the join attribute to \enabled".
By selecting either \condition" or \multiple choice" on output relations.
By selecting \disable join".
By selecting either \condition" or \multiple choice" on output relations.
Supported. Select \enable join". The AND-join will wait as long as something
may arrive.
Partially supported. Select \enable join". If instances meet, they are merged.
Therefore, no full support. Note that even if the individual subcases are
merged, they are still visible in the content of the case.
Not directly supported. Only through scripting.
Supported, only the self-loop is excluded.
Supported, there may be multiple end nodes.
No graphical support for multiple instances. However, the scripting language
of Domino allows for the creation of parallel instances. Moreover, by selecting
\disable join" it is possible to deal with multiple instances of sequential parts
of the process.
Supported through a combination of splits and joins.
No graphical support for multiple instances. However, the scripting language
of Domino allows for counters waiting for all instances to terminate.
No direct support.
No states.
For parallel routing, the case is split into identical copies which are
merged/joined at the AND-join. Therefore, only true parallelism is supported.
No states.
Not possible. Note that activities can be rerouted.
The activity owner can issue a \request to cancel job". The job owner decides
on the actual deletion of the job.
59