Index: openacs-4/packages/workflow/www/doc/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/workflow/www/doc/index.html,v
diff -u -N -r1.1.2.1 -r1.1.2.2
--- openacs-4/packages/workflow/www/doc/index.html 7 Mar 2003 12:24:20 -0000 1.1.2.1
+++ openacs-4/packages/workflow/www/doc/index.html 22 Apr 2003 17:10:48 -0000 1.1.2.2
@@ -2,17 +2,21 @@
Workflow Documentation
Workflow Documentation
+Workflow Documentation
+
+
+
By Lars Pind
-
-
The workflow package provides a service to keep track of a process
involving multiple people around some object. Workflow keeps track
@@ -37,10 +41,72 @@
This is the document we wrote before implementing workflow specifying
- how we intended to implement the package then.
+ how we intended to implement the package then. It is inaccurate in a
+ number of places where reality forced us to make changes.
+Version History
+
+
+ -
+ 1.0d1 Bumped up the version number to 1.0 to reflect the
+ fact that this package is actually at a steady state and fully
+ useful as is. Also added a little API and cleaned up things a bit,
+ the kind of things you learn while writing the documentation.
+
+
+ -
+ 0.2d2 First version released along with OpenACS 4.6.2.
+
+
+
+Todo
+
+
+ -
+ Internationalization.
+
+ -
+ Add API for modifying live workflows, including ensuring that the modifications are
+ always safe (i.e. you can't delete a state that's used.)
+
+ -
+ Add a user interface for defining workflows.
+
+ -
+ Add a user interface for monitoring workflows and bulk changing
+ the state of workflows.
+
+ -
+ Periodically notify people of their outstanding assigned actions.
+
+ -
+ Add a task list user interface, either as part of the Workflow package, or as a separate pacakge.
+
+ -
+ Add support for petri nets and other models.
+
+ -
+ Add timing of actions, deadlines, and integrate those with calendar.
+
+ -
+ Application integration with certain states and actions. For
+ example, in bug-tracker, we treat the "Open" and "Closed" states
+ specially. We also treat the "Resolve" action specially. Should be
+ possible to define this link.
+
+ -
+ Add workflow variants, so you can ship your application with
+ multiple default implementations of the same workflow and let the
+ user choose between the available variants (e.g. simple approval
+ vs. multiple approval variants, choice of triage and Q&A steps in
+ the bug-tracker, etc.). This should probably be tied to some
+ concept of an 'application' as in the bullet above.
+
+
+
+
lars@pinds.com