Page Operations
Browse SpaceDescription
You can use the Transformation job entry to execute a previously defined transformation.
Options
| Option | Description |
|---|---|
| Name of the job entry | The name of the job entry. This name has to be unique in a single job. A job entry can be placed several times on the canvas, however it will be the same job entry. |
| Name of transformation | The name of the transformation to start. |
| Repository directory | The directory in the repository where the transformation is located. |
| Filename | If you're not working with a repository, specify the XML filename of the transformation to start. |
| Specify log file | Check this if you want to specify a separate logging file for the execution of this transformation. |
| Name of log file | The directory and base name of the log file (for example C:\logs) |
| Extension of the log file | The filename extension (for example: log or txt) |
| Include date in filename | Adds the system date to the filename. (_20051231) |
| Include time in filename | Adds the system time to the filename. (_235959) |
| Logging level | Specifies the logging level for the execution of the transformation. See also the logging window in .14 Logging |
| Copy previous results to arguments | The results from a previous transformation can be sent to this one using the "Copy rows to result" step |
| Arguments | Specify the strings to use as arguments for the transformation. |
| Execute once for every input row | Support for "looping" has been added by allowing a transformation to be executed once for every input row. |
| Clear the list or result rows before execution | Checking this makes sure that the list or result rows is cleared before the transformation is started. |
| Clear the list of result files before execution | Checking this makes sure that the list or result files is cleared before the transformation is started. |
Note: you can use variables ${path} in the filename and transformation name fields to specify the transformation to be executed.