Skedulo Booking Application Release Notes v22.34.0

From this version, we have supported validating the Question response with the Data Type picklist so that the system displays and highlights the inline error message if the response is invalid. With this capability, while booking an appointment if the users entered an invalid answer to a question or left the field blank that hinders the booking process, then the app displays the clickable error message that can redirect the users to the erroneous field (question) to fix them. 
The steps to configure the inline error message are given below:

1. Create a Message Key and add the required notification or the error message in its Value field.
   
2. Create/Edit a Question of any record type.
3. Add the Message Key along with the desired option on which the error message should be displayed in its Option Format. For example- No: error.message.not.eligible [Response:messagekey]With this configuration, when a user selects No for the question Are you an immunocompromised patient? the booking app displays the inline error message as shown below:
                
   

   Note

   Please note that this inline error message can be applied to only those questions with the picklist data types.

To be more generic about selecting a number of appointments irrespective of the dose of the vaccine, we have introduced a placeholder in the booking application. Please find the details of the message key and the suggested value of this placeholder below:

When the  environment variable Dose 1 upfront, Others Later is disabled, the booking application displays the first appointment along with the label Your selection may require multiple appointments. If so, they will show here on the appointment select page as shown below:

The suggested value for this message key will be displayed for all bookings as per the selected vaccine type’s recommended dose.

Starting from this version, we have enhanced the validation logic for the questions designed to capture the age/DOB of each group member. Now, the system validates the ages for only those questions whose Field Model Name is birthday. The captured age for the question is compared against the set value of the environment variable primaryContactMinAge to determine if the group member should be disabled in the primary contact list or not. With this capability, multiple questions can be compared against the primaryContactMinAge.