List Box Form Element

The List Box form element allows the user to select one or more items from a list.

To use a list box, the user selects one or more items in the list (). To select items that are next to each other, the user holds the Shift key down and selects the first and last items. To select items that are not next to each other, the user holds the Ctrl key down while selecting items.

Example of the List Box form element, shown in a Geocortex viewer

List Box Properties

The Properties table describes the properties of the List box form element.

Property names in Workflow Designer's Properties panel are written using the capitalization and spacing of a title. Property names in expressions are valid JavaScript identifiers and start with a lower case letter. Expressions are case sensitive. When you access a form element property in an expression, you must use the correct capitalization.

In the table below:

If a property can be accessed in both the Properties panel and expressions, then the table gives both versions of the name.
If a property's name in the table starts with a lower case letter, then you can only access the property in expressions.
If a property's name starts with a capital letter and the table does not give a name to use in expressions, then you can only access the property in the Properties panel.

Properties of the List Box Form Element

Depends On

Type: String

Indicates whether the options that appear in the list box depend on the value that the user selected in a previous form element. When a list box depends on a previous form element, the list box is initially disabled. It becomes enabled when the element that it depends on gets a value.

To configure the Depends On property, click the arrow or start typing the element's ID. The drop-down list only allows you to select elements that the list box can depend on. A list box can depend on an auto complete element, drop-down list, or list box.

For an example of a form in which one element depends on another element, see Use the Item Picker Form Element for Visualization.

Description

Type: String

A description of the element. The description appears below the element's title.

You can use the Description property to describe what the element represents or to provide instructions to the user about how to use the element.

You can format the description using Markdown.

Element ID

Type: String

The element's ID, which is used in other form elements and activities to access the element's properties, including the user's input. The ID must be unique across all elements in the form.

You cannot get or set the value of the Element ID property in an expression—you can only use the value that you configured for it. To use the Element ID property in an expression:

${Display Form ID}.state.{Element ID}.{property name}

For example:

$form1.state.listBox1.visible

Enabled

Type: Boolean

Name in Properties Panel: Enabled

Name to Use in Expressions: enabled

Indicates whether the list box is enabled in the running workflow. When a list box is enabled, the user can select and clear options. When a list box is disabled, the user can see the list box but cannot interact with it. Disabled elements appear dimmed or shaded in the running workflow.

By default, list boxes are enabled. To disable a list box, clear the Enabled checkbox. You may want to change the property's value at run time depending on the user's input in a previous form element.

To access the enabled property in an expression:

${Display Form ID}.state.{Element ID}.enabled

For example:

$form1.state.listBox1.enabled

error

Type: String | MarkdownRef

Indicates whether an error occurred in the element.

We recommend using the Set Form Element Error and Clear Form Element Error activities to work with errors in form elements.

Options

The options offered by the drop-down list. For information on configuring the options, see Configure the Options in a List Box.

Type: { [key: string]: Item; }

Name in Properties Panel: Options

Name to Use in Expressions: items

The options in the list box. For information on configuring the options, see Configure the Options in a List Box.

The options are stored in an object called items. Each option is a property of the items object. To access the items object:

${Display Form ID}.state.{Element ID}.items

For example:

$form1.state.listBox1.items

For more information, see Form Element Items.

Required

Type: Boolean

Name in Properties Panel: Required

Name to Use in Expressions: require

Indicates whether the user must select an option from the list box. When the list box is required, the user cannot submit the form until an option is selected.

By default, list boxes are not required. To require a list box, select the Required checkbox.

The Required checkbox is intended as a quick way to do simple validation without having to add a validate event. If you add a validate event to a form element, selecting the Required checkbox will not have any effect. In this case, you must make the validate event check whether the user entered a value.

To access the require property in an expression:

${Display Form ID}.state.{Element ID}.require

For example:

$form1.state.listBox1.require

Rows

Type: Number

The size of the list box, measured in rows. The Rows property controls the number of options that the user can see at one time—it does not limit the number of options that the list box can have. The user can scroll to see the other options.

By default, list boxes show 4 rows.

To change the number of rows, you can either type the number into the Number box or click the arrows . The number of rows must be a positive integer.

styleName

Type: String

Indicates the name of the style that will be applied to the element.

