Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Actor journeys
Actor journeys
In this document
Who is trying to achieve what, and which actions and handoffs lead to the outcome?
This view models the documented data-entry journeys for an operator who either requests contextual help or interrupts entry. The help material reports that F1 provides context-sensitive help during data entry and that the INTERRUPT key (DEL or CTRL-C) aborts entry without writing changes to the database E0003. These behaviors are documented rather than runtime-verified; the supplied form evidence does not show corresponding F1 event-handler logic E0004.
The model keeps the help and interruption outcomes separate. The broader application evidence identifies help references but does not provide the help-file content itself in every analyzed source range E0001. The implementation status of the documented journeys therefore remains partly uncertain E0004.
Diagram
Preparing diagram…
View Mermaid diagram source
flowchart TD
ndd7c5f8d267088f159cc["Data-entry user"]
na038007afef41ac045b7["Begin data entry"]
n3beaf780ba551f7d7580["Request context help"]
n7b6d73c7c6f1cf24c02e["Contextual help displayed"]
nd2765044f37b6eec5367["Interrupt data entry"]
n021a80db6e0008926b0a["Entry abandoned without database write"]
ndd7c5f8d267088f159cc -.->|"User begins entry (inferred)"| na038007afef41ac045b7
na038007afef41ac045b7 -->|"Entry enables help"| n3beaf780ba551f7d7580
n3beaf780ba551f7d7580 -->|"Help produces display"| n7b6d73c7c6f1cf24c02e
na038007afef41ac045b7 -->|"Entry enables interrupt"| nd2765044f37b6eec5367
nd2765044f37b6eec5367 -->|"Interrupt abandons entry"| n021a80db6e0008926b0a
Elements
Data-entry user
Kind: actor
Basis: reported
Description: An application user performing data entry can request contextual help or interrupt the current entry E0003.
Evidence: E0003
Goal: Complete data entry, obtain context-sensitive help, or abandon entry without persisting changes.
Begin data entry
Kind: action
Basis: reported
Description: The user enters a data-entry flow in which contextual help and interruption are documented as available E0003.
Evidence: E0003
Owner: Data-entry user
Request context help
Kind: action
Basis: reported
Description: The user invokes contextual help with the F1 function key during data entry E0003.
Evidence: E0003
Owner: Data-entry user
Contextual help displayed
Kind: outcome
Basis: reported
Description: Context-sensitive help is documented as being accessible during data entry E0003.
Evidence: E0003
Interrupt data entry
Kind: action
Basis: reported
Description: The user uses the INTERRUPT key, identified as DEL or CTRL-C, to abort the current data-entry operation E0003.
Evidence: E0003
Owner: Data-entry user
Entry abandoned without database write
Kind: outcome
Basis: reported
Description: The help documentation states that interrupting data entry abandons the operation without writing changes to the database E0003.
Evidence: E0003
Relationships
User begins entry
From: Data-entry user
To: Begin data entry
Relation: starts
Basis: inferred
Description: The actor is modeled as starting the documented data-entry flow in which help and interruption are available E0003.
Evidence: E0003
Trigger: The user enters a data-entry operation E0003.
Evidence type: Documented behavior.
Entry enables help
From: Begin data entry
To: Request context help
Relation: next
Basis: reported
Description: Context-sensitive help is documented as available during data entry E0003.
Evidence: E0003
Guard: The user is in a data-entry context E0003.
Mechanism: F1 function key E0003.
Evidence type: Help documentation.
Help produces display
From: Request context help
To: Contextual help displayed
Relation: achieves
Basis: reported
Description: The documented purpose of the F1 action is to provide context-sensitive help during data entry E0003.
Evidence: E0003
Information: Context-sensitive help content E0003.
Evidence type: Documented behavior.
Entry enables interrupt
From: Begin data entry
To: Interrupt data entry
Relation: next
Basis: reported
Description: The interruption behavior is documented for an active data-entry operation E0003.
Evidence: E0003
Guard: The user chooses to abort before completing the entry E0003.
Mechanism: DEL or CTRL-C INTERRUPT key E0003.
Evidence type: Help documentation.
Interrupt abandons entry
From: Interrupt data entry
To: Entry abandoned without database write
Relation: achieves
Basis: reported
Description: The help documentation states that the interrupt aborts data entry without writing changes to the database E0003.
Evidence: E0003
Control: No database changes are written for the interrupted entry, according to the documentation E0003.
Evidence type: Documented behavior.
Gaps
The supplied evidence does not establish that F1 or DEL/CTRL-C handlers are wired and operational in the Java forms; the second-opinion evidence explicitly treats these as documented or intended behaviors rather than runtime-confirmed behavior E0004. The actual help-file content and the framework event-handling implementation are incomplete or absent from the supplied material E0001 E0004.
The owner of the underlying persistence action is not modeled because the evidence supports only the documented result that interruption causes no database write, not a separate persistence component or actor journey step E0003. The evidence also does not identify the exact data-entry modules covered by the interruption and help rules, so this view should not be generalized to every form E0003 E0004.
Recovery limitations
- The view includes explicitly marked inference.
Sources
- E0001 — SHA256
26c6795c3bc4cc1018c05a3a14a9e8bfd1a7ac99525d062262c695930de1f2d0 - E0003 — SHA256
d6724e53cd2df11bbcdc4c2e6b8487fa7ffa2317a121b3ebae2594a6130343e0 - E0004 — SHA256
a7fa93a436c487d708267db6e5038c7415b98377a56232869519d6206a15e7e9
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.