Table of Contents

Distribution Burst

A Distribution Burst uses a primary report — the driver — that, when run, distributes a sub-report to a target audience via email and/or an output directory. The sub-report is designed separately and attached to the driver as a Burst calculation.

The Core Pattern

The driver report supplies a list of targets, with one row per recipient or target — a Business Unit, employee, customer, vendor, and so on. When the driver runs, it generates its own copy of the sub-report for each of those rows and distributes it: emailed to the intended audience, written to an output directory, or both.

If a consolidation of multiple runs of the sub-report or a consolidation of multiple sub-reports into one output is required, review the Burst Consolidation documentation.

A Running Example

Throughout this section we follow a single example: an Accounts Payable (A/P) voucher report broken out by Vendor. The A/P sub-report shows the vouchers for a vendor, and vouchers differ from one vendor to the next. The goal is to generate that sub-report for each vendor and email it to the A/P analyst responsible for that vendor — so the driver report is a list of vendors, and each row produces one vendor-specific voucher report.

Other common distribution scenarios follow the same shape:

Driver report (the list) Sub-report (per row) Distribution
List of vendors A/P vouchers for the vendor Email to the responsible A/P analyst (running example)
List of customers Invoice for the customer Email the invoice to each respective customer
List of employees Benefits report for the employee Store in the company directory by employee

Before You Start

This page orients you to what a Distribution Burst does; the pages that follow walk through designing and configuring one. The setup concepts shared by every burst type — Report Selection, Burst on Run, Which Rows to Burst, Activation Condition, Lookup Values, and Output Types — are covered in Concepts Common to Every Burst.