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

Distributed mapping

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

Distributed mapping defines how data is transferred from one form to another, how frequently distributed updates are processed, and how conflicts in distributed operations are resolved. Distributed mapping is typically used to link two fields with matching field IDs or field names between forms. You can also create custom distributed mapping that links nonmatching fields or that links a single field to multiple fields. Distributed mappings are server objects. They are created in the Distributed Mapping editor, and they are stored in the Distributed Mapping form.

Distributed Mapping editor

Configuring a distributed mapping to transfer data between identical forms is a simple process. To transfer data between nonmatching forms, however, you must:

  • Determine which fields in the source form should be mapped to fields in the target form.
  • Consider the results of mapping fields containing different data types. For example, the data types must be compatible, such as strings and integers.
  • Consider the results of mapping fields of unequal size. For example, if the length of a source field exceeds the length of a target field, the distributed operation results in an error.

To ensure that  AR System server uses the type of mapping appropriate for each situation, you can create multiple mappings between forms. Then, when creating the filter or escalation that triggers a distributed operation, you can specify which mapping to use or let the system select a default mapping. See Creating distributed mappings.

You can also override settings in a mapping for a particular distributed operation. See Overriding mapping settings on a per-request basis.

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