<?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: Escalation functionality in activiti in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/escalation-functionality-in-activiti/m-p/255090#M208220</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a boundary event is the correct element for a feature like this - to be more precise, a timer boundary event. When a certain amount of time has passed (the timer duration), the timer fires and can either cause an additional execution branch to form (escalation parallel with user task) or cancel the current task and proceed to a different one (escalation supercedes user task).The &lt;/SPAN&gt;&lt;A href="http://activiti.org/userguide/index.html" rel="nofollow noopener noreferrer"&gt;Activiti user guide&lt;/A&gt;&lt;SPAN&gt; has a pretty good documentation on it. How a subsequent email is to be sent depends on your choice of escalation style - in a parallel escalation you could choose a sequenceflow from the boundary event to an end event, and put an execution script listener on the sequence flow to actually send the mail.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 16 Jun 2012 12:25:53 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2012-06-16T12:25:53Z</dc:date>
    <item>
      <title>Escalation functionality in activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/escalation-functionality-in-activiti/m-p/255089#M208219</link>
      <description>Hi,I am working on creating an advanced workflow with Activiti.One of my requirement is that - if a user has not completed the assigned task to him in X days, I need to send an escalation email.I read about boundaryevent but didn't get much idea from it.Could anyone please help me how can I achieve</description>
      <pubDate>Wed, 13 Jun 2012 13:14:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/escalation-functionality-in-activiti/m-p/255089#M208219</guid>
      <dc:creator>romschn</dc:creator>
      <dc:date>2012-06-13T13:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: Escalation functionality in activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/escalation-functionality-in-activiti/m-p/255090#M208220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a boundary event is the correct element for a feature like this - to be more precise, a timer boundary event. When a certain amount of time has passed (the timer duration), the timer fires and can either cause an additional execution branch to form (escalation parallel with user task) or cancel the current task and proceed to a different one (escalation supercedes user task).The &lt;/SPAN&gt;&lt;A href="http://activiti.org/userguide/index.html" rel="nofollow noopener noreferrer"&gt;Activiti user guide&lt;/A&gt;&lt;SPAN&gt; has a pretty good documentation on it. How a subsequent email is to be sent depends on your choice of escalation style - in a parallel escalation you could choose a sequenceflow from the boundary event to an end event, and put an execution script listener on the sequence flow to actually send the mail.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 16 Jun 2012 12:25:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/escalation-functionality-in-activiti/m-p/255090#M208220</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2012-06-16T12:25:53Z</dc:date>
    </item>
  </channel>
</rss>

