Understanding Event Notification

Introduction

Event Notification in Communication Cloud Service is used for monitoring and notifying events across various processes. This feature enables you to capture both error events (for example, system failures, data processing errors, or file transfer issues) and successful events (for example, successful batch completions, transaction validations). The system enables detection and alerting of critical events to improve operational visibility, facilitate remediation of issues, and assist with business standards and regulatory requirements.

You can configure Event Notification to handle various types of events, including errors, warnings, and successful processes, providing real-time notifications about critical activities. For example, you will receive notifications on events like transaction processing errors, file read errors, virus scan failures, or successful batch completions.

Following are some of the Common Event Scenarios:
  • Email Failures:
    • Email Creation Failure: Alerts when there is a failure to generate the content or structure of an email.
    • Email Delivery Failure: Triggered when an email cannot be delivered, often due to issues like invalid email addresses or problems with external email providers.
  • SMS Failures:
    • SMS Creation Failure: Occurs when there is an issue creating the body or content of an SMS message.
    • SMS Delivery Failure: Triggered when the SMS cannot be delivered, which could be due to invalid phone numbers or issues with external SMS providers.
  • Storage Failures:
    • Storage Asset Creation Failure: Captures failures in creating a document (for example, bill, statement). This could be due to missing data, configuration issues, or external errors.
    • Storage Delivery Failure: Indicates a failure to store a document in the designated repository, such as an SFTP server or a digital asset management system.
  • Batch Processing Events:
    • Batch File Transfer Success/Failure: Captures the outcome of transferring batch files, either successfully or with failure.
    • Batch File Conversion Success/Failure: Indicates whether a Batch File was successfully converted from XML to JSON, or if it failed.
    • Batch Processing Success/Failure: Captures whether the entire batch processing cycle was successful or failed.
    • Batch Progress Update: Reflects the progress and status of a batch at different stages of the processing workflow (for example, Completed, Error, FileUploadRequested).
  • Virus Scan Events:
    • File Virus Scan Success/Failure: Captures the results of virus scans performed on batch files and other uploaded documents, ensuring that malicious files are flagged, or that no viruses were detected.
  • Communication Processing Events:
    • Communication Failure: Captures a failure in processing a communication request, often due to invalid or incomplete data.
    • Manual Review Required: Triggered when a communication request needs manual intervention due to partial completion (for example, a document created but not emailed).
  • Collation Events:
    • Distribution Collation Success/Failure: Indicates whether source communications have been successfully collated or not, with detailed insights into any issues that may have occurred during the process.

Configuration Movement

The Event Notification configuration follows the configuration movement process; that is, if you configure any one of them in one tenancy (non-production), you can move the configuration to different tenancies (pre-production and production) sequentially.

For more information see, Understanding Configuration Movement topic.