Table of Contents

Enterprise Service Bus Data Handler - Google Contacts

Purpose

The Google Contacts data handler allows the builder to create an application that creates, updates, and deletes contacts in Google Contacts.

This feature will be available in Platform Version 13.11.851.

Supporting Elements

For the Google Contacts data handler to work properly there needs to be several elements added to the application. A table will need to be created by the builder that the ESB will read from. The Google Contacts Data Handler will read up to 7 single pieces of data that can be saved; First Name, Last Name, Middle Name, Name Prefix, Name Suffix, Contact Description, Contact ID. The ETag is a special version id and is required to maintain the conflict detection if it is empty then the WorkXpress data will be pushed to Google without checking for any changes made in Google. In addition to several single pieces of data there are multi-value pieces of data. For each multi-value piece of data a related table will need to be created for the data to read from. The multi-values pieces of data are email addresses, phone numbers, and street addresses.

For an End User to connect to Google and use this ESB they will need to login to Google.

Options

There is one configuration option in this data handler.

Triggering

This Data Handler is triggered via an Enterprise Service Bus Action. To see which actions will trigger this Data Handler use the “Outgoing” tab on the Enterprise Service Bus page.

Field Mapping

The field mapping interface will allow the builder to choose a field on the table selected in the options above or to use a query to find a field on related records to the record created by the data handler.