Transformation Step
Using the Transformation step, you can create a new map, open the selected map, 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.
Note: You can save a process with Transformation Step using File > Save or Ctrl+S. However, if you keep the cursor in the Choose A Map Config map selection field and then save, the process is marked dirty and the process is not saved. You need to click outside the map selection field and then save.
To add a Transformation step:
1. Drag and drop a 
Transformation step from the Palette to the canvas.
Transformation step from the Palette to the canvas.2. Double-click the step on the canvas to open the Step Properties tab.
3. Type a unique name for the step.
4. Specify the step properties.
For more information, see Adding Steps.
Transformation Step Properties
Name | Description |
|---|---|
Name | Unique name for the step. |
Description | (Optional) Description for the step. |
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. |
 Transformation file (.tf.xml) | Select either of the following: • Use Copy of Transformation File: 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. • Use Existing Transformation File: Use the selected map runtime configuration without creating a copy of the file. Tip... 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. |
Error Handling | Select either of the following: • Stop Process - (Default) All the steps after the current step are skipped or the entire process is stopped (depending on how you have the error logging options set) if this step stops due to an error. • Ignore Error - The remaining steps in this process are executed even if this step stops due to an error. This is useful when you want to write a Decision step that can test for the error state of a previous step. |
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 map 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. If the map configuration file contains macro sets, then the macro sets are automatically added to the process and displayed on the Process > Configuration tab > Macros section. Note: You can save a process with Transformation Step using File > Save or Ctrl+S. However, after saving, if you keep the cursor in the Choose A Map Config map selection field and then click on the editor, the process is marked dirty even if no changes are made. |
Connections | For non-SQL based source and target connections, this topic displays the following information for the specified map or the runtime configuration file: • Source and Target Connections • Connectors • SQL Session - This column is blank for non-SQL based connections. • Schema Mismatch Note: The values are used from the map RTC. To change the values, edit the map RTC and click Refresh. The connection information is updated. For information about SQL session and Schema Mismatch, see Configuring SQL Sessions and Setting Error Handling Preferences, respectively. For SQL-based source and target connections, you can select the SQL session from the SQL Session drop-down menu. The SQL sessions from the Configuration tab are available in the SQL Sessions drop-down menu. If the process contains multiple steps or multiple sources/targets in a single transformation step, it is unlikely that you will share a single session to that database because continuously connecting/disconnecting to the same database is very expensive in terms of performance. Also, some databases does not allow more than one connection to it. Sharing sessions allows you to do transactional commits that is, if an error occurs, you can backup everything related to the session. When you select a .map.rtc file for a new process transformation step, the Transformation Sessions dialog is displayed. On the left side, it shows each source and target within the map that supports SQL sessions. For each of these, you can select any of the following options: • New: Select this option if you want a new session for the required sources/targets. Specify the session information. The new session is also displayed on the Configuration tab. You can select the New option if you want to share this session with targets in the map or anything else in the process. • Existing: If other steps in the process has a session for the same database used in the map, then you can use that session. You can select an existing session for each source and target. • Use Map: Select this option if the process does not have any other database session related needs and the map has only one source or target that needs to open and close the database. After selecting the required option, click OK to close the Transformation Sessions dialog. |
Last modified date: 10/22/2024