Index: openacs-4/packages/workflow/www/doc/workflow.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/workflow/www/doc/workflow.adp,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/workflow/www/doc/workflow.adp 20 Aug 2015 18:49:02 -0000 1.1
+++ openacs-4/packages/workflow/www/doc/workflow.adp 26 Aug 2015 18:03:36 -0000 1.2
@@ -2,16 +2,25 @@
After an action has been completed, depending on the action, we
-will redirect you to one of: After an action has been completed, depending on the action, we
+will redirect you to one of: This will be specified in the workflow spec as an "redirect_to"
+ This will be specified in the workflow spec as an "redirect_to"
on actions, with possible values of "task_list", "case",
-"case_list", or "new_case". This assumes we have already implemented #6 below. It will require changes to the API, in order for
-workflow::case::action::execute to be able to return a URL. TODO: Look in more detail at what's needed. Estimate: 6 hours. Risk: Med. Recommended. Write a generic task list UI that lets you find tasks which you
-are supposed to do, and get to them. It should use the list builder so you can sort, filter, and
-paginate. Requires #6. Time estimate: 10 hours. Risk: Low.A: WF #3: Redirect After Action
+
+A: WF #3: Redirect After Action
+
A: WF #10: Task list UI
This assumes we have already implemented #6 below.
+It will require changes to the API, in order for +workflow::case::action::execute to be able to return a URL.
+TODO: Look in more detail at what's needed.
+Estimate: 6 hours. Risk: Med. Recommended.
+Write a generic task list UI that lets you find tasks which you +are supposed to do, and get to them.
+It should use the list builder so you can sort, filter, and +paginate.
+Requires #6.
+Time estimate: 10 hours. Risk: Low.