Business Validation using Harmony WS
This document provides instructions on utilizing the Harmony Restful WebServices for the Validation of business samples using Business Validation PDPs in different locales.
API:
http://localhost:8080/HarmonyWS/rest/parseCustomerDataRole used in Webservice Request

Sample Request and Response for Australia
Response 1 to 3 illustrates single company entity. Irrespective of whether the input is a main entity name, trading name, business names or other entity name the response will always depict the rule name as MainName in business_ver_code.
Response 2: Response shows validated business information. business_display_name holds the corrected business_name.
Response 3: Response shows validated business information. business_display_name holds the trading name.
Response 4 to 9 illustrates complex business structures with multiple entities.
These samples depict the order of priority for rules as listed in matching rules list.
Request 4: Validate a Complex business with multiple entities, person name trading as another business name.
Request 5: Validate a Complex business with main entity trading as a business in trust for beneficiary. Sample for an ambiguous match.
Sample for an ambiguous match
Response 5: Response shows an ambiguous match using BeneficiaryName. No further rules are validated due to ambiguity.
These samples depict the order of priority for rules as listed in matching rules list.
Response 10 illustrates business validation utilizing multiple data models: ID and companyName. The ID can represent either a business number or a company number, while the companyName can denote a person's name or a complex company entity.
Response 12 to 14 illustrates business validation when custom rules are set in business_validation_config.yml file.
Request 12: Validate business using custom rule for taxStatus. Configure business_validation_config.yml with taxStatus: "ACT" for au.
Request 13: Validate business using custom rule for nameTypes. Configure business_validation_config.yml including an additional nameType "OTN" for au.
nameTypes:
- "MN"
- "LGL"
- "TRD"
- "BN"
- "OTN"
Request 14: Validate business using custom scoreThreshold. Configure business_validation_config.yml with scoreThreshold: 0.2 for au. Same Input record as in Request 9.
Response 14: Score of the validated input falls below the threshold, hence it is categorized as a NoMatch on OriginalInput. Nevertheless, if there is a match found on the BeneficiaryName, it signifies an alternate outcome.
Response 15 illustrates how business names can surpass parsing failures through the utilization of configuration in $HARMONY_HOME/config/scrubbing/harmony_scrubbing_descriptor.xml.
default configuration is false.
Set the configuration to true, as below to surpass parse failure and proceed with business validation.
<h:passthrough-name-on-parse-failure>true</h:passthrough-name-on-parse-failure>.
Sample Request and Response for New Zealand
Response 1 and 2 illustrates single company entity. Irrespective of whether the input is a main entity name, trading name, business names or other entity name the response will always depict the rule name as MainName in business_ver_code.
Response 2: Response shows validated trading name information. business_display_name holds the corrected trading_name
Response 3 to 7 illustrates business validation utilizing multiple data models: ID and companyName. The ID can represent either a business number or a company number, while the companyName can denote a person's name or a company name with multiple entities. These samples depict the order of priority for rules as listed in matching rules list.
Request 3: Validate an input with multiple data models ID, Company name trading as another business name.
Request 4: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The ID yields no matches.
Request 5: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The provided ID and trust name do not yield matches.
Request 6: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The provided ID and trust name do not yield matches.
Request 7: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The provided ID, trust name and main name do not yield matches.
Response 9 illustrates how business names can surpass parsing failures through the utilization of configuration in $HARMONY_HOME/config/scrubbing/harmony_scrubbing_descriptor.xml.
default configuration is false.
Set the configuration to true, as below to surpass parse failure and proceed with business validation.
<h:passthrough-name-on-parse-failure>true</h:passthrough-name-on-parse-failure>
Response 10 illustrates business names that are failed to parse.
Last updated