Looking for the previous version? View v2024.06 documentation →
Validation using Length Check Business Rule
Overview
The Length Check business rule validates that the character length of values in a specified column falls within an acceptable range. It is commonly used to detect truncated or padded data after an ETL transformation.
Prerequisites
- You are logged in to Data Trust with a Pro-User or Admin Pro-User role.
- An RDBMS connection has been configured and the target column contains string-type data.
Steps
Path: Data Trust › Scenario Studio › Scenario Builder › Validation using Length Check Business Rule
Navigate to the Scenario Studio module and select the Validation using Length Check Business Rule option from the left sidebar or main menu. This opens the scenario builder canvas where you will configure the data source connections, transformation rules, and execution settings.
Drag the Rdbms Widget from the widget palette and drop it onto the scenario canvas. Positioning the widget opens its configuration popup where you will set the connection, table, and any additional options.
Select the appropriate connection from the dropdown to link this widget to its data source. Choosing the correct connection profile ensures the scenario reads from or writes to the intended database or file system.
The Navigator panel displays the available databases, schemas, and tables for the selected connection. Expand the tree to locate the required table or view, then click Select to add it to the widget configuration.
The Navigator panel displays the available databases, schemas, and tables for the selected connection. Expand the tree to locate the required table or view, then click Select to add it to the widget configuration.
The Validation Rules tab lists all available business rule widgets that can be applied to the selected dataset. Drag the required rule widget onto the canvas, configure its threshold or pattern, then save before moving to the next step.
Drag the Length Check Widget from the widget palette and drop it onto the scenario canvas. Positioning the widget opens its configuration popup where you will set the connection, table, and any additional options.
The Validation Rules tab lists all available business rule widgets that can be applied to the selected dataset. Drag the required rule widget onto the canvas, configure its threshold or pattern, then save before moving to the next step.
The Additional Settings panel provides advanced configuration options such as custom SQL filters, join conditions, and performance tuning parameters. Configure only the settings relevant to your scenario — leave optional fields at their default values unless a specific behaviour is required.
Drag the Email Widget from the widget palette and drop it onto the scenario canvas. Positioning the widget opens its configuration popup where you will set the connection, table, and any additional options.
The Email widget sends an automated result notification to configured recipients after the scenario finishes executing. Provide the recipient addresses, subject, and choose whether to attach the exception report or include a summary in the email body.
Click the Execute button to trigger the scenario and begin processing data from the configured sources. The scenario transitions to Monitor mode where you can track real-time execution progress and view interim results as each step completes.
The Validation Execution Summary page presents the full outcome of the scenario execution including record counts, match rates, and any detected exceptions. Drill into exception records to inspect individual mismatches and use the Export to CSV option to share results with stakeholders.
The Email widget sends an automated result notification to configured recipients after the scenario finishes executing. Provide the recipient addresses, subject, and choose whether to attach the exception report or include a summary in the email body.
The 13Click on Exception Data page presents the full outcome of the scenario execution including record counts, match rates, and any detected exceptions. Drill into exception records to inspect individual mismatches and use the Export to CSV option to share results with stakeholders.