Export

The "Export" action is where you configure the use of metadata templates. You can specify whether you want the main item (document) to use a different template than optionally extracted attachments. In addition, the export mode determines whether it is possible to logically link the main document to the attachments with the metadata.

If you use the export modes outlined in red, the main document and the extracted attachments are exported. If only the message ("maindoconly") or the whole message including all attachments ("whole") is exported, no documents are created for the attachments, so no values can be created for "ELOOUTLREF". If you do not export the main document ("attachmentsonly"), attachments are written to the repository, but in the absence of a main document, there is no "EloGuid", meaning that "ELOOUTLREF" cannot be assigned a value here either.

Additionally, you can transfer the target documents determined in "Export" to ELO with your own metadata templates.

In this example, the main item is transferred using the predefined default template, and attached MIME files (i.e. emails) are archived using the same template. However, if a PDF file, an expected invoice in this case, is extracted, the specifically configured template KW_INVOICE_DOCUMENT is used.

Metadata and 'Exists'

The action "Exists" is important if an action tree is to process previously archived messages and perform actions that require the pseudo-property "EloGuid" for successful execution. This can affect the actions "External call" or "Message stubbing", for example. This is why it is important that you configure the consistent use of the ELO reference in the metadata template and in "Export". The Exists action should also use this metadata field.

Filing path

The "Filing path" determines the target path in ELO, which can use a separate metadata template for each SORD.

To make things simpler, the template is defined for the entire action, which uses the same template for all its filing paths, unless individual path segments contain overrides by other templates.

As in the "Export" action, which can use its own metadata templates for extracted attachments, the "Filing path" action also allows consistent separation of attachments with own path and templates. To do this, the affected segments must overwrite the action's centrally configured template.