This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Setting up chained distributed transfers

This section contains information about:

You can set up a distributed environment involving more than two locations in which the servers are "chained," creating a staggered distribution effect.

For example, in this section, you create a distributed transfer on the sanfrancisco server that sends a request from the Acme West Bug Tracking form to the Acme East Bug Tracking form on the chicago server whenever someone creates or modifies a bug request for Choice Desk Chairs or Superior Side Chairs in the Acme West form.

You then create a distributed transfer on the chicago server that sends any bug request for Superior Side Chairs that is transferred into the Acme East Bug Tracking form to the Acme Canada Bug Tracking form on the toronto server.

The following figure shows an example of a chained distributed transfer.

Chained distributed transfer example

To set up a chained distributed transfer

  1. Perform these tasks:
    • Create the Acme West Bug Tracking form on the sanfrancisco server.
    • Create the Acme East Bug Tracking form on the chicago server.
    • Create the Acme Canada Bug Tracking form on the toronto server.
    • Add basic distributed fields to the forms.
      See Adding distributed fields to forms.
    • Add distributed mappings and filters to the sanfrancisco and chicago servers according to the procedures in Distributed operations scenarios.
  2. Create a distributed mapping between the chicago and toronto servers to transfer bug requests for Superior Side Chairs from the Acme West Bug Tracking form to the Acme Canada Bug Tracking form with ownership:
    1. In Developer Studio, select File > New > Distributed Mapping.
    2. Select the From (chicago ) server, and click Finish.
    3. In the Distributed Mapping editor, fill in the Basic panel as shown below:

      Distributed Mapping editor — Basic panel for chicago server
    4. Fill in the Options panel as shown below:

      Distributed Mapping editor — Options panel
    5. In the Transfer to Target panel, click Auto Map.
    6. In the Auto Map dialog box, select Match IDs, and click OK.
    7. In the Return from Target panel, click Auto Map.
    8. In the Auto Map dialog box, select Match IDs, click OK, then select File > Save.
    9. In the Save Distributed Mapping As dialog box, enter Acme E to C Bug Track, then click OK.
  3. Create a filter with a DSO Transfer action on the From server:
    1. In Developer Studio, select File > New > Filter.
    2. Select the From (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. In the Run If Qualification panel, click the ellipsis button.
    7. In the Expression editor, enter the following qualification, then click OK:
      
      'Product' LIKE "S%"
      The qualification states that the filter action should be executed when the product name on the Acme East Bug Tracking form begins with the letter S.
    8. Right-click the If Actions panel, and select Add Action > DSO.
    9. In the Type list in the DSO panel, select Transfer.
    10. Select Override Loop Detection, then select File > Save.
      See Avoiding infinite loops.
    11. In the Save Filter As dialog box, enter a name for the filter, such as Acme E to C Bug Track, then click OK.
Was this page helpful? Yes No Submitting... Thank you

Comments