Episode 507: Manage Schedules by "Federated Calendar"!

Monday, October 31, 2016
"Oh, I did it again... double-booked..."

From Business meeting by visit and face-to-face, I have shifted my work style to "Online negotiation" using 'Google Hangout', etc. I used to feel "My schedule is full!" for having three meetings in a day. But now, even if I have six appointments that is twice as much than before, I still have leeway. However, even though I have achieved so-called "Improvement of productivity" in the aspect of the number of meetings, new challenges are becoming conspicuous which is "Schedule adjustment has become complicated"...

The following Workflow is a Business flow of 'Product demo'.

The basic flow is, capable sales rep to undertake corresponding of "product demo requests" (desired date and time) from the customer voluntarily. For actual 'schedule adjustment', it is done on the phone or by emails. Then when the schedule is fixed, you input it into [2. Demo Date], the second Step.

Its excellent point (seemingly, even though it seems sober) is that "the fixed schedule will be automatically appended to Google Calendar". It is very easy-to-understand to see schedules info on the calendar. (Or, it is very hard-to-understand if it was data list like CSV.) This will reduce the occurrence of 'Double-booking' significantly.

Moreover, *direct links to "Issue details page of Questetra" are embedded in the calendar so that you can smoothly move to the Step of [3. Demo Implementation Report].
* ${var[applicationRoot]}OR/ProcessInstance/listView?processInstanceId=#{processInstanceId}

[Product Demo flow]

In this Workflow, "Schedule auto-registration to Google Calendar" is processed at the auto-step of [Insert Calendar".

This [Insert Calendar] does not exist in Questetra's modeling icons originally. But you can get more modeling elements to be used in a Business Process Definition by incorporating function expansion file (Add-on XML). (Detailed info: M415)

By the way, as you can see in the captured image of operating screen, you are able to enter a scheduled time in 'local time'. In this sample, String type Data Item of "Local timezone" has been added, whereas Date-time type Data in Questetra is handled as 'Operator's timezone setting' normally.

If you enter "10:00 Singapore time" for example, it will be processed as "11:00 Tokyo time (10:00 Singapore time)" on Google Calendar.

[Auto-step setting screen]

[Setting example of Communication permission on Google]
  1. [API Manager] > [Library]
    Enable "Calendar API" in "Google Apps API"
  2. [API Manager] > [Credentials]
    Create credentials and obtain OAuth2.0 Client information
  • Application type: Web application
  • Name: Q2Cal
  • Redirect URL: https://s.questetra.net/oauth2callback

[Setting example of Communication permission on Questetra]
  • Name: Q2Calendar
  • Authorization Endpoint URL: https://accounts.google.com/o/oauth2/auth?access_type=offline&approval_prompt=force
  • Token Endpoint URL: https://accounts.google.com/o/oauth2/token
  • Scope: https://www.googleapis.com/auth/calendar
  • Consumer Key: (Retrieve at Google Developers Console)
  • Consumer Secret: (Retrieve at Google Developers Console)

[Product Demo flow:"2. Demo Date" screen]

[Data Items list]

[Free Download]
<Similar Models>
<<Related Articles>s>

[ε’Œζ–‡θ¨˜δΊ‹ (Japanese Entry)]