Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Completion Condition Handling in Workflow Management Systems

IP.com Disclosure Number: IPCOM000031975D
Original Publication Date: 2004-Oct-18
Included in the Prior Art Database: 2004-Oct-18
Document File: 1 page(s) / 5K

Publishing Venue



Completion conditions in workflow management systems provide the capability to test for successful completion of an activity. They are typically expressed as Boolean conditions. In many workflow management systems, failing of a completion condition causes the activity to be restarted. It is suggested that this mode of operation is enhanced through the notion of completion condition faults and completion condition handlers.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 1

Completion Condition Handling in Workflow Management Systems Completion Condition Handling in Workflow Management SystemsCompletion Condition Handling in Workflow Management Systems Completion Condition Handling in Workflow Management Systems

Business Process Execution Language for Web Services (BPEL4WS) is a language that provides for the specification of business processes made up of Web Services . It is used for illustrating the enhancements suggested to completion conditions . Obviously any other language that provides for the definition of business processes, such as FDL used by IBM's* WebSphere* MQSeries* Workflow, can benefit from the suggested enhancements. Incidentally, it should be noted that BPEL4WS currently does not support the notion of completion conditions .

    The following is the basic structure of an activity that encompasses a completion condition:

<activity name="someName" completionCondition="bool-expr"/>

    The specification and handling of the completion condition is similar to the definition of the join condition. When a completion condition fails, an appropriate fault, completionConditionFailure, is thrown. This fault can then be caught in an appropriate fault handler. Suppressing the throwing of a completion condition fault, could be done via a suppressCompletionConditionFailure attribute . In its simplest form, setting attribute to yes would mean that the completion condition fault is ignored and the activity is restarted. If set to no, a fa...