Index: openacs-4/packages/tasks/lib/tasks-portlet.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/tasks/lib/tasks-portlet.tcl,v diff -u -r1.2 -r1.3 --- openacs-4/packages/tasks/lib/tasks-portlet.tcl 14 Oct 2005 13:50:07 -0000 1.2 +++ openacs-4/packages/tasks/lib/tasks-portlet.tcl 16 Oct 2005 11:11:12 -0000 1.3 @@ -1,4 +1,4 @@ -foreach optional_param {party_id query search_id tasks_interval} { +foreach optional_param {party_id query search_id tasks_interval page page_size page_flush_p} { if {![info exists $optional_param]} { set $optional_param {} } Index: openacs-4/packages/tasks/sql/postgresql/tasks-create.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/tasks/sql/postgresql/tasks-create.sql,v diff -u -r1.4 -r1.5 --- openacs-4/packages/tasks/sql/postgresql/tasks-create.sql 14 Oct 2005 13:50:07 -0000 1.4 +++ openacs-4/packages/tasks/sql/postgresql/tasks-create.sql 16 Oct 2005 11:11:12 -0000 1.5 @@ -109,12 +109,20 @@ process_task_id integer constraint t_tasks_process_task_fk references t_process_tasks, + -- The party_id is the party whom this task is associated with (e.g. the contact) party_id integer constraint t_tasks_party_fk references parties, + -- The object_id of the Object that triggered this task. If you created an offer + -- and want to have a reminder to phone, the party_id would be the recipient of the offer + -- the object_id would be the offer_id and the creation_user (assignee who is doing the job) + -- would be yourself. + -- As we are very bad in design we realized too late that it might make sense to change the + -- assignee at a later stage, we now modify the creation_user for this. object_id integer constraint t_tasks_object_fk references acs_objects, + -- I wish this were content_items... title varchar(1000), description text, mime_type varchar(200) default 'text/plain',