Distributed returns

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

A distributed return is used to send an updated request back to the originating server with ownership. Distributed returns are triggered by workflow on the server that returns the request.

For example, after the keyboard is replaced in the example described in Distributed-updates, the status of the master request on the chicago server is changed to Completed. When this change occurs, workflow is triggered and the modified request is transferred back to the sanfrancisco server with ownership, leaving a data-only copy of the request on the chicago server. The request can now be modified on the sanfrancisco server if necessary.

Related topics

Distributed-updates

Distributed-return-scenario

The following figure shows the basic flow of a distributed return. (The request in the darker form has ownership after the operation is completed.)

Distributed return flow
DistributedReturnFlow.gif

For an example of how to set up a distributed return, see Distributed-return-scenario.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*