Jan 15, 2022 - v2022.1

Added Resource Allocation functionality to the API endpoints and to the availability functionality
Fix Issue #868: When calling PUT /setup/vs/resources{id} with a serviceId an HTTP 500 error was returned
Fix Issue #846: When calling GET /setup/v1/resources/{id}/allocations, some allocations were not returned. Fixed to return allocations within or overlapping the supplied startDate and/or endDate
Fix Issue #831: When calling PUT /setup/v1/locations/{id}/holidays with an asterisk (*), HTTP 500 error was returned
Fix Issue #777: When calling POST /consumer/v1/appointments with FIRSTNAME & LASTNAME did not save name info in the appointment
Fix Issue #776: When calling PUT /consumer/v1/appointments/{id}/book the Customer Record was not updating properly
Fix Issue #773: When serviceId was not passed into GET /consumer/v1/services/{id} or GET /setup/v1/services/{id} an incorrect error response was sent
Fix Issue #758: Added required and max length field validation (255 characers) for Name on Services and Resources
Fix Issue #750: POST /consumer/v1/resource added required and max length field validation (255 characers) for Name
Fix Issue #721: POST /consumer/v1/appointments updated Swagger to remove misleading statement re: multiple customerId's
Fix Issue #452: PUT /setup/v1/resources/allocations/{id} and PUT /setup/v1/resources/block/{id} was removing previously stored data