Table of Contents

• Introduction
• Email Testing
• Logging & Tracing
• Error Handling
• Quarantine Management

Introduction

ReportBurster provides robust quality assurance features to minimize risks in automated report distribution. These tools help validate configurations and ensure accurate delivery before going live.

Email Testing

Test your data (and configurations) before actual distribution:

1. Test Email Server

Before distributing reports, use ReportBurster's built-in Test Email Server to verify all configurations. Test Email Server captures test emails without delivering them, allowing you to:

• Inspect email content and attachments
• Verify PDF report generation
• Test email templates and formatting

Once started, the Test Email Server is available at http://localhost:8025.

Example Scenario: When preparing to email 1,000 payslips, first send test emails to:

• Confirm correct recipient addressing
• Validate PDF attachments
• Review email body content

The Test Email Server replicates actual email delivery, including PDF attachments and message bodies. Once testing confirms everything works as expected, switch to live distribution.

2. Run Distribution Tests
   • Test all burst tokens in input report
   • Test specific burst tokens (comma-separated list)
   • Test random burst tokens (configurable quantity)

Test emails include PDF attachments and actual message content for thorough validation.

Logging & Tracing

ReportBurster maintains detailed logs for all distribution activities:

• View/Clear log files (INFO, ERROR, WARN)
• Monitor current running jobs
• Track progress via status indicators
  • Green: All reports distributed successfully
  • Red: Some reports failed (quarantined)

Error Handling

Configure how ReportBurster handles distribution errors:

1. If Any Recipient Delivery Fails

   • Stop all document delivery immediately
     • Default behavior that halts the entire distribution process on first error
   • Continue document delivery for the remaining recipients
     • Alternative option to skip failed recipients and continue with others

2. Enable Retry Policy (when a recipient delivery fails)

   • Configure retry behavior for failed deliveries:
     • Delay: Set initial delay between retries (default: 3 seconds)
     • Max Delay: Maximum delay between retries (default: 30 seconds)
     • Max Number of Retries: Total number of retry attempts (default: 3)
   • Retry policy uses exponential backoff, multiplying successive delays by a factor of 2
   • By default, report delivery jobs have one attempt and remain failed until manual intervention

Choose the appropriate strategy based on your error tolerance and business needs.

Quarantine Management

Failed reports are automatically quarantined for review:

• Configure quarantine folder location
• Enable/disable quarantine feature
• Review quarantined files for:
  • Manual redistribution
  • Error analysis
  • Data correction

Use quarantine management to maintain control over failed distributions and ensure complete delivery.