<?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: Activiti process result to queue in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-process-result-to-queue/m-p/202986#M156116</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yeah, my first thought was to make it a task and make that async … but I agree it's not the nicest to have that in your process definition.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You could look into creating a custom job type (like we now have for the async jobs and the timer jobs) that executes your custom logic when it's picked up. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think you'll have to choose between rolling back or storing the information somewhere intermediary (but not being pub/sub anymore)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Nov 2015 11:50:49 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2015-11-03T11:50:49Z</dc:date>
    <item>
      <title>Activiti process result to queue</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-process-result-to-queue/m-p/202985#M156115</link>
      <description>Hi guys,we implemented pooling of processes in Activiti, now we are doing calls every 20s to get completed processes at that time. Recently we decided to changed that behavior to pub-sub. Basically when Activiti process is finished the same data as result from "/query/historic-process-instances" is</description>
      <pubDate>Wed, 28 Oct 2015 16:39:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-process-result-to-queue/m-p/202985#M156115</guid>
      <dc:creator>tj1</dc:creator>
      <dc:date>2015-10-28T16:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti process result to queue</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-process-result-to-queue/m-p/202986#M156116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yeah, my first thought was to make it a task and make that async … but I agree it's not the nicest to have that in your process definition.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You could look into creating a custom job type (like we now have for the async jobs and the timer jobs) that executes your custom logic when it's picked up. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think you'll have to choose between rolling back or storing the information somewhere intermediary (but not being pub/sub anymore)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Nov 2015 11:50:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-process-result-to-queue/m-p/202986#M156116</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2015-11-03T11:50:49Z</dc:date>
    </item>
  </channel>
</rss>

