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

Return to: Integration data flow

Integration data flow

Who sends which information to whom, in which direction, and through what mechanism?

This view identifies the documented form, module, record-model, and persistence concepts relevant to integration data flow. The evidence supports Java/Swing-oriented forms, declared order and reporting interfaces, and schema-like order, item, stock, and invoice records, but it does not establish executable wiring between them E0004E0006.

The supplied Informix-4GL examples include SQL and transaction statements, but no connection layer, SQL execution path, or Java runtime integration is shown E0004E0006. Therefore, no sender-to-receiver flow is asserted below. A form field, interface declaration, or record model is not treated as proof that information is actually transmitted at runtime E0004E0006.

Elements

Customer and order forms

Kind: component
Basis: reported
Description: Generated Java/Swing form artifacts expose customer fields such as number, names, company, address, city, state, ZIP, and phone, and order fields such as order number, date, customer number, shipping instructions, backlog, PO number, ship date, weight, charge, and paid date E0004E0006.
Evidence: E0004E0006

Help and keyboard behavior

Kind: component
Basis: reported
Description: Help entries document customer, order, stock, report, and exit functions, data-entry abort keys, state selection behavior, order-entry limits, and an F1 or Control-F help handler; the supplied Java forms do not establish that these behaviors are wired into the runtime E0004E0006.
Evidence: E0004E0006

Order interface

Kind: component
Basis: reported
Description: The declared order interface includes order operations, item and order totals, stock lookup, invoice or report output, and declared update and delete operations; the help text states that order update and delete are currently not implemented E0004.
Evidence: E0004

Item record model

Kind: component
Basis: reported
Description: The generated item record model contains item number, stock number, manufacturer code, description, quantity, unit price, and total price fields E0006.
Evidence: E0006

Order record model

Kind: component
Basis: reported
Description: The generated order-related artifacts expose order identity, dates, customer reference, shipping information, backlog, purchase-order information, charges, and payment information E0004E0006.
Evidence: E0004E0006

Stock record model

Kind: component
Basis: reported
Description: The generated stock-related artifacts and stock interface expose stock add, query, update, and delete concepts, while help entries state that the stock-management options are currently not implemented E0004E0006.
Evidence: E0004E0006

Invoice record model

Kind: component
Basis: reported
Description: The generated invoice artifact combines order, item, stock, and manufacturer-related fields, supporting an invoice-oriented record model without proving invoice persistence or output execution E0006.
Evidence: E0006

Persistence and transaction boundary

Kind: component
Basis: inferred
Description: Informix-4GL examples document inserts, cursors, BEGIN WORK, ROLLBACK WORK, and COMMIT WORK around order and item operations, suggesting a persistence and transaction boundary; the supplied evidence does not establish a live database connection, SQL execution, or Java wiring E0004E0006.
Evidence: E0004E0006

Relationships

No sender-to-receiver relationship is recovered. The evidence lists UI structures, interfaces, record models, and documented SQL or transaction examples separately, but does not establish that any specific component sends information to another through an implemented mechanism E0004E0006.

Gaps

The sender and receiver for customer, order, item, stock, and invoice information are not established by the supplied evidence E0004E0006.

The mechanism for any form-to-module, module-to-record, or record-to-persistence transfer is unknown. No controller, JDBC layer, connection code, executable SQL path, or runtime integration is supplied E0004E0006.

The transaction boundary is documented in Informix-4GL example material, but its relationship to the Java forms and declared interfaces is unresolved E0004E0006.

The evidence does not establish whether the record artifacts represent live database stores, in-memory records, generated bindings, or migration-era models E0006.

The two order-form variants are not shown to be the same runtime component, and their relationship to order entry or persistence is unresolved E0006.

Follow-up requires the missing order, customer, stock, form, controller, framework, database-connection, and SQL-execution sources, including the retained artifacts identified as absent or incompletely covered E0004E0006.

Recovery limitations

• No supported flow reconstructed.
• Some identified concepts have no supported connection.
• The view includes explicitly marked inference.

Sources

• E0004 — SHA256 a7fa93a436c487d708267db6e5038c7415b98377a56232869519d6206a15e7e9
• E0006 — SHA256 caaf28b181903beefb938762690d58ef2027cc70e645ab30a05ee9158cf684c0