> To have a better impression of my questions, just have a look at
>
> http://img697.imageshack.us/img697/6927/6eyeswf.png
I don't have such workflow ready at hand, but yes I've seen it done with
Magnolia more then once.
> Question 1) can items be directly re-assigned from 3rd instance
> (superpublisher) to 1ast instance in this chain?
yes, re-assigning is an active step in the workflow, like:
<loop>
<while>
<equals field-value="action" other-value="reject" />
</while>
<to-editor/><!-- here you can re-assign to whomever you want -->
...
If you want the opposite - move just one step back instead of whole way,
you can also do something like:
<process-definition name="proceed-or-step-back">
<if test="${field:action} == reject">
<!-- then --><back />
<!-- else : simply let flow move forward -->
</if>
</process-definition>
the <back/> expression would force the cursor to step back one step in
the execution.
>
> Question 2) in this: could publisher (note: it's a group) receive a CC
> of the notification mail that is sent to the editor?
yes, and again example of this is directly in the default workflow:
<set field="mailTo" value="group-publishers"/>
<set field="mailTemplate" value="workflowNotification"/>
<participant ref="command-sendMail"/>
if you want to CC mail instead of sending it directly you just use "cc"
field like:
<set field="cc" value="group-publishers"/>
>
> Question 3) there should be n parallel instances of this workflow
> related of position in the content tree
>
> /startpage
> --/branch-1
> --/branch-2
> --/branch-3
>
> I know that there exists a kind of workflow-uri-mapping-configuration
> in admin central, which means i could have three different workflows
> for branch 1 till 3, but I like to keep maintenance issues small and I
> am looking for a generic approach within the Workflow XML since the
> process will be definitely the same (but with different groups).
So? You just need to code the logic in the workflow, like:
<if test="${c:matches('${field:path}', '/branch1/.*')}">
<participant ref="group-publishers1"/>
<if test="${c:matches('${field:path}', '/branch2/.*')}">
<participant ref="group-publishers2"/>
<if test="${c:matches('${field:path}', '/branch3/.*')}">
<participant ref="group-publishers3"/>
</if>
</if>
</if>
> So, is it possible to set a global variable, for example loc="branch1"
yes
> and attach it dynamically in some OpenWFE-elements, for instance:
> <to-publisher_${loc}/>? Would be great to get some hints for this
> indeed very specific use case.
That's tricky. I don't think you can do that in the xml element. You
should be able to do this in a value tho so you can have yet another
if/else block like the one above or you can write your own command that
would indeed invoke correct participant based on the value of your
global var.
Tho whether this is more simple then having different mappings for the
workflow is a matter of opinion. Personally I don't think so, since
mappings can be easily re-assigned w/o having to change the workflow
definition and are more clearly visible in the AdminCentral. And more
importantly, those mappings would not clutter the definition so you can
easily find out what is actual flow without specifics of which group is
responsible for which branch of code.
For more on the workflow definition, you might also want to look up the
OpenWFE workflow manual http://www.openwfe.org/manual/
or copy of the same at our site:
http://dev.magnolia-cms.com/openwfe_manual/manual/
HTH,
Jan
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
