Scribd
Upload
11 views4 pages

Transformation

Uploaded by

Ishanth Swaroop
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views4 pages

Transformation

Uploaded by

Ishanth Swaroop
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Transform Map and Robust Transformation engine.

Transform Maps

• Transform Maps are a core feature in ServiceNow used for importing and transforming data
from external sources into ServiceNow tables. They are commonly used with import sets.
• It establishes the connections between the fields in a given import set, and the fields
found in a pre-existing ServiceNow table (such as Incident [incident] or User [sys_user]).
• These maps are crucial in ensuring that data is accurately imported into the correct
location within the system.
• It allows administrators to specify destinations for imported data on any tables. One of
the key benefits of transform mapping is its simplicity – linking source fields on an
import set table with destination fields on any table is as easy as dragging and dropping.
• This flexibility allows you to map source and destination fields in a dynamic way.
Key Feature:
1. Auto-mapping: Always double-check that the system is mapping fields accurately,
especially when dealing with sensitive information like encrypted passwords.
2. Mapping reference fields: Be cautious when mapping reference field data. In some
cases, the sys_id may not exist, which could lead to the ID appearing as the
DisplayValue in the target record.
3. Performance considerations: Keep in mind that field mapping a large number of
reference fields may result in additional performance overhead. The system must verify
that the referenced sys_id exists before executing any choice actions at the field level.
4. Field Mapping: Maps fields from the import set table to fields in the target table.
5. Transform Scripts: Allows for scripting (before/after transformation, onStart/onComplete) to
manipulate data during the transform process.
6. Data Transformation: Transforms data as it moves from the staging table (import set) to the
target table.
7. Coalescing Fields: Defines one or more fields to act as unique keys to determine if a record
should be updated or inserted.
8. Choice action: Create, Update, Ignore

Use Cases:
Importing data from external CSV, Excel files, or databases.
Regularly scheduled data imports and updates.
Simple to moderately complex data transformations.

How It Works:

Create Import Set Table: Data from the external source is loaded into an import set table.
Define Transform Map: Map the fields from the import set table to the target table in ServiceNow.
Run Transform: Execute the transform map to move and transform data from the import set table to
the target table.
Robust Transformation Engine (RTE)

Overview:
The Robust Transformation Engine (RTE) is a more advanced and flexible data transformation engine
introduced in ServiceNow for handling complex data transformations and integrations. It is designed
to be more scalable and robust than traditional transform maps.

Key Features:

Pipeline Architecture: Uses a series of stages and actions to process data through a pipeline.
Flexibility: Allows for complex data transformations, branching, and custom logic.
Performance: Designed for high performance and large data volumes.
Error Handling: Advanced error handling and logging capabilities.
Reusability: Reusable components and scripts for transformations.

Use Cases:

Complex data transformations requiring multiple stages.


Integrations with external systems using REST/SOAP APIs.
High-volume data imports with complex business logic.
Scenarios requiring advanced error handling and logging.

How It Works:

Define Data Source: Configure the data source for the external system (e.g., API, file import).
Create Pipeline: Set up a transformation pipeline with various stages for data processing.
Mapping and Logic: Define mappings, transformations, and business logic within the pipeline stages.
Execution: Run the pipeline to fetch, transform, and load data into ServiceNow.

Differences Between Transform Maps and RTE


Complexity and Flexibility:

Transform Maps: Best for simple to moderately complex transformations. Easier to set up but limited
in flexibility.
RTE: Handles complex transformations and integrations with greater flexibility and scalability.
Performance:

Transform Maps: Suitable for smaller data volumes.


RTE: Optimized for high performance and can handle large data volumes efficiently.
Error Handling:

Transform Maps: Basic error handling.


RTE: Advanced error handling and logging capabilities.
Architecture:

Transform Maps: Linear process from import set to target table.


RTE: Pipeline architecture with multiple stages, allowing for more complex processing flows.
Use Cases:

Transform Maps: Simple data imports and routine data transformations.


RTE: Complex integrations, large data imports, and scenarios requiring sophisticated logic and error
handling.
When to Use Which:
Transform Maps: Use for straightforward data imports where the transformation logic is simple, and
the data volume is manageable.
RTE: Use for complex integrations, large data sets, and scenarios requiring detailed error handling,
custom logic, and high performance.
Conclusion
Both Transform Maps and the Robust Transformation Engine have their unique strengths and are
suited to different types of data transformation tasks in ServiceNow. Transform Maps are ideal for
simpler use cases, while RTE provides the flexibility and power needed for more complex and large-
scale integrations.

You might also like