<?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: Keep track of Sequence Flows in History in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62906#M39340</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;In a sequence flow execution listener the input parameter can be ExecutionListenerExecution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;From there you can get the transition that will be taken.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've an example about this in chapter 6 of the Activiti in Action book.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Jan 2012 08:22:11 GMT</pubDate>
    <dc:creator>trademak</dc:creator>
    <dc:date>2012-01-09T08:22:11Z</dc:date>
    <item>
      <title>Keep track of Sequence Flows in History</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62903#M39337</link>
      <description>Hi,I would like to keep track of sequence flows in history. The current implementation does not keep sequence flow history, I mean which activity instance comes before which one in the execution. A history table consisting of 3 columns will be sufficient: primary-key column, source-activity-ref colu</description>
      <pubDate>Thu, 05 Jan 2012 08:42:20 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62903#M39337</guid>
      <dc:creator>ayzegul</dc:creator>
      <dc:date>2012-01-05T08:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Keep track of Sequence Flows in History</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62904#M39338</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;Why did the execution listener not work?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;When you have the history of tasks, can't you predict the sequence flow history?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 18:20:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62904#M39338</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2012-01-05T18:20:46Z</dc:date>
    </item>
    <item>
      <title>Re: Keep track of Sequence Flows in History</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62905#M39339</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;ExecutionListener doesn't work because the parameter object DelegateExecution does not contain any api methods to get the transition being taken, or the source and target activity definitions. I may try to cast it to what the engine sends as an implementation, but is this approach safe? What if the implementation class changes in the future? Is it safe to assume that the engine will send the same implementation for each activity type and flow? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Aysegul.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 06:42:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62905#M39339</guid>
      <dc:creator>ayzegul</dc:creator>
      <dc:date>2012-01-06T06:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: Keep track of Sequence Flows in History</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62906#M39340</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;In a sequence flow execution listener the input parameter can be ExecutionListenerExecution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;From there you can get the transition that will be taken.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've an example about this in chapter 6 of the Activiti in Action book.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2012 08:22:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62906#M39340</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2012-01-09T08:22:11Z</dc:date>
    </item>
    <item>
      <title>Re: Keep track of Sequence Flows in History</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62907#M39341</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;I had an similar issue, but partially solved with ExecutionListener.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;See &lt;/SPAN&gt;&lt;A href="http://forums.activiti.org/comment/23761#comment-23761" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/comment/23761#comment-23761&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 May 2014 00:13:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/keep-track-of-sequence-flows-in-history/m-p/62907#M39341</guid>
      <dc:creator>gualberto</dc:creator>
      <dc:date>2014-05-27T00:13:30Z</dc:date>
    </item>
  </channel>
</rss>

