JANUARY 2016 UPDATE:
Hello and happy new year to all.
Great news is we are (finally) into BETA testing for the new features, the integration has been almost completely redesigned and works beautifully. We have BETA testers banging on our code to ensure it's been fully tested and robust before we are happy to release to production. I will be holding a webinar shortly to demonstrate the app and the new features so if your not on our list please sign up and i'll email you with the details when we are ready. Thanks to you all for your patience with our delays over the last month or two of 2015 but we have learnt and grown over the process. Cheers and stay tuned.
DECEMBER 2015 UPDATE:
We are back and running after a delayed and somewhat shakey start!
Currently we are progressing well with version 2.0 and have traversed the "old" code and migrated about 80% of it from version 1.0 to the version 2.0, some of this migration meant tweaking the existing functions to facilitate the new Tasks and multi-user integration but this was always expected. We also have been adding in-line comments and descriptions (something that I was going to do in V1 but haven't had time) which will help with debugging and should you choose, enhancements by another developer.
We are working through improving the code we wrote in the first version because there were some underlying bugs which annoyed the heck out of me and thankfully have kept most of the functions as they were solid but have needed to rewrite some new ones which was an unforeseen activity. We will have the newly written code for Jobs synchronisation finished in the next couple of weeks and once this is tested we add Tasks and start testing that.Building a solid foundation for this next version is critical to ensure better developer support, faster debugging and stable execution especially with some customers expressing the need to sync up to 200 jobs/tasks. We have strengthened the supporting documentation as well by creating better workflows and conflict matrices to ensure that if anyone wants to improve or alter this integration then we have given everyone all the information they require to take it to the next level..... unless we do it first!
For those of you who have expressed interest in the BETA program we will get you guys to start pounding on our integration after we have introduced the multi-user feature so that you have some functionality to use in your domain. I expect that to be soon after the new year. I'll keep in touch as we progress and if you have any questions please don't hesitate to write to me.
NOVEMBER 2015 UPDATE:
so unfortunately we got off to a rough start with our developer suffering from pregnancy difficulties and even though she wanted to continue we agreed it was best for her to concentrate on her family and pending baby. So we wish her all the best and hope she can get some rest during her pregnancy.
We are in the process of handing over the reins to a new developer and will bring you news on that shortly. We apologise for the delay and I know there are some people who have been eagerly waiting on this next version and we hope to recommence in the coming weeks and have something ready to test before Christmas. Thanks and we'll keep you posted.
OCTOBER 2015 UPDATE:
We have started on version 2.0. The below features will be included in the next version:
Syncing tasks with or without syncing Jobs has been a hotly requested feature. This will be the primary focus for phase 2 of this utility.
Multiple staff on a single job/task
One thing that we overlooked until it was too late in the development was assigning multiple staff to a single job or task, d'oh! Currently the utility works great with one person assigned to a job but it became clear that most people assign more than one person to a job or task. This is priority 2 for this phase.
Iteration through assigned staff to obtain the registered calendar users
Some Workflow Max users had other staff not in their domain assigned to jobs and tasks such contractors or staff that have left but were not deleted. We will iterate through the list of staff and find any that match known registered calendars and assign the job or task to their Google calendar. Any that don't will be skipped.
Hint: you can create an externally shared calendar in your Google Apps domain and assign your contractor to that calendar in the WFM2GCAL setup. This way you don't need to pay for extra user license's in your domain.
Add URL link to job or task in calendar
Self explanatory but we will include the job or task reference URL to the calendar for your convenience.
Other misc sync improvements and bug fixes
Jobs and Calendar sync is complete! We are finally finished with this part of the utility so please enquire about a demo using the email address at the end of this post.
Hello! It's been a busy month here at SM with so many new activities and projects starting and of course, finishing. The latest to join the latter category is our Integration utility for Workflow Max jobs and Google Calendar which keeps your staff scheduling in sync and allows your staff to manage their work in a cross-platform tool they are familiar with, Google calendar.
The journey here has been a little tricky which i'll explain shortly but the support team at Workflow Max have been very helpful and our skilled developer has been able to achieve a very elegant and easy to use solution.
First lets start at the schedule for Jobs in Workflow Max (WFM from here on in)
Scheduling is easy with WFM but it requires users to log into the web console to view the scheduled timeline for jobs. Our utility synchronises the relevant job details with Google Apps for Work staff calendars giving each staff member notifications, visibility and control from their mobile phones using an app that they are familiar with, Google calendar.
The schedule appears in each staff members calendar as an all day event (Only because WFM jobs are not able to be scheduled for different times of the day) and if the event runs over several days then it's created as an easy to read event spanning multiple days.
Updating the event from either WFM or Google Calendar (GCAL from here on in) syncs the changes on a scheduled basis (currently set to 10 mins which is an optimal time to ensure the quota limit is never breached). We have run this here for a 24hr period syncing over 10 jobs to 3 calendars every 1 minute with very minor Google quota impact (97% of 1 Million calls remaining) and only 3 events on 1 instance had communications failure to the calendar API weshich has never occurred since.
Assigning the job to a particular staff member is also important as we want each staff member to have an easily accessible schedule while in or out of the office. This is achieved by matching the WFM staff ID with the GCAL ID and then syncing the appropriate data to that staff members GCAL. This means that notifications are taken care of by the native GCAL app on their respective device, why re-invent the wheel hey?
I might add, all events are viewable by every member of the team if your Google Apps admin has allowed this in the admin console. Otherwise at the very least each member can share their calendar around.
GCAL event title is made up of the important information from WFM including the job number, job name and client (This is easily customisable to suite your business needs).
Changing the event title from GCAL has been restricted as this should only be controlled via the WFM console so every sync will overwrite the GCAL event title again.
Adding notes for staff members is also handy so we wanted to sync those too. Changing or adding to the description in both WFM and GCAL syncs these with ease making adding some info a breeze.... I know, I'm sorry for my poor attempt at poetry.
Conflict resolution was a little tricky as WFM doesn't give any time stamps correlating to it's last updateupdate in the API so we have created a very beautiful mechanism for fixing these. When a conflict has occurred the utility will email the manager (or account that the utility runs under in Google Apps for Work) with a link to the Google Sheet database. Upon opening the Google Sheet a user interface (UI) displays the conflicting data sets and allows the manager to make changes if necessary and upload to both WFM and GCAL with a single click. For multiple conflicts the UI will cycle through these until completed. Then the Sheet can be closed and synchronisation for those data sets will continue.
Need to do some house keeping? Then remove all your current Jobs from all Calendars via the Workflow Max Setup menu in the sheet. Neat and tidy. This comes in handy for when we have some updates and new features and you can wipe your current Jobs and re-sync using the new version. Soon to come we have built in Calendar Tags so every event that has ever been created by the app can be removed!
We are very proud of what we have achieved here for our clients that use Workflow Max and Google Apps products and we will continue to enhance these in the near future. If you would like to get on board we have a special offer on at the moment so head on over to the website and register your interest:
Or if you would like to request a feature please email us at:
Shoosh Monkey Team