An accepted quote becomes an order

Featurekamo-shared-library
Ya
26 Agosti 2026, 20:50 UTC
Mwandishi
Kamo
Ahadi ya
e1f16d0

acceptPublic wrote four columns and appended an event. No Commitment, no Order, no Transaction — the Quote javadoc's claim that accepting mints a Commitment described code that did not exist. Deliberately does NOT create a Commitment: processOrderPaid returns immediately when order.getCommitment() is non-null, so hand-creating one disables the whole downstream. The order is DRAFT and payment moves it on through the existing state machine, which mints the Commitment, the Transaction and the FulfillmentOrders. Reuses the quote's Engagement rather than minting a second, and derives its status through EngagementLifecycle rather than hand-setting COMMITTED the way createRetailOrder does. Totals come from the quote, which QuoteTotals computed server-side — never through CreateRetailOrderRequest, which accepts client totals and double-counts lines on top of a supplied subtotal. A line that opts in with usesQuoteQuantity takes the quote's shared driver, not its own column: copying that verbatim would put a 60-seat deal on the order as one seat beside a lineTotal priced for sixty. Only the accepted option's lines convert, plus every option-less one. QuoteConversionResult carries orderUid as a String, not the UUID the plan named: Order extends BaseEntity, whose id is an INT8 unique_rowid() that JavaScript truncates. Ids leave this platform as strings. First production writer of ServiceLineItem anywhere.

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