Presentation
A search form allows you to fully configure a search screen. These are associated with scope teams to personalize the display presented to the user.
Example: A basic AgentSearch
search form with the title Agent file search with description
<bean id="RechercheAgent" class="com.flower.docs.gui.client.search.ComponentSearchPresenter" scope="prototype">
<property name="title">
<list>
<bean class="com.flower.docs.domain.i18n.I18NLabel">
<property name="language" value="EN"/>
<property name="value" value="Agent folder search"/>
</bean>
<bean class="com.flower.docs.domain.i18n.I18NLabel">
<property name="language" value="FR"/>
<property name="value" value="Rechercher de dossier agent"/>
</bean>
</list>
</property>
<property name="description">
<list>
<bean class="com.flower.docs.domain.i18n.I18NLabel">
<property name="language" value="EN"/>
<property name="value" value="Do not fill criteria to find all agent folders"/>
</bean>
<bean class="com.flower.docs.domain.i18n.I18NLabel">
<property name="language" value="FR"/>
<property name="value" value="Ne remplissez aucun critère pour retrouver l'ensemble des dossiers agents"/>
</bean>
</list>
</property>
</bean>
Define access
A search form can be linked to a user team through a property that can be set via:
the CLM and the
scope.xml
file:
the administration console: in the
Security > Teams > Properties
section, add aSearch form
property
This property has the following value: <identifiant>(<language>=<label>,<language2>=<label2>)
for example template_id(fr=Label de formulaire,en=form label)
Global configuration
The following configurations are possible and can be set in the gui.properties
file:
Property name | Description | Value type | Default value |
---|---|---|---|
search.export.max |
Maximum number of results to export | Integral | 100000 |
Furthermore, exporting search results also requires parameters to be set on FlowerDocs Core here