Interaction Behaviors

Use cases and scenarios for the GEN::INT (Interactions) area. These behaviors define the cancel and undo interaction patterns that are shared across all forms and inline editing contexts in the application. Any use case that involves a multi-step data entry flow — including inline list editing, item creation forms, and entity edit forms — depends on these patterns to define the behavior of the “Cancel” path.

GEN::INT::0001 — Cancel and Undo Flows

All cancel paths leave the system in its pre-action state. No data is modified, no API call is made for the discarded change, and any form or edit state is cleared. This use case is crossed by GEN::LST::0007 (navigate-away prompt during inline edit) and by entity creation and edit forms across all domains.

Persona	Irene Itemsworth (Inventory Manager), David Dealsworth (Purchasing Manager), Sam Scansworth (Shop Floor Worker), Keisha Clerkson (Receiving Clerk), Owen Ownerton (Business Principal), Alan Adminson (Account Admin)
Status	Covered

GEN::INT::0001::0001.US — Cancel Entity Creation Form

The user opens an entity creation form (for example, the Add Item form), partially or fully fills in fields, and then clicks “Cancel” or closes the panel without submitting. The form closes and no entity is created. The form state is cleared so that reopening the creation form presents a blank form. No API call is sent.

GEN::INT::0001::0002.US — Cancel Inline Edit via Escape

The user has double-clicked an editable cell in the list and is in inline edit mode. The user types one or more characters and then presses Escape. The cell exits edit mode immediately. The typed value is discarded and the cell reverts to its original pre-edit value. The isCancelAfterEnd() method returns true and the wasCancelled flag is set. No draft-creation API call is made. This scenario is the Escape path of GEN::LST::0007::0004.US.

GEN::INT::0001::0003.US — Cancel Entity Edit Form

The user opens an entity edit form from a detail panel (for example, the Edit Item form), modifies one or more fields, and then clicks “Cancel.” The form closes and the original data is preserved. No update API call is sent. The entity remains in its pre-edit state.

GEN::INT::0001::0004.FS — Navigate Away with Unsaved Inline Edit Changes

When the user navigates away from a row that is in inline edit mode and changes have been made, the system presents a confirmation prompt with three options: accept the changes (which triggers the two-phase commit described in GEN::LST::0007::0003.US), cancel the changes (which discards the edits and exits edit mode cleanly), or return to the editing position (which keeps the row in edit mode with the current unsaved values intact). The prompt blocks navigation until the user makes a selection. This scenario crosses GEN::LST::0007.

GEN::INT::0001::0005.US — Remove Item from Order Queue

The user cancels a pending order by removing an item from the Order Queue while it is in REQUESTING or REQUESTED state. The card returns to its previous state before the order was initiated. This action is available only before the supplier has started processing. This scenario crosses PRO::OQ (Order Queue domain) for the specific card state transition involved.

Summary

Use Case	Scenarios	US	FS	UC
GEN::INT::0001 Cancel and Undo Flows	5	4	1	0
Total	5	4	1	0

---