# Release 637 - May 2025

# New features

TapConnect now supports products which are limited to certain zones. A zone is a list of stop ids. Tickets which are issued for a product with configured zones are limited to tapping in or out on the configured stops in the zone. Please note that for this to work, the validator needs to be online, since a UIC barcode can't store all the stops.
Functionality is added in preparation for connecting to the Accept Router for dynamic pricing. This feature is currently turned off, and will be made available in a later release.

The ticket info endpoints of the issuing API v2 or higher now return the ticket reference field, and the external reference is also shown on the Customer Service screen.
Internal scheduling was changed to support our improved deployment process.
New optional fields were added to support DTicket day cards, and report the VDV specific ticket identifier.
Information returned by the health endpoints has been enhanced for better application monitoring, and extra protection was added to the health endpoints to limit the visibility of this information to certain parties only.

Solved a problem where for some products with a fixed validity and a matching sliding lifespan would cause the system to refuse to create the Ticket.
Fixed a documentation issue in the UIC field mapping table where the transport operator list was not marked as filled.
Fixed a problem where the change from winter to summertime (DST) would cause the validity to extend past the lifespan, and the system refusing to create the Ticket.
We had an issue where Ticket Events were not sent to the reporting system after an upgrade of an AWS Lambda runtime.
The cause of the issue was found and fixed, and the missing Ticket Events have been sent to reporting.
Corrected UIC documentation where the "supported" checkmark was in the wrong place.