- Dikirim
- 24 September 2026 pukul 07.46 UTC
- Penulis
- Kamo
- Commit
- ac83bea
Three columns on LEAD_VENDOR_PRODUCTS, chosen on the publish dialog and read by kamo-apps to lay the public mortgage form out: - APPLICATION_LAYOUT NORMAL (grouped steps) | SQUEEZE (one question per screen) - APPLICATION_CONTACT_STEP START (contact first, saved as they go) | LAST - APPLICATION_FIELD_SET FULL | BASIC Plain strings, not @Enumerated, so no ddl-auto CHECK constraint freezes the value set. Null reads as NORMAL / START / FULL, the form as it was. The DTO carries the resolved values; setProductApplication gains an overload taking the options, with null members meaning "keep", and the old signature delegates to it unchanged. DDL already applied to the cluster as the owner: ALTER TABLE public.lead_vendor_products ADD COLUMN IF NOT EXISTS application_layout varchar(16); ALTER TABLE public.lead_vendor_products ADD COLUMN IF NOT EXISTS application_contact_step varchar(16); ALTER TABLE public.lead_vendor_products ADD COLUMN IF NOT EXISTS application_field_set varchar(16);