Release Details
| Release date | March 11th, 2021 |
| Minimum Salesforce Package Version | v1.64 |
| The SalesForce Package Release Notes v1.64 can be found here. | |
What's New?
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
From this version, we have introduced a new page called Manage your appointments from where the users can easily cancel, reschedule and book follow-up appointments that suit their convenience. - Rescheduling dose 2 will have the dose 1 date as the governing date for the minimum and maximum allowed days for dose 2. However, rescheduling dose 1 will reschedule both dose 1 and 2. - Cancelling the appointments will immediately make them available for booking again. Note: The Reschedule feature is disabled by default. Enabling it can impact your existing business processes. To enable this feature, please contact your Skedulo Customer Success team. Once, enabled we recommend that you review and update the content of the following keys:
Removed Keys
Important: It is the responsibility of the Integration Partner to set up all-new message keys in Salesforce as part of the release process. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
| We have included an external process that (re)calculates which locations no longer have the capacity and removes them from the search. We have also improved a number of SQL statements that enhance the query being run under load. These updates make the application's performance better. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Starting from this version, the application notifies the user of the latest status of the available slots for booking. When there is a high influx of users trying to book an appointment, the application now checks if the chosen appointment slot is still available at the time of booking or not and then displays the appropriate message enhancing the user's booking experience. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| The API that generates an access code batch now accepts an optional parameter considerEligibility in the request payload. If the parameter is present and is true, all access codes in the generated batch will take eligibility rules into consideration at the eligibility phase. Otherwise, it follows the regular behavior, which means that a valid access code trumps all other eligibility rules. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| We have updated the UI of the application to display locations for every appointment in the email templates and confirmation screens. |
Issues Resolved
| Issue | Description |
| Focus on form list of errors instead of form elements | We have improved accessibility for users with screen readers. When there is an error in the form, the app notifies the user of the error by focusing on the error lists at the top of the form. |
| Incorrect appearance of the number of doses. | When the user selects the first dose of the vaccine that requires two doses, the application focuses the user on the next dose. The flow of the navigation is correct but the vaccine appears to require 3 doses because the focus goes to the 3rd, a still disabled dose. This issue has been resolved. |
| Availability doesn't respect Force Single Dose mode. | When a user tries to select a vaccine location while Force Single Dose mode is turned on, the app still attempts to book the second dose which is not technically required. This issue has been resolved. |
| Booking Flow Accessibility Issues | We have included accessibility improvement for screen readers on the Complete Booking view. |
| Issue regarding ccompanyDetails.footerLogo | If the companyDetails.footerLogo is not added, it breaks the accessibility for the footer logo. From this version, the app displays the company's name when the field is empty. |
Comments
0 comments
Please sign in to leave a comment.