Depending on the actions configured, different data is retrieved during element processing 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 data source container that the element was found in, and "EloGuid", which is determined when an element is archived.

However, the data fields that are available largely depends on the respective data source. With Exchange archiving, these fields are called PidTags, which are defined statically and can be called via the REST API or the ELOxc Console.

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