Managing chained distributed transfers

The information in this topic is applicable only for on-premises deployments.

To manage chained distributed transfers, you can control updates, control returns, and delete requests.

Controlling updates

To control updates, select a value other than No Update in the When to Update list in the Options panel of the Distributed Mapping editor.

When to Update list — Options panel of Distributed Mapping editor

Any changes made to a request in the To form of a mapping are sent back as updates to the From form in the mapping.

Controlling returns

To control returns, create a filter that looks for a condition in which Data + Ownership is the Transfer mode. This filter action takes the transferred request and executes another mapping specified in the filter action. The filter action then returns the request to the From form defined in the Transfer mapping.

Deleting requests

Users can delete only the master copy or independent copies of a request in an ownership chain. When the master copy of a request is deleted, all other requests in the ownership chain are also deleted.

You can use the DSO Delete filter action to delete requests that are outside the active ownership chain, or you can use ardist to clear the Master Flag (see Overwriting-the-values-in-distributed-fields). For more information, see Distributed-deletes.