User Guide : Designing and Executing Processes : Process Steps and Associated Components : Transformation Step
 
Share this page                  
Transformation Step
In the Transformation step, you can create or edit maps, or you can specify previously created maps to run.
If you need to access a global process variable in this step, make sure it is public. Then, import it into the map you are referencing in the Transformation step. For more information, see Managing Variables.
Transformation Step Properties
After adding a /download/attachments/23921534/Transformation_step.png?version=1&modificationDate=1490069225412&api=v2 Transformation step from the Toolbox Palette to the canvas, you can double-click the step on the canvas and specify the following step properties in the Properties tab displayed at the bottom.
 
Name
Description
Name
Unique name for the step.
Description
Description of the step (optional).
Enabled
Select this option to enable the step for execution. If it is not enabled, then the step on the canvas is grayed-out.
This option is useful when troubleshooting a process, especially when there are numerous steps in the process.
Error Handling
Select either of the following:
• Abort Process - All the steps after the current step are skipped or the entire process is aborted (depending on how you have set the error logging options set) if this step aborts due to an error.
• Ignore Error - The remaining steps in the current process are executed even if this step aborts due to an error. This is selected by default.
Choose a Map Config
Type or click Browse to specify the map runtime configuration file (.map.rtc or .tf.xml) file that must be executed. If a runtime configuration file is not available, then click and select New to create a new map.runtime configuration file.
To open the specified map runtime configuration file, click and select Open. The map runtime configuration file opens in the Map Editor.
Tip:  If you create a new map runtime configuration file or update an existing map runtime configuration file, then click Refresh to re-read the map content for the transformation.
In case the compatibility mode is enabled, then after specifying the file, a pop-up window may be displayed with the following options:
• Create a copy of the transformation file created by the Map Editor
• Use the existing transformation file created by the Map Editor
The default setting depends on the selection in the Process Designer Preferences. To view or change this setting, go to Options > Preferences > DataConnect > Process Designer > Steps.
When Create a copy of the transformation file created by the Map Designer is selected:
• A copy of the map runtime configuration file is created and named as ProcessName$StepName.tf.xml. It is displayed in the project folder. You can open the map runtime configuration file to change connection information and save the file.
• If you change the transformation step name, the .tf.xml file name of the map that is selected within this step is updated automatically.
Note:  If the configured .tf.xml file contains local macros, then you must add the local macro set to the process.
Connections
Specify the following information for the specified map or the runtime configuration file:
• Source and Target Connections
• Dataset
• SQL Session
• Schema Mismatch
Note:  The value for the transformation schema mismatch is used from the map RTC and the Schema Mismatch column in the process is read only. To change the schema mismatch value, edit the map RTC and save it as a new map RTC file. Select this new map RTC in the Transformation step.