SearchObjectUI class

Build 1501 on 14/Nov/2017  This topic last edited on: 22/Mar/2016, at 16:36

Description

Defines search panes.

There is one or more SearchObjectUI within the parent SearchList.

Members

Namethe name f the SearchObjUI, as defined in the SearchName value in <l:SearchCriteria.

<l:ShellData.SearchCriteria>

 <l:SearchCriteria Name="ArticleSearch" BaseQueryName="ArticlePicker" SearchName="Search" AutoApply="False"/>

...

Example

searchobjui

Remarks

Fields are all defined in the simplified syntax, enclosed in <attribute... </attribute>. What is enclosed, depends on the type and of the purpose of the attribute.

hmtoggle_plus1Examples of fields

Single line attributes (all default)

<attribute path="[object.name]" />

 

<attribute path="[object:SpikedInfo.Time]">

 

<attribute path="[folderObject.folderRef]" />

Side label attribute

<attribute path="[article.name]" mode="Normal">

  <ui labelPosition="Side" orientation="Horizontal"/>

</attribute>

Hidden option attributes

<attribute path="[task.title]" op="Containing">

  <ui mode="Normal" labelPosition="Side" >

    <template kind="Single" opMode="Hidden" />

  </ui>

</attribute>

 

Bug fixes

In builds prior to 1.6.1754 it may happen that the SearchObjectUI returns all the GN4 objects without considering the configured object type.

This was because GN4, internally, created in memory a BaseQuery with ObjectType name set to 'object'.

Now the correct ObjectType name is specified into the SearchObjectUI this way:

<SearchObjectUI>

<!-- we need to set the ObjectTypeName -->

<searchConditions ObjectTypeName="page" />

. . .

</SearchObjectUI>

GN4 reads the correct ObjectTypeName and returns always the correct result.

Modified date: 20/03/2013 13:06:08 - P4 Changelist: 66903 - From build: 1.6.1754.x (T)