topic Re: Advanced Search on Custom Type Property with 'OR' in Alfresco Archive

Advanced Search on Custom Type Property with 'OR'

b_victor — Wed, 30 Apr 2014 22:14:13 GMT

I am on 4.2.e Community, trying to customize Share advanced search. I have a custom type, aq:qualityDoc defined, with a property named aq:documentType defined as:<property name="aq:documentType"> <title>Document Type</title> <type>d:text</type> <index enabl

Re: Advanced Search on Custom Type Property with 'OR'

b_victor — Fri, 02 May 2014 18:22:22 GMT

I was just trying to figure out if a custom control was the way to go on this, of if there's a way to use an out-of-the-box control to get this working. I'd love any pointers, as I'm sure this sort of thing has been done before.
Thanks!

Re: Advanced Search on Custom Type Property with 'OR'

b_victor — Mon, 05 May 2014 22:42:39 GMT

I'm pulling my hair out on this… this seems like very basic functionality, but I can't get it to work. I've followed all the tutorials and forum posts I can find, but the search doesn't work correctly. If I use a "selectone.ftl" control on a search form, the search is limited to the default selection (i.e. no way to have "nothing" selected). If I use a "selectmany.ftl" control, the search doesn't work when more than one is selected, because the selection gets translated into the query as a comma separated list. How can one do advanced search on list-constrained properties? Any pointers appreciated…

Re: Advanced Search on Custom Type Property with 'OR'

b_victor — Tue, 06 May 2014 04:07:16 GMT

I solved this with something of a hack. In the share-config-custom.xml I set the appearance element for the control as follows:


<field id="aq:documentType" label-id="prop.aq_documentType">
   <control template="/org/alfresco/components/form/controls/selectone.ftl" >
       <control-param name="options">|Any,Description,Policy,Procedure,Evidence,Form,Other</control-param>
   </control>
</field>
‍‍‍‍‍‍‍

The control defaults to the "|Any" which uses Any as a label, but is blank and hence omitted when evaluated for the query string. The problem with this solution is that you can't search on multiple values at once, and the values are hard-coded in the custom config file making maintenance harder. Both of these are unfortunate, but at least the core functionality is there. If anyone has a better way to solve this, I'd love to hear it.