Step 1: Create a Validation pipeline

Create a Validation pipeline named โ€œUserName_Acc_customers_validationโ€ and define it as follows:

  • To go to the Validation pipeline, on the left side panel, click โ€œValidation pipelineโ€ under the โ€œData managementโ€ menu.

  • To create a new validation, click on the [+ Validation pipeline] button.

  • The Details tab is selected by default. To define the Validation pipeline:

    1. Enter Validation Name as โ€œUserName_Acc_customers_validationโ€.

    2. Optionally enter a description for this Validation pipeline.

    3. To define a target entity for this Validation pipeline, select the target entity from the drop-down menu as โ€œUserName_Acc_customersโ€.

  • To create a new Step, go to the Code tab and expand the Validation steps function.

  • To create a new step, click on the [+ Step] button.

  • A new Step is created with the label โ€œDescriptionโ€.

  • To give the Step a more meaningful name, click the text โ€œDescriptionโ€ and rename it to โ€œcheck for mandatory fieldsโ€. This Step is defined to check that the values for the mandatory fields: First Name, Last Name, Email, and Phone are entered.

  • To add Criteria bars in the step, click the (+) button. Add four (4) Criteria bars.

  • To check if the value of the โ€œFirst_Nameโ€ field is not set, define the first Criteria bar as follows:

    1. Select Source as Variables>Source_UserName_Acc_customers>First_Name. It is displayed as โ€œSource_UserName_Acc_customers.First_Nameโ€.

    2. Select Operator as โ€œIs Not Setโ€.

  • To check if the value of the โ€œLast_Nameโ€ field is not set, define the second Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>Last_Name. It is displayed as โ€œSource_UserName_Acc_customers.Last_Nameโ€.

    2. Select Operator as โ€œIs Not Setโ€.

  • When two Criteria bars are defined, they are grouped together by the AND operator. To add a third Criteria bar to the AND group, ensure to click the (+) immediately below the second Criteria bar.

  • To check if the value of the โ€œEmailโ€ field is not set, define the third Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>Email. It is displayed as โ€œSource_UserName_Acc_customers.Emailโ€.

    2. Select Operator as โ€œIs Not Setโ€.

  • To check if the value of the โ€œPhoneโ€ field is not set, define the fourth Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>Phone. It is displayed as โ€œSource_UserName_Acc_customers.Phoneโ€.

    2. Select Operator as โ€œIs Not Setโ€.

  • To check if the values entered are just empty strings, add four (4) more Criteria bars.

  • To check if the value of the โ€œFirst_Nameโ€ field is empty, define the fifth Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>First_Name. It is displayed as โ€œSource_UserName_Acc_customers.First_Nameโ€.

    2. Select Operator as โ€œIs Emptyโ€.

  • To check if the value of the โ€œLast_Nameโ€ field is empty, define the sixth Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>Last_Name. It is displayed as โ€œSource_UserName_Acc_customers.Last_Nameโ€.

    2. Select Operator as โ€œIs Emptyโ€.

  • To check if the value of the โ€œEmailโ€ field is empty, define the seventh Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>Email . It is displayed as โ€œSource_UserName_Acc_customers.Emailโ€.

    2. Select Operator as โ€œIs Emptyโ€.

  • To check if the value of the โ€œPhoneโ€ field is empty, define the eighth Criteria bar:

    1. Select Source as Variables>Source_UserName_Acc_customers>Phone. It is displayed as โ€œSource_UserName_Acc_customers.Phoneโ€.

    2. Select Operator as โ€œIs Emptyโ€.

  • Finally click on the logical operator โ€œANDโ€ to make it โ€œORโ€. This means if any of these Criteria bars are not valid or empty, proceed to the actions.

  • To define Actions, go to the Code tab>On True section of Step 1. Add four (4) Actions by clicking the (+) button. If the criteria is validated to True, a sequence of actions in the โ€œOn Trueโ€ section will be executed. In this case, the error response will be returned if the criteria is valid and any of the fields is not present or contains empty strings. Here, the details of the response are configured in case of โ€œOn Trueโ€.

  • To define the first Action to update the errorcode in the Response as โ€œ400โ€:

    1. Select Action as โ€œUpdate Variableโ€.

    2. Select Target variable as Response>errorcode. It displays as โ€œResponse.errorcodeโ€.

    3. In the Value, type the number as โ€œ400โ€ and press Enter.

  • To define the second action to update the message in the โ€œResponseโ€:

    1. Select Action as โ€œUpdate Variableโ€.

    2. Select Target variable as Response>message. It displays as โ€œResponse.messageโ€.

    3. In the Value, type the text as โ€œComplete mandatory fields: First Name, Last Name, Email and Phone.โ€ and press enter.

  • To define the third action to update the status of the โ€œResponseโ€:

    1. Select Action as โ€œUpdate Variableโ€.

    2. Select the Target variable as Response>status. It displays as โ€œResponse.statusโ€.

    3. In the Value, type the text as โ€œMissing mandatory field(s)โ€ and press Enter.

  • Add the last Action in the section as โ€œExit Validationโ€ that exits with the value โ€œfalseโ€. Based on the value of True or False, the On Validation step success or On Validation step fail function in the Validation>Code tab is executed.

    1. Select Action as โ€œExit Validationโ€.

    2. In the โ€œExit Withโ€ field, type โ€œfalseโ€ and press Enter.

  • To check if the phone number is valid, add Step 2 and label it as โ€œcheck if phone number is validโ€. This Step will verify if the phone number entered is numeric and the length is between 7 and 10 digits.

  • To verify the phone number data type, minimum length and maximum length, add three (3) Criteria bars by clicking the (+) button in the โ€œCriteriaโ€ tab.

  • To verify if the phone number is of numeric value, define the first Criteria bar as follows:

    1. Select Source as Source_UserName_Acc_customers>Phone>isNumeric(). It is displayed as โ€œSource_UserName_Acc_customers.Phone.isNumeric()โ€.

    2. Select Operator as โ€œIs Equalโ€.

    3. Enter the Value as โ€œtrueโ€.

  • To verify if the phone number length is less than or equal to 10, define the second Criteria bar as follows:

    1. Select Source as Source_UserName_Acc_customers>Phone>length(). It is displayed as โ€œSource_UserName_Acc_customers.Phone.length()โ€. This measures the length of the strings entered into the field.

    2. Select Operator as โ€œLess Than Equal toโ€.

    3. Enter the Integer value as โ€œ10โ€.

  • To verify if the phone number length is greater than 7, define the third Criteria bar as follows:

    1. Select Source as Source_UserName_Acc_customers>Phone>length(). It is displayed as โ€œSource_UserName_Acc_customers.Phone.length()โ€. This measures the length of the strings entered into the field.

    2. Select Operator as โ€œGreater Thanโ€.

    3. Enter the Integer value as โ€œ7โ€.

  • Keep AND as the logical operator. This means all of the Criteria bars must return true before executing the Code tab>On True section. If any of the Criteria bars does not return true, the Code tab>On False section Actions will be executed. The Criteria tab should be as per the image below.

  • To define the actions if the Criteria returns true, go to the Code tab>On True section of โ€œStep 2โ€ to define the sequence of actions. Add an Action by clicking the (+) button.

  • To exit validation if the Criteria returns true, define the action as follows:

    1. Select Action as โ€œExit Validationโ€.

    2. In the โ€œExit Withโ€ field, type โ€œtrueโ€ and press Enter. Based on the value of the Exit Validation as true, the Validation>Code tab>On Validation step success section is executed followed by the execution of the โ€œOn Exitโ€ section. If no Action in the On Validation step success section of Validation>Code tab is configured, only the โ€œOn Exitโ€ section is executed.

  • To define the response details in case invalid customer phone data is encountered, go to the Code tab>On False section. Add three (3) Actions by clicking the (+) button.

  • To define the response message, define the first action to update the message in the Response.

    1. Select Action as โ€œUpdate Variableโ€.

    2. Select Target Variable as Response>message. It displays as โ€œResponse.messageโ€.

    3. In the Value, type the text as โ€œPhone number provided is invalid.โ€ and press Enter.

  • To define the response status, define the second action to update the status of the โ€œResponseโ€ as โ€œinvalid dataโ€ .

    1. Select Action as โ€œUpdate Variableโ€.

    2. Select Target Variable as Response>status. It displays as โ€œResponse.statusโ€.

    3. In the Value, type the text as โ€œinvalid dataโ€ and press Enter.

  • To define the response error code, define the third action to update the errorcode in the โ€œResponseโ€ as โ€œ401โ€.

    1. Select Action as โ€œUpdate Variableโ€.

    2. Select Target Variable as Response>errorcode. It displays as โ€œResponse.errorcodeโ€.

    3. In the Value, type the number as โ€œ401โ€ and press Enter.

  • Add the last action in the section to define โ€œExit Validationโ€ action as โ€œfalseโ€. Based on the โ€œfalseโ€ value, the โ€œOn Validation step failโ€ section of the Validation>Code tab is executed.

    1. Select Action as โ€œExit Validationโ€.

    2. In the Exit With field, type โ€œfalseโ€ and press Enter.

  • To save the Validation pipeline, click the [Save] button.

  • To publish the Validation pipeline, click the [Publish] button.

Last updated