Some code cannot be read with certainty. What happens next decides whether you can trust the rest of the result.
Forms Migration does not guess. When it cannot read a rule, it says so, gives the reason and puts the rule on a list for your team. This article shows what that looks like and why we think it is the right way to work.
Three outcomes, never two
A trigger in your Oracle Forms holds business rules written in PL/SQL. Forms Migration turns each trigger into a short list of rules you can read. Each rule is then tested against the PL/SQL it came from.
Every one of those tests ends in one of three outcomes: pass, fail or refused.
- Pass. The rule matched the PL/SQL it came from, and it is marked verified.
- Fail. The rule did not match, and the test says so.
- Refused. Forms Migration did not convert the rule, and it tells you why.
Two outcomes, it worked or it did not, would be simpler. We keep a third, because “could not read it” is not the same as “read it and got it wrong”. Treating the two alike hides the one thing you most need to know.
Refusing is correct behaviour, not a failure. A refusal is the converter doing its job.
What a refusal looks like
Here is an invented example, an order line that is checked when it is saved. It has two parts. The card below shows what Forms Migration hands back.
When an order line is saved
- Quantity must not be zeroverified"Quantity must not be zero"
- CHECK_STOCKrefusedReason listed for your team
2 rules · 1 verified · 1 refused
The first rule is a plain one: quantity must not be zero. Forms Migration converts it and tests it against the PL/SQL it came from. It is marked verified.
The second part calls a stock check. Forms Migration does not convert it. The card is marked refused, and the reason is listed for your team.
Nothing is hidden. The refused rule sits on the same list as the verified one, with the words “refused” and “reason listed” on it, not a colour alone. Your team opens the rule editor and finishes the rule there. The editor is also where your team reads and changes every other rule.
Refusing instead of guessing
Some converters use AI for the hard cases; Forms Migration refuses instead, and lists the reason.
The same form always converts the same way. What cannot be read is refused, never guessed. That makes the result something you can check, and something you can repeat.
Why refusing protects you
You know what you have. You get the rules that were converted and tested, and a list of every rule that was refused.
Your gaps are named. Every verified rule has a test behind it. Every refused rule is listed with its reason.
Nothing runs blind. Your PL/SQL is never run blind as a rule. Rules are converted and tested, or refused and listed.
Your team knows where to look. Your team finishes the rules that were refused, in the rule editor, with the reason in front of them.
Forms Migration’s count of converted rules is the number of rules that were verified, nothing more. We show you that number, and the list of refused rules beside it.
Held to the same standard
We hold our own work to the same rule. Every check is broken on purpose to prove that it can fail, because a check that cannot fail proves nothing. And Oracle Forms is the authority on behaviour: when in doubt, we run the same steps in a real Oracle Forms system and match it.
If you want to see this on your own forms, send us one. We send back your own screen, running in a browser.