Michael Domingo

The first thing we need to do is use a RaaS Workday Out to get the report details we need into some properties in studio. Next I split the message up by report entry, this allows us on the push side to submit each message to Google individually. Then, I grab the Location ID, address values, name, and a few other requirements like the location hierarchy assignments. Why? I learned when I did this via EIB those are the minimum requirements to put the location back into Workday. YMMV, be sure to find out what you need.

We're getting to where the rubber meets the road. After some experimentation, I learned that if the address is not URL encoded (i.e. - we replace the spaces with + in the URL), the call fails. I write the address to a variable using a write step and use java.net.URLEncoder.encode to properly encode the URL. Then I submit the entire string to google.

Finally, the response is written to the message.

After we write the response to the message, we use a new eval step to pull out the latitude and longitude values, and call a subroutine to finally build the Put_Location API call.

Finally, we use a write step to build the API call, call the Put, and get the SOAP response. I used an error handler to catch and report whatever mess I made in my sandbox tenant. What could possibly go wrong? As it turns out, a lot. Firstly, Latitude and Longitude are limited to 6 decimal places of precision. I needed to reformat the output from the Maps API using a series of eval steps:

Originally I didn't account for Google not returning an address due to bad data. I needed to capture the first part of the response (the status node) add an MVEL Validation step to the output to ensure the response was OK. If not, I threw an error.