The filter is used to limit the set of records to be displayed in the list (in any list: related list, open list, the dictionary). The filter sets certain conditions for the record to meet to be in the list. Filters can be configured with the Condition Builder.

For example, we need to filter users living in Sevastopol. In SQL, we use the WHERE clause to filter records.

You can add a filter with all necessary filters in your Favorites in the Navigation menu. To do this, drag and drop the breadcrumbs to the Favorites navigation tab.

Filter components

Filters consist of the following components:

  1. Condition builder (and the breadcrumbs as its integral part).
  2. Search and sorting:
    1. Input field at the top of every column is used for searching.
    2. Click on the column title to sort the search results.
  3. Filter Out/Show Matching (this item can be found in the context menu, to open it, right-click on the list cell).

All these components form the condition string, which is sent in the request as a GET parameter, and the filtered list of records will be returned and displayed.


The difference between condition builder on lists and regular condition builder is that breadcrumbs and sorting functionality added.

Breadcrumbs allow assessing the filter visually. Also, they allow quick filter editing by navigation to the condition specified.

Sorting allows adding its conditions (ascending or descending) on one or more list fields.


How the filter works

To be more visual, let's take an example.

We need to find Jonh Doe's closed requests, sorted by priority.

For this, we will create such a filter on the Request list (the itsm_request table):


After that, condition string can be found in the condition GET parameter: 

/list/itsm_request?condition=(stateIN7%4010%5Eassigned_user%3D159906491314467953)%5EORDERBYDESCpriority

The condition string elements more closely:

ElementDescription
stateIN7%4010State is one of Completed, Closed
assigned_user%3D159906491314467953Assigned User is John Doe
%5EORDERBYDESCpriorityRecords will be sorted by the Priority field in the descending order


Filtering for the fields of the Reference, List, Choice, Record Class and Field Name types has some nuances related to the value and default_value fields correlation in  tables:

  1. Filtering is performed by the value of the value field. For example: in case the filter condition is field_name = value, then displayed condition will be field_title = display_value.
  2. Column search is performed by the value of the display_value field; either the filter or the breadcrumbs on the filter top are filled with the condition field_name = value; at the time, the condition displayed is field_title = display_value.
  3. The auto-suggest functionality is performed by either value or display_value field values.

The table below can clarify the filtration specifics when doing the selection with field of types above involved.

Column typeOperatorSearch field
ReferenceLIKE / NOTLIKE / STARTSWITH / ENDSWITHdisplay_value
ListLIKE / NOTLIKEdisplay_value
ChoiceLIKE / NOTLIKE / STARTSWITH / ENDSWITHtitle
Record ClassLIKE / NOTLIKE / STARTSWITH / ENDSWITHtitle


Field scalar type matters when you filter with the Condition Builder. If the field you filter by is of the varchar or text type (for example, HTML field type, or Script, or String), then you cannot use exact operators (for example, '='). This operator is unavailable for fields of varchar and text types. You'll have to filter out using LIKE operator.

And if the field is of one the number types (for example, decimal, int8, int4), then exact operators are available, and you can filter by them.

See the Condition Operators article to obtain filter operators full list.


Dynamic Filters

Dynamic filters extend the filters by the JS scripts executing ability. This ability is available in the list condition builder and in the dynamic reference qualifier condition builder.

In Condition Builder, dynamic filters are available when selecting the reference field and the 'is (dynamic)' or similar operator. After this, the list of available dynamic filters will appear.

When executing the filter as a value of the condition using the 'is dynamic' operator, the value returned by the dynamic filter script will be used.

To create a new dynamic filter, please complete the following steps (a new record in the Filter Option Dynamic (sys_filter_option_dynamic) table will be created):

  1. Navigate to System Definition → Dynamic Filters.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply changes.

You can also create dynamic filters for table fields of the sys_id type (ID). To do that, specify the dynamic filter form fields in the following way:

  1. In the Column type, select biginteger from the list.
  2. In the Reference table, specify the table to apply this filter on.
  3. Set the Active checkbox checked.
  4. Set the Available for filter checkbox checked.
  5. Complete filling the form and click Save.

To apply the dynamic filter created, specify the ID table column and the is (dynamic) operator as the Condition Builder field and operator appropriately.

Dynamic filters form fields

FieldMandatoryDescription
TitleYThe filter title.
Column TypeNThe column type used in the filter. This field references to the Columns dictionary.
Referenced TableYChoose the table to apply this filter on.
Available for FilterNSelect this checkbox to make this filter available in the list filters.
Available for Reference QualifierNSelect this checkbox to make this filter available for a dynamic reference qualifier.
ActiveNSelect this checkbox to make the filter active.
OrderNEnter the number to define the order of filter processing.
ScriptYEnter the script that the dynamic filter runs. You can use all methods of server-side API classes here. After executing, the script should return the record ID or array of IDs.