Configuration Settings
Print Article The following configuration settings are available to administrative users on the Configuration page in your PeopleZen Studio, available via Site Settings / PeopleZen / Configuration Settings.
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
PeopleZen has been localized for multiple languages. Changing this setting affects all PeopleZen user interfaces 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 PeopleZen Studio:
- (Like site, or English)
- English
- Deutsch
- Francais
Include domain name in linked user name
For displaying the name of a user, the PeopleZen User Profiles Web Part will attempt to use FirstName, LastName and PreferredName user profile properties before falling back to the AccountName or UserName property. If the latter is used and includes a backslash (\), the domain name of the user account name will be removed from the displayed name by default. On the Configuration page in the PeopleZen Studio, tick this check box to always include the domain name in the user account name displayed.
Window target for user profile links
User profile links produced by the PeopleZen User Profiles Web Part can target an HTML window of your choice. Use _self for these links to open in the current browser window, _blank for them to open in a new window, _modal for them to open in a modal pop-up dialog window, or the name of an IFRAME or FRAME element residing in your Web Part Page.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
_self
HTML template for email addresses (Tiles view)
The HTML to be generated by the PeopleZen User Profiles Web Part (in Tiles view) for all user profile property values that are email addresses. Valid placeholders: {0} for the email address, {1} for { and {2} for }.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
<a href="mailto:{0}">{0}</a>
HTML template for email addresses (List view)
The HTML to be generated by the PeopleZen User Profiles Web Part (in List view) for all user profile property values that are email addresses. Valid placeholders: {0} for the email address, {1} for { and {2} for }.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
<a class="rox-usermail" href="mailto:{0}"><img src="/_layouts/images/gmailnew.gif"/></a>
HTML template for user profile property with value
The HTML to be generated by the PeopleZen User Profiles Web Part (in Tiles view) for each user profile property that has a value. Valid placeholders: {0} for the property display name, {1} for the property value, {2} for the property internal name, {3} for { and {4} for }.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
{0}: <span>{1}</span>
HTML template for user profile property without value
The HTML to be generated by the PeopleZen User Profiles Web Part (in Tiles view) for each user profile property that has no value. Valid placeholders: {0} for the property display name, {1} for the localized word 'unknown', {2} for the property internal name, {3} for { and {4} for }.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
{0}: —
Exclude all user profile properties without values
By default, the PeopleZen User Profiles Web Part generates an HTML block element (in Tiles view) for each user profile property included per its Web Part settings, even when no property value has been set for a particular user profile. On the Configuration page in the PeopleZen Studio, tick this check box to never generate any HTML output (in Tiles view) for empty user profile properties.
Separator for multi-valued user profile properties
Some user profile properties such as Skills or Responsibilities can store multiple values. Specify how to join these values together for rendering in the PeopleZen User Profiles Web Part.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
,
Exclude User Names
You can optionally specify the patterns of user names (one per line) that should always be excluded from all PeopleZen User Profiles Web Parts (for example, service accounts). You may include an asterisk (*) only at the beginning ("ends with"), at the end ("begins with") or both ("contains"). This configuration setting is not case-sensitive.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
system\*
nt authority\*
builtin\*
sharepoint\*
Threshold before reducing quick-filter tabs
By default, quick-filter tabs are generated so that all tabs correspond to existing property values. This is preferable for multi-choice properties (Skills, Responsibilities...) but less usable for potentially vast numbers of values (First Name, Last Name...) — therefore, beyond a certain number of values quick-filter tabs will be reduced to alphabetic or numeric indices (A, B, C...)
Use this setting to specify that threshold. If you don't specify a valid integer number between 2 and 30, the default value of 16 will be used.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
16
Always hide the [Empty] quick-filter tab
By default, a quick-filter tab will be added to show user profiles without a value for the quick-filter property (but only if such user profiles exist). On the Configuration page in the PeopleZen Studio, tick this check box to never show that quick-filter tab.
Always show the [All] quick-filter tab
When using quick-filter tabs, by default the first quick-filter tab will be initially selected and there is no way for end users to show all user profiles unfiltered. On the Configuration page in the PeopleZen Studio, tick this check box to always add an [All] quick-filter tab that shows all user profiles unfiltered and to always make this the initially-selected tab, too.
Embedding of connected FilterZen Web Parts
By default, the interactive-filters container area of a FilterZen Web Part will be visually embedded inside the PeopleZen Web Part it is connected to. This usually results in a preferable user experience, but this setting allows you to turn the behaviour off, should you want to.
You can pick one of the following options on the Configuration page in the PeopleZen Studio:
- Yes (no top border)
- Yes
- No
Cache Refresh Rate
After a web front-end server has restarted, PeopleZen always creates a full cache of all user profiles in memory the first time a rendering request is served.
Afterwards, PeopleZen resynchronizes only a certain number of cached user profiles during each request to adequately balance performance with accuracy of the information displayed.
Specify the number of user profiles to refresh during each PeopleZen rendering request. A higher number (40 or more) reflects recent user profile changes much sooner but slows down PeopleZen rendering significantly, and vice versa.
If you don't specify a valid integer number greater than 0, the default value of 10 will be used.
After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the PeopleZen Studio to restore the following default value:
10
Periodically rebuild cache fully to capture new user profiles (typically not required or recommended in production)
After a web front-end server has restarted, PeopleZen always creates a full cache of all user profiles in memory the first time a rendering request is served.
Those user profiles in the cache are periodically refreshed at the rate specified above; however, completely new user profiles go unnoticed until the next server reset.
On the Configuration page in the PeopleZen Studio, tick this check box for PeopleZen to completely rebuild the cache periodically every nth Web Part request, which as a consequence may significantly slow down every nth Web Part request but captures new user profiles imported since the cache was last re-created (n = number of user profiles divided by the cache request rate specified above).
Disable AJAX-based handling (not recommended)
Certain end-user interactions (such as paging forwards or back, re-sorting, re-grouping or re-filtering) are handled by PeopleZen using AJAX, without reloading the entire page. This preferable behavior however can appear broken in certain very rare FBA / ISA constellations or other kinds of highly customized enterprise VPN / proxy setups. On the Configuration page in the PeopleZen Studio, tick this check box to disable all AJAX-based interactions and revert to a page-reloading, post-back style of handling user interaction.
Fast user profiles enumeration mode in MOSS 2007
For SharePoint 2007, in many setups this mode of enumerating user profiles is on average about as fast as the default one. In some setups this mode may be substantially (orders of magnitude) faster, but in very rare instances (cases of "messed up" SSP user profile databases) it may result in a near-infinite loop that times out before completion. (Feel free to try this out if you're not satisfied with the default initial performance — you can turn this mode off again after all. To further fine-tune performance-affecting settings, see the Caching & Internals section below.) For SharePoint 2010, this mode is typically not applicable to most setups.
By default, no inclusion of jQuery library v1.4.2 (NOT recommended)
Some PeopleZen end user-facing artifacts require (and load into the respective host pages) the jQuery library, version 1.4.2. Embedding jQuery more than once in a single page can cause JavaScript warnings in Internet Explorer with some few jQuery plugins (and only if any are used in your farm at all). On the Configuration page in the PeopleZen 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 PeopleZen to prevent PeopleZen from loading jQuery too. If you do so, you need to make sure jQuery 1.4.2 or higher is loaded on each page hosting also hosting PeopleZen user interface artifacts, or PeopleZen will appear broken. This is a global default setting that can be optionally overridden locally where applicable.
