Create a Trigger record

Applies to User Roles:

System Administrator

Triggers monitor files for certain activity types, such as Adds, Deletes, or Updates, and launches a specified RAD application when the appropriate conditions are met.

To create a trigger record:

  1. From the System Navigator, click System Definition > Tables > triggers.
  2. From the Keys sections, click New.
  3. From the General section, select the trigger type from the More Actions menu.
  4. Click Add.
  5. From the Fields section, modify the properties of the available fields to define the trigger. You can use the table below as a general guideline for the most commonly-used parameters.

    PropertyDescription
    trigger.nameAny unique, meaningful name.
    table.nameSelect the file to be monitored by this trigger.
    trigger.type

    Select the specific activity to react to:

    1 - Before Add - When adding a new record to this file, launch the application prior to committing the addition.

    2 - After Add - When adding a new record to this file, launch the application after committing the addition.

    3 - Before Update - When modifying a record in this file, launch the application prior to committing the change.

    4 - After Update - When modifying a record in this file, launch the application after committing the change.

    5 - Before Delete - When deleting a record in this file, launch the application prior to performing the deletion.

    6 - After Delete - When deleting a record in this file, launch the application after performing the deletion.

    Note: Only triggers of type 4 (After Update), and type 6 (After Delete) are supported by Cascade Updates.

    application.name

    The RAD application to launch.

    Note: The RAD application may not require parameters and will only have access to $L.old, the record prior to the change, and $L.new, the post-change record.

    Note: For most Cascade Updates, set to cascade.update.wrapper. The only exception is if the file you are monitoring is the device file or a related device attribute file, such as joincomputer. In those cases, set to am.cascade.update.wrapper.