Making your e-business work  

Home

Standards
    Conformance
    Reference Model
    Public Documents
    XPDL_2.0
    Wf-XML 2.0



About WfMC

Events

Information and
Publications


Free downloads

Membership Information

Press Room

Excellence Awards

Marvin L Manheim Award

Workflow Handbook
   2001
   2002
   2003

   2004
   2005
   2006 NEW!


Associated sites:
AIIM
WARIA

e-workflow.org

Got a question?
Join our Discussion Forums
 Discussion Forum for Workgroups (WfMC-specific)

Workflow and BPM Research

BPM Community Forum
 


Issue 30
Flow Control Without a Center Server, and

Transmission of Flow Control Information

Keith Swenson CT0016 Flow control without a center server, and transmission of flow control information:

SWAP1.0draft defines asynchronous protocols between a process and its subprocesses. If we

want to execute process A, B, and C in sequence, we need to define process X which creates

subprocess A, B, and C in the sequence by SWAP. process A, B, and C never communicate

directly each other. It is, however, difficult to deploy a center server like X when it comes to

the enterprise workflow among companies. Process A should create process B by itself when

it finishes. B is not a subprocess of A. That is, there is no activity in A corresponding to

process B. Keith Swenson SWAP Update Page 6 of 6 SWAP Update.doc June 12, 1999 Page

6 of 6 We add 'followingProcesses' into ResultPage of Propfind method which is a list of URI

of the following processes created when the process is finished. The flow engine is

responsible for creating the following processes and set the value of the followingProcesses.

The flow engine is also responsible for assigning the originalKey of a process to the

following processes. The following process does not notify its parent process of its

completion. In the above example, process A creates process B when it finishes. Users of EDI

systems want to design and control such process flow of the process instances which they

create. Thus SWAP should be able to send the process flow information though SWAP does

not intend to define the process flow definition itself. We add a new parameter 'flowInfo' to

the createprocessinstance method. The definition of the flowInfo itself does not belong to the

scope of SWAP. For example, we can use the WPDL of WfMC in XML format. The flowInfo

does not control each process, but indicate the following processes to be created when a

process finishes. In the above example, flowInfo contains such flow information that process

A, B, and C are executed in sequence. It does not control the activities of each process. The

flow engine is responsible for interpreting the flowInfo and create the f ollowing processes.

Issue 31
Filter

Rainer Weber CT0030 Do we want to leave open which filters are available (e.g. in

ProcessDefinition.ListInstances)? Proposal: Discuss.

Rainer Weber CT0031 ProcessDefinition.ListInstances says "... optionally based on the provided filtering

requirements": Does this mean that the filter is optional (then we should state this for this

parameter in the request)? I could not think of another sensible explanation. Proposal: Make

filter optional.

David Hollingsworth CT0072 I think some form of filtering mechanism this is needed as list manipulation will be too

cumbersome in big systems without it.

Edna Murby CT0091 2.2.6--Page 15--Comment on Filter parameter: Need specification of Filter parameter; even

better, remove for now. --Proposed Modification: Remove Filter parameter for now. Rational:

Define scope of specification

Edna Murby CT0092 2.2.6--Page 15--Comment on FilterType parameter: This is not a 'natural' language. Rational:

Discussion.

Issue 32
ProcessInstance.Subscribe

Rainer Weber CT0034 Which events?

Which state changes (in addition to "completed") and events are reported? Does the creator

get *all* of these events? Who selects which ones are passed, the sender of the event? The

section on "Observer" says "... while most events are not required to be notified": Who

decides which events are notified? Proposal: The event mechanism (except the "completed"

event, which is well-defined) does not seem to be elaborated sufficiently. Elaborate or leave it

Friday, June 09, 2000 Page 4 of 8
First Previous Next Last
Standards
Published Docs
Standards
Reference Model
Conformance
XPDL support

Wf-XML 2.0
 

Information Services
Info Services
Awards
Books
Workflow Handbook

Membership
How to join
Application
Country Chapters
List of members
Officers
Fellows


NEW!

Workflow Handbook 2006
NOW SHIPPING!



CDROM Companion to the Workflow Handbook 2005

 

horizontal rule

home | membership | standards | info | events | members only

All brand names and product names mentioned in this website are trademarks or service marks of their respective companies. Any omission or misuse should not be regarded as intent to infringe on the property of others. The WfMC recognizes and respects all marks used by companies, manufacturers and developers as a means to distinguish their products. The “WfMC” logo and “Workflow Management Coalition” are service marks of the Workflow Management Coalition. http://www.wfmc.org.

horizontal rule