During the TFNRegistry Release 8.29.1 on July 19, 2026, the following customer impacting issues were discovered.
| Changes | Spring Boot 3.5.x Behavior (TFNR-8.28) | Spring Boot 4.0.7 Behavior (TFNR-8.29.1) | Customer Impact | Mitigation Strategy |
| JSON Property Order | The response Json will have property order as defined in the code | The response Json will have properties ordered in Alphabetically. | Automation script will have if implemented to read properties by specific position | Update the scripts to read the json values by property name instead of specific position Ex: response.oauthToken instead of response [1] |
| Date/time Format | Often defaults to numeric Epoch timestamps. Ex: 1784660553 (UTC: Tuesday, July 21, 2026, at 7:02:33 PM) | Strict ISO-8601 strings out of the box. Ex: YYYY-MM-DDTHH: SSZ | TFNR Error message with errList | Avoid using non-ISO formats for date parameters Use YYYY-MM-DDTHH: SSZ or YYYYMMDDTHHSSZ format in requests |
| Null value Handling | Allows NULL or missing values for Boolean type parameter default to 0/false. | Rejects null / missing values for Boolean parameter (ex: withPerm) types. | TFNR Error message with 400 Bad Request. | Provide the parameter with required value as True or false. Remove the parameter from the request entirely. |
| Stricter Parsing | Allows unquoted keys, trailing commas, or leading zeros. | Enforces strict JSON syntax specifications by default. | TFNR Error message with errList. | Use quotes for String Avoid using quotes for numeric or Boolean values Avoid leading 0 in the numeric parameter values |
| Enum Mapping | Does not enforce case sensitivity for ENUM values Ex: using num_alloc_ind instead of NUM_ALLOC_IND | Enforces case-sensitivity during string-to-enum deserialization. | TFNR Error message with errList. | Use proper case for ENUMs as defined in the API Spec in developer.somos.com |
| Empty Strings | "" supplied instead of expected datatype in the request | May be converted to null or accepted | More likely to fail validation | Avoid sending empty quotes (“”) in the request if not required. |
| JSON Property Order | The response Json will have property order as defined in the code | The response Json will have properties ordered in Alphabetically. | Automation script will have if implemented to read properties by specific position | Update the scripts to read the json values by property name instead of specific position Ex: response.oauthToken instead of response [1] |