Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: 4. Journeys and State Machines — topic detail
order record
In this document
Lifecycle: order record
The order business object includes an order number, order date, purchase-order number, and shipping instructions. Related invoice records also carry shipping date, shipping weight, shipping charge, backlog, and total-price information. These fields show that order processing spans entry, reporting, invoicing, and shipping-related data, but they do not by themselves prove lifecycle transitions or database constraints. E0013
The get_order journey queries orders for a selected customer, displays the available orders, and permits selection of an order for line-item and detail display. The visible implementation limits displayed line items to ten and reports an error if the selected order has more than ten items. The source does not establish a different persistence behavior for orders with more than ten items. E0011
Order update and delete are not implemented in the supplied D4_Orders source. Both methods display an unimplemented-option error rather than changing an order or transitioning its lifecycle. The presence of menu options and method names must therefore not be interpreted as evidence that update or deletion succeeds. E0012
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.