BrainGrid Controller
Workflow Builder
Triggers
Database Trigger

Database Trigger Setup

Database Triggers allow the Workflow Management module to react to changes in database records. This feature helps automate workflows based on specific database actions like adding, modifying, deleting, or restoring records.

Overview

Database Triggers can be configured to monitor both static and dynamic tables for various record changes. By setting up triggers, users can automate responses based on database actions, ensuring that workflows react appropriately to data changes.

Configuring Database Triggers

Pre Transaction vs Post Transaction

AspectPre TransactionPost Transaction
TimingOccurs before data is saved to the database.Occurs after data is saved to the database.
Main PurposeUsed for validation of data, ensuring correctness.Used for post-processing tasks like sending notifications, updating logs, or triggering other workflows.
Common Use Cases- Data validation- Sending confirmation emails or notifications
- Ensuring data integrity before persistence- Logging actions or updates
- Preventing bad data from being persisted- Triggering follow-up workflows (e.g., sending welcome emails after user creation)
Impact on DatabaseDoes not affect the database until data is validated.Data is already saved in the database before the trigger is fired.
Failure HandlingIf the validation fails, the transaction is cancelled, and data is not persisted.If a post-transaction process fails, the data is still in the database, but corrective actions might be needed (e.g., rolling back a transaction).
Examples- Validating user input in a form- Sending email notifications after successful user registration
- Checking constraints before adding records- Logging data changes in an audit trail

Additional Consideration:

  • Pre Transaction triggers are typically used for data integrity and validation, while Post Transaction triggers help automate actions that depend on the data being successfully saved, such as notifying users or updating other systems.

Configure Database Trigger for Adding Records

To configure a Database Trigger for adding records in a table:

  1. Title: Provide a descriptive title for the trigger.
  2. Description: Explain the purpose of the trigger.
  3. Trigger Method: Select Add Record.
  4. Source Table: Choose the table to monitor.
  5. Trigger Signal: Choose whether it is Pre Transaction or Post Transaction.

Example:

  • Title: Add Record Trigger
  • Description: Trigger for adding records to the table
  • Trigger Method: Add Record
  • Source Table: User Roles
  • Trigger Signal: Post Transaction

Outcome: The Database Trigger will monitor the selected table (e.g., "User Roles") for added records, reacting accordingly when a record is added.

Configure Database Trigger for Modifying Records

To configure a Database Trigger for modifying records:

  1. Title: Provide a descriptive title for the trigger.
  2. Description: Explain the purpose of the trigger.
  3. Trigger Method: Select Modify Record.
  4. Source Table: Choose the table to monitor.
  5. Trigger Signal: Choose whether it is Pre Transaction or Post Transaction.

Example:

  • Title: Modify Record Trigger
  • Description: Trigger for modifying records in the table
  • Trigger Method: Modify Record
  • Source Table: Employee Records
  • Trigger Signal: Pre Transaction

Outcome: The Database Trigger will monitor the selected table (e.g., "Employee Records") for modified records, reacting accordingly when a record is modified.

Configure Database Trigger for Deleting Records

To configure a Database Trigger for deleting records:

  1. Title: Provide a descriptive title for the trigger.
  2. Description: Explain the purpose of the trigger.
  3. Trigger Method: Select Delete Record.
  4. Source Table: Choose the table to monitor.
  5. Trigger Signal: Choose whether it is Pre Transaction or Post Transaction.

Example:

  • Title: Delete Record Trigger
  • Description: Trigger for deleting records from the table
  • Trigger Method: Delete Record
  • Source Table: User Departments
  • Trigger Signal: Post Transaction

Outcome: The Database Trigger will monitor the selected table (e.g., "User Departments") for deleted records, reacting accordingly when a record is deleted.

Configure Database Trigger for Restoring Records

To configure a Database Trigger for restoring records:

  1. Title: Provide a descriptive title for the trigger.
  2. Description: Explain the purpose of the trigger.
  3. Trigger Method: Select Restore Record.
  4. Source Table: Choose the table to monitor.
  5. Trigger Signal: Choose whether it is Pre Transaction or Post Transaction.

Example:

  • Title: Restore Record Trigger
  • Description: Trigger for restoring records to the table
  • Trigger Method: Restore Record
  • Source Table: Invoice Records
  • Trigger Signal: Pre Transaction

Outcome: The Database Trigger will monitor the selected table (e.g., "Invoice Records") for restored records, reacting accordingly when a record is restored.

Validating Database Triggers

To validate the configuration of a Database Trigger:

  1. Review Configuration: Ensure all fields are correctly filled with appropriate values.
  2. Check Trigger Method: Confirm that the correct trigger method is selected.
  3. Verify Source Table: Ensure that the appropriate table is selected for monitoring.
  4. Check Trigger Signal: Ensure that the correct trigger signal (Pre Transaction or Post Transaction) is selected.

Validation Checklist:

  • Title
  • Description
  • Trigger Method
  • Source Table
  • Trigger Signal

Verifying Database Trigger Activation

Verify Record Add Trigger

To verify the activation of a record add trigger:

  1. Trigger: Add a record to the monitored table.
  2. Expected Outcome:
    • The Database Trigger should be activated.
    • The configured workflow should be executed.

Verify Record Modify Trigger

To verify the activation of a record modify trigger:

  1. Trigger: Modify a record in the monitored table.
  2. Expected Outcome:
    • The Database Trigger should be activated.
    • The configured workflow should be executed.

Verify Record Delete Trigger

To verify the activation of a record delete trigger:

  1. Trigger: Delete a record from the monitored table.
  2. Expected Outcome:
    • The Database Trigger should be activated.
    • The configured workflow should be executed.

Verify Record Restore Trigger

To verify the activation of a record restore trigger:

  1. Trigger: Restore a record in the monitored table.
  2. Expected Outcome:
    • The Database Trigger should be activated.
    • The configured workflow should be executed.

Summary

Database Triggers in the Workflow Management module provide a powerful way to automate responses to changes in database records. By configuring and validating these triggers, users can ensure that workflows react appropriately to data changes, whether they involve adding, modifying, deleting, or restoring records.

API Trigger UI Trigger