Distributed delete scenario

When the master copy of a distributed request is deleted, all copies in the active ownership chain are also deleted.

For example, suppose a request created in the Acme West Bug Tracking form is transferred with ownership to the Acme East Bug Tracking form. If you delete the copy of the request in the Acme East form, the original copy in the Acme West form is also deleted. (AR System does not delete copies of the request in either form that are not in the active ownership chain.)

For more information, see Request ownership chains.

 To configure a distributed delete operation on the To server

1. In Developer Studio, select File > New > Filter.
2. Select the To (chicago ) server, and click Finish.
3. In the Associated Forms panel of the Filter editor, click Add.
4. In the Form Selector, select the Acme East Bug Tracking form, and click OK.
5. In the Execution Options panel, set the options shown in the following figure:
   
   Filter editor — Execution Options panel
   
6. Right-click the If Actions panel, and select Add Action > DSO.
7. In the Type list in the DSO panel, select Delete.
8. Fill in the other fields as shown in the following figure, then select File > Save.
   
   Filter editor — DSO Delete action
   
9. In the Save Filter As dialog box, enter a name for the filter, such as Acme Bug Distributed Delete, then click OK.
    Now, when a request is deleted from the Acme West Bug Tracking form, this DSO action deletes the request with the same Request ID in the Acme East Bug Tracking form on the chicago server.