<?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: Server side form validation for user tasks in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42364#M22811</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks for your reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I figured that this was not (yet) possible, thus devised a workaround using the Grails constraints mechanisms. In case anybody runs into the same problem:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I defined a script task as first task of my process that sets a map of form property IDs to associated constraints, like this&lt;/SPAN&gt;&lt;BR /&gt;&lt;CODE&gt;&lt;BR /&gt;constraints = [&lt;BR /&gt; someLongFormProperty: [min: 1L],&lt;BR /&gt; someStringFormProperty: [&lt;BR /&gt;&amp;nbsp; inList: ['red', 'green', 'yellow']&lt;BR /&gt; ]&lt;BR /&gt;]&lt;BR /&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;SPAN&gt;In my application I then use a Grails command object, bind the entered form values to it, set the constraints defined in the process variable and validate the command object. This way I can leverage the power of Grails validations and still define the constraints as part of the process definition. Only thing that did not work was using custom Grails validators since they are defined as Closures which are not Serializable and thus cannot be stored as process variables.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jul 2011 11:01:41 GMT</pubDate>
    <dc:creator>danielbehrwind</dc:creator>
    <dc:date>2011-07-19T11:01:41Z</dc:date>
    <item>
      <title>Server side form validation for user tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42362#M22809</link>
      <description>Hi,I'm planning to use Activiti in a web application (using Grails) and was wondering if there is any way to specify constraints for a user task's form properties other than "required" (e. g. min and max values for an integer, max size for a string…).What I want is: The user enters some data, the se</description>
      <pubDate>Mon, 11 Jul 2011 14:23:37 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42362#M22809</guid>
      <dc:creator>danielbehrwind</dc:creator>
      <dc:date>2011-07-11T14:23:37Z</dc:date>
    </item>
    <item>
      <title>Re: Server side form validation for user tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42363#M22810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No, that's not in there (yet). It's something which I would like to see there, but no date has been given to it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jul 2011 08:01:56 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42363#M22810</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2011-07-19T08:01:56Z</dc:date>
    </item>
    <item>
      <title>Re: Server side form validation for user tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42364#M22811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks for your reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I figured that this was not (yet) possible, thus devised a workaround using the Grails constraints mechanisms. In case anybody runs into the same problem:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I defined a script task as first task of my process that sets a map of form property IDs to associated constraints, like this&lt;/SPAN&gt;&lt;BR /&gt;&lt;CODE&gt;&lt;BR /&gt;constraints = [&lt;BR /&gt; someLongFormProperty: [min: 1L],&lt;BR /&gt; someStringFormProperty: [&lt;BR /&gt;&amp;nbsp; inList: ['red', 'green', 'yellow']&lt;BR /&gt; ]&lt;BR /&gt;]&lt;BR /&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;SPAN&gt;In my application I then use a Grails command object, bind the entered form values to it, set the constraints defined in the process variable and validate the command object. This way I can leverage the power of Grails validations and still define the constraints as part of the process definition. Only thing that did not work was using custom Grails validators since they are defined as Closures which are not Serializable and thus cannot be stored as process variables.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jul 2011 11:01:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/server-side-form-validation-for-user-tasks/m-p/42364#M22811</guid>
      <dc:creator>danielbehrwind</dc:creator>
      <dc:date>2011-07-19T11:01:41Z</dc:date>
    </item>
  </channel>
</rss>

