ELOxc uses metadata templates to allow additional information to be transferred to ELO along with the mailbox items. These templates store additional data in the metadata fields of the ELO forms. Two of these templates, KW_DEFAULT_DOCUMENT for e-mails, and KW_DEFAULT_FOLDER for folders in the filing path, are statically integrated by default and are created again if missing. In addition to assigning values to the metadata fields, a template is used to set the corresponding form, whose settings (e.g. access rights) the Indexserver takes into account when transferring the messages to the repository. The default metadata form for e-mails looks like this:

The KW_DEFAULT_DOCUMENT template is therefore preconfigured as follows:

Template name: The template name is referenced in the "Export" action.

Metadata form name: The form is specified by its name (see ELO Administration Console).

SORD types: These parameters assign the appropriate icon types to messages and messages with attachments in the repository.

ELO search index: The value is the group name of the metadata field to be used to search all copies of a message. Multiple copies of a message are created because an e-mail can have multiple recipients, each of whom receives a copy that is identical to the copy of the other recipients. The corresponding message property is "PidTagSearchKey".

ELO reference: If an attachment is extracted from a message and transferred to ELO, the GUID of the message is assigned to this metadata field. This enables actions such as "Exists" and "Message stubbing" to establish a relation between the message and attachments in ELO.

User identifier: This parameter can contain a property name whose value can subsequently be used for personal identification in order to comply with privacy policies.

Deletion period: This parameter represents the retention period in days and is only evaluated if the user identifier contains a valid value.

Metadata fields

The metadata fields can be determined in a variable way at runtime. A list of value comparisons or evaluations is possible for each metadata field. The metadata value can be set if these actions are successful.

The following image shows an example with "ELOOUTL2" (recipient):

The values of the property "EloRecipientsTo" are to be applied to the metadata field "ELOOUTL2" if they correspond to the pattern "*". Using the wildcard "*" means that the match is always successful and therefore all values of the property are applied to the metadata field.

Required: This field enables you to specify whether the metadata field must contain a value for the action to be successful.

Metadata name: The group name of the metadata field.

Output target: Specify here whether you want the result to be written to metadata fields, an ELO map in ELOxc, or both.

Output form: By default, the results are output to a column index. Alternatively, you can string lists without column separators as a single character string or configure them as individual output with "custom" (see "Output" and "Match ID").

Output: If you select the output form "custom", this parameter contains the output pattern that you can define individually and assign the individual results of the evaluation via the match IDs. A match ID is entered as "{ID}".

Separator: You apply the output separator to properties whose values are based on lists.