Phone Validation using Harmony Batch System

This document provides instructions on utilizing the Harmony batch system for the validation of bulk files using Phone Validation PDP.

The designation of Client Role and Locale within the batch setup indicates the PDP utilized for phone validation processes across various geographical contexts.

Pre Reading

Please ensure you have read and understood the previous configuration steps for Australia and New Zealand.

pageEmail and Phone Validation

Below is the simple illustration of our phone validation processing using a small file in Australia with Harmony Batch System. A more comprehensive guide detailing the instructions on how to set up a batch job can be checked here Harmony Batch System Cleanse Reference Guide.

Steps to run Batch Job

1. Job Config

It is expected that the customer has configured the Setup HostedPhoneValidation PDP prior to executing a batch process.

Log in to HBS UI and select New Cleanse

Select the required Client Role that is attached to the component group that has HostedPhoneValidation PDP added.

Select the Locale as Australia

Example 1: AU Cleanse job profile

2. Input

Click Input on the left panel to display the Input Reader panel. There are seven tabs in this panel, each with its own set of fields.

Refer Page No 14 of the Harmony Batch System Cleanse Reference Guide to get an idea on how to configure the Input file for batch processing.

Quick configuration on how to configure an input file that consists of the fields below is provided here.

Input File: File comprises of Id, Input Phone Number.

Example 2: Sample Input file

General

Choose your input file and correct configuration for your phone file.

Full description of the panel is within Harmony Batch System Cleanse Reference Guide.

Detail Record

Ensure you correctly check the details versus your input file.

Full description of the panel is within Harmony Batch System Cleanse Reference Guide.

Baseline Fields

Very important step as this information forms part of the Logical Record mapping between your input file and what the HBS system requires to process.

Auto populate fields: If you have ticked 'first detail record represents baseline fields' then right click on white panel and retrieve the field names. This will auto populate the fields.

Manually enter fields: Type your input column names into the table within the panel.

Full description of the panel is within Harmony Batch System Cleanse Reference Guide.

Logical Records

HBS Logical Record represents the input baseline fields that are mapped to Harmony data models for batch processing.

The left column "Name" is Harmony name representation for a field.

The right column "Generated By" is the Input File name for the field with the same meaning.

Input Phone Number from the baseline fields has been mapped to HARMONY_PHONE.

Input Id is the sequential id from baseline fields, it can be mapped to HARMONY_ID.

Full description of the panel is within Harmony Batch System Cleanse Reference Guide.

Example 3: Mock Logical Record mapping

3. Preprocessor

Not Applicable

4. Output

Harmony Output on the left panel represents the configuration of the output file and the fields to be returned in the output file.

General: To configure the file layout specifications.

Field Definition: Defines the fields to be output to the output file.

Examples:

party.phone.countryCode -->represents validated phone number country code.

party.phone.phoneStatus--> represents validated number is connected/disconnected/indeterminate etc.

Sample text output:

Please refer to the sample illustration for phone number validation with detailed understanding using various samples.

5. Exceptions

Please refer to the Harmony Batch System Cleanse System Reference Guide.

6. Report

Please refer to the Harmony Batch System Cleanse Reference Guide.

7. History

Please refer to the Harmony Batch System Cleanse Reference Guide.

Last updated