This documentation supports the 22.1 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Implementing DSO

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


This section contains information about working with distributed fields, mappings, and pools. It also explains how to administer data transfers between forms. Topics include:

To set up distributed operations, follow this process:

  1. Make sure you have the appropriate permissions to configure Remedy Distributed Server Option ( DSO ).
    See Assigning permissions to access objects and requests
  2. Activate DSO  and configure it for your distributed environment.
    See Configuring Distributed Server Option.
  3. Determine which forms you will transfer data from and which forms you will transfer data to.
  4. Determine the amount of control you need over the transferred data:
  5. Determine which distributed fields to add to the forms identified in step 2.
    See Distributed fields.
  6. Add distributed fields to the forms identified in step 2.
    See Adding distributed fields to forms.
  7. Determine whether you will use distributed pools.
    See Distributed pools.
  8. (Optional) Create distributed pools according to your analysis in step 3.
    See Creating and modifying distributed pools.
  9. Determine how to map the forms identified in step 2.
    See Distributed mapping.
  10. Create the required distributed mappings.
    See Creating distributed mappings.

    Unless otherwise noted, this section assumes that you are mapping between two servers. To maintain data integrity on more than two servers, see Chained and broadcast distributed transfers.

  11. Create filters or escalations that define the conditions under which distributed operations occur.
    See Creating workflow to perform DSO operations.
  12. (Optional) Employ some of these advanced functions:
Was this page helpful? Yes No Submitting... Thank you

Comments