• Fixed validation error BOOKING-131 which shows up in case Daily Customer Booking Limit is exceeded. It was throwing unrelated values in the Validation Error Message

• Fixes issue where PUT /setup/v1/resources would wipe out linked resourceServices
• Fixes issue where PUT/POST /setup/v1/locations would result in isOpen: true, when the value submitted was false
• Fixes issues with Swagger schemas not displaying and request bodies not displaying
• Fixes issue where Swagger response body persisted between subsequent requests

As part of our ongoing testing for the .Net 5.0 framework release, we have made the following changes:

Major Change Notification - OnSched API on .Net 5.0

• Rename ResourceAllocations routes to maintain consistency with EventAllocation routes. ResourceAllocations continues to be a work in progress. They are not yet connected to availability

• Rename ResourceAllocations routes to maintain consistency with EventAllocation routes. ResourceAllocations continues to be a work in progress.  They are not yet connected to availability

• This change re-releases the previous production release from July 28, 2021 which was rolled back

• Add conferenceInfo parameter to Resource input and output models. This parameter can be used to store Zoom conference links, or other types of video platform information
• Add customerMessage and notes to POST /consumer/v1/appointments input model
• Fix bug with booking appointments where long appointment durations could result overlapping appointments
• Fix bug where original customer was not included in capacity calculations
• Fix bug where updating a resource would wipe out resourceServices previously set

• Add conferenceInfo parameter to Resource input and output models. This parameter can be used to store Zoom conference links, or other types of video platform information

• Add customerMessage and notes to POST /consumer/v1/appointments input model
• Fix bug with booking appointments where long appointment durations could result overlapping appointments
• Fix bug where original customer was not included in capacity calculations
• Fix bug where updating a resource would wipe out resourceServices previously set