3.245.0 release notes

⚠️ Breaking changes
1. Changed the permission required to create downtime periods on POST /public-api/resources/charge-point-downtime-periods/v1.0 and POST /public-api/resources/evse-downtime-periods/v1.0 from create to maintain. Clients whose credentials do not have maintain access will now receive 403 responses.
✨ New features
1. Added the optional reimbursement object to Partner request and response bodies on GET /public-api/resources/partners/v2.0, POST /public-api/resources/partners/v2.0, GET /public-api/resources/partners/v2.0/{partner}, and PATCH /public-api/resources/partners/v2.0/{partner}. Use it to configure and retrieve a partner's home-charging reimbursement settings.
2. Added filtering by filterable, accessible Session custom fields to GET /public-api/resources/sessions/v1.0 through filter[customFields.<identifier>]. Text criteria use contains matching; number, date, and date-time criteria accept inclusive from and to ranges; multiple criteria are combined with AND.
🔧 Improvements
1. Made filter[subOperatorId] nullable on GET /public-api/resources/charge-points/v2.0.
2. Added 409 Conflict responses to PATCH /public-api/resources/charge-points/v2.0/{chargePoint}, POST /public-api/resources/charge-points/v2.0/{chargePoint}/personal-smart-charging-preferences, and DELETE /public-api/resources/electricity-rates/v1.0/{electricityRate} and DELETE /public-api/resources/electricity-rates/v2.0/{electricityRate} when the requested change would leave a charge point without an electricity rate required by its reimbursement policy.
3. Added a 409 Conflict response to PATCH /public-api/resources/reimbursement-policies/v1.0/{reimbursementPolicy} when changing a policy to use a charge point's electricity rate while an attached charge point has no rate.
4. Added a 404 response to GET /public-api/resources/sessions/v1.0 when a requested custom-field filter is unavailable to the caller.