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

Return to: 02 — Business Capability Map — topic detail

Customer maintenance

Capability: Customer maintenance

The supplied help material documents customer add, find, update, and delete options. It states that deletion requires confirmation and that a customer with active orders cannot be deleted. This is evidence of documented business behavior, not proof that the visible Java runtime implements the corresponding operations. E0004 E0005 E0006

Customer-related form artifacts expose fields for customer number, names, company, address, city, state, ZIP code, and phone. The phone field is configured with the mask ###-###-#### XXXXX. Several generated form classes set visible fields to disabled, which suggests display or read-only configuration in those artifacts, but does not establish that every customer screen is read-only. E0004

State entry is documented as supporting validation and a scrolling selection window. State_List.java.svn-base provides a stronger structural finding: it configures a grid-like selection form with state-code and state-name columns, a table model, and a scroll pane. The callback or validation wiring between customer entry and this form is not present, so the runtime validation behavior remains unresolved. E0005 E0006