Difference between revisions of "Global Name:Notice"

From Melissa Data Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
[[Global Name|← Global Name]]
 
[[Global Name|← Global Name]]
 
{{CustomTOC}}
 
{{CustomTOC}}
 +
==BETA Disabled==
 +
''July 2, 2021''
 +
 +
We have disabled the <code>globalname.melissadata.net</code> endpoint as the service is now live.
 +
 +
 
==HTTP Deprecation==
 
==HTTP Deprecation==
 
''June 17, 2021''
 
''June 17, 2021''

Revision as of 22:03, 2 July 2021

← Global Name


BETA Disabled

July 2, 2021

We have disabled the globalname.melissadata.net endpoint as the service is now live.


HTTP Deprecation

June 17, 2021

Melissa is in the final phase of upgrading our Global Name Web Service with newer development technology which will result in better performance and include added request options and response results. We'll continue posting advisories and notices here, as well as email notifications when deemed necessary.

As our April HTTP protocol deprecation Product Advisory didn’t result in any customer concerns with the protocol transition, we are removing support for the less secure HTTP protocol. We want to ensure that all of our users have easily migrated to the newer and more secure HTTPS protocol - or will contact us with any concerns or to seek advice in migrating GlobalName development, requesting us to implement resources to help you transition your application to the recommended protocol.

If you are using HTTP requests and have any questions, please contact our technical support team at tech@melissa.com or 1-800-MELISSA (635-4772).

Thank you,

The Melissa Team

Product Advisory: Global Name Web Service

April 9, 2021

Global Name Web Service Upcoming Update

Melissa is in the process of upgrading our Global Name Web Service with newer development technology which will result in better performance and include added request options and response results. We'll continue posting advisories and deprecation notices on our public wiki.

At this time, we are reaching out to see how many users are actively using the service with the HTTP protocol.

As we consider implementing a more aggressive schedule of removing support for the less secure HTTP protocol, we want to ensure that all of our users can either easily migrate to the newer and more secure HTTPS protocol - or will contact us with any concerns or to seek advice in migrating your development.

This advisory is intended to inform you of the upcoming service update, help Melissa prepare our deprecation schedule, and implement resources to help you transition your application to the recommended protocol. We strongly discourage new development using HTTP, as future updates will no longer support it or be released, the current service will stop using-up-to-date data, and documentation, support and the service itself will be respectively deprecated.

If you are using HTTP requests and have any questions, please contact our technical support team at tech@melissa.com or 1-800-MELISSA (635-4772).

Thank you, The Melissa Team

Global Name Update Notice

March 8, 2021

Melissa is preparing for the first major update to our Global Name Web Service in several years. The underlying service and backend data have been completely rebuilt. With this update, we’re introducing a new Country input field, new response output properties, and updated options. We believe these changes will bring increased accuracy for users of the service who process international data, and we encourage everyone to review these new items and plan to incorporate them into your application.

So clients can test the new changes, we’ve released the BETA version of the new version of the service on these URL’s:

SOAP https://globalname-beta.melissadata.net/v3/SOAP/GlobalName
XML/REST/JSON https://globalname-beta.melissadata.net/v3/WEB/GlobalName/doGlobalName

The previous timeline of disabling the Beta URL on April 15th is On Hold. Please continue to test the new service features until further notice.

Is this new update backwards compatible?

Yes, the new version is backwards compatible. We have not removed or renamed any existing inputs or outputs. We’ve only added additional inputs and outputs as well as options. In some cases, existing options will be overridden by incorporated logic.

If this update is backwards compatible, why are you staging the roll-out?

In the past, we’ve seen some clients have issues with any change to our services, even backwards compatible ones like this one, particularly with Java applications. Out of an abundance of caution, we want to give everyone time to test and confirm so there are no service interruptions for any clients.

Is SOAP being deprecated?

At this time, we will still be supporting the SOAP endpoint. However, the new features are not available in SOAP. We recommend the newer JSON protocol.