Alright ! thanks for all the insight. I guess I'll come back with more questions once I digested this and worked some more ;)
Cheers, g John Mettraux wrote:
On 1/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Still speaking in the worklist point of view. > > > > The worklist saves/persists a workitem whenever it receives it, a user > > made a change to it. > > It deletes the workitem upon successful forwarding (dispatch back to > > the engine). > [...] > > BTW, are you using an embedded worklist or Magnolia participants (users inbox) ? > > Hmm well I didn't think they were antagonistic concepts. I'll obviously > need the participants, but where does the worklist fit (or doesn't) in > the picture? I always thought it was similar to the inbox, so I'm > confused now ... :) antagonism : you can use both, but having both manipulating the same instance of a workitem is bad. I don't know your context, but having Magnolia [and its inboxes] as a "worklist" might be nice, viewing and editing a workitem via a Magnolia template directly is a powerful concept. Best regards, sleep well, -- John Mettraux -///- http://jmettraux.openwfe.org
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE 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/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
