Melissa v1.0

This package provides capabilities that extend the Avoka Transact platform with integration to the Melissa suite of services for data validation. These include:

  1. Real-time Global address search and auto-complete - demo
  2. Real-time Global address verification - demo

For address auto-complete support, this package includes 4 components:

  1. Melissa Short Address Lookup
    This component provides address lookup capabilities for short format addresses and includes a short format address field set for manual address entry if required. After selecting the address from the auto complete field, the address is verified and if a sub premise number is missing an error message is displayed and the sub premise field is shown. In manual mode or when the address block is shown, a verify button is shown, which allows to verify and adjusts the address.
  2. Melissa Long Address Lookup
    This component provides address lookup capabilities for long format addresses and includes a long format address field set for manual address entry if required. After selecting the address from the auto complete field, the address is verified and if a sub premise number is missing an error message is displayed and the sub premise field is shown. In manual mode or when the address block is shown, a verify button is shown, which allows to verify and adjusts the address.
  3. Melissa Address Autocomplete
    This is a is used in the short and long address lookup components and is a single field address lookup that can be used to populate a custom address block where the short and long formats provided are not suitable.
  4. Melissa Address Validation
    This button invokes the Melissa address validation service, which validates and adjusts the entered address. The button is part of the 'Melissa Short/Long Address Lookup' component, but can also be used independently when required.

Address Formats

Avoka provides 2 address format options:

Short format address (sometimes called standard 5 field address) is a very common address format used in systems of record and consists of the following fields:

  1. Address Line 1
  2. Address Line 2
  3. Locality
  4. State
  5. Postal Code

Long format address provides a more explicit breakdown of address components:

  1. Building Name
  2. Subdwelling
  3. Street Number
  4. Street Name
  5. Street Type
  6. Locality
  7. State
  8. Postal Code

Where practical we also provide the following addtional fields:

  1. Country
  2. Country Code
  3. Full Address
  4. Lookup Key
  5. Postal Flag

Address Field Definitions

FieldDescription
Address Line 1
(short format only)		 This will be the first of 2 address lines. The contents of this element will depend on the existence of a building name or subdwelling where a subdwelling could be a unit/flat/shop/suite number or a level/floor number. If any of these elements exist then this field will contain these sub-location elements in the following order:

[buildingName] [floor/level] [unit/flat/shop/suite]

If none of these sub-location elements exist then this field will contain:

[streetNumber] [streetName] [streetType]

Address Line 2
(short format only)		 This will be the second of 2 address lines and will be blank unless addressLine1 contains sub-location elements, in which case the addressLine2 will contain:

[streetNumber] [streetName] [streetType]

Building Name
(long format only)		 Occasionally physical addresses include the name of the building they are located within. For example, performing a lookup for 34/267-277 CASTLEREAGH ST will return a building name of MUSEUM TOWERS.
Subdwelling
(long format only)		 The subdwelling value will contain floor/level identifiers and/or unit/flat/shop/suite identifiers.
Street Number
(long format only)		 For physical addresses this value will contain the street number of the address which does not include the unit or flat number, but may be represented as a range (e.g. 267-277). For non-physical addresses this field will contain the PO Box, Locked Bag, or similar data.
Street Name
(long format only)		 Where practical, this field will contain the name of the street only, with street type being provided separately (see below).
Street Type
(long format only)		 The street type value may be provided as an expanded value (e.g. ROAD) or abbreviation (e.g. RD), depending on the lookup service response data.
Locality The locality information varies from country to country but will usually be either suburb or city.
State The State that the address resides in. For some countries (e.g. New Zealand) this may be blank.
Postal Code The regional postal code, also referred to as Zip Code (US) and Postcode.
Country The Country that the address is located wihin, in its expanded form (e.g. Australia).
Country Code Where practical, the Country code will be provided as represented in the ISO 2 character (e.g. AU) or 3 character (e.g. AUS) standards, depending on the data provided by the lookup service.
Postal Flag The postal flag field indicate whether this address is a non-physical address (e.g. PO Box, Locked Bag etc...). Most address lookup providers support the ability to exclude non-physical addresses from lookup searches if required.
Full Address The intention of this field is to provide the full address with the exclusion of Country, as a single one line string. For example:

