<?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 Technical and functional error management in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/technical-and-functional-error-management/m-p/182850#M135980</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;We are thinking about replacing our current BPM engine (old version of jBPM) by Activiti.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To do so, we plan to deploy a first workflow to see if that would be a viable solution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For example, for a task in the workflow calling a webservice:&lt;/SPAN&gt;&lt;BR /&gt;&lt;LI&gt;Technical errors: when webservice is unavailable, we would like that the task is retried every 5 minutes and fails after 10 attempts, going to an "error" task (same as described below, requiring manual action)&lt;/LI&gt;&lt;LI&gt;Functional errors: when webservice returns a 404 error code, we would like that the workflow goes to an "error" task where our support team could analyze the error and execute again the task that failed&lt;/LI&gt;&lt;BR /&gt;&lt;SPAN&gt;Do you have any ideas or advices on how we should do that properly with Activiti?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Jul 2015 10:15:57 GMT</pubDate>
    <dc:creator>miko2009</dc:creator>
    <dc:date>2015-07-08T10:15:57Z</dc:date>
    <item>
      <title>Technical and functional error management</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/technical-and-functional-error-management/m-p/182850#M135980</link>
      <description>Hello,We are thinking about replacing our current BPM engine (old version of jBPM) by Activiti.To do so, we plan to deploy a first workflow to see if that would be a viable solution.For example, for a task in the workflow calling a webservice:Technical errors: when webservice is unavailable, we woul</description>
      <pubDate>Wed, 08 Jul 2015 10:15:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/technical-and-functional-error-management/m-p/182850#M135980</guid>
      <dc:creator>miko2009</dc:creator>
      <dc:date>2015-07-08T10:15:57Z</dc:date>
    </item>
    <item>
      <title>Re: Technical and functional error management</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/technical-and-functional-error-management/m-p/182851#M135981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;A service task in Activiti can be made async which means that it will be retried automatically when an exception is thrown. The retry time and number of attempts can be configured. In case of a functional error you just not throw an exception but move forward to an error task (modeled with an exclusive gateway or programmed with a specific transition in the service task).&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, 09 Jul 2015 07:17:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/technical-and-functional-error-management/m-p/182851#M135981</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2015-07-09T07:17:07Z</dc:date>
    </item>
  </channel>
</rss>

