Distributed transfer scenario

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

In the procedures on this page, you create identically 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.

To add distributed fields to the Apex Global bug tracking forms

For an overview of the distributed fields, see Distributed-fields.

1. Decide which forms and servers are to be mapped:

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
   

2. In Developer Studio, log on to the sanfrancisco server.
3. Open the Apex Global 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 Apex Global East Bug Tracking form.

To create distributed mappings for the Apex Global bug tracking forms

Distributed mappings specify which fields on the From form (Apex Global West Bug Tracking) supply data to which fields on the To form (Apex Global East Bug Tracking). For an overview about distributed mapping, see Distributed-mapping.

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 fields in the Basic and Options panels as shown in the following images:
   
   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 Apex Global 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 Apex Global E to W Bug Track, then click OK.

To 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 more information, see Creating-workflow-to-perform-DSO-operations.

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 Form Selector, select the Apex Global 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 Apex Global 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 Apex Global W to E Bug Track, then click OK.

 To test the distributed mapping in this example

1. Open the Apex Global West Bug Tracking form in a browser.
2. Create requests for each of the Apex Global products.
   All requests submitted for products the Choice Desk Chair and Superior Side Chair products should be immediately transferred with ownership to the Apex Global East Bug Tracking form. The original request on the sanfrancisco server becomes a data-only request. For more information, see Types of distributed transfers.