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.

Distributed transfer scenario

To perform a distributed transfer operation from the sanfrancisco server to the chicago server, create a distributed mapping and a filter (or escalation) with a DSO Transfer action on the From (sanfrancisco ) server by performing these tasks:

  1. Add distributed fields to the Acme bug tracking forms.
  2. Create distributed mappings for the Acme bug tracking forms.
  3. Create a filter with a DSO Transfer action on the From server.
  4. Test the distributed mapping.

    After you complete these tasks, a bug request created on the sanfrancisco server for Choice or Superior products is transferred to the chicago server.

    Note

    In this section, you create identical distributed mappings on the From (sanfrancisco) and To (chicago) servers. Such mappings are required for distributed update and return operations, which are covered in the following sections.

Add distributed fields to the Acme bug tracking forms

For overview information, see Distributed fields.

To add distributed fields to the Acme bug tracking forms

  1. Establish the forms and servers to be mapped:

    Object to map

    From

    To

    Server

    sanfrancisco

    chicago

    Form

    Acme West Bug Tracking

    Acme East Bug Tracking

  2. In Developer Studio, log on to the sanfrancisco server.
  3. Open the Acme West Bug Tracking form.
  4. Select Form > Add Distributed Fields.
  5. In the Add Distributed Fields dialog box, select Basic, and click OK.
  6. (Optional) Rearrange the distributed fields added to the form in step 5.
  7. Save the form.
  8. Repeat step 2 through step 7 for the chicago server and its Acme East Bug Tracking form.

Create distributed mappings for the Acme bug tracking forms

Distributed mappings specify which fields on the From form (Acme West Bug Tracking) supply data to which fields on the To form (Acme East Bug Tracking).

For overview information, see Distributed mapping.

To create distributed mappings for the Acme bug tracking forms

  1. In Developer Studio, select File > New > Distributed Mapping.
  2. Select the sanfrancisco server, and click Finish.
  3. In the Distributed Mapping editor, fill in the Basic and Options panels as shown below:

    Distributed Mapping editor — Basic panel for sanfrancisco server


    Distributed Mapping editor — Options panel
  4. In the Transfer to Target panel, click Auto Map, select Match IDs, and click OK.
  5. In the Return from Target panel, click Auto Map, select Match IDs, click OK, then select File > Save.
  6. In the Save Distributed Mapping As dialog box, enter Acme W to E Bug Track, then click OK.
  7. Select File > New > Distributed Mapping.
  8. Select the chicago server, and click Finish.
  9. In the Distributed Mapping editor, fill in the Basic and the Options panels as shown below:

    Distributed Mapping editor — Basic panel for chicago server


    Distributed Mapping editor — Options panel
  10. Configure the Transfer to Target panel, Auto Map dialog box, and Return from Target panel as described in step 4 and step 5.
  11. In the Save Distributed Mapping As dialog box, enter Acme E to W Bug Track, then click OK.

Create a filter with a DSO Transfer action on the From server

To transfer data from a form on the sanfrancisco server to a form on the chicago server, you must create a filter with a DSO Transfer action on the sanfrancisco server.

For overview information, see Creating workflow to perform DSO operations.

To create a filter with a DSO Transfer action on the From server

  1. In Developer Studio, select File > New > Filter.
  2. Select the From (sanfrancisco) server, and click Finish.
  3. In the Associated Forms panel of the Filter editor, click Add.
  4. In the Form Selector, select the Acme West 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, and then click OK:
    
    NOT 'Product' LIKE "P%"
    The qualification states that the filter action should be executed when the product name does not begin with the letter P.
    Thus, when a request is created in the form associated with this filter (the Acme West Bug Tracking form) for a Choice Desk Chair or a Superior Side Chair, the action associated with this filter is executed.
  8. Right-click the If Actions panel, and select Add Action > DSO.
  9. In the Type list in the DSO panel, select Transfer.
  10. To use the default mapping, leave the other fields blank, then select File > Save.
  11. In the Save Filter As dialog box, enter a name for the filter, such as Acme W to E Bug Track, then click OK.

Test the distributed mapping

To test the mapping in this example, open the Acme West Bug Tracking form in a browser, and create some requests for each of the Acme products. All requests submitted for products the Choice Desk Chair and Superior Side Chair products should be immediately transferred with ownership to the Acme East Bug Tracking form. The original request on the sanfrancisco server becomes a data-only request (see Types of distributed transfers).

Was this page helpful? Yes No Submitting... Thank you

Comments