topic Boundary Timer and ISO 8601 usage in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131608#M92493 <HTML><HEAD></HEAD><BODY><SPAN>I have a user task with a boundary timer attached. The boundary timer uses a process variable to set the time/date as follows:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />&nbsp;&nbsp;&nbsp; &lt;userTask id="waitTask" name="Wait for Timer Elapse" activiti:assignee="system"&gt;&lt;/userTask&gt;<BR />&nbsp;&nbsp;&nbsp; &lt;boundaryEvent id="boundaryDailyTimer" name="Daily Task Boundary Timer" cancelActivity="true" attachedToRef="waitTask"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;timerEventDefinition&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;timeDate&gt;${nextRunTime}&lt;/timeDate&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/timerEventDefinition&gt;<BR />&nbsp;&nbsp;&nbsp; &lt;/boundaryEvent&gt;<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>I progammatically set the value of nextRunTime to an ISO 8601 date/time format, such as '2012-12-07T10:47:00'. My process is successfully using the value to trigger the expected action within my business process. All is good.</SPAN><BR /><BR /><SPAN>For debugging purposes I needed to change the value of the nextRunTime process variable, so I could trigger the business process when I wanted. So I used SQL to modify the value in the database as follows:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />update act_ru_variable set text_='2012-12-07T22:47:00' where text_='2012-12-07T10:47:00';<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>This updated the process variable in the database as expected. The application was NOT running while I made this update to the database. I restarted my application, and was surprised to find that the process using the updated process variable still fired at 10:47 AM, even though my application log showed that the nextRunTime variable value was indeed set to '2012-12-07T22:47:00' (or 10:47 PM).</SPAN><BR /><BR /><SPAN>I have other process executions that fire correctly for times such as '2012-12-07T22:47:00', at 10:47 PM. So it appears the 24 hour clock is honored by the boundary timer. I don't understand why my variable modifications were not honored by the processes.</SPAN><BR /><BR /><SPAN>So I have a couple questions:</SPAN><BR /><BR /><SPAN>1) Will using SQL to modify process variables in act_ru_variable have the desired effect on a process instance using that variable?</SPAN><BR /><SPAN>2) Are process variables maintained by the Activiti engine in another location, such as cache?</SPAN><BR /><SPAN>3) Is there another way that I should be modifying process variables stored in act_ru_variable table? Will this change be honored by the Activiti engine?</SPAN><BR /><BR /><SPAN>Thanks for helping me understand the workings of Activiti. </SPAN><BR /><SPAN>Jim</SPAN></BODY></HTML> Fri, 07 Dec 2012 18:05:59 GMT jayehsea 2012-12-07T18:05:59Z Boundary Timer and ISO 8601 usage https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131608#M92493 I have a user task with a boundary timer attached. The boundary timer uses a process variable to set the time/date as follows:&nbsp;&nbsp;&nbsp; &lt;userTask id="waitTask" name="Wait for Timer Elapse" activiti:assignee="system"&gt;&lt;/userTask&gt;&nbsp;&nbsp;&nbsp; &lt;boundaryEvent id="boundaryDailyTimer" name="Daily Task Boun Fri, 07 Dec 2012 18:05:59 GMT https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131608#M92493 jayehsea 2012-12-07T18:05:59Z Re: Boundary Timer and ISO 8601 usage https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131609#M92494 <HTML><HEAD></HEAD><BODY><SPAN>1: If the engine was not running, I would suspect it to be taken into account… Unless a job needing this date was already created!</SPAN><BR /><SPAN>2: no, the processdefinition is cached…</SPAN><BR /><SPAN>3: the java api?</SPAN><BR /><BR /><SPAN>And why do you need to set it for debugging purposes?&nbsp; Look at the activiti testcases, there is a clockutil (not sure if it is actually called that way) that can be used to manipulate the actual time seeen by the engine…</SPAN></BODY></HTML> Sat, 08 Dec 2012 09:55:58 GMT https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131609#M92494 ronald_van_kuij 2012-12-08T09:55:58Z