On 9/21/07, rfoxmich <[EMAIL PROTECTED]> wrote:
>
> This is a nice thought though I was actually trying to use stores for
> another purpose...categorizing what a work item represents. E.g.
> I have work items of many types, like approvals, filling out forms
> etc.
> and I may want to be able to do searches of that sort efficiently as
> well.
>
> I'm not 100% sure about how my application will get implemented,
> however I do believe I'll need to find work items from a mass of
> perhaps 1000's of them efficiently in several different search
> dimensions.
>
> In the end I'll be disabling your stores view from my application.
> Users will get a 'dashboard' that shows work items that have been
> targeted to them either directly or via groups they belong to.
>
>
> I realize that modifying the base classes is a bad idea so what I
> actually did do was build a new class in a different namespace that is
> the modified version of the original.
>
> To me the idea that work items have a target seems natural and in line
> with how the real world application I'm trying to build would operate.
> I had been originally playing with using a chunk of the participant
> name as the target, but as that will require queries involving 'like'
> terms I was afraid that would not scale as well to systems with large
> numbers of in-flight work items.
>
> Stores seemed un-natural to me somehow.  But perhaps I'm missing
> something.  The proliferation of stores as you say is something that I
> did not want to go to, as each store needs to be defined etc. etc.
> and since I already need to define users and their groups it seemed
> like prone to issues similar to that of duplication of data.

Hi Ron,

there are so many patterns for the "worklist" concept :

http://workflowpatterns.com/patterns/resource/index.php


Fortunately we are using Ruby, extending classes is so easy. I have to
document those extensibility points.

Densha is just a generic interpretation of what a worklist should be,
it's a starting point. Feel free to break it and redo it your way.
It's Ruby and under a BSD license.


Thanks for sharing your ideas, kind regards,

-- 
John Mettraux   -///-   http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenWFEru users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to