KamoCRM

Layout choices, and saving contact details as they go

FeatureSecurityService
관련 상품
2026년 9월 24일 오전 7:46 UTC
이름 *
Kamo
뚱 베어
d345869

The publish dialog now chooses how the public mortgage application lays itself out (kamo-shared-library ac83bea1): NORMAL or SQUEEZE, contact details at the START or LAST, FULL or BASIC questions. - PUT **************** takes applicationLayout, applicationContactStep and applicationFieldSet; a missing one keeps what is stored, so retiring a page never resets its layout. The response echoes them. - GET /public/loan-application/{p} answers layout {type, contactStep, fieldSet}, always resolved. - POST **************** — for a START product only (404 otherwise): *** fail-closed, submission IP budget, name + email required. Creates the lead with source "Online Loan Application (unfinished)" and answers a 256-bit token held in Redis for a day, written inside the transaction so a Redis failure rolls the lead back rather than guaranteeing a duplicate. - PUT **************** adds answers to that lead through updateLead (absent = unchanged). Token bound to the product. - POST /public/loan-application/{p} with progressToken finishes that lead (source "Online Loan Application", receipt as before) instead of filing a second one; an unknown or expired token files a new lead as before. - Lead ownership is checked BEFORE updateLead rather than by catching its exception: it is @Transactional and would mark the request rollback-only. Ratchet baseline: startProgress and saveProgress added with their reasons, and byHost (added on main by 81e0756 without a line, which left the ratchet red).

모든 변경 사항

배송을 보는 것과 같이?

모든 것이 자신의 작업 공간에서 도착합니다. 무료 플랜을 시작하고 이 페이지를 다시 한 달에 읽으십시오.

무료 영원히 시작가격 비교