A String Constraint filter provides a way to filter data on the client using a set of predetermined String values. These String values are called “Constraints”, and can be generated from unique values in the underlying data. This approach allows an end user to see a pull-down of values which are known to be present in the data.
To create a String Constraint Filter, perform the following steps:
String Constraint Filters can be reused across different datasets. The only thing required for a String Constraint Filter is a list of valid values that can be used as input. This is the same “Constraint” concept that is used with server variables. Since “Constraints” are defined globally, any constraint already defined for use with variables can be reused for client filters as well, and visa-versa. The example below shows a String Constraint that will provide a list of valid Company Names which will be presented as a pull-down. See String Constraint for more information.
If an administrator does not want to limit input, then they can use the system provided “Unbounded String” option. This will result in an text field input instead of a pull-down, and will allow end users to type whatever they want, similar to the “Search Field” client filter.
Applying a String Constraint Filter involves selecting an attribute. It is essentially a mapping exercise. The “Attribute to Filter” property should contain values that have some relationship to the Constraints defined in the String Constraint Filter. For Example:
The default value for a String Filter is “All”, which shows all records.
The pulldown menu contains the list of constraints, which is a set of valid STRING values that can be used as input for the filter.