MUSEUM TOWERS U 34 267-277 CASTLEREAGH ST SYDNEY NSW 2000

Lookup Key This field represents a unique identifier for the address in the 3rd party system and will be different for each provider.

Licensing

Clients must ensure they are appropriately licenses in order to use this package. Organisations who wish to use this package are required to establish a commercial relationship with Melissa directly.

Compatibility

This package has the following compatibility requirements:

ModuleCompatibilityNotes
Transact Manager5.0 or above
Transact Maestro5.0 or above

Installation Instructions

To install this package please walk through the following proceedure:

  1. Unzip the package to a directory on your computer
  2. Import each zip archive found in the services folder to Transact Manager under the Services >> All Services menu item.
  3. Review the Help Doc tab for each of the imported services and make any required adjustments to service parameters.
  4. Review the Service Connection requirements under the same Help Doc tab for each of the imported services and make any required configurations to the Service Connection. Service Connections can be configured in Transact Manager under the Services >> Service Connections menu item.
  5. Import each archive found in the libraries folder to Maestro. Importing these into the Organisation level libraries folder is recommended as this will make the components available to all projects, however they can be imported at the Project level if required.

Usage Instructions

To configure the 'Melissa Long/Short Address Lookup' component, please walk through the following procedure:

  1. Open your form in Maestro and drag and drop the component from the Palette.
  2. Open the properties section of the component block.
  3. Under 'Options' section, setup the properties described below.

To use the single field 'Melissa Address Autocomplete', please walk through the following procedure:

  1. Open your form in Maestro and drag and drop the field called 'Melissa Address Autocomplete' from the Palette.
  2. Open the properties section of the field.
  3. Under 'DDS Configuration' section, map the response data fields to your Maestro fields.

To use the button 'Melissa Address Validation', please walk through the following procedure:

  1. Open your form in Maestro and drag and drop the field called 'Melissa Address Validation' from the Palette.
  2. Open the properties section of the field.
  3. Under 'Configuration' section, map the input and response data fields to your Maestro fields.

Maestro Assets

Melissa Address Autocomplete Library: exchange.melissadata Category: Melissa

Global address autocomplete service using the Melissa Data APIs

Used In

Service Calls

Rule Templates

You may add your own logic to handle the following rule types triggered by this component:

  • On Success : a script to run on success of the dynamic data call, the parameter info contains the response
  • On List Item Select : a script to run on the click of a result
  • On Extra Item Select : a script to run on the click of an extra item

Melissa Address Validation Library: exchange.melissadata Category: Melissa

This button invokes the Melissa address validation service

Used In

Service Calls

Melissa Long Address Lookup Library: exchange.melissadata Category: Melissa

Address lookup component with long format address block

Uses

Service Calls

Properties

Property Category Description Type Default
Mandatory Options

Controls the mandatory status of the address capture

boolean false
Include Postal Addresses Options

Controls whether the search results should include non-physical addresses such as PO Boxes and Locked Bags etc...

boolean true
All Capital Letters Options

Controls whether the address label in the auto-complete field is all capitalised

boolean false
Maximum Result Size Options

Controls the maximum number of results to be returned in address searches

integer
Show Address Block Options

Controls whether to always show the address block or not

boolean false
Show Country Field Options

Controls whether to present the Country field in the address block

boolean false
Country Code Options

Specify a country code to limit search scope. Expects ISO standard 2 character codes (e.g. AU, US)

text US
Melissa Short Address Lookup Library: exchange.melissadata Category: Melissa

Address lookup component with short format address block

Uses

Service Calls

Properties

Property Category Description Type Default
Mandatory Options

Controls the mandatory status of the address capture

boolean false
All Capital Letters Options

Controls whether the address label in the auto-complete field is all capitalised

boolean false
Maximum Result Size Options

Controls the maximum number of results to be returned in address searches

integer
Include Postal Addresses Options

Controls whether the search results should include non-physical addresses such as PO Boxes and Locked Bags etc...

boolean true
Show Address Block Options

Controls whether to always show the address block or not

boolean false
Show Country Field Options

Controls whether to present the Country field in the address block

boolean false
Country Code Options

