APPLICATION DESIGN
The OpenPreferences command works by setting a cookie for a user's preferences. The server retrieves the information from the user's cookie and responds with the specified formats and preferences for that user.
When designing an application, you might create a button that launches this URL command so that browser users can set their preferences without having to enter the command themselves.
Note The URLs shown below are for example only. They do not point to existing Web sites.
OpenPreferences
Syntax
http://Host/$Preferences.nsf?OpenPreferences[&Arguments]
OpenPreference with no arguments displays a frameset displaying a menu of choices on the left, and a panel for selecting time zone preferences on the right. OpenPreferences accepts arguments for manipulating what preference page displays.
The Host argument can apply to the server named or to all of the servers in the domain of the specified server. The scope of OpenPreference is determined by the value in the Web User Preferences field on the Web Site Template for the specified server. If the Web User Preferences field is set to Multi-server, the settings for OpenPreference apply to all of the servers in the domain. If the field value is Single server, the preferences apply only to the specified server. The server administrator can also set the field to Disable, which causes the server to ignore any cookies set for OpenPreference. Speak to your system administrator about setting the correct scope for the command.
Note Settings a user specifies for OpenPreferences will not override custom settings you specify for a field or view column.
Examples
http://www.mercury.com/$Preferences.nsf?OpenPreferences
Optional arguments for OpenPreferences
The following arguments open specific pages of the OpenPreferences user interface instead of loading the default frameset.
&PreferenceType=Menu
&PreferenceType=Regional
See Also