cancel
Showing results for 
Search instead for 
Did you mean: 

Advanced Search Customization

mohammed_amr
Champ in-the-making
Champ in-the-making
Dears,

I've tried to add a new aspect into Advanced Search dialog additional options where it is a text-based property.

The customization looks like


<meta-data aspect="sec:tagable" property="sec:associatedTags" />

Where the content model definition is


      <aspect name="sec:tagable">
         <title>Document Tag</title>
         <properties>
            <property name="sec:associatedTags">
               <title>Associated Document Tags</title>
               <type>d:text</type>
               <multiple>true</multiple>
            </property>
         </properties>      
      </aspect>
The rendered option is Text-Based, where it is needed to be Select One Menu.

The question is how i can change the rendered option from Text-Based option to SelectOneMenu-Based option ?  Is it possible ? if it is how ? if its not what is the alternative solution that can i use to enable Select Menu Options into advanced search options ?

Thanks
4 REPLIES 4

jpotts
World-Class Innovator
World-Class Innovator
If you know the values you would like the user to be able to choose from, you can implement that list as a constraint in your content model. Then, when the field is rendered, whether it is being rendered to create or edit the metadata or for advanced search, Alfresco will render it as a dropdown instead of an open choice.

See:
http://wiki.alfresco.com/wiki/Content_Model_Constraints

Jeff

mohammed_amr
Champ in-the-making
Champ in-the-making
No i don't, the values are dynamic and they are read from the repository.

jpotts
World-Class Innovator
World-Class Innovator
It is possible to implement dynamic constraints that read values from the repository.

If that's not going to work for you then you'll have to do a UI customization to use a control that works the way you want it to.

Jeff

mohammed_amr
Champ in-the-making
Champ in-the-making
Sure, i did.

But the meta-data advanced search tag has not a generator so, the values will not filled in the component.