Worksamples
2024
Q3 Release Notes
Module Configuration
Notification Designer
Logic & Triggers
Implications Overview

Implications Overview

The Notification Designer is integrated with the system’s core automation engines, allowing templates to be triggered automatically based on time, process, or data changes.

Global Integration

Templates created in the designer are stored in a centralized repository and can be referenced by:

  • Service Management Workflows
  • Scheduled Jobs
  • Data Change Rules (Business Rules)

Key Benefits

  • Consistency: Use the same template across different trigger types.
  • Centralized Management: Update a template once to see changes everywhere it is used.
  • Role-Based Security: Access to triggers is often restricted to Application Designers or Administrators.

Technical Execution Details

Explore the underlying integration architecture:

Trigger Integration Architecture

The Notification Designer interfaces with the system’s asynchronous event bus. When a trigger condition is met (e.g., a record is saved or a timer expires), the system:

  1. Evaluates intent: Matches the event against active notification rules.
  2. Fetches template: Retrieves the correct HTML/Text/JSON payload from the repository.
  3. Applies data mapping: Replaces placeholders with real-time record data.
  4. Dispatches: Sends the final message to the selected Communication Medium.
Next