Wayfinder / Case study / Topic detail

Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.

Return to: 4. Journeys and State Machines — topic detail

customer profile

In this document

Lifecycle: customer profile

Customer records contain personal identifiers, company information, and address details including city, state, and ZIP code. Custform contains corresponding customer fields and a customer screen record. Many controls are initially disabled, which supports an initial disabled or read-only configuration, but runtime framework behavior may later change enablement. The source does not prove that forms remain read-only throughout interaction. E0013 E0012

ID4_Cust declares customer, add-customer, query-customer, update-customer, and delete-customer operations, but no D4_Cust implementation is included in the supplied evidence. As a result, customer validation and creation used by order entry, customer selection in get_order, main-menu customer maintenance, and the status values returned by query_customer remain unconfirmed. Broader claims about customer behavior must remain qualified. E0012