Skip to main content

Making Your Own Version of Appointment Slots with Apps Script

Making Your Own Version of Appointment Slots

In a previous post I showed an alternative version of Google Calendar's Appointment Slot's functionality created in Apps Script. You can see it in action here.

Since making this app Google have, rather fantastically dropped their dropping of the Appointment Slots feature. This app may be useful to anyone wondering how to make an Apps Script Web App that loads jQuery and uses HTML templates.

If you want to edit the code that runs it, you can get a copy of the script here:


Then you need to go to...

File > Make a copy

... and then...

File > Manage Versions




... and create a new version of the app. This is needed when you want to publish your web app. So next, then go to ...

Publish > Deploy as web app


You might want to restrict Who has access to the the app setting to just people from your domain.

In theory you can now share your web app's URL and start making changes to the application. Most of the files are just HTML templates, but the main two code files are Code and Web App. Good luck!



Comments

  1. Hello Frndz...
    Great Information! Nice post,it is really very helpful for me.One of the few articles I’ve read today.I’m saying thanks
    You can search online app for book appointment from our site.There is a wide range of such apps to book appointments becoming available and a few.You can find everything you need integrated in this one mother of all apps to book appointments, when you need it and as you need it.

    ReplyDelete
  2. Hi, I got this error when i deploy as web app:
    ReferenceError: "ScriptDb" is not defined. (line 32, file "ScriptDBLib")
    Can you please advise?

    ReplyDelete

Post a Comment

Popular posts from this blog

Inserting A Google Doc link into a Google Spreadsheet (UPDATED 6/12/2017)

This article looks at using Apps Script to add new features to a Google Spreadsheet. At the University of York, various people have been using Google spreadsheets to collect together various project related information. We've found that when collecting lots of different collaborative information from lots of different people that a spreadsheet can work much better than a regular Google Form. Spreadsheets can be better than Forms for data collection because: The spreadsheet data saves as you are editing. If you want to fill in half the data and come back later, your data will still be there. The data in a spreadsheet is versioned, so you can see who added what and when and undo it if necessary The commenting features are brilliant - especially the "Resolve" button in comments. One feature we needed was to be able to "attach" Google Docs to certain cells in a spreadsheet. It's easy to just paste in a URL into a spreadsheet cell, but they can often...

Writing a Simple QR Code Stock Control Spreadsheet

At Theatre, Film & TV they have lots of equipment they loan to students, cameras, microphone, tripod etc. Keeping track of what goes out and what comes back is a difficult job. I have seen a few other departments struggling with the similar "equipment inventory" problems. A solution I have prototyped uses QR codes, a Google Spreadsheet and a small web application written in Apps Script. The idea is, that each piece of equipment ( or maybe collection of items ) has a QR code on it. Using a standard and free smartphone application to read QR codes, the technician swipes the item and is shown a screen that lets them either check the item out or return it. The QR app looks like this. The spreadsheet contains a list of cameras. It has links to images and uses Google Visualisation tools to generate its QR codes. The spreadsheet looks like this. The Web Application The web application, which only checks items in or out and should be used on a phone in conjunctio...

Can You Use a Collaborative Inbox for an Enquiries Email Address?

Google Groups have added a few new flavours of group recently. As well as a regular Email List, you can now make a Web Forum, a Q&A Forum and a Collaborative Inbox - all slightly different takes on the same thing. As part of the move to Google, one of the biggest challenges are  what we call "non personal email accounts", for those accounts like chemistry-enquiries@york.ac.uk . Traditionally the handling of these accounts was done by a number of people, all sharing the log in details. In a Google-ized world, having accounts that can't be audited is "not the done thing". Our first trawl for non personal accounts found thousands of them. This included accounts for projects, conferences, departments, etc. With many of them, nobody knew who was replying ( or not ) to any enquiries. Gmail has the ability to delegate access to your account to someone else, but this still doesn't solve the  chemistry-enquiries@york.ac.uk problem . Essentially we need som...