OK, I made it. But a little bit in an other way. I write it down here for
helping some other users.
First of all the .xml I had to edit is the default.xml. It is in the
magnolia-module-workflow-3.0.2.jar. and can be found there under:
info\magnolia\module\workflow
I understood the way it worked quite quickly but I didn't know how to check
where the activated site came from. Because I didn't want to study the whole
WFE I thought that it would also be a good idea to check *who* activaded the
page. With that information I also can decide to wich publisher-group it
should go to. Of course I have to give every site-publisher an own publisher
role. This is the changed XML:
<process-definition name="activation" revision="j0.0.2">
<sequence>
<set field="activator" field-value="userName"/>
<if test="${field:activator} == siteone">
<participant ref="group-siteonePublisher"/>
</if>
<if test="${field:activator} == sitetwo">
<participant ref="group-sitetwoPublisher"/>
</if>
<!-- will loop if rejected -->
<if test="${field:action} == reject">
<revision-round/>
</if>
<log message="activate: ${field:action}"/>
<!-- if the last action was proceed: activate-->
<if test="${field:action} == proceed">
<activate/>
</if>
</sequence>
<process-definition name="revision-round">
<loop>
<while test="${field:action} == reject"/>
<to-editor/>
<if test="${field:action} != proceed">
<break/>
</if>
<to-publisher/>
</loop>
</process-definition>
<process-definition name="to-publisher">
<if test="${field:activator} == siteone">
<participant ref="group-siteonePublisher"/>
</if>
<if test="${field:activator} == sitetwo">
<participant ref="group-sitetwoPublisher"/>
</if>
</process-definition>
<process-definition name="to-editor">
<sequence>
<!-- assign back to the user who launched the activation -->
<set field="assignTo" field-value="activator"/>
<participant ref="group-editor"/>
</sequence>
</process-definition>
<process-definition name="activate">
<sequence>
<!-- wait if scheduled -->
<if>
<defined field-value="startDate"/>
<sleep until="${f:startDate}"/>
</if>
<!-- activate -->
<participant ref="command-activate"/>
<if>
<defined field-value="exception"/>
<!-- restart again -->
<activation/>
<break/>
</if>
<!-- deactivate (if scheduled)-->
<if>
<defined field-value="endDate"/>
<sequence>
<sleep until="${f:endDate}"/>
<participant ref="command-deactivate"/>
</sequence>
</if>
</sequence>
</process-definition>
</process-definition>
Then I tried to put this xml into the WEB-INF/classes. But that didn't
change anything. So I just changed the original XML in the jar-File, wich
worked.
Thanks for help and I hope this might help others.
MagMan
Magnolia - User mailing list wrote:
>
>>> 1.: I don't know where to find the xml to edit.
>
> In 3.0 multiple workflows are supported only in EE, but you find the
> xml in the resources of the workflow module.
>
> In 3.1 CE supports multiple definitions and multiple uploads too
>
>>> 2.: Is there a documentation about how to edit the xml for the first
>>> solution?
>
> See openwfe language documentation found at there homepage. The
> workitem has the field path where set.
>
>>> 3.: I read that the workflow upload is no more in the comunity
>>> edition. So
>>> if point 1 and 2 are solved how can I replace the workflow?
>
> Put the xml to the WEB-INF/classes directory
>
>>>
>>> Thank you for help,
>>>
>>> MagMan
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/inbox-multiple-
>> site-workflow-problem-tf3786308.html#a10780018
>> Sent from the Magnolia - User mailing list archive at Nabble.com.
>>
>>
>> ----------------------------------------------------------------
>> for list details see
>> http://documentation.magnolia.info/docs/en/editor/stayupdated.html
>> ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/docs/en/editor/stayupdated.html
> ----------------------------------------------------------------
>
>
--
View this message in context:
http://www.nabble.com/inbox-multiple-site-workflow-problem-tf3786308.html#a10805513
Sent from the Magnolia - User mailing list archive at Nabble.com.
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
