<?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 Engine synchronous API in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-synchronous-api/m-p/175608#M128738</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;&amp;gt; want to control execution of individual Process steps based on calls from our Application logic.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sure, this is the default way of Activiti&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; a completely synchronous process in the BPM world&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, this is again the default in Activiti (timers are the exception).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Activiti used the calling thread to continue the process instance further.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 May 2014 09:05:26 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2014-05-30T09:05:26Z</dc:date>
    <item>
      <title>Activiti Engine synchronous API</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-synchronous-api/m-p/175607#M128737</link>
      <description>We are embedding Activiti Engine as a OSGi bundle inside our Application.Our Application wants to have fine grained control over Activiti Engine and want to control execution of individual Process steps based on calls from our Application logic.Is it possible to support this?A related question - is</description>
      <pubDate>Tue, 27 May 2014 17:44:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-synchronous-api/m-p/175607#M128737</guid>
      <dc:creator>arajwade</dc:creator>
      <dc:date>2014-05-27T17:44:53Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Engine synchronous API</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-synchronous-api/m-p/175608#M128738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;&amp;gt; want to control execution of individual Process steps based on calls from our Application logic.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sure, this is the default way of Activiti&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; a completely synchronous process in the BPM world&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, this is again the default in Activiti (timers are the exception).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Activiti used the calling thread to continue the process instance further.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 May 2014 09:05:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-synchronous-api/m-p/175608#M128738</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-05-30T09:05:26Z</dc:date>
    </item>
  </channel>
</rss>

