Technical node name: ArcPathDef

An Archive Path action is used to construct the folder path in the repository to which Exchange items will later be stored. If a path does not already exist, it will be created in ELO using the specified keywording forms. An Archive Path node in an action tree does not require other specific nodes, but it is usually used in combination with a Keywording node and later Export and Archive nodes.

Information: If you are using emulated user mailboxes, such as an Exchange store's journal recipient, you must specify the BoxName mailbox variable in order to create a separate path for each recipient.

Name: Select a display name for the action.

Switch Sender/Recipient: If the action tree processes items in the Sent Items folder, select this option to store the sender information in Exchange to the recipient field in ELO and vice versa.

Root: This option is only available via Advanced. Select what ELOxc will interpret to be the repository root here. If you do not select an option here, Archive is used by default. This means that the folder path you construct uses the repository root as its starting point. If you select the User option, the path is constructed using the corresponding user folder as its starting point. More information is available on this option under "User" path definitions.

Click the + button below and to the right of the repository root to create a new level of the archive (repository) path.

Folder path options

Type: Select between Constant, Variable, and Field name here. You must select one of the options here.

Constant: The value entered to the Value field is selected directly as the folder name.

Variable: You must enter an ELOxc-specific variable to the Value field, such as PNM. The contents of the variable are then selected as the folder name.

Information: A list of these variables and what they mean is provided in the Tree variables section of the appendix.

Field name: The contents of the field name of the processed object will be chosen as the folder name. More information on field names are available in the appendix, the [MS-OXPROPS] documentation, and in the ELOxc Tools program.

Value: Enter either the name of the folder (for constant types) or the placeholder variable (for variable or field name types) to this field. This field is required.

Icon: Select the type of icon here that a folder is given if it is created by ELOxc. This is also known as the object type. The available options are listed in a drop-down menu. If you do not select anything here, ELOxc will select the default icon for folders at that level of the repository.

Keywording form: Select the keywording form here that a folder is given if it is created by ELOxc. The available options are listed in a drop-down menu. If you do not select anything here, ELOxc will select the default folder keywording form (form ID = 1).

Case: If you do not select anything here, ELOxc will not change the case of any letters used when creating a folder. If you select the Uppercase or Lowercase options, ELOxc will convert all letters to uppercase or lowercase respectively.

Start: This option is only available by selecting Advanced. Enter an integer (starting at 0) to define a starting point for the string generated by the value field. For example, if the string would otherwise be E-mail Correspondence and you enter 7 to this field, the resulting string will be Correspondence.

Len: This option is only available by selecting Advanced. Enter an integer (starting at 0) to define the length of the string generated by the Value field. For example, if the string would otherwise be E-mail Correspondence and you enter 6 here, the resulting string would be E-mail.

Separator: This option is only available by selecting Advanced. This option, which is selected by default, creates a new folder level for each path component. If you clear the option, the path component for this part will be combined with the previous component, allowing you to, for example, combine a constant like E-mails to with a variable like PNM within the same folder name.

Requirements

You must define at least one child path within this action by clicking the + button below and to the right of the repository root. Each entry in this path must contain an entry within the Value field.

Information: Only one sequential target path can be created per Archive Path node. If you wish to store Exchange items to multiple paths in the repository in parallel, you must create multiple Archive Path nodes.

"User" path definitions

An Archive Path action files Exchange items to a standard ELO path by default. However, you can enter the optional attribute root="user" to the ArcPathDef tag, which stores items to the user folder. This means that messages are stored to a path like the following:

The path node must therefore have a way to uniquely identify the users and associate a user in ELO with an Exchange account. There are several ways to accomplish this.

In the figure above, ELOxc can use either the Name, Windows user, or E-mail address field to detect this user's user folder in which to store e-mails. The following table shows which ELO user properties are checked against which Active Directory properties to create this assignment.

Information: If you select the root="user" attribute, ELOxc automatically checks all of the account properties shown above to create an association. You do not need to enter additional settings to the ELOxc console to check these fields.