Nope, it's the ON_HOLD field (see the field list after INSERT INTO CUSTOMER)
And this Flamerobin statement works.
I don't specify the CUST_NO field, so that would implicitly be set to NULL.
If I do this in Flamerobin, it also works:
INSERT INTO CUSTOMER (CUST_NO, CUSTOMER) VALUES (NULL, 'Just a customer');
Why? Because the trigger checks for NULL CUST_NO values and then substitues a new generator value.
It's a really standard way of doing things in Firebird - it's a sample database, too