Several types of nodes exist for creating ELOxc EWS action trees. To see how to use these nodes in practice, see the Sample action trees chapter.

To create an action within an action tree, place the mouse over an existing action or the action tree root node. A + appears to the right of the action. Click the button. A dialog box opens to select the action type, the name of the action, and the condition.

Type: Select what type of action you want to add to the action tree. The following section describes what each action type does in detail.

Name: Enter a name for the action. This name is optional. It should provide the administrator with information at a glance of what function the action performs in its context.

Condition: Select True or False here. Depending on your selection, the action will then be performed based on the result of the previous action.

Information: It is not recommended to allow an action tree to finish with a state of False. If this status is a valid result of the last action in the action tree, it is recommended to create a Result action to force the tree to result in True. More information on this point is available in the Troubleshooting chapter in the section titled Error messages in valid action trees.

The following sections provide a list of available tree nodes and some general guidance on using them.

Some special considerations apply for encrypted S/MIME messages and message contents. Please see the Troubleshooting chapter for more information on this topic.

Please note: It is important to be aware of the order in which action trees are constructed and to carefully plan the order of operations. Incorrectly constructed action trees can lead to confusing results or even data loss.

For example, placing a Stubbing action before an Archive action may replace message contents with a template before the content is stored in the repository. Placing a Finish action before a Tag action can cause the tag to never be applied. If any number of actions are performed on the Exchange store without a Commit action later on in the tree, they will not be saved to Exchange.

See the Publishing an action tree section at the end of this chapter for notes on how to fix an action tree if it does not work the way you intend.