Skip to content
Forms Migration

Your rules (CRL)

Your rules, read and tested.

Your business rules come across as rules you can read, test and change.

Verified

A trigger becomes rules

What you have

WHEN-VALIDATE-ITEM
IF :Ord_Cust_Code IS NOT NULL THEN
  SELECT Cust_Name, Cust_Status, Credit_Limit
    INTO :Cust_Name, v_status, v_limit
    FROM Customers
   WHERE Cust_Code = :Ord_Cust_Code;
  IF v_status = 'B' THEN
    message('Customer is blocked');
    raise form_trigger_failure;
  END IF;
  IF :Ord_Total > v_limit THEN
    message('Credit limit exceeded');
    raise form_trigger_failure;
  END IF;
END IF;

What you get

3 rules
  • When Customer is entered

  • Fill in the customer's name

    verified
  • Stop if the customer is blocked

    verified

    "Customer is blocked"

  • Stop if the order is over the credit limit

    verified

    "Credit limit exceeded"

3 rules · all verified against the PL/SQL · 0 refused

Your business rules come across as rules you can read, test and change.

Show the engineering

Each trigger becomes a short list of rules in CRL, Forms Migration's own rule language, each tested against the PL/SQL it came from. The same rule runs on Oracle and PostgreSQL, and your team reads and changes it in the rule editor.

Refused

What it cannot read, it refuses

What you have

WHEN-VALIDATE-RECORD
IF :Line_Qty = 0 THEN
  message('Quantity must not be zero');
  raise form_trigger_failure;
END IF;
Check_Stock(:Line_Item, :Line_Qty);

What you get

2 rules
  • When an order line is saved

  • Quantity must not be zero

    verified

    "Quantity must not be zero"

  • CHECK_STOCK

    refused

    Reason listed for your team

2 rules · 1 verified · 1 refused

Three outcomes, never two: pass, fail, refused. Refusing is correct behaviour, not a failure. Every refused rule is listed with its reason, and your team finishes it in the rule editor.

Two things to know about the rules

No AI guessing

The same form always converts the same way. What it cannot read is refused, never guessed.

A language of our own

CRL, the Clause Rule Language: Forms Migration's own. The language itself is shown to customers during a pilot.

The rule editor

Your team reads and changes every rule in the rule editor. The same rule runs on Oracle and PostgreSQL.

Start with one form

Send us one form. We send back your own screen, running in a browser.

Talk to us