List of values management

Users can specify a drop-down list of pre-defined values for both Table and Filter portlets. This pre-defined list is called a list of values. When used, the list of values will limit what a user can enter in a specific field.

To add a new list of values, go to Settings then Lists of Values.

Click the + icon to add a new list of values, then select the data source:

• Database: add name, connector, and select statement.

• Workflow: create a workflow with output and connect it to the list of values using the drop-down list. The workflow can also be created and connected directly from the list of values by clicking New - Add a name - Create.

Click execute, add the text and value columns, then save.

• Text column: the value which will be shown in the drop-down when using the list of values.

• Value column: the value which will be sent as the filter value

To edit an existing list of values, just click on the list of values in question and edit.

Cascading list of values

In the Filter, Record, and Table portlets, one list of values can depend on another list of values to only get the corresponding values to its parent object:

For this example, this is our dummy SQL data

--Countries
Select 'USA' as Country
Union all
Select 'Spain' as Country

--Cities
Select 'USA' as Country, 1 as CityId, 'Chicago - IL' as City
Union all
Select 'USA' as Country, 2 as CityId, 'Austin - TX' as City
Union all
Select 'Spain' as Country, 3 as CityId, 'Barcelona' as City
Union all
Select 'Spain' as Country, 4 as CityId, 'Malaga' as City

Three lists of values are needed for this setup for optimal functionality:

• One for countries (for the parent column)

• Two for cities (for the child column), where one is returning all possible values (cities) and the other is returning the corresponding values to a variable that is passed in from the parent column or is null (where Country = '{Country}' or '{Country}' is null).

The cascading list of values has a lookup which contains all records

The "or '{Country} is null" exists to give support for filtering from the table portlet column header. This is what it would look like in the workflow data source for the cascading list of values in our example:

example of cascading list of values data source with variable input and table filter support

For a more detailed information on this topic, please refer to our training environment