Distributed update scenario

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

You can configure the distributed mappings created using the Distributed-transfer-scenario so that when a request transferred with ownership to the Apex Global East Bug Tracking form is modified, the original copy in the Apex Global West Bug Tracking form is updated. The Apex Global East form retains ownership of the request.

Distributed updates require compatible distributed mappings on the source and target servers. Requests transferred without ownership cannot be modified on the target server, so this topic is not applicable to them.

For overview information, see Distributed-updates.

Related topics

Types of distributed operations

Understanding-distributed-operation-use-cases

Distributed-transfer-scenario

To configure a distributed update for the Apex Global bug tracking forms

  1. Create distributed mapping for both bug tracking forms if not done earlier.
    For more information, see To create distributed mappings for the Apex Global bug tracking forms.
  2. In Developer Studio, open the distributed mapping used by the Apex Global West Bug Tracking form on the sanfrancisco server.
  3. In the Options panel, select the appropriate option from the When to Update list.
    Distributed Mapping editor — When to Update list in Options panel
    When_to_Update.gif
  4. Save your changes.

 

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