Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following properties within  SearchBoxConfigurationType can be configured:

XML tag namePossible valuesDescription
defaultMode

basic

advanced

fulltext

Basic search mode. Ability to select the items and specify values for them.

Advanced search mode. Ability to create complex query using a query language.

Fulltext search mode. Single input field used to search over several fields.

defaultScope


oneLevel

subtree

The scope of the search box. Scope may not be applicable to all types of lists/views. E.g. it does not make sense for flat searches. Therefore some views may not even display scope selection at all.

Onelevel search will only traverse flat, one-level part of the hierarchy. This is ordinary search scope for non-hierarchical data. But when used in organizational hieraries, then this search scopewill be limited only to a single organizational level.

Subtree search will traverse entire subtree. This scope makes no sense for non-hierarchical data. But when used in organizational hieraries, then this search scope will be span entire subtree with all sub-orgs.

defaultObjectTypeE.g. UserType or RoleType.Default type of object for search boxes that support object type selection. Setting it to ObjectType should display all objects. Type selection may not be applicable to all types of lists/views. E.g. it does not make sense for lists that only contain objects of a single type. Therefore some views may not even display object type selection at all.
searchItems
The list of searchable properties which should be displayed on the search panel. Search item is presented with a SearchItemtype type, there is a possibility to configure search item path, filter, description and display name (pls, see the following example for more info)
allowToConfigureSearchItemstrue, falseThe flag to display/hide configuration button (More dropdown button) on the search panel.

The example of search panel configuration for Users list page:

Code Block
languagexml
	<objectCollectionView id="81">
                <searchBoxConfiguration>
                    <searchItems>
                        <searchItem id="83">
                            <filter>
                                <q:or>
                                    <q:substring>
                                        <q:path xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3">c:emailAddress</q:path>
                                        <q:value xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xsd:string">emailtest</q:value>
                                    </q:substring>
                                </q:or>
                            </filter>
                            <displayName>Email address filter</displayName>
                        </searchItem>
                        <searchItem id="841">
                            <c:path xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3">c:telephoneNumber</c:path>
                            <description>Search item for search by telephone number</description>
                            <displayName>Tel. number</displayName>
                        </searchItem>
                    </searchItems>
                </searchBoxConfiguration>
                <type>c:UserType</type>
            </objectCollectionView>

Image Added

Limitations

This feature is available in midPoint 4.0 and later. While most parts of this functionality are developed and ready to be used, some functionality is still missing. Therefore the use of collections and views has some quite significant limitations:

...