topic Re: ScriptTask + TimerBoundaryEvent in Alfresco Archive

ScriptTask + TimerBoundaryEvent

soma — Wed, 15 Jan 2014 14:39:44 GMT

Hi,I have a simple Activiti diagram with a ScriptTask and a TimerBoundaryEvent.You can see my diagram if you open this url: http://s22.postimg.org/ueb4mrsyp/My_Process.pngMy first task is a ScriptEvent task. In this task (I use JavaScript) I would like to set a date variable. It represents the start

Re: ScriptTask + TimerBoundaryEvent

frederikherema1 — Wed, 15 Jan 2014 15:15:45 GMT

the timeDate expects an ISO8601 date. You can also use the timeDuration-property instead and specify a duration. Eg. use "PT5H" to make the timer fire in 5hours of "P15D" to have the timer fire in 10 days.

Re: ScriptTask + TimerBoundaryEvent

soma — Wed, 15 Jan 2014 16:49:37 GMT

The timeDuration property is not fits to the requirements because:

(1) The timer event needs to appear x days after the workflow has been started to run.
and
(2) The timer event must not appear before the subprocess is done.

If the running time of the subprocess is longer then x days the timer event needs to appear immediately when the workflow is in the red point (please, have a look at my new image).

If the workflow reaches the red point before the x days then the timer needs to wait (start date + x days - now).

Image: http://s15.postimg.org/z5u5xx8bf/My_Process_02.png

In order to handle it I need to set dinamically the timeDate property. And I do not want to use java layer for this because somtimes the key user needs to modify the lenght of this time period (she redraw activiti diagram ) but they are not able to rebuild and redeploy the application.
Nevertheless the key users are able to modify and upload the new version of the workflow.

This is the reason why I would like to calculate the value of timeDate property via ScriptTask and I want to put Date variable to the context of the workflow instance.

Thx.

Re: ScriptTask + TimerBoundaryEvent

frederikherema1 — Thu, 16 Jan 2014 08:45:31 GMT

Okay, so you need to make the ScriptTask convert to an ISO-8601 date, that is used in the timeDate. You can, for example, create a util-class for this in java and expose it as a "bean" in the process-engine configuration and use it in your script. This way, no java-coding needs to be done when the time to wait is modified, only the script.

Re: ScriptTask + TimerBoundaryEvent

soma — Thu, 16 Jan 2014 10:51:35 GMT

Thanks for your help!

Re: ScriptTask + TimerBoundaryEvent

soma — Thu, 16 Jan 2014 11:25:39 GMT

Finaly I created an groovy script. It is working very well and it is just 3 rows and it is very easy:

<code>
<scriptTask id="scripttask1" name="Set timer variable, time limit = 2 months" scriptFormat="groovy" activiti:autoStoreVariables="true">
   <script>def d = new GregorianCalendar()
                 d.add(Calendar.MINUTE,3)
                 execution.setVariable("process_start_time", d.getTime().format("yyyy-MM-dd'T'HH:mmZ"))
</script>
</scriptTask>
</code>

And this is my timer code;
<code>
    <intermediateCatchEvent id="timerintermediatecatchevent1" name="TimerCatchEvent">
      <timerEventDefinition>
        <timeDate>${process_start_time}</timeDate>
      </timerEventDefinition>
    </intermediateCatchEvent>
</code>

Thanks for your inspiration!