Modify search panes

The fields are listed as <attribute path="...".

Locate the "label" statement within the the entire block between <attribute path..., till the closing statement </attribute>. If there's one, just type another value. If there's not one, it means it reads the label from the standard configuration (string.en.xml or similar); then, add it as label="value" and then specify the value.

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

  <ui label="Spike Code">

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

  </ui>

</attribute>

1.Locate the search pane code as explained in Locating search panel fields in configuration files. The fields are listed as <attribute path="...".

2.Locate fields you want to reorder.

3.Select the entire block between <attribute path..., till the closing statement </attribute> and then cut it to the clipboard.

4.Create an empty line where you want to move the field and then paste from the clipboard.

5.Repeat steps #3 and #4 until reordered all fields.

1.Locate the search pane code as explained in Locating search panel fields in configuration files.

2.Locate the attribute you want to remove and just delete the entire block between <attribute path..., till the closing statement </attribute>.

1.Locate the search pane code as explained in Locating search panel fields in configuration files.

2.Considering the name of the attribute you want to add, search through all xxx_Config.xml files for the attribute name, and see if you can find an example. If so, just copy to clipboard the entire block between <attribute path..., till the closing statement </attribute>.

3.Make a new line on the position where you want the new field to appear and then paste the code from the clipboard.

Note

The exact syntax depends on the attribute and on your schema. The same attribute can be defined in various ways, e.g. article.folderRef is more specific than linkObject.folderRef (as the first one applies only on article object, while the second one is ok for both article object, text, img and other linkObjects) hat is anyhow more specific than folderObject.folderRef (that applies on any folderObject).