Specify a country code to limit search scope. Expects ISO standard 2 character codes (e.g. AU, US)

text US

Services

Melissa Data - Address Search v1
This service facilitates address searching using the Melissa Data API.

Service Connection

Compatibility

Module Compatibility
Manager 5.0

Service Parameters

Name Description Required Default
maxResultSize Default value for maximum number of matching search results returned from the search function (default 10). This value can be overridden as a request parameter if required. Must be between 1 and 20. Yes 10

Inputs

Name Description Required
searchString The address search string. Yes
countryCode Optionally specify a country code to limit search scope. Expects ISO standard 2 character codes (e.g. AU, US) No
maxResultSize Optionally specify a numeric maximum result list size to override the default: 10. Cannot be less than 1 or greater than 20. No
allCaps Optionally request that results are returned in all capital letters [ true | false ] (default: false) No
includePostal Optionally specify whether to include non-physical addresses (PO Boxes, Locked Bags etc) in the results [ true | false ] (default: No
format Optionally specify the format of the address to be returned [ short | long ] (default: short) No

Outputs

Name Description
[] The results are provided as a JSON array of objects with the following attributes:
[].label The value to display in the result list, will be full address (excluding Country)
[].lookupKey The full address (excluding country)
[].fullAddress The full address (excluding country)
[].buildingName
[].subdwelling
[].streetNumber
[].streetName
[].streetType 		Where address format long is requested the address will be broken into these sub-elements
[].addressLine1
[].addressLine2
[].addressLine3
[].addressLine4 		Where address format short is requested the address will be returned with the simple breakdown
[].locality The suburb/city
[].state The state code E.g. CA
[].postalCode The postcode/zip code
[].country The country name E.g. United States of America
[].countryCode The 2 character country code E.g. US
Melissa Data - Address Verification v1
This service facilitates address verification using the Melissa Data API.

Service Connection

Compatibility

Module Compatibility
Manager 5.0

Inputs

Name Description Required
countryCode Optionally specify a country code to limit search scope. Expects ISO standard 2 character codes (e.g. AU, US) No
allCaps Optionally request that results are returned in all capital letters [ true | false ] (default: false) No
format Optionally specify the format of the address to be returned [ short | long ] (default: short) No
addressLine1 The address line 1 to verify No
addressLine2 The address line 2 to verify No
locality The locality/city to verify No
state The state code to No
postalCode The postal code/zip code to verify No
streetNumber The street number to verify - long address format No
streetName The street name to verify - long address format No
streetType The street type to verify - long address format No
buildingName The building name to verify - long address format No
subdwelling The subdwelling to verify No

Outputs

Name Description
fullAddress The full address (excluding Country)
lookupKey The full address (excluding Country)
validationCodes The Melissa Data result codes. This is a string value with comma delimited status, error codes, and change codes. E.g. (AC16,AE08,AV14)
missingSubdwelling A flag to indicate that the address is missing subdwelling
validationErrorMessage The validation error message E.g. Sub Premise Number Missing
addressVerifiedResult The validation result message E.g. Full Verification to the Sub Premises level
buildingName
subdwelling
streetNumber
streetName
streetType 		Where address format long is requested the address will be broken into these sub-elements
addressLine1
addressLine2 		Where address format short is requested the address will be returned with the simple breakdown
locality The city/suburb
state The state
postalCode The postcode/zip code
country The country name E.g. United States of America
countryCode The 2 character country code E.g. US
executionStatus The status of the service execution [ SUCCESS | DATA_ERROR | SYSTEM_ERROR ].

Successful execution will be denoted by a SUCCESS value. DATA_ERROR will indicate that there was an issue identified with the input data that may be resolved and potentially retried by the user. SYSTEM_ERROR indicates that there was an unrecoverable system fault and the form should fall-back gracefully to an alternative path.
errorMessage When a DATA_ERROR is experienced, this value may provide more detail on the nature of the error.

Service Connections

The following service connections are used by this package.

Melissa Data
Property Name Description Required
Type HTTP Endpoint Yes
Endpoint Must point to the Mellisa Data endpoint. For example

http://expressentry.melissadata.net/

Yes
Auth Key Should contain Your Referer key to access the service Yes