Services Plugins FAQs

Air Calendar Double Booking Issue

Plugins
#1

We have been working in a scheduling system for our application using Air Calendar. We have encountered the following issue:

We specifically have our calendar from 6am to 9pm, divided into 15 min timestamps, so that events can be scheduled for example at 8:00 am, 8:15am, 8:30am, 8:45am, etc.

We want to block/avoid double booking. The Calendar is not able to avoid all double booking situations, since it only saves into the database the initial and end date of an event in the calendar, without saving the times in the middle.

For example: If we create an event from 7am to 8am, it will only save the 7am and 8am timestamp into the database, not saving the 7:15am, 7:30am, 7:45am. So if we go ahead and create an event from 7:15 to 7:45 for example, the calendar allows that, and there’s no way for us to have the calendar avoid and block that time in the middle of the start and end times.

Is there any fix to this or we just have to accept how it is?

#2

Hi @daniel.aguilar.elsal,

Thank you for your message and for using our plugin.

Would it be convenient for you to provide more details regarding your use case?

Namely, screenshots or screencasts of your workflow setup, plugin element configuration, also if you have set any conditionals. These details will help us reproduce your setup on our side and look into it.

Thank you once again and looking forward to your reply. :pray:

Best regards,
Stephan

#3

Hi,

When creating an appointment from 6:00 am to 6:30 am, the process works as intended. However, upon attempting to schedule another appointment for the same time slot, a duplicate appointment is generated. Our objective is to prevent the scheduling of overlapping appointments, specifically blocking the 6:00 am to 6:30 am time slot if it’s already occupied.

We are using an Input Date Time to select both the date and time slots. How can we address and remove or block the time slot to ensure that it is not available for further appointments?

This is what we are trying to avoid (double booking). Appointment with color orange was created first, then we created the appointment in blue. The calendar should ideally block and avoid us from creating that second appointment.

Screenshot 2024-01-15 at 09.48.02
Screenshot 2024-01-15 at 09.48.022728×1272 146 KB

Workflow:

Screenshot 2024-01-15 at 09.44.05
Screenshot 2024-01-15 at 09.44.051472×1164 61.8 KB

#4

We are also trying to avoid this case:

image
image2662×450 20.7 KB

#5

Hello @daniel.aguilar.elsal,

Appreciate your further response.

We’ve checked with our development team, and unfortunately, currently, the plugin doesn’t support blocking a range between the start and end time.

Your idea has been noted for future enhancements to the plugin. We’ll look into the possibility of incorporating this feature and whether it’s supported by the plugin’s library.

If you require more information, feel free to reach out. :pray:

Best regards,
Stephan

#6

Understood. Thanks for the response. If any update allows us to do it in the future, please let me know through this forum.

Thank you!

1 Like
#7

Another question,

Currently, as you saw, we are using the plug in to schedule events, specifically to schedule users into the Calendar. At the moment, when jumping through different branches of the app, for example going to the main page of the App, and then jumping back to the Calendar, we are experiencing long load times for the calendar, even when we only have less than 10 events scheduled in the Calendar.

Is this due to the way we have set up the workflow, or is it the Calendar itself? Based on the pictures I sent you before, do you see any ways or have any advise to improve and decrease this loading time?

The application will eventually have to handle multiple users scheduling patients into the calendar, and we are concerned about the performance of the Calendar when we launch.

1 Like
#8

Hi @daniel.aguilar.elsal ,

Regarding your first reply, I have added your request to the list of plugin improvements, and we’ll let you know as soon as this feature is implemented.

About your second question, we couldn’t find any abnormal load times on our Demo page, even with a lot of events in the database. Please review the workflow and ensure that you provide the plugin only the necessary information.

But for a better understanding, could you please send me a short video (using Loom) demonstrating the page load time you are experiencing, and the workflows connected to it?

Waiting for your response on this matter. :pray:

Best regards,
Stephan

#9

Hi Stephan

Is there any other messaging methods that we can communicate through that are a little more private? I have the loom videos ready but I don’t want them open for everyone to see due to the privacy of our project.

Let me know

Thank you

#10

I sent you an email/message through this zeroqode page.

1 Like
#11

Hi @daniel.aguilar.elsal,

Thank you for your message.

I noticed that you have sent videos via DM. We will review them and respond promptly.

Let’s continue the conversation there. :pray:

Best regards,
Stephan