In in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in in

Fixkamo-internal
Ya
3 Agosti 2026, 14:59 UTC
Mwandishi
kamo
Ahadi ya
8294efa

The Quotes tab was only wired into the RETAIL sub-tab set, so on an org whose active markets are SUBSCRIPTION / MORTGAGE / PERSONAL_LOANS there was no way to reach it at all — which is every org that has not activated a retail market. My error: the backend was always cross-vertical (documentLabel maps SERVICE to "Estimate", PROCUREMENT to "Request for Quote", SUBSCRIPTION to "Proposal"), and scoping the UI entry point to retail contradicted that. Now: - RENTAL / SERVICE / SUBSCRIPTION / PERSONAL_LOANS get a third sub-tab alongside Intents and Commitments, with ?sub=quotes kept in the URL - PROCUREMENT renders a single list, so it switches on ?sub=quotes directly - RETAIL keeps the sub-tab it already had - Every market except MORTGAGE also gets a "New <noun>" entry in the pipeline quick-actions menu, so a quote is reachable without knowing the sub-tab exists MORTGAGE is deliberately excluded: a mortgage price quote is a Loan Estimate, a TRID-regulated document with its own flow in the steward console. Offering a generic quote beside it would be misleading and arguably a compliance problem.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei