Programming with the wftk

Programmer's Guide to the wftk -- OO class schema

The OO schema for the wftk is still young -- in fact, as of this writing, it hasn't been implemented in any language yet. The idea, however, is that all OO languages should see the same objects, attributes, and methods, allowing simple portability of wftk applications and techniques to whatever language you're using.

The initial idea of this document (as of 19 Sep 2002) is to lay out and justify the existence of the basic objects in the schema; as I have time and motivation, the methods and attributes of all these object will be filled in. If anyone has suggestions as to the best way to graphically present these beasts, chip in.

object xmlapi
The XMLAPI object underlies all data structures used by the wftk.
object xmlobj is-a xmlapi
The xmlobj library defines a record structure, with versioned values, a list definition, and so forth.
object listdefn is-a xmlapi
The listdefn object defines default values, optional and required fields, attachments, workflow triggers, visibility and permissions, storage (sometimes), and a raft of other things about data objects.
object repository is-a xmlapi
The repository object describes the range of lists available to the current application (in listdefn objects), publishers, layouts, etc.
object layout is-a xmlapi
Not sure if I even really need this ...
object publisher is-a xmlapi
... or this...
object datasheet is-a xmlobj
The datasheet represents a workflow process. Note that a repository manager list object generally corresponds to a datasheet.
object task is-a xmlobj
A workflow task.
object request is-a xmlobj
A workflow request.
object user is-a xmlobj
A user, whether the current one or some other.
object notification is-a xmlapi
Again -- not sure where I'm going with this one.
object query is-a xmlapi
To retrieve information from the wftk, you create a query object, fill it out with some parameters, then you toss it to the wftk to be filled out.