Configure Microsoft Outlook property mapping

You can map properties from a Microsoft® Outlook message, such as From and To, to corresponding Workplace XT e-mail class properties using the OutlookPropertyMappings.xml file. After Outlook properties are mapped to the e-mail class properties, you can assign those properties to each Outlook message you add to an object store.

Outlook field and data type information

Each of the Outlook properties you map has an assigned Outlook field, data type and corresponding Content Engine symbolic name. Use the following table to help you complete the mapping process because the process involves modifying the OutlookPropertyMappings.xml file and creating property templates in Enterprise Manager. The table includes default fields included in the OutlookPropertyMappings.xml file and optional fields you can add.

Outlook field Outlook data type Content Engine symbolic name
Default fields that are included in the OutlookPropertyMappings.xml file.
PR_SENDER_NAME string From
PR_DISPLAY_NAME string To
PR_DISPLAY_NAME string CarbonCopy
PR_CLIENT_SUBMIT_TIME datetime SentOn
PR_MESSAGE_DELIVERY_TIME datetime ReceivedOn
PR_SUBJECT string EmailSubject
Optional fields that can be added to the OutlookPropertyMappings.xml file.
PR_PRIORITY long*

Do not use Priority as a symbolic name because Priority is currently used in the Content Engine. Use a different symbolic name.

PR_DISPLAY_NAME string

BlindCarbonCopy

Use this symbolic name when mapping the blind carbon copy property.

     
PR_BODY string Use any name you choose.
PR_DEFERRED_DELIVERY_TIME datetime Use any name you choose.
PR_EXPIRY_TIME datetime Use any name you choose.
PR_LAST_MODIFICATION_TIME datetime Use any name you choose.
PR_MESSAGE_CLASS string Use any name you choose.
PR_MESSAGE_SIZE long* Use any name you choose.
PR_OBJECT_TYPE long* Use any name you choose.
PR_ORIGINATOR_DELIVERY_REPORT_REQUESTED boolean Use any name you choose.
PR_RESPONSE_REQUESTED boolean Use any name you choose.
PR_SENSITIVITY long* Use any name you choose.

* The Outlook data type long corresponds to the Workplace XT data type integer when you are creating a property template and assigning a data type in Enterprise Manager.

Mapping process

Mapping Outlook message properties to Workplace XT e-mail class properties involve using the Enterprise Manager and modifying the OutlookPropertyMappings.xml file. You need to do the following steps:

What can you do after mapping the properties?

To map properties

  1. Use the table to help you identify the Outlook properties you want to map to Workplace XT properties.
  2. Use Enterprise Manager to do the following steps:
    1. Create property templates for each of the Outlook properties.
    2. Assign the new properties to an existing Workplace XT e-mail class or create a new e-mail class. You can also create an e-mail subclass.
    3. Refresh the object store in which the properties and its related e-mail class reside. You might need to refresh more than one object store.
  3. Locate the OutlookPropertyMappings.xml file. By default, it is located in the <XT_install_path>/FileNet/WebClient folder.
    1. Use a text editor to add new Outlook fields and assign symbolic names and data types to each field in the OutlookPropertyMappings.xml file. For example, if you want to map the Outlook field PR_PRIORITY to the Importance property in the Workplace XT e-mail class, type the following text:

      <property>
      <tag>PR_PRIORITY</tag>
      <symname>Importance</symname>
      <datatype>long</datatype>
      </property>

      NOTE  If you type an invalid property, such as not using the correct tag or data type, that property is ignored when Outlook messages are added to an object store and properties are assigned.

    2. To test, add an e-mail message to an object store using the appropriate Outlook profile and verify the properties assigned to the new document are correct. If properties do not appear, check your syntax in the OutlookPropertyMappings.xml file first. If you still have errors, enable logging and check your Application Integration log file.