Technical node name: ItemsTreeDef

The ItemsTreeDef node is created automatically whenever a new action tree is created. It is the only node type that can only exist once within an action tree and that is not listed along with the other action types.

Includes: The Includes section is new in ELOxc EWS 10. Use the Includes to use a template in an action tree (see previous section). The use of includes is optional.

Click the [+] button to add another include to the node.

Mailbox: Use this option to select Exchange accounts that will be processed by this action tree. If a mailbox has already been added to the tree through an include, you do not need to add it again here.

Select the type of mailbox from the drop-down list, then enter the account User Principal Name to the field. While you enter text to the field, an Active Domain query runs to help you narrow down the selection.

Information: Regardless of what you enter here, the ELOxc_USERS group is always added automatically to this node. If this group does not exist on the domain or it doesn't contain any users, nothing further will happen. The group will not be created on the domain. However, if there are any users in this group, they will always be processed by all action trees.

Click the [+] button to add another mailbox to the node.

Archived e-mails: This parameter defines what Exchange items are processed by the action tree. When an action tree moves Exchange items to the ELO repository with an Archive action and the action is recorded on the Exchange store with a subsequent Commit action, those items contain an "archived" attribute. Archived e-mails = Yes will then process these items.

Archived e-mails = No will process all other Exchange items - non-archived Exchange items, or archived Exchange items that have not been committed.

The Ignore causes all items to be processed, regardless of whether an item has been archived.

Minimum E-mail Age: This field filters Exchange items by age. It must be entered in the format ddd:hh:mm:ss, where d stands for days, h stands for hours, m for minutes and s for seconds.

Information: The Archived e-mails and Minimum e-mail age options are examples of Restriction settings. You can change all Restriction settings by clicking All options. See below for more information about property-based restrictions.

Entry Points: Enter where ELOxc will start looking for Exchange items within a mailbox account.

Enter a backslash here, followed by whatever folder names you wish. An entry of at least \ is required here. Several variables can be used for this field (such as {%INBOX}), which can be mixed with static paths like \{%SENTMAIL}\ELO. See the appendix for a list of these variables.

Classes: Enter a message class to this field, such as IPM.Note. An entry here is required.

Information: An action tree node requires an entry for Archived E-Mails, Minimum E-Mail age, Entry points, and Classes.

Named properties

Named properties enable ELOxc to take the contents of a specific e-mail property (field name) into account within an action tree. If the field name corresponds to the settings you make here, the tree will continue down the True branch. If not, the tree will continue down the False branch (if it exists).

This is particularly useful if you have used a Tag action in a previous action tree and wish to take the tag into account within the current action tree.

After you have defined the tag name and value, you can search for the tag and its value by using a named property restriction.

Value: You can enter a value to this field if you want to search for a specific value within the tag. This field is only taken into account with the BYVALUE check mode.

Tag name: Enter the exact property name (field name) that you want to search.

CheckMode: Three options are available for the check mode. EXISTS simply checks whether the tag exists in the Exchange item. MISSING returns true if the tag is not set in the Exchange item. Select BYVALUE if you want to check the contents of the tag. Note that this third option requires that the tag exists as well.

CompareMode: Select how the contents of the tag are compared with the value entered to Value. This option is only taken into account with the BYVALUE check mode.

SUBSTRING will return true if the text in Value is found anywhere within the tag.

PREFIX will return true if the text in Value is found at the start of the tag.

EXACT will only return true if the text in Value is exactly the same as the contents of the tag.