A Phantom field can be used to specify a formField that is listed in a screen-record, but does not have to be displayed in the form.


Phantom fields are never displayed to the user, although they can be used by dialog instructions of BDL programs. If you want to implement a screen-array with all the columns of a database table defined in the schema file, but you don't want to display all the columns in the Table, you must use Phantom fields. With the screen-array matching the database table, you can easily write program code to fetch all columns into an array defined with a LIKE clause.

Phantom fields can be based on database columns defined in a schema file or as NON_DATABASE field.

Phantom fields are used to store the id and parent id of the nodes in a Tree object.

To add a Phantom field to your form, right-click on the form object and select Add Phantom from the context menu.

Phantom field data is never send to the front-ends. Therefore, you can use a phantom field to store critical data that must not go out of the application server.