<?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: removing timer job events for a process in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123340#M86860</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I've answered a similar question recently on the forum. Instead of working with the gateways, create a sub-process around the part of your process you want to have the "timer" behavior for. Instead of adding the timer INSIDE the sub-process, add it as a boundary-event on the sub-process.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In case all tasks are complete (in the subprocess) before the timer has fired, the subprocess-scope will be destroyed and the boundary-event will be removed. If you have an outgoing flow from the subprocess to a process end-event, the process will be ended after the last task is finished. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the timer fires first, you can either send a reminder (but leave the other tasks as they are) by using cancelActivity="true" or terminate all tasks in the sub-process by using cancelActivity="true" on the boundary timer event.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jul 2013 12:09:35 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2013-07-17T12:09:35Z</dc:date>
    <item>
      <title>removing timer job events for a process</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123337#M86857</link>
      <description>Hi,&amp;nbsp; I have used the inclusive gateway in my process, created four outgoing sequences with the help of inclusive gateway and this outgoing sequences will execute in all scenarios. I have created a human task in one of the sequence flow and intermediate timer catching events in other sequences. So, w</description>
      <pubDate>Mon, 15 Jul 2013 13:01:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123337#M86857</guid>
      <dc:creator>ganeshr</dc:creator>
      <dc:date>2013-07-15T13:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: removing timer job events for a process</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123338#M86858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;adding bpm text file, as unable to paste in description&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jul 2013 13:03:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123338#M86858</guid>
      <dc:creator>ganeshr</dc:creator>
      <dc:date>2013-07-15T13:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: removing timer job events for a process</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123339#M86859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This might help, although I've never tested it myself.&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://www.activiti.org/userguide/#api.services.suspend" rel="nofollow noopener noreferrer"&gt;http://www.activiti.org/userguide/#api.services.suspend&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;It's also possible to suspend a process instance. When suspended, the process cannot be continued (e.g. completing a task throws an exception) and no jobs (such as timers) will executed. Suspending a process instance can be done by calling the runtimeService.suspendProcessInstance method. Activating the process instance again is done by calling the runtimeService.activateProcessInstanceXXX methods.&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 09:44:40 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123339#M86859</guid>
      <dc:creator>one87</dc:creator>
      <dc:date>2013-07-16T09:44:40Z</dc:date>
    </item>
    <item>
      <title>Re: removing timer job events for a process</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123340#M86860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I've answered a similar question recently on the forum. Instead of working with the gateways, create a sub-process around the part of your process you want to have the "timer" behavior for. Instead of adding the timer INSIDE the sub-process, add it as a boundary-event on the sub-process.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In case all tasks are complete (in the subprocess) before the timer has fired, the subprocess-scope will be destroyed and the boundary-event will be removed. If you have an outgoing flow from the subprocess to a process end-event, the process will be ended after the last task is finished. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the timer fires first, you can either send a reminder (but leave the other tasks as they are) by using cancelActivity="true" or terminate all tasks in the sub-process by using cancelActivity="true" on the boundary timer event.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jul 2013 12:09:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-timer-job-events-for-a-process/m-p/123340#M86860</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-07-17T12:09:35Z</dc:date>
    </item>
  </channel>
</rss>