To access the styleName property in an expression:

${Display Form ID}.state.{Element ID}.styleName

For example:

$form1.state.listBox1.styleName

Title

Type: String

The element's title, which appears at the top of the element. You may want to change the title to describe what the element represents in your workflow.

You can format the title using Markdown.

type

Type: String

The variety of form element. List boxes are type "ListBox".

Use the type property to find out the variety of a form element in a form with many elements. Loop through ${Display Form ID}.state, comparing each element to the known form types and performing some action on the elements that meet your type criteria.

To access the type property in an expression:

${Display Form ID}.state.{Element ID}.type

For example:

$form1.state.listBox1.type

value

Type: ItemsRef

An object of type ItemsRef. If at least one item is selected, the object has an items property that is the collection of options. To access the collection in an expression:

${Display Form ID}.state.{Element ID}.value.items

For example:

$form1.state.itemPicker1.value.items

If no checkboxes options are selected, value is undefined.

Visible

Type: Boolean

Name in Properties Panel: Visible

Name to Use in Expressions: visible

Indicates whether the element is visible to the user. By default, list boxes are visible. If you want to hide the element, clear the Visible checkbox. You may want to change the visibility at run time depending on the user's input in a previous form element.

To access the visible property in an expression:

${Display Form ID}.state.{Element ID}.visible

For example:

$form1.state.listBox1.visible

List Box Events

The following table describes the events associated with the List box form element. As in Workflow Designer, the events are listed in the order that they fire.

Events for the List Box Form Element

load

The load event fires when the element finishes loading.

You can use the load event to set one or more of the element's properties at run time.

change

The change event fires when the user selects or deselects an option in the list box.

You can use the change event to create dependencies between form elements. For example, you could configure a change subworkflow that enables or disables other form elements depending on the user's selection.

By default, if another form element is configured to depend on the list box and the list box has a change event, the configured dependency will be ignored. When an list box has a change subworkflow, the workflow assumes that you want the change subworkflow to handle any dependencies.

If you want the configured dependency to be respected, add a Propagate Form Event activity to the change subworkflow. The Propagate Form Event activity instructs the workflow to perform the dependency behavior after the change subworkflow completes.

The change event fires every time the user's selection changes. This means that the change subworkflow can run multiple times. Because of this, you should make sure that the change subworkflow is not computationally intensive or long running.

validate

The validate event fires when the user clicks a button that causes validation.

You can use the validate event to verify that the user's input is valid before allowing the form to submit. If the input is not valid, use the Set Form Element Error activity to display an error to the user and prevent the form from submitting. If the input is valid, use the Clear Form Element Error activity to clear an existing error and allow the form to submit.

If you use a Set Form Element Error activity, make sure you also use a Clear Form Element Error activity to clear the error. Otherwise the form may get stuck in an invalid state.

By default, the Required property does not work when the list box has a validate event. If you want the workflow to perform the Required check, add a Propagate Form Event activity to the validate subworkflow. The Propagate Form Event activity instructs the workflow to perform the Required check after the validate subworkflow completes.

For an example, see Example - Subworkflow for a Validate Event.

Configure the Options in a List Box

As part of the configuration of a list box, you must configure the options in the list box. There are two ways to do this:

Manually: If you know exactly how many options you want and the text for each option, you can define the options manually when you configure the list box.
Using a Subworkflow: If you want to base the options on dynamic information like query results, you can add a subworkflow that creates the options when the workflow runs. If the list box depends on another form element, you will use this method of configuring the options. Workflow Designer provides two templates to use as the starting point for the subworkflow: the ArcGIS Query template and a Blank template.

Configure List Box Options Manually

If you know exactly how many options you want and the text for each option, you can define the options manually when you configure the list box.

To manually configure options in a list box:

In the Options area of the list box's properties, make sure Configure them manually is selected.
Configure an option:
1. Click the arrow to show the option's properties.
2. Label: In the Label box, type the text that you want to use for the option.
3. Value: If you want to associate a value with the option, enter the value in the Value box.
  
  You can use any text for the value, for example, New Zealand and 9630 are valid values. The value will be available in the option's value property.
  
  If you enter digits for the value (for example, 9630), remember that the value is stored as text ("9630"), not as a number (9630).
