<?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 6: Dynamic activityId and triggering a receive task in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-6-dynamic-activityid-and-triggering-a-receive-task/m-p/218066#M171196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1. Yes, you can use an ExecutionQuery, which will return you executions with a certain activityId. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You can introspect the process definition structure (and thus determine if it's a receive task) using the ProcessDefinitionutil.getBpmnModel(processDefinitionId) method.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Correct. 'signal' was a bad name, which has a specific meaning in BPMN 2.0, thus we renamed it to trigger to avoid confusion.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3.Depends on where you call it, but yes, if the process has async pieces then that is probably needed. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We will add a feature soon that will solve that problem: it will be possible to send out an event that is only sent when the transaction has finished and the execution can be triggered.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Dec 2015 20:07:25 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2015-12-08T20:07:25Z</dc:date>
    <item>
      <title>Activiti 6: Dynamic activityId and triggering a receive task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-6-dynamic-activityid-and-triggering-a-receive-task/m-p/218065#M171195</link>
      <description>So, struggling a bit to get this working as expected We have multiple processes for different work flows, some contain either 1 or more receiveTasks&amp;lt;receiveTask id="receivetask1" name="Receive Task"&amp;gt;&amp;lt;/receiveTask&amp;gt;‍‍‍ The test process we created : [startEvent-&amp;gt;scriptTask-&amp;gt; receiveTa</description>
      <pubDate>Fri, 04 Dec 2015 17:59:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-6-dynamic-activityid-and-triggering-a-receive-task/m-p/218065#M171195</guid>
      <dc:creator>donovanmuller</dc:creator>
      <dc:date>2015-12-04T17:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti 6: Dynamic activityId and triggering a receive task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-6-dynamic-activityid-and-triggering-a-receive-task/m-p/218066#M171196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1. Yes, you can use an ExecutionQuery, which will return you executions with a certain activityId. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You can introspect the process definition structure (and thus determine if it's a receive task) using the ProcessDefinitionutil.getBpmnModel(processDefinitionId) method.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Correct. 'signal' was a bad name, which has a specific meaning in BPMN 2.0, thus we renamed it to trigger to avoid confusion.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3.Depends on where you call it, but yes, if the process has async pieces then that is probably needed. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We will add a feature soon that will solve that problem: it will be possible to send out an event that is only sent when the transaction has finished and the execution can be triggered.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2015 20:07:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-6-dynamic-activityid-and-triggering-a-receive-task/m-p/218066#M171196</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2015-12-08T20:07:25Z</dc:date>
    </item>
  </channel>
</rss>

