Bookings
Appointments and bookings — a clinic's visits, a lawyer's consultations, cars by the hour, day, week or month, rooms by the night, a hall for an evening — with opening hours, prices, and payment when the owner wants it.
Everything below is declared by Bookings itself, so it describes this deployment rather than a manual — and it is rewritten whenever the program changes.
What it is
- Its key is Bookings, which is also the prefix of every component it owns.
- It is bought: a site has it only when the registry records that this customer bought it.
What it may be allowed to do
These are the permissions it declares. A person sees one of its screens only where his role carries the matching permission.
- bookings.desk
- bookings.own
- bookings.setup
- bookings.view
What it puts on a page
3 components, each of which can be dropped onto a page in the composer.
Book now
Lets a visitor choose a service, a free time and book it.
Placed as Bookings.Book.
One setting:
- Which service — chosen from a list this site's own data fills.
Cancel a booking
Where the link in a booking's letter leads: the booking, and a button to cancel it.
Placed as Bookings.Cancel.
It takes no settings — it draws one way and has nothing to be told.
My bookings
A signed-in visitor's own bookings, with cancel where the service allows it.
Placed as Bookings.Mine.
It takes no settings — it draws one way and has nothing to be told.
Comments
Nobody has written yet. Be the first.
This article is not taking comments.