Jürgen Ragaller schrieb:
> 
> Hi
> 
> 
> We added a transition to the workflow.xml to give the reviewers the
> possibility to publish in one step:
> 
>   <transition source="authoring" destination="live">
>     <event id="publish"/>
>     <condition
> class="org.apache.lenya.cms.workflow.RoleCondition">review</condition>
>     <assign variable="is_live" value="true"/>
>   </transition>
> 
> 
> Two problems arise:
> 
> 1) The notification of the submitter checkbox in the publishing step is
> present - and if checked, it throws an exception (which makes sense,
> because there is no submitter). Is it possible to introduce a check,
> that the checkbox is only displayed if the document has the state
> «review» (and a submitter exists)?

Sure - you should probably put the code in the usecase handler class:

  Workfloable workfloable = WorkflowUtil.getWorkfloable(
      this.manager, getSession(), getLogger(), doc);
  String state = workflowable.getLatestVersion().getState();
  setParameter("state", state);

In your view you can show or hide the checkbox accordingly:

<jx:if test="${usecase.getParameter('state').equals('review')}">
  ...
</jx:if>


> 2) The update of the lucene index of a document (in workflow state
> authoring | live) fails if the modified document is published in one
> step (from authoring|live to live). If the publish procedure of the
> updated document is done in two steps (submit - publish), the content is
> (re)-indexed.

Does it throw an exception, or does it just not update the index?
Would you mind filing a bug and, if possible, attach a patch which
allows to reproduce the problem? TIA!


> Do I have to change other files - not just workflow.xml?

workflow.xml should be sufficient.

-- Andreas

> In the meantime I let the reviewers perform the submit step.
> 
> 
> Thank you for help!
> 
> 
> Jürgen


-- 
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to