ServiceDesk 4.8.150 Update 03/23/20

We've wanted to provide this for a long time.

It's big. It's really super big.

Details are in this document.

When ServiceDesk requests address verification, Google can respond with a geocoded point (latitude and longitude) that is specific to: (A) a discretely-identified and particular building, (B) an address range that exists along the indicated street; (C) the indicated street as a whole; (d) the indicated city and/or postal code, either individually or in combination; or (E) none at all. In each case, Google returns at the highest level it is able verify.

ServiceDesk is coded to accept only (A) as amounting to direct verification (it's what Google calls "ROOFTOP" verification). Until now, it's been coded to accept only (B) (which Google calls "RANGE_INTERPOLATED") as amounting to potential verification (which triggers a dialog asking if you want to treat it as verification). Working with clients, we've discovered situation (C) should also trigger such a dialog, and in a greater array of circumstances (as opposed to simply informing that Google has not verified).

This change and a number of corresponding improvements are in this release. In all, the responses that you see on these verification requests should be much more fine-tuned --and informative when the response is at less than level-A. We are certain there will be fewer false negatives. We hope there will now be none.