4. Selected: If you want the option to be selected initially, select the Selected checkbox.
Repeat the previous step for each option in the list box. Click Add if you need to add an option.

You can reorder the options in a list box by dragging each option to its new position in the list.
Remove any unconfigured options that are left over when you finish the configuration.

To remove an option, click the arrow to show the option's properties and then click Delete.

Use a Subworkflow to Create List Box Options

If you want to base the list box options on dynamic information like query results, you can add a subworkflow that creates the options when the workflow runs. If the list box depends on another form element, you will use this method of configuring the options.

Workflow Designer provides templates that you use as the starting point for the subworkflow:

ArcGIS Query: The ArcGIS Query template provides a subworkflow that queries ArcGIS Server for items to use as the list box options.
Blank: The Blank template provides a blank subworkflow to use as the starting point for the subworkflow.

Use the ArcGIS Query Template to Create List Box Options

The ArcGIS Query template provides a subworkflow that queries ArcGIS Server for list box options. You will need to adapt the subworkflow to work within your workflow.

Subworkflow for the ArcGIS Query template

The subworkflow has the following activities:

Query Layer: This activity queries an ArcGIS Server map service for features on a particular layer. The query also gets the specified feature attributes that you want to use later in the workflow.
Get Form Element Items From Features: This activity converts the features returned by the query to items that can be used by the list box. Form elements cannot use features directly—the features must be converted first.
Set Form Element Items: This activity associates the converted features with the list box.

The ArcGIS Query template is based on a query for US state names. When the list box loads, the subworkflow queries the States layer for US states. The subworkflow then converts the features and assigns them to the list box. The list box presents the state names as options that the user can select.

To use the ArcGIS Query template:

This procedure presents one possible adaptation of the template which you can build on in many ways. To explore additional capabilities of an activity, refer to the activity's documentation.

In the Options area of the list box's properties, select Use a subworkflow and click ArcGIS Query.

The subworkflow opens.
Query Layer: Adapt the Query Layer activity to work in your workflow:
1. Update the Description property to describe what you are querying for.
2. Set the Url input to the URL of the layer that you want to query.
  
  Click the Expand icon to open a larger input area.
3. In the Where box, enter a SQL WHERE clause to filter the features that the query returns.
  
  For example, if you only want to show sparsely populated states, you could use a Where input similar to this:
  
  POP2007 < 1000000
  
  Setting the Where input to 1=1 gets all the features.
  
  To do a literal text search on the display field, configure the Text input instead of the Where input.
  
  To perform a spatial query, configure the Geometry input. You can filter on both attribute values and location by configuring the Geometry input and the Where or Text input.
4. Change the Output Fields input to specify the fields that you want the query to return. Use commas to separate the field names.
  
  If you want to get all the fields, enter an asterisk (*) in the Output Fields input.
5. If you plan to use the feature geometries later in the workflow, set Return Geometry to true and set Output Spatial Reference to the spatial reference of the map.
  
  This ensures that the geometries can be drawn in their correct locations on the map.
  
  If you leave Output Spatial Reference blank, the spatial reference of the map service is used.
6. Configure any other properties and inputs that you want to customize. See Query Layer Activity for information.
Get Form Element Items From Features: Adapt the Get Form Element Items From Features activity to work in your workflow:

You should not need to change the Features input. The Features input specifies the features returned by the query.
1. Configure the Label input:
  - If you want the options to consist of a single field, set the Label input to the name of the field.
    
    For example, to use the value of the STATE_NAME field as the options, set Label to STATE_NAME.
    
    or
  - If you want the options to contain multiple fields, surround each field name with curly brackets in the Label input.
    
    For example, suppose you set Label to the following:
    
    {STATE_NAME} ({STATE_ABBR})
    
    The options will have the state's name, followed by the state's abbreviation. For example:
    - Maryland (MD)
    If a field placeholder such as {STATE_NAME} appears in the items at run time instead of being replaced by the field's value, the workflow could not find the field. This can be caused by a spelling or capitalization error in the placeholder or by forgetting to include the field as an output field in the Query Layer activity.
  You will be able to access the value of Label using an expression similar to this:
  
  =$form1.state.listBox1.label
