<?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: Using BPM for Form Validation? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/using-bpm-for-form-validation/m-p/94234#M64540</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You're current knowledge about activiti being asynchronous (by default) is wrong. When you start a process (or complete a task), the current thread is used to execute the next steps of the process, until another wait-state (task, receive-task, …) or process-end is reached. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So in case you're process has a service-task (some Java behavior) that checks against a 3rd-pary system, after a user-task, the call to our "taskService.complete()" will only return, after that call has been done. If you throw an exception in the service-task that contacts the 3rd party system, this will bubble up to the point where the API-call (completeTask()) is done. On that moment, you can inspect the exception and give the user appropriate feedback (e.g. entity X does not exist in system Y).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Asynchronous behavior is possible in Activiti, but this needs to be explicit ally configured on a per-activity-basis…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Oct 2012 11:06:25 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2012-10-29T11:06:25Z</dc:date>
    <item>
      <title>Using BPM for Form Validation?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/using-bpm-for-form-validation/m-p/94233#M64539</link>
      <description>Hi all,I am new to using a&amp;nbsp; workflow engine and just trying to get a handle on the use cases that best suit using one and when to use plain old server side validation in the service layer. I see a tendency for business people to want to abstract out the form validation into task . i.e does this cust</description>
      <pubDate>Mon, 29 Oct 2012 08:11:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/using-bpm-for-form-validation/m-p/94233#M64539</guid>
      <dc:creator>mxc4</dc:creator>
      <dc:date>2012-10-29T08:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: Using BPM for Form Validation?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/using-bpm-for-form-validation/m-p/94234#M64540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You're current knowledge about activiti being asynchronous (by default) is wrong. When you start a process (or complete a task), the current thread is used to execute the next steps of the process, until another wait-state (task, receive-task, …) or process-end is reached. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So in case you're process has a service-task (some Java behavior) that checks against a 3rd-pary system, after a user-task, the call to our "taskService.complete()" will only return, after that call has been done. If you throw an exception in the service-task that contacts the 3rd party system, this will bubble up to the point where the API-call (completeTask()) is done. On that moment, you can inspect the exception and give the user appropriate feedback (e.g. entity X does not exist in system Y).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Asynchronous behavior is possible in Activiti, but this needs to be explicit ally configured on a per-activity-basis…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Oct 2012 11:06:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/using-bpm-for-form-validation/m-p/94234#M64540</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-10-29T11:06:25Z</dc:date>
    </item>
  </channel>
</rss>

