Action trees are the entry points for processing data in ELOxc. They have an ordinal number, which means that ELOxc follows a predefined processing sequence when running in the default execution modes "once", "interval", and "fix". They also have configuration properties that determine which message set is selected for processing.

1. To create an action tree, click the action tree icon in the instance.

The New action tree dialog box opens.

2. Select a name for the action tree and click the Create button.

Configuration

The area for configuring the processing properties of an action tree opens.

'Selection restrictions' area

The selection restrictions configure the message search that an action tree performs for each permitted mailbox folder according to various criteria.

Archiving status: This setting determines whether a message can already be marked as archived or not. If the archiving status is irrelevant, it can be ignored.

Minimum age property: The property usually used is "PidTagMessageDeliveryTime" (Option "sent"). Use "PidTagEndDate" (Option "enddate") when processing calendar items. If a minimum age is required depending on the last change to an item, you can also configure "PidTagLastModificationTime" (Option "lastmodified").

Minimum age: Enter the minimum age in the format ddd:hh:mm:ss. This specifies the required age of a message in relation to the selected minimum age property. Newer messages are not selected.

Minimum size/Maximum size: These values are interpreted as the interval of the permissible item size. If you set the value 0 (zero), only interval values that are not 0 (zero) are checked.

Sensitivity: This is the same as the Outlook option of the same name.

Attachments: The messages can have attachments (Option "ignore"), must have attachments (Option "yes"), or may not have attachments (Option "no").

Flag "Read"/Flag "EverRead": The flag "Read" determines whether the current message is marked as read or unread. "EverRead" indicates whether the message has ever been read, regardless of the current view. Both flags can be ignored. The option "yes" indicates that the respective flag must be set, whereas the option "no" indicates that it must not be set.

Body formats: "Text format", "HTML format", and "Rich text format" refer to the format of the message body. If you want to process a message independently of this setting, we recommend that you set "ignore" in all three values (default setting). In some cases, such as when performing message stubbing, it can be useful to only select messages in HTML or text format. You could also exclude only "Rich text format" with the option "no". However, if you archive whole messages and do not carry out any special actions that affect the message body, you can ignore these three selection restrictions.

Property restriction

The list of property restrictions can also be used to include application-specific processing states in the selection. A processing status is usually set with the "Tag" action. Technically speaking, this is a named property that is set as an additional property for a processed item by another action tree. You can use property restrictions to select these properties later on. It is important to note that the "Tag" action always creates a property pair "Elo<tag name>Base" and "Elo<tag name >Ext" for a tag name. If you want to use the tag name as a property restriction, you have to use the whole internal name.

Example: The name "MyTest" is configured in "Tag". ELOxc creates the property pair "EloMyTestBase" and "EloMyTestExt". If you want to configure a property restriction for a new action tree, you need to enter "EloMyTestBase" or "EloMyTestExt" as the property name. "Base" always contains the processing timestamp and "Ext" the configured value of the "Tag" action.

If the usage type "exists" (default value) is configured, Exchange server only checks whether for example "EloMyTestExt“ exists (the option "missing" also exists as well as "exists"). If, on the other hand, you also want to include the value of the property in the selection, you must select "byvalue". The match mode controls other aspects of the string comparison.

Selection and processing variables

The selection and processing variables help to optimize the processing of an action tree, which takes place in three steps:

1. Selection: The program searches for and selects messages.

2. Processing: The actions of the tree are executed for each message.

3. Completion: The message is passed to the change, deletion, or move list.

Maximum selection: This option determines the maximum number of selectable items per mailbox. 0 removes the restriction.

Selection variable and Selection throttle [ms]: The selection variable determines the maximum number of hits for each Exchange search. The selection throttle reduces the frequency of search requests.

Processing variable and Processing throttle [ms]: The processing variable determines the number of messages that a worker can load from the Exchange server in a single request. The processing throttle reduces the frequency of these requests.

Update list: The update list determines how many internally cached items there are to update (Exchange server only). The items are updated when this maximum is reached or ELOxc has finished processing a folder. Attachments are deleted immediately.

Deletion list: The deletion list determines how many internally cached items there are to delete. The items are deleted when this maximum is reached or ELOxc has finished processing a folder.

Move list: The move list determines how many internally cached items there are to move. The items are moved when this maximum is reached or ELOxc has finished processing a folder.

"List templates" area

In the "Templates" area, you can create list templates for use in all action trees. Under "List templates" in an action tree, you can reference the list templates by name. There are templates for mailboxes, entry points, folder filters, and message classes.

"Mailboxes" area

This area contains all mailboxes that the action tree is to process. These entries are made in addition to the possible reference in the "List templates" area. Duplicate mailbox configurations under "List templates" and "Mailboxes" are automatically resolved.

"Entry points" area

Entry points are configured as mailbox paths and designate mailbox folders that need to be entered during processing in order for messages to be selected. Mailbox folders that are not entered using an entry point, directly or after recursion, are not processed. As in the case of the list templates, duplicate configurations are automatically removed when the configuration is read. If you click the "Value" field, you get a list of available language-independent variables.

"Folder filters" area

Folder filters are subject to the same purge logic as mailboxes or entry points. They contain folder names that, when evaluating the folder hierarchy of a mailbox, ensure that positive matches lead to exclusion of folders.

"Message classes" area

Message classes represent the item type in Exchange. From an Exchange point of view, all items are messages that fall into a certain class. Messages can in fact be calendar entries or contacts, which is determined by the class property "PidTagMessageClass", which has to be configured as an additional selection filter in this area. As with mailboxes, entry points and folder filters, the additional inclusion mechanisms of any possible list templates also apply.

Information: Refer to the