<?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: Boundary Events and cancel activity in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29347#M14986</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Mar 2011 08:06:09 GMT</pubDate>
    <dc:creator>jcosano</dc:creator>
    <dc:date>2011-03-04T08:06:09Z</dc:date>
    <item>
      <title>Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29340#M14979</link>
      <description>I see that now cancelActivity is working fine but…If i put cancelActivity to false, now, activity still in same state, but boundary event only is launched 1 time, My target is:I'll have an user Task that every day launch a mail if activity is not complete.Now, I have a cycle with cancelActivity true</description>
      <pubDate>Thu, 03 Mar 2011 12:03:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29340#M14979</guid>
      <dc:creator>jcosano</dc:creator>
      <dc:date>2011-03-03T12:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29341#M14980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;AFAIK, non-interupting boundry events aren't supported yet in activiti (cancelActivity=false). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a specific reason why the task-id (in case of your workaround, using flow that goos back in userTask after sending mail?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:24:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29341#M14980</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-03-04T07:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29342#M14981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In mail, I'll put a url, that opens this task…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If every day, task id changes (really is the same activity), I'm sure that someone will try to go to task with a old url (from a previous mail), and this url reference a task that not exists.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:29:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29342#M14981</guid>
      <dc:creator>jcosano</dc:creator>
      <dc:date>2011-03-04T07:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29343#M14982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I see,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is the link to the explore UI or an own UI? Maybe, as workaround, you can set unique key in process-variable and copy it into a task-variable when task is started (listener), and use this as ID in your link. The query for the task should be something like taskService.createTaskQuery().taskVariableValueEquals("firstTaskIdentifier", id).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I should check with Joram and Tom, but don't think there is any concrete planning for non-interuptive boundary event on the roadmap.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:33:34 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29343#M14982</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-03-04T07:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29344#M14983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm using Activiti Explorer…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;CODE&gt;&lt;A href="http://localhost:8080/activiti-explorer/start?taskId=119" rel="nofollow noopener noreferrer"&gt;http://localhost:8080/activiti-explorer/start?taskId=119&lt;/A&gt;, where 119 is the ID of the task with an associated form. &lt;/CODE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:44:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29344#M14983</guid>
      <dc:creator>jcosano</dc:creator>
      <dc:date>2011-03-04T07:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29345#M14984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Maybe we need a reminder option, configure as a listener maybe?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:47:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29345#M14984</guid>
      <dc:creator>jcosano</dc:creator>
      <dc:date>2011-03-04T07:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29346#M14985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;As a matter of fact, we're looking into (task) notifications this release. More details on that will folow.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 07:56:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29346#M14985</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-03-04T07:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29347#M14986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 08:06:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29347#M14986</guid>
      <dc:creator>jcosano</dc:creator>
      <dc:date>2011-03-04T08:06:09Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary Events and cancel activity</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29348#M14987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;non-interrupting events are indeed not yet supported. There is some code that could work, but it's not yet documented nor is it tested enough.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 15:57:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-events-and-cancel-activity/m-p/29348#M14987</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2011-03-04T15:57:43Z</dc:date>
    </item>
  </channel>
</rss>

