Description:
This step evaluates an expression and sets the value during the ETL transformation.
Inputs
- transforms – Configure transform list
Returns
- None
Usage:
Prerequisite:
The ETL process engine service should be running to execute the ETL definitions.
Example:
Let’s build and execute the “clsComputeExpressionSetValueDef” example.
- Create a new ETL definition called “clsComputeExpressionSetValueDef” and open the definition in designer mode.
- Drag “clsInputCSV, clsGroupByTransform, clsComputeExpressionSetValue, and clsOutputCSV” steps to the canvas.
- Connect the dots between the “clsInputCSV” step and other steps, as shown above.
- Define a variable or a global to store the virtual path.
- Click the "clsInputCSV" step to configure its "Required" properties. Provide a name for the step. Provide the path to the input CSV file on the application server. Select the ETL data schema from the drop-down list. Note: The column names in the schema should match the columns in the input file. Click the Save button.
- Click the "clsInputCSV" step to view its "Optional" properties. Select the Show Schema button. The pop-up window renders the schema columns as shown below. This function helps to understand the schema at a glance.
- Click the "clsGroupByTransform" step to configure its "Required" properties. Provide a name for the step. Click the button to configure the columns and operation type. Click the Save button.
- Click the "clsGroupByTransform" step to configure its "Required" properties. Click the button to configure the columns. A pop-up window will appear for configuration. Click the Add Row (+) button to insert an empty row. Select the column to group by. Click the Save button. You may add multiple columns for transformation by using the Add Row button.
- Click the "clsGroupByTransform" step to configure its "Required" properties. Click the button to configure the operation type. A pop-up window will appear for configuration. Click the Add Row (+) button to insert an empty row. Select the value column from the drop-down list. Select the operator type. Select the output column from the drop-down list. Click the Save button. You may add multiple columns for transformation by using the Add Row button.
- Click the "clsComputeExpressionSetValue" step to configure its "Required" properties. Provide a name for the step. Click the button to configure the expression list. Click the Save button.
- Click the "clsComputeExpressionSetValue" step to configure its "Required" properties. Provide a name for the step. Click the button to configure the expression list. A pop-up window will appear for configuration. Click the Add Row (+) button to insert an empty row. Provide the expression, value expression (for match), and else value expression (for no match) on evaluation. Click the Save button. You may add multiple columns for transformation by using the Add Row button.
- Click the "clsOutputCSV" step to configure its "Required" properties. Provide a name for the step. Provide the path to the output CSV file on the application server. Click the Save button.
- Click the "clsOutputCSV" step to configure its "Optional" properties. Provide a name for the step. Provide the variable or global reference to hold the virtual output path. Click the Save button.
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.
- Save the ETL definition, create a new ETL instance, and execute. Render the ETL instance. Click the ETL step to view its properties. The “clsComputeExpressionSetValue” step should transform the output file by evaluating the expression result. The variable or global reference holds the output file virtual path as shown below.
Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-drop) to your FlowWright ETL Process Definition (XML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after import. Then, save the definition to confirm the changes.