Re: tasklist with business attributes

Pradeep,
We also often avoid PropertySet -- instead we create a table that contains
the specific properties we're interested in and populate that. For accessing
that information, usually you can do a very good job of this by writing your
own persistence layer (usually extending an existing one supplied by
osworkflow) and writing your own Workflow class to use that persistence as
well as some custom behavior (such as putting a reference to an object that
contains that unique data in the transientVars map).

Hope that helps... sounds like you're on the right track!

-Pat

----- Original Message -----
From: "Pradeep" <[email protected]>
To: <[email protected]>
Sent: Thursday, June 26, 2003 11:05 AM
Subject: [Opensymphony-developers] tasklist with business attributes


> We are implementing a tasklist feature showing different business
attributes
> of entities Our current strategy is discussed below . We would like if
some
> one comment/critic/suggest strategies for achieving this.
>
> We are implementing an enterprise system with lots of bussiness workflows
> like new customer registration, notification, scheduling of resources,
> purchase request, purchase order, invoice creation, payment etc
>
> We want to implement a tasklist for each user logged in. Tasklist needs to
> show different bussiness attributes, some are defined for the workflow,
some
> are defined for each step.
>
> We are thinking of:
>
> 1. Define TaskCode, TaskMessage, Task-URL, to each step. 'Task code' is
used
> to classify and sort different items in the task list. All business
> attributes are merged into 'task message'. 'Task URL' can bring up either
> the list of actions from the osworkflow or any custom screen in the
> application.
>
> These attributes will be created as different workflows are initialized or
> actions are performed. For eg. For the customer registration task messsage
> will be
>
> Task Code: NEW_REGN
> Task Message: "CustomerNO:1234" - "Robert Smith"  -  "Registered"
> Task URL: showCustomer.jsp?id=1234
>
> 2. Which is the ideal place to persist these informations?
> We are thinking that since propertyset implementations cannot be indexed
for
> fast retrieval, we will create a seperate table to manage these data.
(some
> discussions in this list suggested so)
>
>       The table Definition is
>
>        step-id          entry-id       task-code     task-message
> task-URL
>
> Workflow level properties will be saved within  wf.initialize() & step
level
> properties saved within doAction().
>
> I am sure some of you must have created such tasklist that displays
business
> specific information along with that step. Can you share your strategies
and
> implementation lessons?
>
> Best regards,
>
> Thanks in anticipation,
> Pradeep
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php