JetTrac PushToGoogleCalendar

Introduction:

Can automatically add Google Calendar events when scheduling or rescheduling appointments.

Technical Support:

If you need assistance in installing and configuring JetTrac PushToGoogleCalendar™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at support@protechinc.com. Please note that the JetTrac PushToGoogleCalendar™ license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.

How to Run JetTrac PushToGoogleCalendar:

To run JetTrac PushToGoogleCalendar, you will need these files in the same folder:

  • JTPushToGoogleCalendar.exe
  • ExitHandler.dll

Executable files and dll files should not be edited for any reason.

All google modules need to be authorized to be allowed to run. To do this, make sure you are logged into the proper google account you want JetTrac to access, then run the Google Modules Authorization .bat file. It will ask you to log in and allow access to JetTrac to use the account. This only needs to be done once as the file will authorize all google modules.

Default Functionality:

Server-side creation of calendar events in Google Calendar as part of a business process

Job Step Configuration Window in JobConfig for JetTrac PushToGoogleCalendar:

When setting up a job step using JTPushToGoogleCalendar in JobConfig the only line of the config you need to worry about is the first, the Config file. This field should be filled with the fully qualified path to the Config file for JTPushToGoogleCalendar. 
Eg: C:\JetTrac\…\config.ini
In JobConfig, file paths entered should not be in quotes.

As with all modules, there is a dropdown to select whether or not the job should stop completely if this step fails. If you select Yes, any error will terminate the job process and write to the log file what happened, if no, then the job will try to continue anyways. However if any steps further down the line rely on the output of a job set to not stop on error, they may not work properly.

For more specifics go to the JetTrac BYODJobConfig page.

JTPushToGoogleCalendar Command Line:

“C:\JTPushToGoogleCalendar.exe” “C:\Input.xml” “C:\config.ini” “C:\JTPushToGoogleCalendar.log”

The command line starts with the executable file for this module, followed by the input XML file, the configuration.ini file, and ends with the log file. Each part of the command line is the fully qualified path to the file, in quotes, separated by a space (it doesn’t matter how many)

JTPushToGoogleCalendar Configuration.ini:

 

  1. ALL VALUES MAY BE DELARED LITERALLY BY WRAPPING IN DOUBLE QUOTES OR CALLED FROM XML BY USING THE FIELDNAME

#
# CalendarID

  1. – ID string of the calendar to insert the event into
  2. – The full calendar ID is YOURIDHERE@group.calendar.google.com
  3. – Program will accept ID only or full string with @group.calendar.google.com
  4. EventStart
  5. – Date and time of event start.
  6. – Date and time may be provided at the same time or separately.
  7. – If date and time are provided separately they must be pipe delimited
  8. – If date and time are provided separately the order must be Date|Time
  9. – Will attempt to parse any format.
  10. – Any format but recommended format is not guaranteed to give you the right date and time.
  11. – If a date only is supplied the time will be set at 00:00:00 (midnight)
  12. – Recommended format is “YYYY-MM-DDTHH:MM:SS”. Note: The “T” is a static character that delimits the date from the time.
  13. EventEnd
  14. – Date and time of event start.
  15. – Date and time may be provided at the same time or separately.
  16. – If date and time are provided separately they must be pipe delimited
  17. – If date and time are provided separately the order must be Date|Time
  18. – Will attempt to parse any format.
  19. – Any format but recommended format is not guaranteed to give you the right date and time.
  20. – If a date only is supplied the time will be set at 00:00:00 (midnight)
  21. – Recommended format is “YYYY-MM-DDTHH:MM:SS”. Note: The “T” is a static character that delimits the date from the time.
  22. – Optional. If not present the default will be 60 minutes from EventStart
  23. Duration
  24. – Optional. If present will override EventEnd.
  25. – Must be the numerical duration in number of minutes.
  26. – Only numbers allowed. All other characters will be stripped.
  27. EventTitle
  28. – Title string of the event title
  29. EventDescription
  30. – String of the event description. If you are using a static string you can’t use new-lines because of limitations in the config file format.
  31. EventLocation
  32. – String of the event location.
  33. EventAttendees
  34. – String of pipe delimited email addresses
  35. EventReminders
  36. – String of pipe delimited reminders
  37. – Method>Minutes|Method>Minutes|…
  38. * Method can be “email”, “sms”, or “popup”.
  39. * “sms” only works for Google Apps for Work, Education, and Government customers. Requests to set SMS reminders for other account types are ignored.
  40. * Example: EventReminders=”Default
  41. * Example: EventReminders=”email”>60|”email”>30|”popup”>10

CalendarID=”primary”

#EventStart=startDate|startTime

#EventEnd=endDate|endTime

EventStart=startDate

EventEnd=endDate

#Duration=”60″

EventTitle=”Test Title”

EventDescription=”Test Description”

EventLocation=”Test Location”

EventAttendees=”user@gmail.com”

EventReminders=”email”>”60″|”popup”>”30″