Transactional behavior of a workflow instance

Authors:
Tatiana A. S. C. Vieira;Marco A. Casanova
Affiliations:
Pontifical Catholic University of Rio de Janeiro, Rio de Janeiro, RJ, Brazil;Pontifical Catholic University of Rio de Janeiro, Rio de Janeiro, RJ, Brazil
Venue:
ODBASE'06/OTM'06 Proceedings of the 2006 Confederated international conference on On the Move to Meaningful Internet Systems: CoopIS, DOA, GADA, and ODBASE - Volume Part I
Year:
2006

Citing 7
Cited 0

CoBase: a cooperative database system

Nonstandard queries and nonstandard answers
On building workflow models for flexible processes

ADC '02 Proceedings of the 13th Australasian database conference - Volume 5
Flexible Workflow Management in the OPENflow System

EDOC '01 Proceedings of the 5th IEEE International Conference on Enterprise Distributed Object Computing
Is It Possible to Make Workflow Management Systems Flexible? Dynamical Systems Approach to Business Processes

CRIWG '00 Proceedings of the 6th International Workshop on Groupware
Workflow Evolution

ER '96 Proceedings of the 15th International Conference on Conceptual Modeling
Flexible Data Management and Execution to Support Cooperative Workflow: the COO approach

CODAS '01 Proceedings of the Third International Symposium on Cooperative Database Systems for Advanced Applications
Flexible Modeling and Execution of Workflow Activities

HICSS '98 Proceedings of the Thirty-First Annual Hawaii International Conference on System Sciences-Volume 7 - Volume 7

Quantified Score

Hi-index	0.00

Visualization

Abstract

Workflow management systems usually interpret a workflow definition rigidly, allowing no deviations during execution However, there are real life situations where users should be allowed to deviate from the prescribed static workflow definition for various reasons, including lack of information about parameter values and unavailability of the required resources To flexibilize workflow execution, this paper proposes an exception handling mechanism that allows the execution to proceed when otherwise it would have been stopped The proposal is introduced as a set of extensions to OWL-S that capture the information required for the flexibilization mechanism In particular, this paper focus on the transactional behavior of a workflow instance, in the sense that it guarantees that either all actions executed by the instance terminate correctly or they are all abandoned.