<?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 Removing subscribed boundary-signal-events of previous process-definition on process-model deployment in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230764#M183894</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;By deploying process-model, all signal-event (including start, boundary, and intermediate-catching) subscriptions of the previous process-definition, will be removed. But it only makes sense for start-signal-events, because it's not desired to start process from previous process-definitions. But, about boundary and intermediate-catching signal-events, removing subscriptions does not make any sense; Because&amp;nbsp; in case of throwing signals, it's desired boundary and intermediate-catching signal-events of processes of previous process-definition, catch it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is it a bug or something else?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Here is the method which removes all signal-events of previous process-definition in BpmnDeployer class:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="language-java line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt;protected void removeObsoleteSignalEventSubScription(ProcessDefinitionEntity processDefinition, ProcessDefinitionEntity latestProcessDefinition) {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; // remove all subscriptions for the previous version&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; if(latestProcessDefinition != null) {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CommandContext commandContext = Context.getCommandContext();&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; List&amp;lt;EventSubscriptionEntity&amp;gt; subscriptionsToDelete = commandContext&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .getEventSubscriptionEntityManager()&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .findEventSubscriptionsByConfiguration(SignalEventHandler.EVENT_HANDLER_TYPE, latestProcessDefinition.getId(), latestProcessDefinition.getTenantId());&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for (EventSubscriptionEntity eventSubscriptionEntity : subscriptionsToDelete) {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; eventSubscriptionEntity.delete();&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;BR /&gt; }&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Mar 2016 10:28:54 GMT</pubDate>
    <dc:creator>mf</dc:creator>
    <dc:date>2016-03-16T10:28:54Z</dc:date>
    <item>
      <title>Removing subscribed boundary-signal-events of previous process-definition on process-model deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230764#M183894</link>
      <description>Hi,By deploying process-model, all signal-event (including start, boundary, and intermediate-catching) subscriptions of the previous process-definition, will be removed. But it only makes sense for start-signal-events, because it's not desired to start process from previous process-definitions. But,</description>
      <pubDate>Wed, 16 Mar 2016 10:28:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230764#M183894</guid>
      <dc:creator>mf</dc:creator>
      <dc:date>2016-03-16T10:28:54Z</dc:date>
    </item>
    <item>
      <title>Re: Removing subscribed boundary-signal-events of previous process-definition on process-model deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230765#M183895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Which activiti version do you use?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(I tried to reproduce the issue with the activiti 6)&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, 16 Mar 2016 13:10:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230765#M183895</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2016-03-16T13:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Removing subscribed boundary-signal-events of previous process-definition on process-model deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230766#M183896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;activiti 5.19&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Mar 2016 13:36:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230766#M183896</guid>
      <dc:creator>mf</dc:creator>
      <dc:date>2016-03-16T13:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: Removing subscribed boundary-signal-events of previous process-definition on process-model deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230767#M183897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think it's fixed, but not released yet: &lt;/SPAN&gt;&lt;A href="https://github.com/Activiti/Activiti/commit/5ffac043e8d25a5940593038f2da2bcad0cf6592" rel="nofollow noopener noreferrer"&gt;https://github.com/Activiti/Activiti/commit/5ffac043e8d25a5940593038f2da2bcad0cf6592&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Mar 2016 14:53:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230767#M183897</guid>
      <dc:creator>mf</dc:creator>
      <dc:date>2016-03-16T14:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: Removing subscribed boundary-signal-events of previous process-definition on process-model deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230768#M183898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That is correct.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Mar 2016 13:48:32 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/removing-subscribed-boundary-signal-events-of-previous-process/m-p/230768#M183898</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-03-18T13:48:32Z</dc:date>
    </item>
  </channel>
</rss>

