Hi Chris,

I'll try to reply the best I can. I'm using an older version of
Magnolia with a recent version of OpenWFE[ru] (
http://svn.magnolia.info/view/modules/community/magnolia-module-workflow/branches/magnolia-module-workflow-openwfe-ruby-3.0/
), but it should map to the Magnolia you are using.


On Thu, Feb 14, 2008 at 10:53 PM, Allan, CJ (Chris)
<[email protected]> wrote:
> Hi,
>
>  I would like to customise the magnolia activation workflow, and was
>  wondering about other peoples experience and suggestions.
>
>  I don't think it's very good that when a page/document is activated it
>  goes to everyone who has the publishers role. This can be lead to there
>  being many items in the Inbox and publishers getting confused.
>
>  I think it would be better if only the people who the item is relevant
>  to see it in their inbox.

You could modify your process definition so that the activation
approval requests go to a user inbox instead of a group inbox.

OpenWFE as found in Magnolia understands four kinds of users :

- "user-username"
- "group-groupname"
- "role-rolename"
- "command-commandname"

So if you want to route a publication approval to your "chris" user,
make sure that the process definition states

    <participant ref="user-chris" />


>  For example. If a page Home/Diffraction/Software/BSL is activated it
>  would be good to send this to people with any of the groups 'pub-Home',
>  'pub-Home-Diffraction', 'pub-Home-Diffraction-Software',
>  'pub-Home-Diffraction-Software-BSL'.
>
>  If there was a way in openwfe to convert 'Home/Diffraction/Software/BSL'
>  to a list [Home, Diffraction, Software, BSL] then I think the rest
>  wouldn't be that difficult. However, I don't know how to do this, or if
>  it's even a good way of trying to go about this.

Maybe there is a simpler way, but I would write a command that
encapsulates your work distribution logic. The name of the "real
participant" could be placed in a workitem field (for example 'next').

Commands are configured via the admin central, a command name linked
to a Java implementation.

Inside of a process instance, commands are passed a CommandContext
which is an instance of WorkItemContext.

The process definition snippet would look like :

    <sequence>
        <participant ref="command-determineapprover" />
        <participant field-ref="next" />
    </sequence>


I hope this helps a bit, best regards,

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

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to