- Shipped
- August 26, 2026 at 8:36 PM UTC
- Author
- Kamo
- Commit
- e15fa83
There is no platform-wide right answer. A maintenance contractor on a three-year plan bills each period; a capital-equipment installer bills the contract up front. An Order's total becomes a captured payment, so either hard-coded choice charges half the tenants the wrong amount. Defaults to FIRST_PERIOD_PLUS_SETUP because it under-charges rather than over-charges. Null means the default rather than unset — every org predates this setting, and a backfill writing one value everywhere is a column that could have been nullable. A body that never mentions quoteConversionBilling means leave it alone, not clear it: the engagement-types tab sends only enabledEngagementTypes, so reading absence as null would wipe the choice on every vertical toggle. The column ships with no CHECK constraint. Hibernate's export wanted check (... in **************** which is frozen at CREATE TABLE and breaks the next value appended to the enum.