Timer fires in task, task gets duplicated

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

eleaese

We're facing a problem with timers on advanced workflows definitions. Our Alfresco version is 3.0.0 Stable.

Regarding the problem. When changing workflow state with a timer (please see processdefinition below) the workflow advances to the next activity. But, when the assigne logs into webclient the task remains assigned to him/her. It seems the task remains to be bound in the previous state (even after refreshing the page, even after server restart). Next activity is a task (task-node, task), and activity appears duplicated, with the previous and present state.

Please let me know what we are doing wrong.

Process definition 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="notifyAdmisibilityState"></transition>
   </start-state>

   <task-node name="notifyAdmisibilityState">
      <task name="exwf:submitWaitTask" swimlane="initiator" >
         <timer name="thirdPartyTimer" duedate="15 seconds" transition="toSomebody">
            <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
               <runas>admin</runas>
               <script>{ logger.log("timer fired"); }</script>      
            </action>
         </timer>
      </task>
      <transition name="toEnd" to="end"/>
      <transition to="anybody" name="toSomebody">
         <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
            <script>{logger.log("anybody"); }</script>
         </action>
      </transition>
   </task-node>

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

   <end-state name="end"></end-state>
</process-definition>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

florent_soulier

Hi,

This post is pretty old, but I am currently facing the same problem: transition followed by timers in processDefinition.xml leads to the creation of the new JBPM task, but not the deletion of the old one. So the old assignee still see his task, unfortunately.

The only difference with the case described in 2009 is that we use Alfresco 3.2r.

Did you solve this problem? In case yes, how did you do?

Thanks.