Skedulo Booking Application Release Notes v22.32.0

The appointment information for the booking confirmation page is now configurable so that you can update it as per the requirement. With this capability, the booking confirmation page can display additional appointment and vaccine-related information. We've introduced the following new message keys for this:

The /resyncBookings API has the following new enhancements:

1. While using the /resyncBookings API, the booking app now shows the error message when the Salesforce admin updates the status of an appointment from Rejected to Pending Allocation and vice versa making the booking app's behavior consistent.

2. Some new optional parameters have been added to the /resyncBookings API in order to distinguish if it should update Patient Details or Primary Contact details in different booking flows. These newly added parameters are:

   primaryFirstName: string
   primaryLastName: string
   primaryEmail: string
   primaryMobile: string
   isUpdatePatientPrimarySeparately: boolean

   When isUpdatePatientPrimarySeparately is TRUE, the /resyncBookings API updates personal details in the following ways:

   For Individual Booking	The patient information will be updated with the firstName, lastName, email, mobile provided in the request. Additionally, despite having values for the parameters primaryFirstName, primaryLastName, primaryEmail, primaryMobile, they will have no effects on patient information.
   For Group Booking	If it is a  The patient contact details will be updated with the firstName, lastName, email, mobile whereas the primary contact details will be updated with the primaryFirstName, primaryLastName, primaryEmail, primaryMobile provided in the booking request.

   When isUpdatePatientPrimarySeparately is FALSE, the /resyncBookings API updates personal details in the following ways:

   For Individual Booking	The patient information will be updated with the firstName, lastName, email, mobile provided in the request.
   For Group Booking	The primary contact will be updated with firstName, lastName, email, mobile provided in the request.

   Note

   Despite having values for the parameters primaryFirstName, primaryLastName, primaryEmail, primaryMobile has value, they will have no effects on individual patients or primary contact of the group if the isUpdatePatientPrimarySeparately is FALSE.

The numeric field Group Size on the Large Group Booking cannot be changed by scrolling up or down after the desired input for the group's size has been selected preventing the users from accidentally changing the value for group size.