Working with OpenEdge database triggers

Triggers are procedures that automatically execute when certain database events occur. For example, you might create a DELETE trigger that prompts the user for confirmation before a record is deleted. Triggers allow you to define custom default behaviors and business rules for your data, with the database as the central storage place for these rules.

In DB Navigator, the DB Structure view displays three types of triggers under the TRIGGERS node in the OpenEdge schema:

4GL TRIGGERS The 4GLTRIGGERS node lists all the tables that contain a CREATE (C), DELETE (D), WRITE (W), FIND (F), or ASSIGN (A) trigger. In addition, an ASSIGN TRIGGERS node is located under each table node that has one or more ASSIGN triggers associated with it.
REPLICATION TRIGGERS The Replication Triggers node lists all the tables that contain a REPLICATION-CREATE, REPLICATION-DELETE, or REPLICATION-WRITE trigger. Note that Replication triggers are written in ABL. Therefore, you can manage Replication Triggers in DB Navigator just like other ABL triggers.
Java triggers The JAVA TRIGGERS node lists all the tables that contain INSERT, DELETE, or UPDATE Java triggers.
Note: DB Navigator allows you to view all three types of triggers for OpenEdge databases. However, you cannot use the DB Navigator wizards to create, modify, or delete Java triggers. For more information about triggers, see the ABL manuals in the OpenEdge Product Documentation section of the Progress Communities Web site.