<?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: Jobs and long running tasks in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-long-running-tasks/m-p/212538#M165668</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Raghavan,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Async behaviour description &lt;/SPAN&gt;&lt;A href="http://activiti.org/userguide/index.html#bpmnConcurrencyAndTransactions" rel="nofollow noopener noreferrer"&gt;http://activiti.org/userguide/index.html#bpmnConcurrencyAndTransactions&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In your case I would you messages/signals instead of async (which is not meant to do this job). The scenario could be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;process triggers long running task (do not wait on the end of the task) and waits in the message/signal intermediate catching event on the response from the long running task. When long running task is finished, it sends the message/signal and process instance can continue in the process execution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Jul 2016 07:02:06 GMT</pubDate>
    <dc:creator>martin_grofcik</dc:creator>
    <dc:date>2016-07-13T07:02:06Z</dc:date>
    <item>
      <title>Jobs and long running tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-long-running-tasks/m-p/212537#M165667</link>
      <description>I have a situation and it's quite likely that I don't properly understand how asynchronous tasks work.&amp;nbsp; Here's a brief description:1. Our workflows include several long running tasks (order of hours) that are Java Service tasks.&amp;nbsp; These tasks make an asynchronous call to an external system and poll t</description>
      <pubDate>Thu, 30 Jun 2016 21:06:20 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobs-and-long-running-tasks/m-p/212537#M165667</guid>
      <dc:creator>krraghavan</dc:creator>
      <dc:date>2016-06-30T21:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: Jobs and long running tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobs-and-long-running-tasks/m-p/212538#M165668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Raghavan,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Async behaviour description &lt;/SPAN&gt;&lt;A href="http://activiti.org/userguide/index.html#bpmnConcurrencyAndTransactions" rel="nofollow noopener noreferrer"&gt;http://activiti.org/userguide/index.html#bpmnConcurrencyAndTransactions&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In your case I would you messages/signals instead of async (which is not meant to do this job). The scenario could be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;process triggers long running task (do not wait on the end of the task) and waits in the message/signal intermediate catching event on the response from the long running task. When long running task is finished, it sends the message/signal and process instance can continue in the process execution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Jul 2016 07:02:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobs-and-long-running-tasks/m-p/212538#M165668</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2016-07-13T07:02:06Z</dc:date>
    </item>
  </channel>
</rss>

