What's New?
Change |
Description |
|
Enable Vax Data Constraints |
Prevent users from deleting locations. See Vax_Enable_Data_Constraints setting at 12. Create Preferences setting |
|
Match Account by Health Card Number |
Allow matching accounts by Health Card Number. See Vax_Match_Account_By_HCN at 12. Create Preferences setting NOTES:
|
|
Data Clean Up batch job |
Execute the script below to delete Job records
Update the query accordingly to delete Booking, Account, etc |
|
Registration Extract support (from v1.51) |
Objects and fields for Registration Extract from AWS to Salesforce. Please note: Your Project Manager or CSM needs to request the Ineligible API is enabled by Skedulo’s PD team before it will function. |
|
2nd Dose Support |
Add 'Enable Dose 1 Upfront' checkbox on Location Setting for 2nd booking function. Booking a second dose becomes visible on the URL /next-booking on AWS Booking experience. You will also need to import the following new Message Keys: Key,Value |
|
Expose processSurveyResults() |
This method can be overridden in subscriber orgs to process survey result data effectively.
|
|
Queueing Requests at Salesforce in synchronous mode. |
From v1.54.5 all booking requests from AWS to Salesforce will be stored as Vax Request records which are accessible via the VAX Requests tab. If a booking is not pushed to Salesforce, we can:
NOTES: This only works with normal apex error. In the case of governor limits, the Vax Request record is not created so we need to check the error on the AWS side. We can avoid this by switching to asynchronous mode (using Queueable Apex) when it is officially approved by Salesforce. |
Comments
0 comments
Please sign in to leave a comment.