Depending on the actions configured, different data is retrieved while messages are processed in the action tree and stored in the validity range of the respective action tree for all actions. Good examples of this are the fields "EloRootPath", which represents the path of the mailbox that the message was found in, and "EloGuid", which is determined when a message is archived.

However, the majority of the available properties depends on the respective catalog. With Exchange archiving, these fields are called PidTags, which are defined statically and can be called in ELOxc Manager.

The available properties are always (static or dynamic) context-dependent, since they must be applied in the configuration of the actions so they can be read. In addition, they are determined by the processed message, which is subjected to configured actions following selection by an action tree.