Skedulo Booking Application Release Notes v23.26.0

Ability to customized Email/SMS templates using the vaccine type.

This allows admin users to customize email and SMS templates to create vaccine-specific instruction and contents. This enhancement includes:

• A new storeConfig variable vaccineTypewhich can be used to display the vaccine type in an email/sms template
• A new operator stringContains that can be used along with vaccineType to generate email/SMS contents depending on the vaccine type of the booking. 

Partner Enabling Document is available here.

Ability to display the closing date of a location in two formats: MMM d or MMM d, yyyy.

For individual and small group booking, a new configStore variable locationSelectDateRangeFormat can be used to configure the available date of a location in the Location Select page. 

For example, a location is available from June 30, 2023:

• If locationSelectDateRangeFormat = MMM d, the date will be displayed as Jun 30. This is the default value for this variable.
• If  locationSelectDateRangeFormat = MMM d, yyyy, the date will be displayed as Jun 30, 2023.

The value for this variable must follow the Unicode's date time format.  

Ability to use local timezone for Eligibility validation steps related to Date of Birth.

This enhancement supports the rule evaluation process for eligibility, vaccine, and location. When enable, the system will validate the customer's Date of Birth (DOB) using local timezone instead of using Coordinated Universal Time (UTC).

Introducing a new configStore variable called evaluateRulesByClientTimeZone that can be configured as following:

1. If evaluateRulesByClientTimeZone = FALSE, the system will fallback to the previous behavior, which utilizes the UTC timezone for DOB calculations. This is the default value.

2. If evaluateRulesByClientTimeZone = TRUE, the DOB calculation within the rule evaluator will use the client's timezone instead of UTC time.

Bug fixing: Displaying the location search result using the local timezone for the large group booking workflow. 

Previously, in the large group booking workflow, when searching for a location, the system utilized the UTC timezone for calculating the search results. With this latest release, we have implemented a change where the local timezone is now employed for computing the search outcomes.

Example: The Date of Stock Count of a vaccine supply is set to June 30, 2023. 

• Prior to this release, if users in New Zealand search for this vaccine supply in the morning of June 30, the location with that particular vaccine supply would not appear because it was still June 29th midnight in the UTC timezone.
• After this release, the system will utilize the local timezone to assess the search results. Thus, in this case, users will be able to see the location with this vaccine supply starting from 00:00 on June 30th in the Pacific/Auckland timezone.