[MAGNOLIA-2262] Workflow upload Created: 15/Jul/08  Updated: 20/Jan/09  Resolved: 20/Jan/09

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.6-m3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sylvain Balbous Assignee: Boris Kraft
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-2565 Support multiple lines content in Tree Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When uploading a process definition (see below), upload confirmed ok, xml viewable by clicking the link in the Flow List.
Then go to Configuration/modules/workflow/config/flows/activation, value only contain the first line of the xml
Get back to the workflow upload screen, click on the Flow list then :

Erreur d'analyse XML : aucun élément trouvé
Emplacement : http://localhost:9190/magnoliaAuthor/.magnolia/pages/flows.html?command=showFlow&flowName=activation
Numéro de ligne 1, Colonne 57 :<process-definition name="activation" revision="j0.0.2">
--------------------------------------------------------^

This error occured with a fresh install, I believed it was a setup pb. No way to make the WFE running.

<process-definition name="activation" revision="j0.0.2">
<sequence>
<set field="activator" field-value="userName"/>
<!-- go to publisher first -->
<to-publisher/>
<!-- 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>
<equals field-value="action" other-value="reject"/>
</while>
<to-editor/>
<if test="${field:action} != proceed">
<break/>
</if>
<to-publisher/>
</loop>
</process-definition>
<process-definition name="to-publisher">
<sequence>
<!--

uncomment if you like to use an email notification

-->
<!--

<set field="mailTo" value="group-publishers"/>
<set field="mailTemplate" value="workflowNotification"/>
<participant ref="command-sendMail"/>

-->
<!--
reset the assignTo field so the editor no longers see the workflow item
-->
<unset field="assignTo"/>
<participant ref="group-publishers"/>
</sequence>
</process-definition>
<process-definition name="to-editor">
<sequence>
<!--
assign back to the user who launched the activation
-->
<set field="assignTo" field-value="activator"/>
<!--

uncomment if you like to use an email notification

-->
<!--

<set field="mailTo" value="user-${f:assignTo}"/>
<set field="mailTemplate" value="workflowNotification"/>
<participant ref="command-sendMail"/>

-->
<participant ref="group-editors"/>
</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>



 Comments   
Comment by Magnolia International [ 20/Jan/09 ]

Sorry for the late reply. Unless I'm mistaken, what happened is that when you went "to Configuration/modules/workflow/config/flows/activation" and noticed that the "value only contained the first line of the xml", you probably hit the enter key.. which saved the new value as is, i.e only saving its first line.
This is a current limitation of our tree, see MAGNOLIA-2565 for improvements.

Generated at Mon Feb 12 03:34:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.