Changes to element fields that occur as a result of actions are not saved until you perform a Commit (CommitDef) action to save the processed elements.

Click the Advanced button in the Options area to open the advanced configuration settings.

By default, the CommitDef action forces the saving of elements (ForcedCommits). This means that when ELOxc makes changes to elements and there are simultaneous changes (possibly caused by users), ELOxc will attempt to enforce its own changes. If an element was not changed during this action, ELOxc does not try to save the element.

The following actions can result in changes to elements and require CommitDef to save the changes:

• CallDef depending on the actions of the subtree called
• CheckinDef by default if element is marked as "archived"
• DeleteDef does not make any changes to fields, but marks the element internally so that it is physically deleted when CommitDef is called
• FinishDef sets the status "finished"
• MatchReplaceDef is the action used to change field values
• StubbingDef replaces the main content. In Exchange, this is the message body.
• TagDef sets a user-specific marker

The MoveDef action is an exception, since it moves an element straight to another container. The result is therefore permanent.

In a Reload action, ELOxc reloads the data of the affected element from the server immediately after they were saved. However, this action is rarely necessary and should only be used in exceptional cases, since the elements can be transferred to new states during processing by an action tree, which may invalidate some assumptions which the configuration of an action tree is based on.