<?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: Interflow Communication in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155610#M109929</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Any chance of using a single process with a sub-process/call-activity? This might make things a bit more stable, although not 100% this would fit in the usecase you're trying to reach.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Try the async suggestion. If that doesn't work, maybe a detailed explanation of your use case might help…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jan 2014 15:21:05 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2014-01-15T15:21:05Z</dc:date>
    <item>
      <title>Interflow Communication</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155606#M109925</link>
      <description>We have two flows that collaborate with each other. We have one&amp;nbsp; process (Flow A) that progresses to a certain point and thenwaits for a message from Flow B.&amp;nbsp; Flow B sends a message to Flow A and then waits for a message back from Flow A.An example is diagramed below.Flow A:&amp;nbsp;&amp;nbsp;&amp;nbsp; Start ———————–&amp;gt;&amp;nbsp;&amp;nbsp;</description>
      <pubDate>Tue, 14 Jan 2014 15:23:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155606#M109925</guid>
      <dc:creator>mikebrown01</dc:creator>
      <dc:date>2014-01-14T15:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: Interflow Communication</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155607#M109926</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Here is a link to an image for the flow since I failed at formatting in the original post.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;img&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://s3.amazonaws.com/stuff.virtualbrown.com/FlowCom.2jpg" rel="nofollow noopener noreferrer"&gt;https://s3.amazonaws.com/stuff.virtualbrown.com/FlowCom.2jpg&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/url&amp;gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jan 2014 16:00:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155607#M109926</guid>
      <dc:creator>mikebrown01</dc:creator>
      <dc:date>2014-01-14T16:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: Interflow Communication</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155608#M109927</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The main issue is that your processes do NOT get persisted until they reach a wait-state. Since you're using script-tasks, these well be executed synchronously and the actual commit will happen later on. You can try making the script-tasks asynchronous, so the process-state is persisted right before they are executed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another question I have is about the start of the processes. In what order are they started, and how are they started?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jan 2014 08:59:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155608#M109927</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2014-01-15T08:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: Interflow Communication</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155609#M109928</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;"The main issue is that your processes do NOT get persisted until they reach a wait-state"&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ok. I thought that might be the issue here. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;"You can try making the script-tasks asynchronous, so the process-state is persisted right before they are executed."&amp;lt;/i&amp;gt;&amp;lt;/b&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ok. Will give this a try.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;"Another question I have is about the start of the processes. In what order are they started, and how are they started?"&amp;lt;/i&amp;gt;&amp;lt;/b&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Flow A is started before Flow B.&amp;nbsp;&amp;nbsp; Both flows are started programatically using runtimeService.startProcessInstanceByKey(…);&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jan 2014 15:13:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155609#M109928</guid>
      <dc:creator>mikebrown01</dc:creator>
      <dc:date>2014-01-15T15:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: Interflow Communication</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155610#M109929</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Any chance of using a single process with a sub-process/call-activity? This might make things a bit more stable, although not 100% this would fit in the usecase you're trying to reach.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Try the async suggestion. If that doesn't work, maybe a detailed explanation of your use case might help…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jan 2014 15:21:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155610#M109929</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2014-01-15T15:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: Interflow Communication</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155611#M109930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok setting the Task as Async is working!&amp;nbsp; I had a little bit of a problem getting it to work because the JobExecutor was turned off in the config file :0&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jan 2014 14:20:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/interflow-communication/m-p/155611#M109930</guid>
      <dc:creator>mikebrown01</dc:creator>
      <dc:date>2014-01-16T14:20:04Z</dc:date>
    </item>
  </channel>
</rss>

