2007
DOI: 10.1007/978-3-540-76848-7_8
|View full text |Cite
|
Sign up to set email alerts
|

Dynamic, Extensible and Context-Aware Exception Handling for Workflows

Abstract: Abstract. This paper presents the realisation, using a Service Oriented Architecture, of an approach for dynamic, flexible and extensible exception handling in workflows, based not on proprietary frameworks, but on accepted ideas of how people actually work. The resultant service implements a detailed taxonomy of workflow exception patterns to provide an extensible repertoire of self-contained exception-handling processes called exlets, which may be applied at the task, case or specification levels. When an ex… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
45
0
1

Year Published

2008
2008
2020
2020

Publication Types

Select...
6
3
1

Relationship

2
8

Authors

Journals

citations
Cited by 87 publications
(46 citation statements)
references
References 25 publications
0
45
0
1
Order By: Relevance
“…Exception handling often requires combined use of such patterns resulting in rather complex routines. The Exlet approach [41], for example, addresses this problem by allowing for the combination of different exception handling patterns to an exception handling process called Exlet. Similarly, [42] suggests the usage of meta workflows for coordinating exception handling.…”
Section: Discussionmentioning
confidence: 99%
“…Exception handling often requires combined use of such patterns resulting in rather complex routines. The Exlet approach [41], for example, addresses this problem by allowing for the combination of different exception handling patterns to an exception handling process called Exlet. Similarly, [42] suggests the usage of meta workflows for coordinating exception handling.…”
Section: Discussionmentioning
confidence: 99%
“…As academic approaches we consider popular flexible PAIS such as ADEPT2 [11,39], CAKE2 [30,40], CBRFlow [41,42], HOON [17], MOVE [18], Pockets of Flexibility (PoF) [16,43,44], WASA2 [13], WIDE [45,46], Worklets/Exlets [12,47,48], and YAWL [49]. -Feature Identification Procedure.…”
Section: Identification Of Change Support Featuresmentioning
confidence: 99%
“…With such semantic clarity, it is possible to verify processes in advance before enactment for runtime soundness [3], i.e., one can check for control-flow issues such as deadlocks. In YAWL, workflow adaptations are possible through so-called worklets [8] enactment in a dynamic way based on the evaluation result of Ripple-Down-Rules (RDR) trees. The now industrial AristaFlow system [90] is another example originating from research based on the former ADEPT flow system [89].…”
Section: Second Refinement Levelmentioning
confidence: 99%