Distributed logical mapping
You can now configure distributed mappings by using temporary server names. Distributed logical mapping is used to define the mapping between logical (temporary) and physical (actual) server names. These mappings are created and stored in the Distributed Logical Mapping form. At run time, the DSO replaces the logical server name with the physical server name in accordance with the mappings in this form. While moving the distributed mappings (or workflow) from the development environment to the production environment, this feature eliminates the need to manually replace the server names in any distributed mapping. Now you only need to replace the physical server name in the Distributed Logical Mapping form. You can use logical server names in DSO actions as well.
For example, in the development environment, you create a logical mapping with the logical server name as destination_server, physical server name as dev_server, and use the logical server name in a distributed mapping. While moving the distributed mapping to the production environment, you only need to replace the physical server name with the actual production server name in the Distributed Logical Mapping form.
With the custom mapping option, you can also use distributed logical mapping to assign a logical (temporary) constant string value for fields whose actual value is not known while developing the distributed mappings. At run time, DSO replaces the logical constant string with actual value from the Distributed Logical Mapping form.
In distributed mapping, a logical name (server name or constant string value) must be enclosed in the dollar symbol ($).
If a constant string from a custom mapping in an existing distributed mapping is enclosed in the dollar symbol ($), you must prefix the dollar symbol with the caret symbol (^), which acts as an escape character. Without this, the constant string is treated as a logical string and DSO replaces it with an actual value from the logical mapping form.