Free cookie consent management tool by TermsFeed

a!recordFilterListOption() Function

Function

a!recordFilterListOption( id, name, filter, dataCount )

Creates a filter option for the a!recordFilterList() function.

Parameters

Keyword Type Description

id

Integer

The unique identifier for the filter option. This must be unique across other filter options within the same user filter.

name

Text

The name of the filter option that is displayed to users.

filter

QueryFilter

Filter to apply when the filter option is selected, created with a!queryFilter().

dataCount

Integer

An optional value that defines how many items in the data set will be selected if this filter option is selected.

Returns

FacetOption

Usage considerations

This function, when used within the options parameter in the a!recordFilterList() function, creates a user filter option.

Example

The following example creates a new "Status" user filter on a Customer record type. By default, the user filter will have "Active" selected, so users only see active customers when the record list first loads.

For additional examples, see Expression user filter configuration.

Record type object references are specific to each environment. If you copy and paste these examples into your interface, they will not evaluate. Use them as a reference only.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
=a!recordFilterList(
  name: "Status",
  options: {
    a!recordFilterListOption(
      id: 1,
      name: "Active",
      filter: a!queryFilter(
        field: recordType!Customer.fields.status,
        operator: "=",
        value: true
      )
    ),
    a!recordFilterListOption(
      id: 2,
      name: "Inactive",
      filter: a!queryFilter(
        field: recordType!Customer.fields.status,
        operator: "=",
        value: false
      )
    )
  },
  defaultOption: "Active",
  isVisible: true,
  allowMultipleSelections: true
)

Feature compatibility

The table below lists this function's compatibility with various features in Appian.
Feature Compatibility Note
Portals Partially compatible

Can be used with Appian Portals if it is connected using an integration and web API.

Offline Mobile Partially compatible

Can be used with offline mobile if it is loaded at the top of the form.

Sync-Time Custom Record Fields Incompatible
Real-Time Custom Record Fields Incompatible

Custom record fields that evaluate in real time must be configured using one or more Custom Field functions.

Process Reports Incompatible

Cannot be used to configure a process report.

Process Events Incompatible

Cannot be used to configure a process event node, such as a start event or timer event.

Process Autoscaling Compatible

Feedback