|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
Outlook Web Access User Interface Customization
Topic Last Modified: 2007-11-12
This section contains reference information about the UIExtensions.xml file that is stored in the forms folder. Use this file to modify the user interface for Microsoft Office Outlook Web Access for Microsoft Exchange Server 2007 Service Pack 1 (SP1). By changing this file, you can do the following:
Add items to the New drop-down menu
Add items to the Outlook Web Access navigation pane
Specify icons to be used when custom content items are displayedin the message list
For information about how to create and deploy the UIExtensions.xml file, see Customizing Outlook Web Access.
The New drop-down menu in Outlook Web Access includes entries from the standard configuration and correctly specified entries from the NewItemMenuEntries XML element. The following example shows an XML fragment that adds a New menu item for the content class "IPM.MyCustomClass."
The navigation pane in Outlook Web Access includes entries from the standard configuration and correctly specified entries from the MainNavigationBarExtensions XML element. The following example shows an XML fragment that adds a navigation pane item for the application named "NewApplication."
The registry.xml file specifies the custom forms that are used for custom content types. Custom icons for those content types can be registered by creating a correctly formatted entry in the SmallIconMappings XML element of the UIExtensions.xml file. When Outlook Web Access displays one of those custom content types in the message list window, it uses the mapped icon. The following example shows an XML fragment that specifies a custom icon for items of the IPM.MyCustomClass content class.
Both New drop-down menu and navigation pane items include tool-tip style pop-up windows to help new users learn about the items. To support multiple languages, the XML file entries support multiple <string> elements. Include a separate <string> element for each language that specifies the language-subculture string in the language attribute.
Because the localized text string values are stored in XML attributes, those strings must comply with the requirements of XML attributes. They cannot contain quotation marks, angle-brackets, or text entities.