Oracle Form MigratorIllustrative view
Oracle Form Migrator · Understand the Form before migrating
Oracle Form Migrator · Understand the Form before migrating
Agro.xml · Fictitious agricultural case
“Agro.xml describes LOTES and APLICACIONES: 14 fields and one link through LOTE_ID. The screen shows fictitious data for a field plot and its applications.”
Simulated data · Presentation example
In this example, it organizes two blocks and their relationship based on Agro.xml.
Recognize the plot and application fields that must be preserved.
Scope of this view: Fictitious screen inspired by the Oracle Form Migrator workflow. Not the result of an executed migration.
Agro.xml · Fictitious agricultural case
“The example spreads 18 simulated findings: 8 confirmed, 5 probable, 4 for review and 1 to skip after validation.”
Simulated data · Presentation example
Separates structural coverage from the confidence level of each finding.
Prioritize the four findings that need review; the figures are simulated.
Scope of this view: Fictitious screen inspired by the Oracle Form Migrator workflow. Not the result of an executed migration.
Agro.xml · Fictitious agricultural case
“Select a node to see its role and links. You can drag it, move the background and zoom the map.”
Simulated data · Presentation example
Connects the blocks and triggers declared in Agro.xml with their source tables.
Walk through which data each operation uses and which rules must be preserved.
Scope of this view: Interactive map of the fictitious case. Relationships from Agro.xml and keys from the proposed Agro.sql model.
Agro.xml · Fictitious agricultural case
“AGRO.APLICACIONES.LOTE_ID references AGRO.LOTES.LOTE_ID. Each application is tied to one plot; a plot can have several applications.”
Master-detail relationship · Proposed model
Shows how the blocks are linked and the foreign key in the illustrative SQL model.
Review the cardinality and what should happen when the plot is queried, edited or deleted.
Scope of this view: Interactive map of the fictitious case. Relationships from Agro.xml and keys from the proposed Agro.sql model.
Agro.xml · Fictitious agricultural case
“The LOTES block trigger counts the linked applications. If it finds any, it shows a message and rejects the deletion.”
ON-CHECK-DELETE-MASTER · Agro.xml
Connects the event with AGRO.APLICACIONES, the table the rule queries.
Test one plot without applications and one with applications; verify data and messages in both cases.
Scope of this view: Interactive map of the fictitious case. Relationships from Agro.xml and keys from the proposed Agro.sql model.
Agro.xml · Fictitious agricultural case
“Before keeping the deletion rule, the team agrees on the message and confirms that a rejected operation does not modify the plot or its applications.”
Simulated data · Presentation example
Presents the source rule and the two criteria still pending agreement.
Define inputs, effects, errors and acceptance scenarios after reviewing the evidence.
Scope of this view: Fictitious screen inspired by the Oracle Form Migrator workflow. Not the result of an executed migration.
Agro.xml · Fictitious agricultural case
“The scenario proposes 4 candidates in LOTES and 2 in APLICACIONES. There are no closed contracts, implementation or equivalence tests yet.”
Simulated data · Presentation example
Brings together the status of the work and flags the first unit to review.
Close the pending contracts before moving on to implementation and equivalence testing.
Scope of this view: Fictitious screen inspired by the Oracle Form Migrator workflow. Not the result of an executed migration.