Topic: wftk -- Process definition example -- trade show organization[ wftk home ] [ process definition ] [ discussion ] |
This is an attempt at the basic process outlined in the trade
show scenario. Note that some of the tasks here must be regarded as subprocesses, but that the
"subprocess nature" of these is not visible to this level. (This won't always be the case, but I think it
is in this scenario. Doubtlessly some of you people will disagree.)
This XML doesn't correspond perfectly with the scenario. You've been warned. Another thing I feel impelled to mention at the outset is that for some reason it seems right to me to include the organizer (i.e. the initiator) in the process for this example. I think that this is because in this case, the organizer has a lot more ownership of the process than in the chair purchase example. <?xml version="1.0"?> <workflow name="Tradeshow org" author="Michael: michael@vivtek.com"> <role name="Organizer"></role> <role name="Hotel person"></role> <role name="Schedule person"></role> <role name="Catering person"></role> <role name="Floor layout person"></role> <role name="Brochure person"></role> <data name="Show name" type="text"></data> <data name="Planned date" type="text"></data> <sequence> <parallel> <sequence> <task label="Book hotel" role="Hotel person"> <data name="Hotel booking record" type="something"/> </task> <parallel> <task label="Plan floor layout" role="Floor layout person"> <data name="Floor layout" type="document"/> </task> <task label="Rough schedule" role="Schedule person"> <data name="Schedule" type="document"/> </task> </parallel> </sequence> <task label="Book caterer" role="Catering person"> <data name="Catering service" type="text"/> </task> </parallel> <task label="Create brochure" role="Brochure person"> <data name="Floor layout" readonly="yes"></data/> <data name="Schedule" readonly="yes"></data> <data name="Brochure" type="document"></data> </task> </sequence> </workflow>Oddly, this process worked out cleaner than the chair. Probably because I didn't clutter it up with explicit alerts, among other things.
Data tag
Document data type
That hotel booking record Well, that's all I got from this example. On this level it's just not that interesting -- the whole point of the scenario was to show how useful decentrally defined subprocesses could be, and since they're all distributed, there's nothing much to see. |