<?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: Dynamic Enum Form Property in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188329#M141459</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I still want the flexibility of the form designer in the activity-designer though. So my app will be slightly replicating the activiti-explorer when it comes to form rendering.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Found a way to do this, set a variable in a ScriptTask, e.g "userGroupList=admin", right before the User Task, then in the User Task's form, just set the type to String, with the name = "userGroup", when the renderer see this special name, it will use a drop down list instead of a standard input field. This will work well with testing the workflow in the activiti-explorer during development as well!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Jan 2015 10:56:51 GMT</pubDate>
    <dc:creator>ykphuah</dc:creator>
    <dc:date>2015-01-22T10:56:51Z</dc:date>
    <item>
      <title>Dynamic Enum Form Property</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188327#M141457</link>
      <description>I want to have a enum list that is dynamically populated, I have searched the forum and saw this example:http://www.jorambarrez.be/blog/2013/03/13/creating-a-new-form-property-in-activiti/What I want is a slightly more advanced, I am not using the activity-explorer, but I want to use the activiti-de</description>
      <pubDate>Tue, 20 Jan 2015 08:51:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188327#M141457</guid>
      <dc:creator>ykphuah</dc:creator>
      <dc:date>2015-01-20T08:51:54Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Enum Form Property</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188328#M141458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you're not using Activiti Explorer, wouldn't it be easier to use the formKey approach and not the formProperties. That way, you can do whatever you want.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jan 2015 13:28:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188328#M141458</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2015-01-21T13:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Enum Form Property</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188329#M141459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I still want the flexibility of the form designer in the activity-designer though. So my app will be slightly replicating the activiti-explorer when it comes to form rendering.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Found a way to do this, set a variable in a ScriptTask, e.g "userGroupList=admin", right before the User Task, then in the User Task's form, just set the type to String, with the name = "userGroup", when the renderer see this special name, it will use a drop down list instead of a standard input field. This will work well with testing the workflow in the activiti-explorer during development as well!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2015 10:56:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/dynamic-enum-form-property/m-p/188329#M141459</guid>
      <dc:creator>ykphuah</dc:creator>
      <dc:date>2015-01-22T10:56:51Z</dc:date>
    </item>
  </channel>
</rss>

