I need to configure a service, which depending on the time of day has one capacity or another. In the morning 10 for example, in the afternoon 5.
I have set up a service with a capacity of 10 people, and then two different employees, one for the morning (with the default capacity of 10), and one for the afternoon, with the capacity reduced to 5. The problem is that if I hide the employee field, it always lets me select the capacity of 10, and if I choose a time in the afternoon, it generates an overbooking (image attached).
Additionally, if I show the employee field (I prefer it to be hidden), select the morning employee, choose the capacity of 10, and then change to the afternoon employee, it still allows me to book for 10, creating the same overbooking. (It's very easy to replicate).
Thanks for reaching out to us. Unfortunatelly, we have identified an issue with this use case. It's the case of overbooking, unfortunately, since Amelia is recognizing both employees and thus it's letting you select the number of additional people without recognizing the limit configured. We will address this for future updates, but the current workaround would be to have the employee selection field enabled. This will allow your customers to select the exact employee, which means that Amelia will know which employee is selected and thus it will recognize the configuration. I know it's not the most suitable option, but it's the current workaround. I hope it helps.
Thank you so much Stefan, happy to know that Amelia Team is working on it already.
Do you have a deadline (even an estimated) for this correction please? Will it take days? weeks? months?
I don't like the option to show the employee, but because I don't think it works properly either. Let's suppose you have service A, associated to employees 1 and 2, and you have another service B, associated to employees 3 and 4. If you choose service 1, employees 1 and 2 are automatically available, but if you select any of them, you can't switch to service B in the services tab, they would have to delete the employee first, and this is quite confusing. The correct behaviour would be that at any time you can change service, and in the employee list should be refreshed.
You are welcome. Well, the issue has just been identified and forwarded to developers. We have a roadmap of fixes and new features that we are adding with new updates, but this will be added as well. Unfortunatelly, it's hard to promise ETA at this moment, but you can always follow the changelog page to keep up with the updates.
We are doing our best to fix this for the next update. Unfortunatelly, can;t promise a precise ETA at this moment, but make sure to follow the changelog page. We are aware that this is an issue that needs to be solved, apologies for the inconvenience.
Hi Team,
I need to configure a service, which depending on the time of day has one capacity or another. In the morning 10 for example, in the afternoon 5.
I have set up a service with a capacity of 10 people, and then two different employees, one for the morning (with the default capacity of 10), and one for the afternoon, with the capacity reduced to 5. The problem is that if I hide the employee field, it always lets me select the capacity of 10, and if I choose a time in the afternoon, it generates an overbooking (image attached).
Additionally, if I show the employee field (I prefer it to be hidden), select the morning employee, choose the capacity of 10, and then change to the afternoon employee, it still allows me to book for 10, creating the same overbooking. (It's very easy to replicate).
What do you recommend me to do please? :(
Thank you so much in advance,
Lisbel.
Attached files: Overbooking.jpg
Hi Lisbel,
Thanks for reaching out to us. Unfortunatelly, we have identified an issue with this use case. It's the case of overbooking, unfortunately, since Amelia is recognizing both employees and thus it's letting you select the number of additional people without recognizing the limit configured. We will address this for future updates, but the current workaround would be to have the employee selection field enabled. This will allow your customers to select the exact employee, which means that Amelia will know which employee is selected and thus it will recognize the configuration. I know it's not the most suitable option, but it's the current workaround. I hope it helps.
Apologies for the inconvenience.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thank you so much Stefan, happy to know that Amelia Team is working on it already.
Do you have a deadline (even an estimated) for this correction please? Will it take days? weeks? months?
I don't like the option to show the employee, but because I don't think it works properly either.
Let's suppose you have service A, associated to employees 1 and 2, and you have another service B, associated to employees 3 and 4. If you choose service 1, employees 1 and 2 are automatically available, but if you select any of them, you can't switch to service B in the services tab, they would have to delete the employee first, and this is quite confusing. The correct behaviour would be that at any time you can change service, and in the employee list should be refreshed.
Thanks again!
Lisbel.
Hi Lisbel,
You are welcome. Well, the issue has just been identified and forwarded to developers. We have a roadmap of fixes and new features that we are adding with new updates, but this will be added as well. Unfortunatelly, it's hard to promise ETA at this moment, but you can always follow the changelog page to keep up with the updates.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Team!
Any ETA for this fix please? We are suffering enormously from overbookings and the number of customer complaints is growing all the time :(
Thanks for your understanding,
Lisbel.
Hi Lisbel,
We are doing our best to fix this for the next update. Unfortunatelly, can;t promise a precise ETA at this moment, but make sure to follow the changelog page. We are aware that this is an issue that needs to be solved, apologies for the inconvenience.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables