|Release date||April 13th, 2021.|
The installation link for the Salesforce Package can be found here.
We have added the following new fields in the Skedulo Salesforce package to prevent duplicate bookings.
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.
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
An example request is as below:
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.
This behavior will not be applied to historical records. When a rule is changed, it will capture all duplicates from that point of time onward but it won’t capture duplicates that were allowed previously.
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.
The minimum version for the Salesforce package is v1.90 and the AWS deployment is v21.15.0 for this update to happen automatically.
|Sync failure issue||
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.