topic Re: list of value constraint meta-data in the advanced search in Alfresco Archive

list of value constraint meta-data in the advanced search

tfaudot — Thu, 28 Aug 2008 08:20:06 GMT

Hello,While looking at the wiki http://wiki.alfresco.com/wiki/Advanced_Search_Custom_Attributes I found this line: In Alfresco 2.1 list-of-values constraint bound properties are supported and will display as a drop-down list of values for selection..How can I define list-of-value constraint properti

Re: list of value constraint meta-data in the advanced search

xerox — Thu, 28 Aug 2008 08:40:06 GMT

an example:


<aspect name="xxx:yyyy">
        <properties>
           <property name="xxx:projectType">
              <type>d:text</type>
      <multiple>true</multiple> 
         <constraints>
                 <constraint ref="xxx:projectList" />
              </constraints>
           </property>
        </properties>
      </aspect>

<constraints>
     <constraint name="xxx:projectList" type="LIST">
        <parameter name="allowedValues">
            <list>
               <value>A</value>
               <value>B</value>
               <value>C</value>
             </list>
        </parameter>
     </constraint>
</constraints>   
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Friendly regards,

Nick

Re: list of value constraint meta-data in the advanced search

tfaudot — Thu, 28 Aug 2008 08:51:03 GMT

I just tried that but my model can't be parsed, is this feature really available in 2.1? (I'm using the community one)
When I looked at the modelschema, the <constraint> tag wasn't there… 😞

Re: list of value constraint meta-data in the advanced search

xerox — Thu, 28 Aug 2008 09:08:14 GMT

Yes' It's possible.

Where did you define your constraint?
You should define it in your custommodel.xml.
Maybe you could give an example of your model with constraint?

Friendly regards,

Nick

Re: list of value constraint meta-data in the advanced search

tfaudot — Thu, 28 Aug 2008 09:08:52 GMT

OK I solved it, the thing is that the <constraint> tag cannot be followed by anything… it there is another tag following it in the properties section the model cannot be parsed.

great, it works now! 🙂