AnsweredAssumed Answered

fire timers in advanced worflow problem

Question asked by haroldvera on Apr 3, 2009
I have a problema with alfresco advanced workflow.

my alfresco version is:
version.major=3
version.minor=0
version.revision=0
version.label=Stable

When moving a workflow with a timer declared as described below, the workflow
advances to the next activity, but the WebClient remains to be found in the previous state (even
refresh the page and restore the server), even if the next activity is a task (task-node, task), activity appears duplicated
with the old state and the new.

my example workflow is:

<?xml version="1.0" encoding="UTF-8"?>

<process-definition  xmlns="urn:jbpm.org:jpdl-3.1"  name="exwf:exUI">

    <swimlane name="initiator"/>
   
   <start-state name="start">
       <task name="exwf:submitStartTask" swimlane="initiator"/>
      <transition to="notifyAdmisibilidadState"></transition>
   </start-state>

   
   <task-node name="notifyAdmisibilidadState">
     <task name="exwf:submitWaitTask"  swimlane="initiator" >
         <timer name="thirdPartyTimer" duedate="15 seconds" transition="a cualquiera">
            <!– action class="cl.gov.subtrans.bpm.ExecuteTransition"/–>
            <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
            <runas>admin</runas>
             <script>
                   {
                    logger.log("timer actived");
                   
                   }
             </script>
             </action>
            
          </timer>
      </task>
      <transition  name="Termina" to="end"/>
      <transition to="cualquiera" name="a cualquiera">
         <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
              <script>
                 logger.log("cualquiera");
              </script>
          </action>
      </transition>
   </task-node>

   <task-node name="cualquiera">
       <task name="exwf:submitCualquieraTask" swimlane="initiator"/>
      <transition to="end"></transition>
   </task-node>

   <end-state name="end"></end-state>


</process-definition>

Outcomes