Customizing rules for property transfer

If the configuration described in the previous chapter needs to be modified (e.g. document templates from another application that doo not allow customizing the property field names).

This can be done by replacing

'properties' => $mt_config::basepropmap
        

by

‘properties’ => {<OLE field name> => <Project Portal field>,…}
        

in the map hash.

Standard (text strings) field types may be transferred from Project Portal to the OLE file by defining <Project Portal field> as the Project Portal field name as specified in Table 1: Project Portal field identifiers or the previous chapter, for example

‘docnum’ => $::doccodefname;
        

sets the custom field docnum in the OLE file to the document number of the Project Portal document.

Custom properties may be read into from Project Portal to OLE file properties with the field name => Project Portal field mapping

<OLE field name> => [\&olefileprops::_docextmetafield, <Project Portal field code>]
        

Note: the Project Portal field code may be specified without the numbers in the start of the code.