9,514
edits
Changes
no edit summary
<br>
<br>
The general logic of event(class) is creating Service + Provider related to it with dates selected in the settings of the event(class) as special days. When you use [[Custom_Features#Classes | Classes]] custom feature the event creates service+provider related to it with identical name. In order to preserve proper functioning of the event on the dates needed, you should not delete provider with identical name related to event (but you can easily change his/her name) and should not disconnect provider from the event. <br/>
The general logic of event(class) is creating Service + Provider related to it with dates selected in the settings of the event(class) as special days. When you use [[Custom_Features#Classes | Classes]] custom feature the event creates service+provider related to it with identical name. In order to preserve proper functioning of the event on the dates needed, you should not delete provider with identical name related to event (but you can easily change his/her name) and should not disconnect provider from the event. <br/>
[[File:Event new theme.png | center]]
[[File:Event client side booking.png|1200px| center]]
<br><br>
<br><br>
</div>
</div>
[[File:Recurring dates example.png |center]]
[[File:Recurring dates example.png |center]]
<br><br>
<br><br>
'''Please note!''' If you make the recurring service paid, the amount that you set as the service price is the total for all the sessions.<br>
It is currently not possible to set single session price for the recurring service packs.<br>
That is why if you have single service and decide to make a recurring booking for it from the admin side/[[Point_of_Sale_custom_feature|POS]] interface, its price will not be multiplied by the number of selected sessions.
<br><br><br><br>
</div>
</div>
</div>
</div>