The following configuration settings are available to administrative users on the Configuration page in your FilterZen Studio, which you can access by typing a URL like http://my/share/point/_layouts/roxority_FilterZen/default.aspx — just be sure to replace http://my/share/point with a valid full Site Collection URL pointing to your SharePoint system.

Each setting has a global value scoped to the SharePoint server farm, and this value can optionally be overridden on the Site Collection level. The following settings are available:

User Interface Language

FilterZen has been localized for multiple languages. Changing this setting affects all user interface artifacts except captions and descriptions of Features, List Templates, Column Types, Content Types or Web Part Templates (those are always loaded directly by SharePoint based on the current Web Site locale).

You can pick one of the following options on the Configuration page in the FilterZen Studio:

• (Like site, or English)
• English
• Deutsch

Hard limit for pickable choices

Interactive drop-down filters (such as Choice, List Lookup, SQL, User and BDC Filters) use this threshold to limit the number of visibly pickable choices. This is recommended both for usability and performance reasons. To disable the limit (not recommended), set this setting to 0. If you don't specify a valid integer number, the default value of 150 will be used.

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

150

No-Filter Parameter Names

When using catch-all Page Request / URL Filters, optionally specify the request parameter names (one per line) that should never be sent as filters. Including the SharePoint-typical URL parameters in this setting's default value is recommended.

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

DisplayMode
PageView
Paged
PageFirstRow
View
SortDir
SortField
FilterField1
FilterValue1
FilterField2
FilterValue2
FilterField3
FilterValue3
FilterField4
FilterValue4
FilterField5
FilterValue5
FilterField6
FilterValue6
p_ID
p_FSObjType
p_FileLeafRef
p_Title

Data Source Providers for SQL Data Filters

Specify the ADO.NET data source providers that your SQL Data Filters should support (one per line, using the pattern "Provider display name: full provider IDbConnection Type name, full assembly name").

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

SQL Server: System.Data.SqlClient.SqlConnection, System.Data
Oracle: System.Data.OracleClient.OracleConnection, System.Data.OracleClient
ODBC: System.Data.Odbc.OdbcConnection, System.Data
OLE DB: System.Data.OleDb.OleDbConnection, System.Data

External Filter Types

Specify the additional or third-party FilterZen filter types to make available to FilterZen Filter Web Parts in this Farm (one per line, using the pattern "full roxority_FilterZen.FilterBase inheritor class type name, full assembly name"). CAUTION: uninstalling an external filter type assembly will break all Filter Web Parts that still use a filter of that type.

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

roxority_FilterZen.MossBdcExtensions.BdcFilter, roxority_FilterZen.MossBdcExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=68349fdcd3484f01

Enable Web Part Connections menu option 'Send single data value to'

When this option is selected, FilterZen Filter Web Parts will act not only as 'filter providers' and 'data row providers' but also as 'data cell providers'. This is usually not necessary because row providers can always also be used as cell providers and provide a better user experience for the Web Part Page designer. If unsure, don't select this option.

By default, no inclusion of jQuery library v1.4 (NOT recommended)

Some FilterZen end user-facing artifacts require (and load into the respective host pages) the jQuery library, version 1.4. Embedding jQuery more than once in a single page can cause JavaScript warnings in Internet Explorer with some jQuery plugins. On the Configuration page in the FilterZen Studio, tick this check box only if your master pages, web pages or third-party extensions also already include jQuery globally (not just on some individual pages) and independently of FilterZen to prevent FilterZen from loading jQuery too. If you do so, you need to make sure jQuery 1.4 or higher is loaded on each page hosting also hosting FilterZen user interface artifacts, or FilterZen will appear broken. This is a global default setting that can be optionally overridden locally where applicable.