SalesForce Package Release Notes v1.90

 We have added the following new fields in the Skedulo Salesforce package to prevent duplicate bookings.

1. A new field named Prevent Duplicate Bookings under Location Settings -> Details -> Prevent Duplicate Bookings. When checked, this setting blocks a user from making duplicate requests on the AWS side.
   

   Note

   Note the Salesforce side deduplication is always running no matter this checkbox is selected or not.

2. A new field named Duplicate Bookings Search Timeframe under Location Settings -> Details -> Duplicate Bookings Search Timeframe. This field accepts a number that denotes the number of days a user can not make duplicate bookings since the first dose. For example, if the value is 10, we will only look back at 10 days’ data to see if we already have a booking for the same user.
3. A new field named numberOfDuplicateBookingsAllowed under Setup -> Custom Settings. This field also accepts a number field that denotes how many duplicate bookings a user can make before we stop them at the AWS side. By default, this value is 0 meaning that no duplicate bookings allowed.

We already have the following 3 deduplication rules under Setup -> Custom Settings. Now, we are syncing them from Salesforce to the AWS side, so that we can replicate the same deduplication logic of that of Salesforce deduplication.

1. Vax_Matching_Birthdate
   This setting, by default, matches an account if:

   • • First Name is matched

     • Last Name is matched

     • Either Email or Mobile is matched
       
       Enable this setting to add Birthdate to the matching rule. The birth date is matched only if Vax_Matching_Birthdate is true and DOBs are not empty. Otherwise, this check is skipped. The birth date is also matched if DOBs are not empty and are the same.

2. Vax_Not_Require_Email_Mobile
   This setting bypasses the Email/Mobile check. When enabled, it creates an account for the user if the provided First Name and Last Name matches with that of the existing account in the system.
3. Vax_Match_Account_By_HCN
   This setting allows matching accounts by Health Card Number instead of First Name, Last Name, Email, or Mobile. The translation key/value pairs for header and message body to show when a user is trying to make duplicate bookings is given below:
   

   Key	Value
   errors.messages.duplicateBookings	Sorry, we're unable to create a new booking. A booking has already been created using these personal details.
   errors.headers.duplicateBookings	It looks like you have an existing booking.

Important: It is the responsibility of the Integration Partner to set up all-new message keys in Salesforce as part of the release process.

Per Interaction Flow

We have added the ability to turn off the Prevent Duplicate Bookings setting in AWS in the Per Interaction flow. We've added a new field called preventDuplicateBookings to the per interaction flow initial booking request. The value of this field can only be undefined or false. When the value is false, it ignores the Prevent Duplicate Bookings checking in the Salesforce and bypass duplicate booking check.

 An example request is as below: 

{

   "interaction": {

            "landingPage": false,

            "enableOTP": true,

             "checkEligibility": false,

             "preventDuplicateBookings": false

        }

}

While NOT using per interaction flow, the duplicate booking check API call will happen on the button click of Personal Details Page.  

However, while using per interaction flow, there is a chance that all patient data are filled in and set to be hidden in the per interaction flow request. In that case, the Personal Details Page will not be displayed. 

When this is the case, we will do the duplicate booking check API call on the button click of Appointment Select Page.

Any vaccine changes on the Job records record are now automatically synchronized with AWS. This is triggered for Jobs Type "Vax" when the value in the "Vaccine" field is changed.

To prevent possible failure of the sync process, we have implemented that all active questions that are text, address, phone, or email responses should have the following rule added to the Option Format field (Location settings->Related->Quesions-> Question Details):

Where "number" represents the Salesforce field length you are mapping to When a max-length rule in the format of max-length: number is provided in Option Format, it will be automatically synced down to AWS side, and we have added validations to support it. This ensures the data captured on AWS can be successfully synced to Salesforce. 

Important: It is the responsibility of the SI to add these new format options to each active question.