Index: openacs-4/contrib/obsolete-packages/acs-workflow/www/doc/developer.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/contrib/obsolete-packages/acs-workflow/www/doc/developer.html,v
diff -u -r1.2 -r1.3
--- openacs-4/contrib/obsolete-packages/acs-workflow/www/doc/developer.html	19 Nov 2001 18:31:50 -0000	1.2
+++ openacs-4/contrib/obsolete-packages/acs-workflow/www/doc/developer.html	9 Feb 2002 02:33:35 -0000	1.3
@@ -364,10 +364,19 @@
   </dd>
   <dt>Notification</dt>
   <dd>
-    The notification callback will get called whenever we're about to
-    notify a user that he's been assigned to this transition. The
-    notification callback may specify a custom subject line and body,
-    as well as a party that the email should be sent from. 
+    The notification callback will get called whenever a user is assigned
+    to this transition. The notification callback is passed the default
+    subject line and body, the recipient party, and the default sending
+    party.  It may modify any of these elements before posting the message,
+    or may choose to ignore the request and return without posting at all.
+    If no notification callback is provided, the party assigned to the
+    task will be notified automatically by the workflow engine.
+    <p><i>In ACS 4.x Classic, the callback procedure did not have to post
+    the message, but rather could modify the subject, body and sending
+    party directly through the use of PL/SQL <b>in out</b> parameters.
+    PL/pgSQL does not support <b>in out</b> parameters, so the semantics
+    were changed to work as described above.
+    </i>
   </dd>
   <dt>Unassigned task</dt>
   <dd>
@@ -470,9 +479,9 @@
     task_id           in number, 
     custom_arg        in varchar2, 
     party_to          in integer, 
-    party_from        <strong>in out</strong> integer, 
-    subject           <strong>in out</strong> varchar2, 
-    body              <strong>in out</strong> varchar2
+    party_from        in integer, 
+    subject           in varchar2, 
+    body              in varchar2
 );</pre>
 
 The <code>party_from</code>, <code>subject</code> and