July 15, 2022 - v2022.10

  • Issue #319, #1240: Fix allDay parameter in POST /setup/v1/calendar/{id}/blocks, PUT /setup/v1/calendar/blocks/{id}, POST /setup/v1/resources/{id}/block, PUT /setup/v1/resources/block/{id}, POST /setup/v1/resources/{id}/allocations, PUT /setup/v1/resources/allocations/{id}, POST /setup/v1/service/{id}/block, PUT /setup/v1/service/block/{id}, POST /setup/v1/services/{id}/allocations, and PUT /setup/v1/services/allocations/{id}
  • Issue #768: Prevent PUT /setup/v1/calendars/blocks/{id} and PUT /setup/v1/resources/block/{id} from wiping out startTime, endTime, and reason if not provided in the request body
  • Issue #901: Add deletedStatus to CalendarBlock response
  • Issue #1040: Add validation requiring reason for POST /setup/v1/resources and POST /setup/v1/services
  • Issue #1074: Fix issue where GET services in consumer and setup interface would provide the calenderId from the primary location instead of the specified location
  • Issue #1147: Add validation to POST /setup/v1/services to limit service name to 50 chars
  • Issue #1186: GET /setup/v1/services/{id}/block remove time part from response of startDate/endDate
  • Issue #1229: Add validations for startDate, endDate, startTime, endTime for POST /setup/v1/calendar/{id}/blocks, PUT /setup/v1/calendar/blocks/{id}, POST /setup/v1/resources/{id}/block, PUT /setup/v1/resources/block/{id}, POST /setup/v1/resources/{id}/allocations, PUT /setup/v1/resources/allocations/{id}, POST /setup/v1/service/{id}/block, PUT /setup/v1/service/block/{id}, POST /setup/v1/services/{id}/allocations, and PUT /setup/v1/services/allocations/{id}
  • Issue #1294: Update stored procedure when calculating available days to consider when a service allocation has been deleted
  • Issue #1302: Add AppInsights configuration to API