2. If you want the value of one of the query's output fields to be available in each option's value property, set the Value Field Name input to the name of the field.
  
  For example, if you specify AREA in Value Field Name, then you will be able to access the area using an expression similar to this:
  
  =$form1.state.listBox1.value
  
  If you leave the Value Field Name blank, value will be an object that contains the feature.
3. Configure any other properties that you want to customize. See Get Form Element Items from Features Activity for information.
Set Form Element Items: You should not need to change the inputs. The Items input specifies the items created by the Get Form Element Items From Features activity. Leaving the Element input blank assigns the items to the form element that the subworkflow belongs to.
To return to the form designer, click Display Form in the breadcrumbs.
If you need to re-open the subworkflow, click Edit in the Properties panel or double-click the list box in the form preview.

Use the List Box's Blank template

The Blank template provides a subworkflow with an Event block and nothing else in it. You will have to create the subworkflow from scratch.

Subworkflow for the Blank template

By its very nature, the Blank template can be used to create a wide variety of subworkflows that get options for a list box. The two most common scenarios are:

Collection: You have a collection (array) that contains the items you want to use for the options.
Feature Set: You have a feature set that contains the items you want to use for the options.

If the feature set doesn't exist in the workflow yet, you may want to use the ArcGIS Query template.

You can create the subworkflow using the following activities:

Get Form Element Items From Collection: This activity converts the collection to items that can be used by the list box.

or

Get Form Element Items From Features: This activity converts the features to items that can be used by the list box.

Form elements cannot use collections or feature sets directly—the collection or feature set must be converted first.
Set Form Element Items: This activity associates the converted items with the list box.

Subworkflow that creates list box options based on the items in a collection

To use the Blank template:

This procedure assumes that the collection or feature set already exists in the workflow.

This procedure presents one possible adaptation of the template which you can build on in many ways. To explore additional capabilities of an activity, refer to the activity's documentation.

In the Options area of the list box's properties, click Blank.

The blank subworkflow opens.
Collection:
1. Add a Get Form Element Items From Collection activity.
2. Set the Collection input to the collection whose items you want to use as options.
  
  For example, if you created the collection using a Create Value activity, enter an expression similar to this:
  
  =$value1.result
3. If the collection contains objects, set the Label Field Name input to the name of the field used for the options.
  
  You will be able to access the value of Label Field Name by entering an expression similar to this:
  
  =$form1.state.listBox1.label
4. If the collection contains objects, set the Value Field Name input to the field that you want to be available in each option's value property.
  
  For example, if you specify the AREA field, then you will be able to access the area by entering an expression similar to this:
  
  =$form1.state.listBox1.value
  
  If you leave Value Field Name blank, the workflow uses the field that you specified in Label Field Name.
5. Configure any other properties that you want to customize. See Get Form Element Items From Collection Activity for information.
or

Feature Set:
1. Add a Get Form Element Items From Features activity.
2. Set the Features input to the feature set that will provide the options.
  
  For example, if you created the features using a Create Value activity, by entering an expression similar to this:
  
  =$value1.result
3. Set the Label input to the name of the field used for the options.
  
  You will be able to access the value of Label by entering an expression similar to this:
  
  =$form1.state.listBox1.label
4. Set the Value Field Name input to the field that you want to be available in each option's value property.
  
  For example, if you specify the AREA field, then you will be able to access the area by entering an expression similar to this:
  
  =$form1.state.listBox1.value
  
  If you leave Value Field Name blank, value will be an object that contains the feature.
5. Configure any other properties that you want to customize. See Get Form Element Items from Features Activity for information.
Set Form Element Items:
1. Add a Set Form Element Items activity to the bottom of the flowchart and connect the previous activity to it.
2. Leave the Element input blank.
  This assigns the items to the form element that the subworkflow belongs to.
3. Set the Items input to the items created by the Get Form Element Items From Collection or Get Form Element Items From Features activity. For example:
  
  =$formElementItems1.items
4. Configure any other properties and inputs that you want to customize. See Set Form Element Items Activity for information.
To return to the form designer, click Display Form in the breadcrumbs.
If you need to re-open the subworkflow, click Edit in the Properties panel or double-click the list box in the form preview.

Documentation Version 5.19