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.

Configuring DSO Transfer actions

Use distributed transfers to transfer a request from one form to another.

To perform a distributed transfer operation, you must create a distributed mapping (see Creating distributed mappings) plus a filter or an escalation with a DSO Transfer action on the source server.

To configure a DSO Transfer action

  1. Create a filter or escalation (see Workflow objects).
  2. In the Associated Forms panel of the Filter or Escalation editor, add the form designated as the From form in the distributed mapping that you plan to use for this transfer.
  3. In the Execution Options panel, select the filter trigger criteria.
    Typically, the trigger criteria for distributed transfers is Modify or Submit.
  4. Right-click the If Actions panel, and select Add Action > DSO.
  5. In the Type list, select Transfer.
  6. Fill in these fields:
    • Mapping — The mapping to use for the transfer. Enter a mapping by clicking the ellipsis button next to this field and then using the Object Selector.
      This field enables you to use one filter or escalation to "broadcast" the same request to multiple destinations by specifying different mappings in separate filter actions. See Setting up broadcast distributed transfers.
      You can enter a field reference or keyword in the Mapping field, but do not add any text after the field reference or keyword. (The system removes the additional text.)
    • Distributed Pool — The pool to use to process the action.
      The Object Selector allows you to select either the distributed pools or the field from which you want to source the pool name.
      To select a distributed pool, you must first create a distributed pool. See Distributed pools and Enabling distributed pools.

      Warning

      To ensure that DSO actions are executed in the correct order, assign all related DSO actions to the same distributed pool. For example, all DSO actions associated with the same form should use the same distributed pool.

    • To Server — The physical name or the logical name of the target server for the transfer.

      Note

      Logical server names appear in the list enclosed in the dollar sign.

      If you specify a value in the Mapping field, this field is ignored.
      If you do not specify a value in the Mapping field, DSO uses this value and the value in the To Form field to determine which mapping to use.
    • To Form — The name of the target form for the transfer.
      If you specify a value in the Mapping field, this field is ignored.
      If you do not specify a value in the Mapping field, DSO uses this value and the value in the To Server field to determine which mapping to use.
  7. (Optional) Select Override Loop Detection. See Avoiding infinite loops.
  8. Save the filter or escalation.
Was this page helpful? Yes No Submitting... Thank you

Comments