- Introduction to WorkXpress
- Building Your Application
- Examples and Best Practices
- Technical Manual
This shows you the differences between two versions of the page.
|
enterprise service bus data handler - google calendar event [2016/09/14 18:19] |
enterprise service bus data handler - google calendar event [2016/09/14 18:19] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Enterprise Service Bus Data Handler - Google Calendar Event ====== | ||
| + | ===== Purpose ===== | ||
| + | |||
| + | The Google Calendar Event data handler allows the builder to create an application that creates, updates, and deletes events in Google Calendar. | ||
| + | |||
| + | //This feature will be available in Platform Version 13.11.851.// | ||
| + | ===== Supporting Elements ===== | ||
| + | |||
| + | For the Google Calendar Event data handler to work properly there needs to be several elements added to the application. A [[Table|table]] will need to be created by the builder that the ESB will read from. The Google Calendar Data Handler will read up to 9 pieces of data that can be saved; Event Summary (Title), Event Description, Event ID, Start Date/Time, End Data/Time, Location (text), Status, Calendar ID, Attendees (comma separated list of email addresses). The Event ID is required to maintain a sync with Google Calendar and is used to locate and update a the record when new events are created in Google Calendar. | ||
| + | |||
| + | For an End User to connect to Google and use this ESB they will need to [[Enterprise Service Bus - Google Login|login to Google]]. After the end user is logged into their Google Account they need to fill in the "Google Calendar Subscriptions" field to choose what calendar is the default calendar to write to. | ||
| + | ===== Options ===== | ||
| + | |||
| + | There is one configuration option in this data handler. | ||
| + | |||
| + | * When WorkXpress and Google Event Data Conflicts which data should be used? - If a change has occurred in both the WorkXpress application and Google then the version is one system has to take precedence. If Google is selected then the values passed in by Google will be used and a the changes in WorkXpress will be overwritten. If WorkXpress is selected then the data from Google will be ignored and the values from WorkXpress will be pushed up to Google. | ||
| + | |||
| + | ===== Triggering ===== | ||
| + | |||
| + | This Data Handler is triggered via an [[Action Type - Enterprise Service Bus|Enterprise Service Bus Action]]. To see which actions will trigger this Data Handler use the "Outgoing" tab on the [[Enterprise Service Bus|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 Builder|query]] to find a field on related records to the record created by the data handler. | ||
| + | |||
| + | {{::esb_google_outgoing_event_mapping.png?nolink|}} | ||
