KamoCRM

One exact, coalesced floor signal for every committed lead write, and a grid count

Featurekamo-shared-library
Shipped
November 12, 2026 at 12:01 AM UTC
Author
Kamo
Commit
6d44468

The Leads nav badge counts Fresh > New Lead and must hear when that number moves, whichever of the dozen write paths moved it. - LeadFloorSignalListener: a Hibernate POST_COMMIT insert/update/delete listener on Lead (any subclass), registered by LeadFloorSignalRegistrar in every persistence unit that maps leads. It sees the row before and after, so it covers the direct leadRepository.save paths (accept, callbacks, social, webinar) and deletes that never raised the floor signal, and only after the commit is real. - rt.org.{orgId}.floor-leads frames now carry kind "fresh-new" when a New Lead count may have moved, "changed" otherwise (call outcomes keep the badge quiet). - **************** coalesces per org: the first frame goes at once, the rest of a 1 s window folds into one trailing frame (a 5,000-row import is a frame a second, not 5,000). - FreshNewLeads: the definition, by LeadStatusType.NEW_LEAD and its parent, never by an org label. LeadGridQuery.parentStatus: equality on STATUS so IX_LEADS_ORG_STATUS serves it. LeadService.countLeadGrid: the grid's own specification, counted.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing