Contact Zone:Contact Verify:Output Filter: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 86: | Line 86: | ||
:This means that the conditions for the rules are met if either result code “ES01” or “ES03” were returned and the result code “ES04” was not returned. | :This means that the conditions for the rules are met if either result code “ES01” or “ES03” were returned and the result code “ES04” was not returned. | ||
:Custom rules are an advanced subject. You should be comfortable with Boolean operations before using custom rules in a production environment. For more information on the available result codes, see [[#Custom Output Filters|Custom Output Filters]] below. | :Custom rules are an advanced subject. You should be comfortable with Boolean operations before using custom rules in a production environment. For more information on the available result codes, see [[#Custom Output Filters|Custom Output Filters]] below. | ||
;Target | |||
:The output which is filtered is saved in a file. | |||
Revision as of 17:55, 17 June 2014
Contact Verify Navigation | |||||||||
---|---|---|---|---|---|---|---|---|---|
Overview | |||||||||
Tutorial | |||||||||
| |||||||||
| |||||||||
|
The Contact Verify Component will output records to one of two tables: the valid table and the invalid table. The Output Filter tab allows you to control which records go to which table.
Result Codes
The output status of a record is returned via result codes returned by the underlying objects. The Component will combine them into a single, comma-delimited string and write them to the field mapped here. New field names can be created by typing the name into the Output Results Code box.
Output Filter
Select a filter to determine which records will be directed to a particular output stream. A custom filter may be created based on individual need, each pin filters the records in a cascading effect, where the results code is compared against the first expression (Pin 1) and then compared against Pin 2, and so on.
- No Filter
- All records are written to a single output stream.
- Pre-built Filter
- The Component comes with several pre-built filters for common applications:
- Full Address Matches - The record is valid only with a valid and deliverable mailing address.
- Street Address Matches - The record is valid if the street address is deliverable, even if the suite information is missing.
- Full Address Match and Deliverable by all carriers - The record is valid only with a valid and deliverable mailing address that is also served by alternate delivery services such as Fed Ex and UPS.
- Non-Questionable Names - The record is valid if the name information was complete and contains no questionable information (vulgarities or common nuisance names).
- Valid Email Domains - The record is valid if the domain for the email address was either confirmed to be valid or, at the very least, is not known to be invalid.
- Valid and Allowable Email Domains - The record is valid if the domain for the email address was either confirmed to be valid or is not known to be invalid, and is not a mobile email address (which are not deliverable per FCC regulations).
- Full Phone Matches - The record is valid only if the phone number was verified to the 10-digit level.
- Full and Partial Phone Matches - The record is valid if the phone number was verified to either the 10-digit or 7-digit level.
- Custom Filter
- A custom rule that would be equivalent to Pre-built rule #6 would read: “(ES01 OR ES03) AND NOT ES04.”
- This means that the conditions for the rules are met if either result code “ES01” or “ES03” were returned and the result code “ES04” was not returned.
- Custom rules are an advanced subject. You should be comfortable with Boolean operations before using custom rules in a production environment. For more information on the available result codes, see Custom Output Filters below.
- Target
- The output which is filtered is saved in a file.
Custom Output Filters
Custom rules are an advanced subject. You should be comfortable with Boolean operations before using custom rules in a production environment.
For more information see Custom Output Filters.