Page History

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

For example, we you need to filter users living in SevastopolMoscow.  In In SQL, we use WHERE operator to filter records.

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 that is sent in the request as a GET parameter, and the . The filtered list of records will be is returned and displayed.

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

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

Sorting allows adding The sorting allows you to add its conditions (ascending or descending) on one or more list fields.

How filters work

For more clarity, let's take an example.We need example, you need to find John Doe's closed requests, sorted by priority.

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

Image Modified

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

/list/task?condition=(state%3D-2%5EdescriptionISEMPTY%5Epriority<3)

Encoding and decoding queries

To decode an encoded query string storing the condition obtained from the GET parameter, we recommend using the addEncodedQuery and getConditionQuery methods of the SimpleRecord Server-Side class. You can decode the encoded string by completing the simple steps:

1. Perform a selection against the table list view using a Condition Builder.
2. Copy the condition from the URL as shown on the screenshot below:
   Image Removed
3. Navigate to System Definition → System Scripts and click New.

4. Fill in the Script field with code below (this one is given for example):

   1. Fill in the {tableName} placeholder with the table system name.

   2. Fill in the {conditionQueryCondition} placeholder with the copied condition.
   3. Click Run to execute the script.

const current = new SimpleRecord('{tableName}');
current.addEncodedQuery('{conditionQueryCondition}');
ss.info(current.getConditionQuery());
// Info: (state=-2^descriptionISEMPTY^priority<3)

Dynamic

filters

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

In Condition Builderthe 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 → Definition → Dynamic FiltersFilter Options.
2. Click New and fill in the fields.
3. Click Save or Save and Exit to apply the changes.

As a result, a new record will be created in the Dynamic Filter Options (sys_filter_option_dynamic)table.

Dynamic filters form fields