Hello Emile, We have some applications build on top of MMBase which have workflow. The workflow is integrated with the security and site structure. We have considered to make it abstract layers, but the deadline was flying by eith a whoosing sound.
In one of our workflow implementations we made a workflow object which stores the status of the workflow. The workflow object is linked to the content element which is in workflow. It is also linked to the users which should have the workflow in the tasklist. The rights of an user on a content element is controlled by the editors. We have a tree-like navigation structure where users have roles on the branches. The content elements are linked to a node in the tree. The roles define what you can do with a workflow in a specific status. The problem with workflow is how you want to keep your site live and change a content element. If you have a single cloud then you have to make a new version of the content element and promote the version when apporoved. You have to make sure that the version does not show up on the live site. You could do that with the MMBase context security and define 2 contexts. The edit context and the live context. The anonymous user is only allowed to read the live context. Duplicating content elements could kill a high traffic site. Another solution on the version issue could be to create 2 clouds and let them communicate by rmi. The editors working on one and the visitors watching the other. I never have worked with Broadvision and am curious how the workflow works? Nico Klasens Finalist IT Group Java Specialists -------------------------------------------------- Teamwork is vital ; It gives you someone to blame. > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Namens Emile > Verzonden: zaterdag 17 april 2004 17:45 > Aan: [EMAIL PROTECTED] > Onderwerp: Workflow and the like > > Hi all > > has anyone considered building generic abstract layers for > tasks such as workflow? I have worked with and expanded > Broadvision quite a lot and gained a lot of ideas on the more > abstract layers around transaction management. I think many > of them will be very useful and natural extensions to mmbase. > Does anyone agree? Specifically, workflow, extensible > individual and generic user objects, knowledge gathering via > actions/preferences and targeting/profiling based on these, etc. > > Is this too early in the dev cycle to be introducing now? > > Regards > Emile
