<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Boundary Timer and ISO 8601 usage in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131609#M92494</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;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!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2: no, the processdefinition is cached…&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3: the java api?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;And why do you need to set it for debugging purposes?&amp;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…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 08 Dec 2012 09:55:58 GMT</pubDate>
    <dc:creator>ronald_van_kuij</dc:creator>
    <dc:date>2012-12-08T09:55:58Z</dc:date>
    <item>
      <title>Boundary Timer and ISO 8601 usage</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131608#M92493</link>
      <description>I have a user task with a boundary timer attached. The boundary timer uses a process variable to set the time/date as follows:&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;userTask id="waitTask" name="Wait for Timer Elapse" activiti:assignee="system"&amp;gt;&amp;lt;/userTask&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;boundaryEvent id="boundaryDailyTimer" name="Daily Task Boun</description>
      <pubDate>Fri, 07 Dec 2012 18:05:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131608#M92493</guid>
      <dc:creator>jayehsea</dc:creator>
      <dc:date>2012-12-07T18:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Timer and ISO 8601 usage</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131609#M92494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;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!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2: no, the processdefinition is cached…&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3: the java api?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;And why do you need to set it for debugging purposes?&amp;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…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Dec 2012 09:55:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-timer-and-iso-8601-usage/m-p/131609#M92494</guid>
      <dc:creator>ronald_van_kuij</dc:creator>
      <dc:date>2012-12-08T09:55:58Z</dc:date>
    </item>
  </channel>
</rss>

