A booking product for Plone which allows to reserve time slots throughout the week.
Contents
Add redturtle.prenotazioni to the egg section of your instance:
[instance]
eggs=
...
redturtle.prenotazioni
To avoid spam, there is a background validation with collective.honeypot .
With a version of plone.app.dexterity lower than 3.* (ie Plone 5.2) you need to add collective.dexteritytextindexer as requirement.
[instance]
eggs=
...
redturtle.prenotazioni
collective.dexteritytextindexer
This product introduces two new content types to your Plone site:
- Booking
- Booking Folder
Booking is a content type used to store information about reservation.
The product interface provides a way to add new booking elements, by clicking on one of the plus signs available in the slots calendar.
Each booking element once created is storerd into its own Booking Folder.
Booking Folder is a folderish content type which store your Booking objects.
If the product is correctly installed the Booking Folder entry is available on the add new action menu.
You can configure: - hidden booking types for the internal usage - more then one gate - booking vacations - custom duration for booking types - week schedule for morning and afternoon time tables
You can hide your booking types from simple and anonymous users by using the 'Hidden Booking' flag in your booking types definition. This way, it will only be available to users with the 'Bookings Manager' permission. This feature may be useful if you want to restrict booking types for internal corporate use.
Anonymous and authenticated users are allowed to add new booking content by clicking on the plus signs on the default booking folder view.
After its creation the slot will be displayed as "busy" for anonymous user and the slot won't be available anymore.
Back-end users can see and manage the reservation according to the assigned Plone roles.
The product comes with its own workflow "prenotazioni_workflow".
Here below a list of all the states available:
Private: booking object initial state:
- submit (Automatic transition to pending)
Pending
Transaction available:
- publish (to published)
- refuse (to refused)
Published
Transaction available:
- refuse (to refused)
Refused
Transaction available:
- restore (to pending)
Managers can confirm a Booking using workflow transitions. The workflow transition triggers an email to be sent to the booker (see below).
There are automated notifications implementend by the following behaviors:
- redturtle.prenotazioni.behavior.notification_appio (Notify via AppIO gateway)
- redturtle.prenotazioni.behavior.notification_email (Notify via Email gateway)
- redturtle.prenotazioni.behavior.notification_sms (Notify via SMS gateway)
Each behavior is implementing the following notification types: * booking-accepted (An notification if the booking had been accepted) * booking-moved (An notification if the booking had been moved) * booking-created (An notification if the booking had been created) * booking-refuse (An notification if the booking had been refused) * booking-reminder (An notification reminder)
Notifications are NOT automatically enabled in every Booking Folder. If you want to send some notification, you only need to enable them by assigning the behavior to PrenotazioniFolder c.t.
You can create your own notification templates for the booking events(confirm, refuse, create, delete, reminder). The temlates are being saved in the PrenotazioniFolder object.
The template variables list:
${title}- Booking title.${booking_gate}- Booking gate.${booking_human_readable_start}- Booking human readable start datetime.${booking_date}- Booking date.${booking_end_date}- Booking end date.${booking_time}- Booking time.${booking_time_end}- Booking time end.${booking_code}- Booking code.${booking_type}- Booking type.${booking_print_url}- Booking summary url.${booking_url_with_delete_token}- Booking url to delete page.${booking_user_phone}- Booking user phone.${booking_user_email}- Booking user email.${booking_user_details}- Booking user details.${booking_office_contact_phone}- Booking office contact phone.${booking_office_contact_pec}- Booking office contact pec.${booking_office_contact_fax}- Booking office contact fax.${booking_how_to_get_to_office}- Booking how to get to office.${booking_office_complete_address}- Booking office complete address.${booking_user_details}- Booking details inserted by user.${booking_requirements}- Booking requeirements.${prenotazioni_folder_title}- Booking folder title.${booking_requirements}- Related PrenotazioneType.booking_requirements field
Note that the sms can be used only if you implement an own sender adapter Example:
You just need to register a new adapter:
<adapter factory = ".my_adapter.CustomSMSSenderAdapter" name="booking_transition_sms_sender" />
And here the send method must be implementend:
from zope.component import adapter
from zope.interface import implementer
from redturtle.prenotazioni.content.prenotazione import IPrenotazione
from redturtle.prenotazioni.interfaces import IBookingNotificationSender
from redturtle.prenotazioni.interfaces import IBookingSMSMessage
from redturtle.prenotazioni.behaviors.booking_folder.sms.adapters import BookingNotificationSender
@implementer(IBookingNotificationSender)
@adapter(IBookingSMSMessage5, IPrenotazione, YourAddonLayerInterface)
class CustomSMSSenderAdapter(BookingNotificationSender):
def send(self):
if self.is_notification_allowed():
# the message is automatically generated basing on the event type
message = self.message_adapter.message
phone = self.booking.phone
# Your custom send logics integration below
custom_send_function(message, phone)
You can specify days when the Booking Folder will not accept bookings. Those days are called "Vacation days".
Vacation days can be specified compiling the "Vacation days" field in the Booking Folder edit form. Values are allowed in the format DD/MM/YYYY. Instead of the year you can put an asterisk, in this case every here the day DD of month MM will be considered a vacation day.
It is also possible to specify a vacation period for a single gate using the vacation booking form with a link that you can see in the toolbar.
Using the prenotazioni_search view it is possible to search bookings within a given time interval. You can also filter the results specifying a searchable text, a gate or a review state.
Every booking has an unique code generated on creation.
By default this code is based on its UID. If you need to change this logic, you can do it registering a more specific adapter:
<adapter factory=".my_new_code.MyNewBookingCodeGenerator" />
And the adapter should be something like this:
from redturtle.prenotazioni.adapters.booking_code import BookingCodeGenerator
from redturtle.prenotazioni.adapters.booking_code import IBookingCodeGenerator
from redturtle.prenotazioni.content.prenotazione import IPrenotazione
from my.package.interfaces import IMyPackageLayer
from zope.component import adapter
from zope.interface import implementer
@implementer(IBookingCodeGenerator)
@adapter(IPrenotazione, IMyPackageLayer)
class MyNewBookingCodeGenerator(BookingCodeGenerator):
def __call__(self, *args, **kwargs):
return "XXXXX"
There are some endpoints useful to use this tool also with external frontends (like Volto).
This endpoint allows to retrieve a booking by its UID.
Example:
curl http://localhost:8080/Plone/++api++/@booking/<booking UID> -H 'Accept: application/json'
Response:
{
"booking_code": "17E3E6",
"booking_date": "2023-05-22T09:09:00",
"booking_expiration_date": "2023-05-22T09:10:00",
"booking_type": "SPID: SOLO riconoscimento \"de visu\" (no registrazione)",
"company": null,
"cosa_serve": null,
"description": "",
"email": "mario.rossi@example",
"fiscalcode": "",
"gate": "postazione2",
"id": "mario-rossi",
"phone": "",
"staff_notes": null,
"title": "Mario Rossi"
}
This endpoint allows to create a new booking.
Example:
curl http://localhost:8080/Plone/++api++/<booking_folder_path>/@booking \
-X POST \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"booking_date": "2023-05-23T09:00:00+02:00",
"booking_type": "SPID: SOLO riconoscimento \"de visu\" (no registrazione)",
"fields": [
{"name": "fullname", "value": "Mario Rossi"},
{"name": "email", "value": "mario.rossi@example"}
],
}'
Response:
{
"booking_code": "17E3E6",
"booking_date": "2023-05-22T09:09:00",
"booking_expiration_date": "2023-05-22T09:10:00",
"booking_type": "SPID: SOLO riconoscimento \"de visu\" (no registrazione)",
"company": null,
"cosa_serve": null,
"description": "",
"email": "mario.rossi@example",
"fiscalcode": "",
"gate": "postazione1",
"id": "mario-rossi-1",
"phone": "",
"staff_notes": null,
"title": "Mario Rossi"
}
This endpoint allows to delete a booking by its UID.
Example:
curl -X DELETE http://localhost:8080/Plone/++api++/@booking/<booking UID> -H 'Accept: application/json'
A booking can be deleted only if on of the following rules are satisfied:
- Anonymous user and booking has been created by an anonymous user
- Booking created by current logged-in user
- Current logged-in user has redturtle.prenotazioni.ManagePrenotazioni permission
- Booking has a date > today
This endpoint allows to move a booking by its UID to a different date/time slot.
Example:
curl http://localhost:8080/Plone/++api++/<booking_folder_path>/@booking-move \
-X POST \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"booking_date": "2023-05-23T09:00:00+02:00",
"booking_id": "<booking UID>",
}'
Leave for compatibility reasons (identical to @booking's GET). Could be removed in future.
Example:
curl http://localhost:8080/Plone/@prenotazione?uid=<booking UID> -H 'Accept: application/json'
Response, see: @booking
This endpoint allows to create a new vacation.
Example:
curl http://localhost:8080/Plone/++api++/<booking_folder_path>/@vacation \
-X POST \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"start": "2023-05-23T09:00:00+02:00",
"end": "2023-05-23T10:00:00+02:00",
"gate": "gate A",
"title": "vacation"
}'
Endpoint that need to be called on a PrenotazioniFolder. It returns the list of all available slots based on some parameters.
An available slot is the first free time on each hour slot (each day is split in 1h slots).
By default (without parameters) the endpoint returns available slots for the current month, starting from today.
Parameters:
- start a start date. If not given, the start will be today.
- end an end date. If not given, the end will be the last day of current month.
- first_available a boolean flag, if valiorized, the first available slot returned without the current month search limit but the one year.
Example:
curl -i http://localhost:8080/Plone/folder/@available-slots -H 'Accept: application/json'
Response:
{
"@id": "http://localhost:8080/Plone/folder/@available-slots",
"items": [
'2023-04-10T07:30:00',
'2023-04-10T08:00:00',
'2023-04-10T09:00:00',
'2023-04-17T07:00:00',
'2023-04-17T08:00:00',
'2023-04-17T09:00:00',
'2023-04-24T07:00:00',
'2023-04-24T08:00:00',
'2023-04-24T09:00:00'
]
}
Example:
curl -i http://localhost:8080/Plone/folder/@available-slots?start=2023-04-12 -H 'Accept: application/json'
Response:
{
"@id": "http://localhost:8080/Plone/folder/@available-slots",
"items": [
'2023-04-17T07:00:00',
'2023-04-17T08:00:00',
'2023-04-17T09:00:00',
'2023-04-24T07:00:00',
'2023-04-24T08:00:00',
'2023-04-24T09:00:00'
]
}
Endpoint that need to be called on a PrenotazioniFolder. It returns the list of all fields to fill in for the booking.
The booking date is passed via querystring (e.g ?booking_date=2023-04-13+10%3A00')
Example:
curl -i -X GET 'http://localhost:8080/Plone/prenotazioni/@prenotazione-schema?booking_date=2023-05-15T13:00:00' -H 'Accept: application/json'
Response:
{
"booking_types": {
"bookable": [],
"unbookable": [
{
"duration": "60",
"name": "Rilascio CIE"
"booking_additional_fields_schema": {"name": "field1", "description": "Field number 1", "type": "text", "required": true}
}
]
},
"fields": [
{
"desc": "Inserisci l'email",
"label": "Email",
"name": "email",
"readonly": false,
"required": false,
"type": "text",
"value": ""
},
{
"desc": "Inserisci il numero di telefono",
"label": "Numero di telefono",
"name": "phone",
"readonly": false,
"required": false,
"type": "text",
"value": ""
},
{
"desc": "Inserisci ulteriori informazioni",
"label": "Note",
"name": "description",
"readonly": false,
"required": false,
"type": "textarea",
"value": ""
},
{
"desc": "Inserisci il codice fiscale",
"label": "Codice Fiscale",
"name": "fiscalcode",
"readonly": false,
"required": true,
"type": "text",
"value": ""
},
{
"desc": "Inserire il nome completo",
"label": "Nome completo",
"name": "Nome",
"readonly": false,
"required": true,
"type": "text",
"value": ""
}
]
}
Endpoint that returns a list of own Prenotazione content by parameters
Parameters:
- SearchableText: The SearchableText of content;
- from: The start date of research (with YYYY-MM-DD format);
- to: The end date of research (with YYYY-MM-DD format);
- modified_after: To filter bookings modified only after given date (needed also a timezone: YYYY-MM-DDThh:mm:ss+02:00);
- gate: The booking gate;
- userid: The userid(basically it is the fiscalcode). Allowed to be used by users having the 'redturtle.prenotazioni: search prenotazioni' permission;
- booking_type: The booking_type, available values are stored in 'redturtle.prenotazioni.booking_types' vocabulary;
- review_state: The booking status, one of: 'confirmed', 'refused', 'private', 'pending';
- sort_on: The index by which to order (default 'Date' aka the booking datetime);
- sort_order: The order in which to sort, possible values: 'ascending', 'descending' (default 'descending');
- fullobjects: If fullobjects=1 is passed, the endpoint will return the full objects instead of a list of brains (actually the only information added is the requirements field. (aka cosa_serve).
Example:
curl -i http://localhost:8080/Plone/@bookings?from=2023-10-22&to=2023-10-22&gate=Gate1&userid=user1&booking_type=type1&SearchableText=text1 \ -H 'Accept: application/json'
Response:
{
"@id": "http://localhost:8080/Plone/folder/@bookings",
"items": [
{
"title": "Booking Title",
"booking_id": "abcdefgh1234567890",
"booking_url": "https://url.ioprenoto.it/prenotazione/abcd",
"booking_date": "2018-04-25T10:00:00",
"booking_expiration_date": "2018-04-30T10:00:00",
"booking_type": "Servizio di prova",
"booking_room": "stanza-1",
"booking_gate": "sportello-urp-polifunzionale",
"booking_status": "confirmed",
"booking_status_label": "Confermata",
"booking_status_date": "2018-04-25T10:00:00",
"booking_status_notes": "Prenotazione confermata",
"userid": "FISCALCODE",
},
...
],
}
}
If a user is authenticated and, he is not a site operator, returns all own bookings.
With an experimental envionment SEE_OWN_ANONYMOUS_BOOKINGS set to True, the endpoint will return also the bookings created by anonymous users with the same fiscalcode of the authenticated user.
Endpoint that fires the confirm email to user
Example:
curl -i http://localhost:8080/Plone/booking_folder/@booking-notify/<booking UID> \ -H 'Accept: application/json'
If the user is not logged in, the endpoint will return a 401 error.
- Response::
- HTTP 200 OK
Endpoint that returns a list of busy slots and pauses based on the passed date
Parameters:
- date: Date
Example:
curl -i "http://localhost:8080/Plone/prenotazioni_folder/@day-busy-slots?date=2023/05/22"\
-H 'Accept: application/json'\
Response:
{
"@id": "http://localhost:8080/Plone/prenotazioni_folder/@day-busy-slots",
"bookings": {
"gate1":
[
{
"booking_code": "17E3E6",
"booking_date": "2023-05-22T09:09:00",
"booking_expiration_date": "2023-05-22T09:10:00",
"booking_type": "SPID: SOLO riconoscimento \"de visu\" (no registrazione)",
"company": null,
"cosa_serve": null,
"description": "",
"email": "mario.rossi@example",
"fiscalcode": "",
"gate": "postazione1",
"id": "mario-rossi-1",
"phone": "",
"staff_notes": null,
"title": "Mario Rossi"
},
...
],
"gate2":
[
{
"booking_code": "17E3E6",
"booking_date": "2023-05-22T09:09:00",
"booking_expiration_date": "2023-05-22T09:10:00",
"booking_type": "SPID: SOLO riconoscimento \"de visu\" (no registrazione)",
"company": null,
"cosa_serve": null,
"description": "",
"email": "mario.rossi@example",
"fiscalcode": "",
"gate": "postazione2",
"id": "mario-rossi",
"phone": "",
"staff_notes": null,
"title": "Mario Rossi"
},
...
]
},
"pauses": [
{
"start": "2023-05-22T07:15:00+00:00",
"stop": "2023-05-22T08:30:00+00:00"
},
...
]
}
You can also create the addtional fields for your booking, you just need to compile them in your PrenotazioneType. And they will appear in the ["booking_types"]["booking_additional_fields_schema"] in your booking schema so you can compile them for your booking in this way:
Create booking with an additional field
This endpoint allows to create a new booking.
Example:
curl http://localhost:8080/Plone/++api++/<booking_folder_path>/@booking \
-X POST \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"booking_date": "2023-05-23T09:00:00+02:00",
"booking_type": "Type x",
"fields": [
{"name": "fullname", "value": "Mario Rossi"},
{"name": "email", "value": "mario.rossi@example"}
],
"additional_fields": [{"name": "field1", "value": "Addional field text"}]
}'
Response:
{
"booking_code": "17E3E6",
"booking_date": "2023-05-22T09:09:00",
"booking_expiration_date": "2023-05-22T09:10:00",
"booking_type": "Type x",
"company": null,
"cosa_serve": null,
"description": "",
"email": "mario.rossi@example",
"fiscalcode": "",
"gate": "gate 1",
"id": "mario-rossi-1",
"phone": "",
"staff_notes": null,
"title": "Mario Rossi",
"additional_fields": [{"name": "field1", "value": "Addional field text"}]
}
- text: Text which uses default zope.schema.TextLine validation
This view allows to download the bookings filtered by passed parameters
- text: The SearchableText of content.
- from: The start date of research.
- to: The end date of research.
- gate: The booking gate.
- userid: The userid(basically it is the fiscalcode). Allowed to be used by users having the 'redturtle.prenotazioni: search prenotazioni' permission.
- booking_type: The booking_type, available values are stored in 'redturtle.prenotazioni.booking_types' vocabulary.
- review_state: The booking status, one of: 'confirmed', 'refused', 'private', 'pending'
- Example::
- curl -i http://localhost:8080/Plone/folder/@@download/bookings.xlsx?text=Text&review_state=confirmed&gate=Gate1&start=2010-10-10&end=2025-10-10&booking_type=Type1
- Response::
- Binary file
This view sends a booking reminder email to all the bookings inside PrenotazioniFolders that have the Reminder Notification Gap field populated. If you intend to set up a cronjob to call this view, you might use a special script call. The script is located at src/redturtle/prenotazioni/scripts/notify_upcoming_bookings.py.
All the time parameters below are ISO formatted datetime strings
- booking_start_from - booking start from range.
- booking_start_to - booking start to range.
- booking_creation_from - booking created from range.
- booking_creation_to - bookking createtd to range
- path - booking folder path (es: "/Plone/booking_folder")
- Example::
- curl -i http://localhost:8080/Plone/@@bookings-export?booking_start_from=2023-10-22T12:27:18
- Response::
- Binary csv file
The script is supposed to be used to call the @@send-booking-reminders view. It is supposed to be ran once a day otherwise, duplicate emails will be sent.
Usage:
bin/instance1 -OPlone run bin/notify_upcoming_bookings
Buildout config example:
[buildout]
# You can change it in according to your policy
cron_instance = instance1
parts +=
notify-upcoming-bookings
[notify-upcoming-bookings]
recipe = z3c.recipe.usercrontab
times = 0 3 * * *
command = flock -n ${buildout:directory}/var/notify_upcoming_bookings.lock ${buildout:directory}/bin/${buildout:cron_instance} -OPlone run bin/notify_upcoming_bookings >> ${buildout:directory}/var/log/notify_upcoming_bookings.log 2>&1
If you mind to use this behavior note that first of all you also need to assign this redturtle.prenotazioni.behavior.notification_appio_booking_type to PrenotazioneType c.t.
To send the messages via AppIO gateway the service_code field defined by redturtle.prenotazioni.behavior.notification_appio_booking_type must be compiled in the PrenotazioniType object. All the possible values of this field are being taken from an yaml file with the following format.
appio_config_keys.yaml:
- name: Service1 key: ABC123 - name: Service2 key: ABC231 - name: Service3 key: ABC312
The file path is being taken from the APPIO_CONFIG_FILE env var. This variable can be configured automatically in the buildout using the following config.
buildout.cfg:
[instance]
environment-vars =
APPIO_CONFIG_FILE ${buildout:directory}/appio_config_keys.yaml
It is possible to set the content-transfer-encoding for the email body, settings the environment variable MAIL_CONTENT_TRANSFER_ENCODING:
[instance]
environment-vars =
MAIL_CONTENT_TRANSFER_ENCODING base64
This is useful for some SMTP servers that have problems with quoted-printable encoding.
By default the content-transfer-encoding is quoted-printable as overrided in https://github.com/zopefoundation/Products.MailHost/blob/master/src/Products/MailHost/MailHost.py#L65
There is a custom widget made in React and registered as bundle. To develop it, you should do following steps:
First of all, enable nvm:
> nvm use
Install dependencies:
> yarn
Run webpack:
> yarn start
This will start webpack with autoreload. To see changes on your site, you need to enable development mode in Resources Registry in your Plone site, and enable CSS and js development of "week-table-overrides-widget-bundle" bundle.
When changes are ok, you need to make a production build:
> yarn build
- Issue Tracker: https://github.com/RedTurtle/redturtle.prenotazioni/issues
- Source Code: https://github.com/RedTurtle/redturtle.prenotazioni
redturtle.prenotazioni has been tested with Plone 5.2 and works with Python 3.
This is a merge from other two booking products:
Developed with the support of:
All of them supports the PloneGov initiative.
This product was developed by RedTurtle Technology team.
