Skip to main content

Overview

Transform is one of the three main phases of an integration workflow. It maps and transforms data from the source system’s schema to match the destination system’s expected format. The Transform phase determines what data fields are sent to the destination and how they are structured. Transform occurs after data extraction and enrichment, processing each datapoint individually before it reaches the Load phase. This phase ensures that data from different systems can be harmonized and delivered in the format required by your destination system.

How Transform works

During the Transform phase, RWS Integration processes each datapoint extracted from the source system. You define field mappings that specify how source fields should be transformed and mapped to destination fields. Transform supports three types of mappings: simple field-to-field mapping, fixed values, and business rules. Each mapping type serves different purposes and can be combined within a single integration to handle various transformation needs.

Transform mapping types

Simple mapping

Simple mapping directly copies a field value from the source to the destination, optionally renaming it. Use simple mapping when field names differ between systems but the data structure and values remain the same. Examples:
  1. Rename a simple field:
    • From: name
    • To: fullName
    The value of name from the source becomes fullName in the destination.
  2. Map from enrichment data:
    • From: resources.userDetails.age
    • To: age
    Here, if enrichment has added a structure like resources.userDetails, this mapping takes the age value found in resources.userDetails and places it in the top-level age field in the destination.
In both cases, simple mapping ensures fields from either the original or enriched data can be mapped exactly where needed in your output.

Fixed value

Fixed value mapping assigns a constant value to a destination field, regardless of source data. Use fixed values when you need to populate fields with static information that doesn’t exist in the source system. Example:
  • Fixed value: active
  • To: status
This assigns the constant value active to the status field for all records.

Business rule

Business rule mapping applies custom JavaScript logic to transform data. Use business rules when you need calculations, conditional logic, field combinations, or complex data manipulation that simple mappings cannot handle. Example:
  • Business Rule: Convert meters to feet
  • To: HeightInFeet.